Clock Watchdog Timeout

[toby12f]

System:

- EVGA RTX 3080 TI FTW3 Ultra Gaming OC
- Asus Rog Strix Z690-F Gaming Wifi
- Corsair Dominator Platinum DDR5 5600 MHz CL36 2x16 GB
- Intel i9-12900K
- Corsair H170i AIO (420mm radiator)
- Western Digital SN850 2 TB NVMe SSD
- SeaSonic Focus 850W 80+ Platinum

Apologies in advance if this is not the right spot for this question, in which case I would appreciate if you could point me in the right direction.

I keep getting CLOCK_WATCHDOG_TIMEOUT BSODs. I have tried with and without XMP II, with and without Asus AI overclocking, and even 100% default settings. I also thought it might have been because the motherboard jumper for additional CPU voltage wasn't 'enabled', so I moved it, but I am still getting this BSOD in <10 minutes on Prime95. The thermals on the CPU are all under 100°C on each core. Even with stock settings, the cores reach 5.3 MHz. I have been told this is an issue with the voltage, and I should raise VCore slightly, however I don't know how to do this. It even BSODs occasionally on idle loads, with only 1% of CPU in use. All my drivers are up to date, as is the BIOS. If the problem is indeed the CPU voltage, how do I go about raising it safely? Thanks again, any help is appreciated.

[toby12f]

Silent Scone@ROG wrote:
There’s a problem with your memory OC, yes. One which is easier diagnosed with something other than Prime. At this point, all other clock domains should be stock. The post above outlines valid reasons to avoid using P95 at all, and doesn’t pertain to any one issue that can’t be resolved by other means (like a dedicated memory stress test ;))

* You need to be able to understand there’s a distinct difference there and are confusing the methodology with your own issue. Hence why I asked why you were even using P95 to diagnose a memory problem in the first instance.

HCI Memtest Pro

Karhu Ramtest

TM5

GSAT

To list but a few suites that will find memory instability better than Prime95.

Increase VDD and VDDQ to 1.4v and see if this helps further.

Set MCVDD to 1.25v (Extreme Tweaker>Advanced Memory Setting). You need to pick a suite from the above, I’d recommend Karhu Ramtest. Keep tuning until you’re able to pass for at least 1500-2000% coverage.

I left it with the people who sold me the motherboard to repair. It’s their problem now haha. The reason I am using Prime95 is because it is quick and easy to detect issues. Some people have said they left it running for over a day. Someone suggested I leave it over night. I wouldn’t dare to do anything like that, partly because it’s overkill and partly because I am worried what something might go wrong lol. Since the issue was at first the CPU and then the memory and now I have no idea, I used Prime95 since it covers both CPU and memory. As well, I would only use it for about thirty minutes maximum (if it ever makes it past ten). You must agree that any machine you designate as stable should be able to run Prime95 for at least 30 minutes if not more, correct? It is simply an easy way to tell if it is UNSTABLE. Maybe it will pass Prime95 one day and still be unstable, but for now it has only failed, indicating instability. And as for what you said about memory OC, it has issues without any XMP profiles enabled, so no, it’s not just that. The motherboard is probably defective.

[Silent_Scone]

toby12f wrote:
I left it with the people who sold me the motherboard to repair. It’s their problem now haha. The reason I am using Prime95 is because it is quick and easy to detect issues. Some people have said they left it running for over a day. Someone suggested I leave it over night. I wouldn’t dare to do anything like that, partly because it’s overkill and partly because I am worried what something might go wrong lol. Since the issue was at first the CPU and then the memory and now I have no idea, I used Prime95 since it covers both CPU and memory. As well, I would only use it for about thirty minutes maximum (if it ever makes it past ten). You must agree that any machine you designate as stable should be able to run Prime95 for at least 30 minutes if not more, correct? It is simply an easy way to tell if it is UNSTABLE. Maybe it will pass Prime95 one day and still be unstable, but for now it has only failed, indicating instability. And as for what you said about memory OC, it has issues without any XMP profiles enabled, so no, it’s not just that. The motherboard is probably defective.

Hello,

The direction of advice was based on your own feedback:

toby12f wrote:
So I got it stable by lowering the default memory clock from 5600 MHz to 4800 MHz and turning on adaptive VCore instead of auto in BIOS. How do I now go about allowing it to use 5600 MHz

If the system was stable at 4800 then nothing is defective. This is the default operating frequency for 1 DIMM per channel configuration and indicates the problem is when the memory is overclocked to its 5600MHz SPD profile.

Hence the settings advised above. However given all the confusion, handing to a system integrator is likely the best option.

[Chainbold]

Silent Scone@ROG wrote:

4. P95 with AVX routines can degrade a CPU depending on the applied overclock and impede overclocking range.

This would be a matter of concern. Is this an "assumption", or based on some research / evidence?

I guess though that any extended stress testing will eventually degrade the CPU or RAM.

[Squall_Leonhart]

Silent Scone@ROG wrote:
Hello,

This philosophy is so outdated now that it's borderline flat-out incorrect. So much so that by leading users up this path you're potentially impeding their overclocking potential for no good reason. Unless it was built to run Prime. By endorsing this method other people will always be able to clock higher than you and be as stable as they need to be.

Remember, no overclock is ever 100% stable - that's something some users fail to wrap their heads around. For some reason, there are still Pro-Prime camps of users who like to subject their CPUs to copious amounts current that otherwise, their normal workload won't ever see. Depending on the workload, all you are doing is impeding your own overclocking range in real-world tasks. The fact Intel quickly acknowledged this by implementing the AVX offset function speaks volumes.


Even with all that aside, as far as stress testing memory is concerned there are far better tests than running large FFT (or small) Prime that isolate the memory subsystem. I and others in-house haven't used Prime to test stability since Haswell-E and use our systems crash-free on a daily basis. Of course, what you choose to take away from that depends on your mindset.

Nonsense, an overclocked system should not suffer random bsod or crash events, period.
1 offs every few months mean the system is not stable, period.

Prime95 is a tool in achieving that.
Should it be relied on alone to achieve stability?, No.

once prime95 is stable, you follow up with AVX testing.

[Silent_Scone]

Squall Leonhart wrote:
Nonsense, an overclocked system should not suffer random bsod or crash events, period.
1 offs every few months mean the system is not stable, period.

Prime95 is a tool in achieving that.
Should it be relied on alone to achieve stability?, No.

once prime95 is stable, you follow up with AVX testing.

What exactly in the post is nonsense?

1. What tests unearth instability depends on the platform, CPU architecture, and which subsystem is unstable.

2. Claiming an overclocked system should not experience random BSOD is categorically an invalid statement and objectively incorrect. Perhaps you can elaborate on what you mean by this.

3. If a system is stable for your use case and data integrity is not critical, then the system is stable enough.

4. It's possible for a stock system to fall over given enough time. Thereby, the same premise applies when running a system outside of reference code or stock parameters. For example, if you ran a memory stress test for several days, overclocked or not, there is a chance that the system would eventually flip a bit.

5. P95 is not by any means the best way to stress test memory.

It's more accurate to say that some overclocks are less conditional than others. Should that mean that you should accept that stop codes are normal when using the machine? Absolutely not, but if the crashes only occur in certain synthetic loads where the system is drawing almost twice the amount of current and not when you're using the machine on a daily basis, then that comes down to one's own physcy / preference.

[Squall_Leonhart]

Silent Scone@ROG wrote:
What exactly in the post is nonsense?

1. What tests unearth instability depends on the platform, CPU architecture, and which subsystem is unstable.

2. Claiming an overclocked system should not experience random BSOD is categorically an invalid statement and objectively incorrect. Perhaps you can elaborate on what you mean by this.

3. If a system is stable for your use case and data integrity is not critical, then the system is stable enough.

4. It's possible for a stock system to fall over given enough time. Thereby, the same premise applies when running a system outside of reference code or stock parameters. For example, if you ran a memory stress test for several days, overclocked or not, there is a chance that the system would eventually flip a bit.

5. P95 is not by any means the best way to stress test memory.

It's more accurate to say that some overclocks are less conditional than others. Should that mean that you should accept that stop codes are normal when using the machine? Absolutely not, but if the crashes only occur in certain synthetic loads where the system is drawing almost twice the amount of current and not when you're using the machine on a daily basis, then that comes down to one's own physcy / preference.

There is no "Depends" math is math, if the cpu can't process some math at times its because its unstable.

[Silent_Scone]

Squall Leonhart wrote:
There is no "Depends" math is math, if the cpu can't process some math at times its because its unstable.

Different data patterns result in different swings in current, which is why one stability test might find instability whereas another one will not.

The result is the CPU may be more than stable enough for the desired workload, but perhaps not so much for another that the user has no intention on using.

Hope this helps.

[MKKROG]

Hi;

see this :: https://www.partitionwizard.com/partitionmagic/dpc-watchdog-violation.html

I want to ask you :: I want to upgrade my system to ROG Z690 -F WiFi , i7 12700K and RAM DDR5
I see on the Internet that there are many problems in the gen12 and M.B. Z690
do you recommend me ???

[ACraigL]

MKKROG wrote:
Hi;

see this :: https://www.partitionwizard.com/partitionmagic/dpc-watchdog-violation.html

I want to ask you :: I want to upgrade my system to ROG Z690 -F WiFi , i7 12700K and RAM DDR5
I see on the Internet that there are many problems in the gen12 and M.B. Z690
do you recommend me ???

That's exactly my config and it's running great. Stable at 5.1GHz and 32GB (2x16) G.SKILL DDR5 at 6000MHz (XMP 1 profile). Temps are good too, mid-20s at idle and under 70c running Cinebench.

[toby12f]

So I got it stable by lowering the default memory clock from 5600 MHz to 4800 MHz and turning on adaptive VCore instead of auto in BIOS. How do I now go about allowing it to use 5600 MHz