PC shuts off abruptly under CPU load with q-code 00 on mother board

ANNIHILATOR284

Commendable
Aug 19, 2016
3
0
1,510
a>
so I've had this problem since 3 days and it only got worse last night. every night i play rainbow six siege for 2-3hrs. and while in game 50-60mins down the pc would shut off as if someone has pulled the plug off the wall. it would then give 00 q-code on the motherboard. i then will have to cut the power for a good 5-10 minutes to get it to post again. since last night it has gotten worse. the second the cpu gets some load, the pc shuts off and then i'll have to go through the entire process to get it to start again. PC specs below

Here are the trouble shooting processes i've gone through so far:

1) run gpu stress tests (pass)
2) run prime 95 (fail)
3) monitor cpu tems ( max 75 dig C at full load) (i monitored this before the problem became worse)
4) monitor gpu temps ( max 65digs c)
5) monitor motherboard temps ( max 45digs c)
6) monitor power voltages using HWMonitor ( nothing un usual, everything where it needs to be)
7) made sure all cables were in properly
8) run memtest86 for 6hrs (pass)

PC Specs:
i7 4790k@ 4.8ghz, 1.39v
Asus Maximus vii hero motherboard
corsair H100i cpu cooler
12gb ddr3 memory
gigabyte HD7870 OC GPU
corsair gs700 psu
2x samsung 850evo 120gb SSD
seagate 1tb HDD
seagate 500gb HDD
WD green 2tb HDD
DVD read write drive (why not :p)

i've had the overclock since day one and had never faced an issue. it's been 100% stable so i don't think it's an oc issue.
my temps are way below the 'i should under clock to get them sub zero temps' feeling

when running prime95 it does not even last a second. while gaming it would run a good hour before shutting off but now as soon as the game is up, it's off.

i am running the intel burn test as of now and the temps are fluctuating between 75 and 100dig c. but the pc didnot crash yet.

aida64 is a whole another story. i don't know what it means by stability test failed. please let me know.
gDy2cl5.png

Maeq4wk.png

w4F7w0V.png

Yp7tlEf.png

rbvieWK.png
 
Solution


My Bad, alwasy annoys me when I stare at a list for a few minutes and can't see the information that's there and I think may be relevant.

There really are only two possible explanations for failures as you describe (maybe some more esoteric ones exists, but I've never encountered them).

1. Temperature.
2. Power.

Those are the two components that increase dramatically under load situations.

The one place these two things meet in the computer is where the VRMs are situated. If I had to debug this, I'd monitor voltages and the temperatures of the VRMs on the motherboard (or on the processor chip if this is the model where...


My Bad, alwasy annoys me when I stare at a list for a few minutes and can't see the information that's there and I think may be relevant.

There really are only two possible explanations for failures as you describe (maybe some more esoteric ones exists, but I've never encountered them).

1. Temperature.
2. Power.

Those are the two components that increase dramatically under load situations.

The one place these two things meet in the computer is where the VRMs are situated. If I had to debug this, I'd monitor voltages and the temperatures of the VRMs on the motherboard (or on the processor chip if this is the model where Intel placed VRM modules on the processor chip).



 
Solution