Oc'd processor giving up? bugcheck 0124

K

kandor

Gawd
Joined
Aug 24, 2005
Messages
632
Hi, the last few weeks, while under 100% load my main system has bsod'd with the following bugcheck, which appears to relate to hardware fault.

It's an i7 2600k, mobo p67 sabretooth which has been running at 4.7ghz (h70 cooler) since I built it in maybe 2011.

System is 24/7 and never bluescreened until about a month ago. I need to make it 100% reliable so I'm willing to buy a new mobo, cpu and memory. But I don't mind saving money too. So how can I isolate what part is failing?

Note, last night I ran prime95 for a few hours with no troube, core4 max'd to 75c. So it seems stable with prime. It's when I'm rendering in my 3d software that it blue screens.

Thanks for any advice!

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa800d77d028, 0x00000000be000000, 0x0000000000800400).
 
There's really no way to "know" without troubleshooting individual parts (typically by replacing them)

In my experience however, it's usually the motherboard's power delivery that starts to give up the ghost before the CPU
 
Sounds like a ram or HDD issue maybe? Test out the GPU too. I'm sure it isn't motherboard or CPU related, those two usually either work or it doesn't.

Run a HD tune if it's a HDD, followed up by a mem test. If those ends up clear then it's time to stress test the gpu at stock settings.
 
I'd also like to add, the cheapest way to gain stability would be to simply lower your OC by a couple hundred MHz. Won't cost you anything and you aren't likely to miss the performance.
 
Agenesis said:
Sounds like a ram or HDD issue maybe? Test out the GPU too. I'm sure it isn't motherboard or CPU related, those two usually either work or it doesn't.

Run a HD tune if it's a HDD, followed up by a mem test. If those ends up clear then it's time to stress test the gpu at stock settings.
Click to expand...

That's not at all accurate. In fact, the only time I've had motherboards either work or not work is if they were DOA. Every board I've ever had that wasn't DOA but developed issues later in life had varying degrees of failure, and none just quit outright.

As far as CPU's, I've destroyed a few Socked A Athlons back in the day, and one quit outright while others had varying degrees of failure.

ETA: I actually have had a board quit outright, but was a failed power supply that killed it.
 
Isn't 0x124 not enough vcore on SB? You probably need to up it a bit or reduce the OC.
 
Sounds like degradation to me. 124 BSOD is usually voltage related, so either increase voltage or lower the OC on the CPU and keep same voltage.

kandor said:
Hi, the last few weeks, while under 100% load my main system has bsod'd with the following bugcheck, which appears to relate to hardware fault.

It's an i7 2600k, mobo p67 sabretooth which has been running at 4.7ghz (h70 cooler) since I built it in maybe 2011.

System is 24/7 and never bluescreened until about a month ago. I need to make it 100% reliable so I'm willing to buy a new mobo, cpu and memory. But I don't mind saving money too. So how can I isolate what part is failing?

Note, last night I ran prime95 for a few hours with no troube, core4 max'd to 75c. So it seems stable with prime. It's when I'm rendering in my 3d software that it blue screens.

Thanks for any advice!

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa800d77d028, 0x00000000be000000, 0x0000000000800400).
Click to expand...
 
Thanks for the input everyone. I'm going to try a memtest now ( I remember I swapped out the original 8gb kit for a 16gb kit a year or so ago.) I will also try scaling back to a 45 multi and test again. I can pretty reliably make it blue screen doing a 2 hour render or so. Did it on 2 consecutive days thursday and friday.

Video card is 6 months old quadro K4000. Interesting maybe that I hooked up one of those cheap seiki 4k monitors beside my 30" dell about 2 months ago. I wonder if that being hooked up is stressing the vid card out when the whole system is loaded?

Barring that, I may run out and pick up a spare mobo / cpu and ram kit.

Thanks again!
 
If it is a core voltage issue, then you might just be burning out the chip. Voltage Migration could easily be getting the best of your CPU.
 
Just an FYI...

I've had Athlon X2's that were OC'd for years and started running into instability. I needed to regularly give them more voltage or lower the OC to maintain stability. I eventually took it back to stock speeds and it needed a slight over-voltage just to operate at stock speeds.

I had a Q6600 with the exact same problem... But in this case, when I moved it to a different board, it was like a brand new processor all over again and hit 3.4GHz with ease.

In one case it was the CPU degrading, it the other it was the motherboards power delivery degrading.
 
Hmm, Ok - so I've upped the sabretooth bios from 3302 to 3602. Which essentially put me back at default settings. So I'm running prime right now and turbo has it at 3.8. Temps are 60 and below. I ran memtest overnight, no errors after 3 passes. I'll try some rendering after this and if it checks out I'll try bumping the oc up a bit at a time.
 
I haven't seen you post your voltage, yet

what are (or were) you giving the chip?
 
I should have saved those settings before the bios update. I remeber I used something like a .025 + offset so I think it was auto volting, I know I had checked it in cpu-z and it was low for that chip. Problem is I overclocked almost 2.5 years ago and didn't touch it for a long time. Maybe it ran underload around 1.3 and change.
 
You must log in or register to reply here.
Back
Top