kernel power error on R4BE

[WDxpanzer3]

hi guys,

i am really about to have a mental breakdown here.

i am fighting this pc for a good month now to find the cause of my kernel power error (event 41 bull**** reboots)

this error seems like it was put in windows for the sole purpose of giving you a migraine.

specs:

Rampage 4 black edition ("end of life edition", not a single update to anything, thx)
i7- 4930k 6core (cuz why the hell not) "stock settings till error is fixed"
4x4gb of corsair vengeance "stock settings till error is fixed"
2x GTX 680 ti's (yeah these are gonna get upgraded, had to whait)
1000w supernova 2g EVGA (bought with a gfx upgrade in mind)

well guys, i have done every single test i know to try and pinpoint a problem, but i cant find anything...

Prime95 - temps dont go over 60 (h100i on cpu)
occt - power supply test (the voltages dont go lower van their standard values, no weird hiccups)
occt - gfx test (temperatures are not going over 70 degrees, no errors or artifacts)
furmark - gfx and cpu burn (same as occt and prime95's test results)
evga precision scanner - no artifacts or signs of dieing cards
memtest - no errors after 10 passes, tested every single stick, on both stock and xmp settings
Driver verifier - nvidia driver flagged as bugged (353.30 has TDR problems, installed hotfix 353.38, problem solved)
no further errors after that.
checkdisk in cmd - no errors or bad sectors in any drive i got

checked every connection inside the case, everything is how it should be.
did a s.m.a.r.t. check on every disk, everything is healthy, not a single dropped value

and still this pc reboots like hell, doesnt matter what i do on the pc when it crashes.
one day i can play armored warfare or witcher 3 for hours and it will reboot on a youtube video.
the other day i cant even write 3 sentences in this window and it reboots twice, damn im glad this page autosaves.

do you guys have any idea what i can do further to find the problem.
everything is working how it should, no performance issues whatsoever.

the last time i had this error was a few years back, notifying me of a dead msi big bang xpower mobo, yeah i could pick the pieces of the south bridge from its heatsink, it actually blew up.
please tell me this mobo is fine, i really dont want to spend another 450 euro's 😞

[Jollydet]

are you using the XMP profile ? also i would recommend switching to the second bios, and reflashing the first bios and see how you go,

[WDxpanzer3]

Jollydet wrote:
are you using the XMP profile ? also i would recommend switching to the second bios, and reflashing the first bios and see how you go,

Not running any overclock on anything.
Already reflashed the bios. No improvement

[WDxpanzer3]

After 90 kernel power crap outs since july after a complete format i am lost.
Please is there someone out there who has any idea.

I already replaced the psu with every cable imaginable, i kept testing everything.
I even downclocked the cpu at this point.

Please guys please i am out of any options.
Everything simply works..

I am willing to rma every single component although everything works how it should.

Anyone got any idea?

[Arne_Saknussemm]

Try raising CPU current capability to 170 or 180%...this is 100% safe...simply gives CPU leeway it needs with current changes...

In DIGI+ section of BIOS

OR (not and...or) set CPU Current Inrush to Enabled.

Try curent cap first and if that doesn't work try the inertia setting

Have you tried a different PSU?

Finally what RAM exactly...and is it a single quad channel kit? Have you tried tweaking VCCSA or VTT or setting Current capability for RAM to 120/130% in DIGI+ and setting phases to optimized or extreme...?

[WDxpanzer3]

I use a single quad kit of 4x4gb corsair vengeance ddr3 1600mhz.

Already tried those bios settings multiple times or combinations of it.
Now again trying to run this silicon crapsicle on default settings.

Already changed the psu, i even changed every cable that allowed changing in the case.
Even unplugged the case from the mobo to make sure the power button isnt screweing me over by itself

[Arne_Saknussemm]

Hmm...OK....so you've tried clean OS install?

Tried any other RAM?

[WDxpanzer3]

The entire pc was cleaned of every bit.

The pc was working fine for almost a year long.
Been testing the memory for months without errors.
I never had any issues with the memory.
Would be epic if the board just decided to not accept this memory anymore.
Never seen a blue screen with this board

[Arne_Saknussemm]

Well the thing is sometimes something does deteriorate and since the big three are CPU mother board and RAM (PSU too but if you've substituted) in the end it comes down to substituting them out to eliminate. Vengeance was so bad on that platform I am immediately suspicious of it and it was SBE and RVE oriented not so great on IBE and later BIOS on the RVE or on the RVBE (not to say that is the cause but a posibility)

You have tried a clean OS install? even on an old HDD?

Do you have a local PC store / friend that could lend you a different CPU

RMAing the board sounds like a good idea if you've done everything else

Finally..I have seen people RMA board CPU RAM and finally find their house power supply is not stable or a change of cables or power socket resolves issues...try everything

[WDxpanzer3]

Arne Saknussemm wrote:
Well the thing is sometimes something does deteriorate and since the big three are CPU mother board and RAM (PSU too but if you've substituted) in the end it comes down to substituting them out to eliminate. Vengeance was so bad on that platform I am immediately suspicious of it and it was SBE and RVE oriented not so great on IBE and later BIOS on the RVE or on the RVBE (not to say that is the cause but a posibility)

You have tried a clean OS install? even on an old HDD?

Do you have a local PC store / friend that could lend you a different CPU

RMAing the board sounds like a good idea if you've done everything else

Finally..I have seen people RMA board CPU RAM and finally find their house power supply is not stable or a change of cables or power socket resolves issues...try everything

In the 22 years that i have been building/troubleshooting pc's i have never encountered such an annoying error.
Usually the symptoms speak for itself..
Someone seriously need to develop something to do tests on a hardware level instead of software.