Clock Watchdog Timeout BSOD: i5 2500K Overclocked, GTX 960 - Possible Overclocking Issue?

13680 11

Treść została przetłumaczona

Zobacz oryginalną wersję tematu

Reply | New topic

#1 17893901 08 Apr 2019 18:21

Anonymous Anonymous

Level 1

» |

Post #1
17893901 08 Apr 2019 18:21

Hello, I've been having a problem with the CLOCK WATCHDOG TIMEOUT bluescreen pop-up for some time now.
I have an i5 2500K overclocked to 4.4GHz
8GB of ram
GTX 960

Perhaps it is caused by overclocking the processor, I would like to ask for help how to solve this problem and whether it can be due to overclocking ~~prock~~ CPU because I overclocked about 3 weeks ago, and the problem has only been present for a week. For the first two weeks, almost everything worked fine.
ADVERTISEMENT
Helpful post

#2 17893916 08 Apr 2019 18:29

Pedros050 Pedros050

Level 43

» | Helpful post? (+2)

Helpful post
Post #2
17893916 08 Apr 2019 18:29

Hello. The CLOCK_WATCHDOG_TIMEOUT error means that your CPU is having trouble cooperating with its cores and threads. Threads are tasks performed by cores, and some cores can download multiple threads at the same time. The problem is that a thread is waiting for a proper response from another thread - or a core is waiting for a response from another core - and those responses are not coming. That's why you get this BSoD error. Updating the BIOS should help.
ADVERTISEMENT
#3 17893918 08 Apr 2019 18:32

Anonymous Anonymous

Level 1
» |

Post #3
17893918 08 Apr 2019 18:32

And here I put my settings in the bios after overclocking if everything is good, I suggested the settings on the same ~~proc~~ processor somewhere on YouTube. I have an Asrock p67 pro board and I heard that updating the bios to 3.30 often ends badly.

EDIT
I tried to update the bios, unfortunately, when I enter instant flash, the message "no image file detected" pops up. How to upload bios?

Added after 29 [minutes]:

Ok, I managed to update the bios to version 3.30. Now the question is should I give the same OC settings or some other? I was up to 4.4 ~~GHZ~~ GHz and such settings as in the pictures.

merged. RADU23

Attachments:

IMG_20190408_182619.jpg Download (2.33 MB)

IMG_20190408_182633.jpg Download (2.21 MB)
#4 17894024 08 Apr 2019 19:17

Pedros050 Pedros050

Level 43

» | Helpful post? (0)

Post #4
17894024 08 Apr 2019 19:17

Set the CPU to AUTO in the BIOS. And check if the BSoD persists?
ADVERTISEMENT
#5 17894031 08 Apr 2019 19:21

Anonymous Anonymous

Level 1

» |

Post #5
17894031 08 Apr 2019 19:21

The BSOD occurred intermittently not every day so should I set it to auto and wait a few days? I can't give the first settings like what I had and see if it occurs or not?
#6 17894080 08 Apr 2019 19:44

Pedros050 Pedros050

Level 43

» | Helpful post? (0)

Post #6
17894080 08 Apr 2019 19:44

Some misconfigured drivers can cause slow performance, and bad drivers mostly cause BSoDs like CLOCK_WATCHDOG_TIMEOUT.
ADVERTISEMENT
#7 17894103 08 Apr 2019 20:32

Anonymous Anonymous

Level 1

» |

Post #7
17894103 08 Apr 2019 20:32

Ok, then I'll wait and let you know if any BSOD appears, and for now thank you very much for your help :)

Added after 37 [minutes]:

One more thing, when I set the oc of the processor, I had an offset mode of -0.005V because I read somewhere that it is good, but for example in this video there is an offset of +0.015V that I should apply to my processor and motherboard ??
#8 17894495 08 Apr 2019 21:49

aachi aachi

Level 24

» | Helpful post? (+1)

Post #8
17894495 08 Apr 2019 21:49

Often, in addition to errors in the drivers, also the OC can contribute to this error. A few weeks ago someone also had the error 0x101 and it turned out that the cause was the OC of the processor (by increasing the FSB frequency).
#9 17894919 09 Apr 2019 08:07

Anonymous Anonymous

Level 1

» |

Post #9
17894919 09 Apr 2019 08:07

And is it better to use offset mode or fixed mode? Because I had offset mode -0.005V all the time. Maybe if I switched to fixed mode it would be better?
#10 20457158 25 Feb 2023 06:44

qcoopoznan qcoopoznan

Level 2

» | Helpful post? (0)

Post #10
20457158 25 Feb 2023 06:44

Pedros050 wrote:
Updating the BIOS should help.

Between the version of the BIOS that I have and the current one, there are a few intermediate fixes. Is it better to install them sequentially or only the last one?
#11 20457224 25 Feb 2023 09:00

artaa artaa

Level 43

» | Helpful post? (0)

Post #11
20457224 25 Feb 2023 09:00

If the manufacturer does not prescribe any fancy order, the latest one is enough.
#12 20457226 25 Feb 2023 09:01

Kolobos Kolobos

IT specialist

» | Helpful post? (0)

Post #12
20457226 25 Feb 2023 09:01

@qcoopoznan it all depends on what the manufacturer has given on his website, sometimes you can get the latest one right away, sometimes some intermediate ones + other updates are required.
Create an account, log in and become active in a forum and ads will not appear. You will receive points by participating in discussions.
Join this discussion.

Install the application

Reply | New topic

Report a violation of the law

Topic summary

The discussion revolves around a CLOCK_WATCHDOG_TIMEOUT BSOD issue experienced by a user with an overclocked Intel i5 2500K CPU at 4.4GHz, 8GB RAM, and a GTX 960 GPU. The user suspects the overclocking may be the cause of the problem, which started a week after the overclocking was applied. Responses suggest that the error indicates a communication issue between CPU cores and threads, and recommend updating the BIOS as a potential solution. Users also discuss adjusting BIOS settings, including setting the CPU to AUTO and experimenting with voltage offsets. The importance of driver configuration is highlighted, as misconfigured drivers can also lead to BSOD errors. The conversation includes inquiries about the best practices for BIOS updates and voltage settings for overclocking.
Summary generated by the language model.