Help with a 2500 k OC problem that has recently started? Pics included

[Phoenix1]

Hi there,

So i've been running an OC of 4.5 Ghz on an old 2500k sandy for about 6 months. I followed a couple of youtube videos that were recommended on this site and all was well. I've been playing games such as the Witcher 3 etc and i'd only ever experienced 2-3 system crashes which I couldn't pin on the cpu.

I have now upgraded to Windows 10 (Not sure if this may cause problems) and have had 4-5 crashes in the last two weeks with the message clock watchdog timeout.

Now, the only game I have played in those two weeks is world of warcraft (don't judge me lol ) which I guess could be somewhat cpu intensive. I ran a quick intel burn test on high for 20 cycles this evening and received the same error after approximately 12 cycles.

It's a bit odd really as this has only just started cropping up. Does anyone have any theories or thoughts/solutions to this? I did bought the cpu off a friend about a year and a half ago and sadly I don't know if he thrashed the crap out of it when he had it, which could mean its just slowly dying?

I have attached pics of my bios for perusal. If anyone can spot any immediate concerns etc or tweaks then please let me know. I'm currently attempting an offset of 0.022v.

Standard temps run at around 30 degrees with load running at about 57.

 

[P4-630]

CPU's degrade over time when you run them overclocked all the time.

 

[Phoenix1]

Yeh agreed, that's horribly inevitable. However, a sandy of a k variety with adequate cooling shouldn't die that fast :/ The k chips were designed for oc'ing to an extent, couple that with a oc motherboard and cooling and you should be ok for a fair few years?

 

[brandonwh64]

same thing here! My 2600K was rock solid in the OC and now I can not even boot to windows 10 with it OCed..... I have posted this in several threads pertaining to OC and windows 10 and I still believe MS did something to the microcode of the OS to stop OCs

 

[TheMailMan78]

same thing here! My 2600K was rock solid in the OC and now I can not even boot to windows 10 with it OCed..... I have posted this in several threads pertaining to OC and windows 10 and I still believe MS did something to the microcode of the OS to stop OCs

I think it might have a virus.

 

[brandonwh64]

I think it might have a virus.

Is windows 10 a virus..... *Apply's tin foil hat*

 

[jboydgolfer]

Win 10 caused my 4.5 2500k to crash often, either try default , or back to win 7.

 

[HWTactics]

I wonder if Win 10 isn't doing something funky with the C states on the processor. Might try turning off any power saving features on the mobo.

If you lock it at your 45 multiplier with a set voltage it should smooth out the peaks and valleys in the power delivery too, though it probably wouldn't be very good for the CPU in the long run set that high. Dropping down to 42 or 43 is also an option and low enough to not sacrifice reliability much.

Maybe the motherboard is truly the component showing signs of wear. The ASRock board you're using looks plenty capable though and trying the CPU with a different mobo is a tall order anyway.

 

[kn00tcn]

so why arent you raising the voltage a tick or playing with the LLC setting (i personally am against LLC)

http://www.anandtech.com/show/2404/5
http://www.anandtech.com/show/2404/6

i know it's getting old now (but there might be a newer one from them or techreport that shows small amounts of LLC are usable, while large amounts are still a problem)

the other thing is there are multiple clocks in a system, different OSs use different clocks, & potentially drivers can act different when overclocked

i hardly would consider this a dying chip

 

[basco]

do what kn00tcn said.

or just for example: nearly all worldrecords are on win xp because of lower strain on the cpu
http://valid.x86.fr/b0sdl3

 

[OneMoar]

bump the voltage you are only at +0.020 now you have plenty of headroom
you likely didn't have enough voltage to begin with and its just starting to show ...
bump the core to +0.35 and that should fix her right as rain

and yes windows 10 as much much more aggressive with voltage and cstates
my chip idles all the way down to 0.368v in windows 10 in windows 8.1 it sits at 0.800v minimum
not only that but it used a adaptive voltage table for individual states
e.g 800mhz @ 10% load = 0.368v 800Mhz @ 25% load=0.423v 800Mhz @ 500% load 0.552v

 

[jaggerwild]

1.8 CPU PLL? You can lower that............ also you have the voltage on auto for the CPU IGPU(I assume your not using it) as you list a 970 in your spec's. Turn it off if your not.

 

[OneMoar]

1.8 CPU PLL? You can lower that............ also you have the voltage on auto for the CPU IGPU(I assume your not using it) as you list a 970 in your spec's. Turn it off if your not.

1.8v is fine
igpu can stay enabled if hes using it for quicksync
neither of which has anything todo with his stability issues so hush

 

[jaggerwild]

1.8v is fine
igpu can stay enabled if hes using it for quicksync
neither of which has anything todo with his stability issues so hush

http://hwbot.org/user/PhIlLy ChEeSe StEaK/

LOLZ^

1.8v is fine
igpu can stay enabled if hes using it for quicksync
neither of which has anything todo with his stability issues so hush

http://hwbot.org/submission/2234142_philly_cheese_steak_cpu_frequency_core_i5_2500k_5544_mhz

 

[brandonwh64]

@jaggerwild

Please use the edit button and do not double or triple post