Win10 Stop Code: CLOCK_WATCHDOG_TIMEOUT

I just got a blue screen of death last night on Win10 while playing (Stop Code: CLOCK_WATCHDOG_TIMEOUT), this has never happened before (with anything), I recently downloaded the update and selected the DirectX Beta option, so perhaps it has something to do with that, but if anyone can offer any advice on something I should check out, I'd appreciate it.

Hey,

Have you had any progress with solving this? I'm experiencing the exact same issue.

So far, I've formatted my OS drive, emptied and cleaned my storage, reinstalled Win10, x64, all needed drivers and updates, POE + some software, issue persists.

Thanks!

"

galacticpresident wrote:

I just got a blue screen of death last night on Win10 while playing (Stop Code: CLOCK_WATCHDOG_TIMEOUT), this has never happened before (with anything), I recently downloaded the update and selected the DirectX Beta option, so perhaps it has something to do with that, but if anyone can offer any advice on something I should check out, I'd appreciate it.

change back to Vulcan or DX11 then.

"

HanSoloDK wrote:

"

galacticpresident wrote:

I just got a blue screen of death last night on Win10 while playing (Stop Code: CLOCK_WATCHDOG_TIMEOUT), this has never happened before (with anything), I recently downloaded the update and selected the DirectX Beta option, so perhaps it has something to do with that, but if anyone can offer any advice on something I should check out, I'd appreciate it.

change back to Vulcan or DX11 then.

Even though you quoted OP, I'm chiming in.

1. Boot drive format + fresh Win10 install w/ all updates and drivers, POE running DX11/DX12/Vulkan, only POE, minimal other software installed - same issue

2. Flashed BIOS, updated to the latest version - same issue

3. Ran memtest - no errors or issues w/ RAM

4. PC does not crash in any way, shape or form whilst doing anything other than POE.

5. Will run 3DMark and report.

I have a hard time believing this is anything but POE related, as my PC blue-screened 15minutes into a play session after having worked properly for several hours.

Furthermore, I never had this issue in the previous League and my PC generally never crashes, for any reason, let alone this error.

SMH... not sure if anyone at GGG will even look at this forum and provide assistance...

EDIT:

Ran 3DMark ever since my last post.

TimeSpy - 20 passes, no errors, passed.
Fire Strike - 20 passes, 97.3% - passed.
TimeSpy - 50 passes, 98.7% - passed.

All tests ran at GPU and CPU at 100% load, 0 errors or issues. CPU & GPU temps performing as expected, flat across the tests within normal operational temps.

PC did not crash, stutter or otherwise stall for any reason during the tests.

I'm very much stumped.

Hello, GGG?

Could you please answer more than one thread per week?

Seems like multi-threading is the root cause of this issue. I've checked my history with a friend where we both discussed crashes, and this coincides with the HH update patch.

Can we actually receive an acknowledgement that this information is forwarded somewhere?

Disabling multi-threaded rendering makes the game unplayable.

"

kri4o9 wrote:

Hello, GGG?

Could you please answer more than one thread per week?

Seems like multi-threading is the root cause of this issue. I've checked my history with a friend where we both discussed crashes, and this coincides with the HH update patch.

Can we actually receive an acknowledgement that this information is forwarded somewhere?

Disabling multi-threaded rendering makes the game unplayable.

GGG doesn't offer TECH support "for the moment" (been like this for several years now), so properly not.......

"

HanSoloDK wrote:

"

kri4o9 wrote:

Hello, GGG?

Could you please answer more than one thread per week?

Seems like multi-threading is the root cause of this issue. I've checked my history with a friend where we both discussed crashes, and this coincides with the HH update patch.

Can we actually receive an acknowledgement that this information is forwarded somewhere?

Disabling multi-threaded rendering makes the game unplayable.

GGG doesn't offer TECH support "for the moment" (been like this for several years now), so properly not.......

I've worked for a video gaming company as CS/Tech support and I know how that is.

At the very least, we answered emails and provided assistance.

The funny part is that really, disabling multi-threaded rendering resolves the issue, meaning it's a problem with the HH update.

All I want is acknowledgement that they're aware...

"

kri4o9 wrote:

I've worked for a video gaming company as CS/Tech support and I know how that is.

At the very least, we answered emails and provided assistance.

The funny part is that really, disabling multi-threaded rendering resolves the issue, meaning it's a problem with the HH update.

All I want is acknowledgement that they're aware...

Oh I understand completely, but look at the forum posts and you can see the answer....

PROBLEM SOLVED:
- it turns out the issue was being caused by a faulty mouse cable. The Razer Viper 8K mouse (according to a local techy guy) had the exact same problem as he had with another Razer mouse ... apparently they wrap the cables too tightly into the packaging at the factory, and this causes fraying of the cable, which over time gets worse, and they've done nothing to solve the problem at the factory.
- after getting the mouse replaced, the problem went away.

NOTE: no other application had an issue with this while that faulty mouse was plugged in, so there must be something about this game which cannot cope with that fault and thus triggers the blue screen of death.

"

galacticpresident wrote:

PROBLEM SOLVED:
- it turns out the issue was being caused by a faulty mouse cable. The Razer Viper 8K mouse (according to a local techy guy) had the exact same problem as he had with another Razer mouse ... apparently they wrap the cables too tightly into the packaging at the factory, and this causes fraying of the cable, which over time gets worse, and they've done nothing to solve the problem at the factory.
- after getting the mouse replaced, the problem went away.

NOTE: no other application had an issue with this while that faulty mouse was plugged in, so there must be something about this game which cannot cope with that fault and thus triggers the blue screen of death.

Plugged in a brand new Logitech mouse, cabled, your jack of all trades LGTech mouse, same thing.

This makes no sense to me, although, I didn't hold my breath that changing the mouse would work.

The interesting thing is that it always takes a different amount of time to end up at this BSOD. And it happens in any scenario, including afk.

I'm scared to boot the game now, I'm sure these force shutdowns aren't safe at all.