- Joined
- Nov 22, 2014
- Messages
- 13 (0.00/day)
System Name | PC |
---|---|
Processor | Intel Core i5 2500k 3.3ghz |
Motherboard | Asrock z77 Fatal1ty Professional-M |
Cooling | Cooler Master Hyper 212 EVO (120mm) |
Memory | Corsair CMZ8GX3M2A1600C9 Vengeance 8GB (2x4GB) DDR3 1600 Mhz CL9 |
Video Card(s) | MSI Nvidia 970 |
Storage | (OS) Intel 520 240 GB (SSD), 1 7200rpm 320 gb HHD, 1 500gb 7200rpm HDD, 1 200gb 7200pm HDD |
Display(s) | LG E2442 24 INCH 1920 x 1080 |
Audio Device(s) | - |
Power Supply | 650 WATT Corsair |
Mouse | MMO R.A.T 7 Gaming Mouse |
Keyboard | Mad Catz Cyborg V.5 Gaming Keyboard |
Software | Windows 7 64 bit Home Premium |
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.
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.