Rip 3930k?

[Arne_Saknussemm]

Weird day here.....my rig has been BSODing every 5 to 10 minutes all day......loads of codes a bit of everything from 09C to 101 the whole range...

My question is, to those of you who have had CPUs die...do they die slowly and like this?

I have replaced RAM replaced PSU fresh installed on two different SSDs swapped out GPUs disconnected everything but mouse and keyboard......flashed BIOS changed BIOS chip.

So I am left with RIVE or CPU. RIVE is a couple of months old.....

Any other posibilities?

[Arne_Saknussemm]

Thanks tracker64.....truth be told I have no idea what that means 😮

But this option has appeared in BIOS for the first time...never had this appear before...



I have also been testing and find the BSODs are pretty consistent in happening when the CPU transitions from load to idle or at idle....


Much like this post http://rog.asus.com/forum/showthread.php?33152-RIVE-BSOD-124-solution-BIOS-4004-bugs which was never really resolved in my opinion...

I notice my ME firmware is 8.1.40.1416 still despite flashing the BIOS.....is this area not flashed doing a BIOS flash when going backwards?

EDIT: flashed 1005 on BIOS 2 but win 8 UEFI boot wont work on that will try a fresh win 7 install on that bios tater.....also flashed BIOS 1 with 2003......ME now shows as N/A ! but the good news is my normal OC is stable so far......(maybe a bit early to say that yet but so far so good)

[Arne_Saknussemm]

Thanks tracker64.....truth be told I have no idea what that means 😮

But this option has appeared in BIOS for the first time...never had this appear before...



I have also been testing and find the BSODs are pretty consistent in happening when the CPU transitions from load to idle or at idle....


Much like this post http://rog.asus.com/forum/showthread.php?33152-RIVE-BSOD-124-solution-BIOS-4004-bugs which was never really resolved in my opinion...

I notice my ME firmware is 8.1.40.1416 still despite flashing the BIOS.....is this area not flashed doing a BIOS flash when going backwards?

EDIT: Going from bad to weird here. Used FTK toolkit to get ME firmware sorted.....but I am getting Google chrome crashes....and one BSOD (x101) that resulted in that message appearing again and the odd BIOS boot option appearing too.....is this corruption....LAN weirdness?

[doze]

Is your PCH fan spinning?

Arne Saknussemm wrote:
Thanks tracker64.....truth be told I have no idea what that means 😮

But this option has appeared in BIOS for the first time...never had this appear before...



I have also been testing and find the BSODs are pretty consistent in happening when the CPU transitions from load to idle or at idle....


Much like this post http://rog.asus.com/forum/showthread.php?33152-RIVE-BSOD-124-solution-BIOS-4004-bugs which was never really resolved in my opinion...

I notice my ME firmware is 8.1.40.1416 still despite flashing the BIOS.....is this area not flashed doing a BIOS flash when going backwards?

EDIT: Going from bad to weird here. Used FTK toolkit to get ME firmware sorted.....but I am getting Google chrome crashes....and one BSOD (x101) that resulted in that message appearing again and the odd BIOS boot option appearing too.....is this corruption....LAN weirdness?

[alyupb]

Arne Saknussemm wrote:
Thanks tracker64.....truth be told I have no idea what that means 😮

But this option has appeared in BIOS for the first time...never had this appear before...



I have also been testing and find the BSODs are pretty consistent in happening when the CPU transitions from load to idle or at idle....


Much like this post http://rog.asus.com/forum/showthread.php?33152-RIVE-BSOD-124-solution-BIOS-4004-bugs which was never really resolved in my opinion...

I notice my ME firmware is 8.1.40.1416 still despite flashing the BIOS.....is this area not flashed doing a BIOS flash when going backwards?

EDIT: Going from bad to weird here. Used FTK toolkit to get ME firmware sorted.....but I am getting Google chrome crashes....and one BSOD (x101) that resulted in that message appearing again and the odd BIOS boot option appearing too.....is this corruption....LAN weirdness?

Hey Arne,

I get the same BSODs (124) as the person in the link you posted. It happens with my system under the same circumstances (stressing the CPU and then turning off Prime to watch it BSOD as the voltage drops to idle). However, I'm talking about using a negative offset which is around -0.110 or so which gives me an idle voltage of around 0.7, it never happens to me with idle voltage above 0.8.

Another factor is the Turbo Ratio setting, which seems to cause the same BSOD on my system when it is set to Per Core instead of By All Cores. This sets the CPU to run at "stock" turbo conditions, and in this scenario the BSOD happens under the same circumstances as mentioned above.

It's interesting to note that I never had this BSOD happen when I'm overclocking, even though the multipliers are at 42-45 and negative offset is applied which brings idle voltage close to 0.8.

[Arne_Saknussemm]

Hey doze! Yes the PCH fan is spinning; even on 4102 you can set it to user mode to have it run....but it does not need to run until something daft like 80 degrees apparently so the auto setting leaves it off mostly....

I have no explanation for the sudden pop up of this BIOS option after crash on my first BIOS chip BIOS 3504.

My second BIOS 3301 is rock stable as long as I give the CPU more voltage...so I am still leaning to degraded CPU at this point unless anyone can help with the above....

[Arne_Saknussemm]

It is stable with more voltage....all the combinations of hardware/BIOS/software etc. that I have tried just result in needing more volts to run

I don't know if that means CPU or if that can be produced by a bad motherboard.....but the rig will not work at stock settings so I'm going to RMA the CPU....have contacted Intel...

alyupb....that does sound like the negative offset might be a bit too much for idle voltage sometimes...

[Masterbobo]

Arne Saknussemm wrote:
It is stable with more voltage....all the combinations of hardware/BIOS/software etc. that I have tried just result in needing more volts to run

I don't know if that means CPU or if that can be produced by a bad motherboard.....but the rig will not work at stock settings so I'm going to RMA the CPU....have contacted Intel...

alyupb....that does sound like the negative offset might be a bit too much for idle voltage sometimes...

Same thing just happened to my gigabyte board. RMA'd it again, its the board I wanna say for sure. Rare the chip be faulty, ussualy always the board. What about just running it on auto setting letting the board decide the voltages running it stock? does it still crash?

[Arne_Saknussemm]

Yes, stock crashes....defaults and optimised defaults and all the BSOD's are either x101 or RAM errors...which is making me think about the IMC going south on the CPU. Not sure what could go wrong with a new board to give the same symptoms.....but still testing stuff....have disabled all onboard devices except LAN....will disable that today....

LOL but I have to say everyone is suspecting the board more than the CPU.....

[Nodens]

Arne, the GBE stuff you are seeing is because the option for Network Stack is enabled on the UEFI. As it was said, it's for PXE boot..booting from a network. It's nothing bad, you just enabled the network stack by accident while trying stuff I guess.

Other than that, I'm rather sure your CPU has degraded:( Requiring more voltage than it did before is the very definition of CPU degradation 😞

ME Region is not flashed to backwards versions like that indeed. It will also not update to newer if it is corrupted. Coderush's FTK is your friend in any ME Region related endeavours;) Still I think you're beating a dead (or rather degraded) horse here 😕

[Arne_Saknussemm]

Well the funny thing is the GBE stuff enabled itself twice on 4102 after the crash.....it's not something I did or that has ever shown up before.....weird!!

But yeah The rest I sorted good and proper with Coderush's rather nifty tools...and yeah I hear you re the CPU seems like it's doing a James Dean....