[SOLVED] System wont POST (completed checklist) MTB or CPU?

seapizzle

Reputable
Jul 27, 2015
21
0
4,510
Firstly I have been through the checklist here: http://www.tomshardware.co.uk/forum/261145-31-perform-steps-posting-post-boot-video-problems

I built this PC about 2 years ago and it has suddenly decided to no longer POST. It shut down one night absolutely fine and the next morning it began having issues. There is no beep, usually there is a 'pip' noise that indicates it has posted successfully. It started turning itself off and on every few seconds which was fixed with a new CMOS battery. I have attempted to reset the CMOS using the jumpers on the motherboard although it's hard to tell if this has done anything as there is still no video output and no beep. I have stripped the system down to to just the motherboard, cpu, psu and 1 stick of RAM. I have tried my corsair RM750 PSU and another 700w which has made no difference. I have tried 2 different types of ram, 2 different monitors and nothing seems to make a difference. Removing the RAM completely does produce the expected beeps from the onboard speaker so I'm not sure whether the problem lies with the motherboard or the CPU. I only have the one motherboard and cpu so cannot find a way to identify which is causing the issue.

Specs:
MTB: ASUS h81M-A
CPU: Intel i5 (unsure of exact model)
ram: tried both corsair and kingston

Sorry if I've missed anything out. Thanks in advance

EDIT:
Currently turning on by shorting the power pins, the fans and motherboard light power on but there is not POST success beep or signal to monitor.

EDIT: New motherboard has fixed the problem.
 

seapizzle

Reputable
Jul 27, 2015
21
0
4,510


Sorry I forgot to mention, the fans do power on as does the motherboard light. I am shorting to turn it on at the moment. There is no picture however and no POST success beep.
 

seapizzle

Reputable
Jul 27, 2015
21
0
4,510


It was a little confusing because in the manual it says to move from 1-2 to 2-3 then put back after 15 seconds. However theres 2 jumpers next to each other set as 1-2, 1-2. I tried putting both to 2-3 then back but nothing.
 

seapizzle

Reputable
Jul 27, 2015
21
0
4,510


Like so?
IMG_0385_zpskyx9dsyp.jpg


I moved the USB jumper and tried resetting CMOS for 15 sec again. No change.

IMG_0386_zpsjz00zntb.jpg
 

seapizzle

Reputable
Jul 27, 2015
21
0
4,510


It's in the left slot there. I have tried it in both. My other stick only fits in the right so I generally keep that one in the left.
 
Hmm and youre sure its not hitting it or knocking it out of the slot

One reason I dont install bigger cpu fans. It can cause probs if it hits something on the mobo

What video connections are you using?

How are you testing it to see if it turns on if its not in the case?? Shorting the pwr pins on the mobo?
 

seapizzle

Reputable
Jul 27, 2015
21
0
4,510


I've moved it to the right slot for the sake of testing. Doesn't appear to be touching anything else. I'm using the onboard at the moment with DVI. also tried VGA to an older monitor and nothing. No signal through my R9 290 when that's connected either.
 

seapizzle

Reputable
Jul 27, 2015
21
0
4,510


No adapters just cables. Ive been using this monitor & cable for about 6 months without any issues. The motherboard always makes a short 'pip' noise when it starts successfully though and it hasn't made that since the trouble started.
 

seapizzle

Reputable
Jul 27, 2015
21
0
4,510


Yeah CPU, fan and motherboard are hooked up.
IMG_0390_zpssugpxcgw.jpg
 

seapizzle

Reputable
Jul 27, 2015
21
0
4,510


It's definitely in there. I think it was just the angle of the photo.
IMG_0396_zpsm4iny7fs.jpg
 

seapizzle

Reputable
Jul 27, 2015
21
0
4,510


I kind of wish it didnt know it wasn't there so I knew it wasnt the CPU that's broke. Motherboard is a lot cheaper to replace! And yeah it's got a Kingston HyperX Blue 8gb in it at the moment and I've tried it with a Corsair VengeanceLP 8gb too.
 

seapizzle

Reputable
Jul 27, 2015
21
0
4,510


I can't find the stock fan. That fans been in there for 2 years though so I don't think it's the issue.