F5F Stay Refreshed Software Operating Systems Issue a blue screen on my laptop due to error CLOCK_WATCHDOG_TIMEOUT

Issue a blue screen on my laptop due to error CLOCK_WATCHDOG_TIMEOUT

Issue a blue screen on my laptop due to error CLOCK_WATCHDOG_TIMEOUT

S
SnifePvP
Posting Freak
872
10-23-2022, 03:51 AM
#1
Hi everyone
Before I begin, I’m a bit concerned because I speak Spanish and communication might not come through clearly. My issue started yesterday when my laptop began showing persistent blue screens with the error code CLOCK_WATCHDOG_TIMEOUT. Recently, I’ve been using multiboot between Windows 11 Home and Linux Mint (though I later removed one of them). The crashes occur randomly, but they tend to happen while playing video games—even when I’m not in a game.

I’ve already created a minidump with the verifier tool, but it didn’t identify which driver was faulty. I’m sharing the minidump so you can help me troubleshoot.

Device details:
- HP VICTUS 15 Gaming Laptop
- CPU: i5-13420H
- RAM: KINGSTON FURY IMPACT 16 GB 3200 MT/s DDR4 (2 modules, ~32GB total)
- Storage: WD_BLACK SN850X 2000GB
- GPU: Nvidia GeForce RTX 3050 6GB Laptop GPU
- OS: Windows 11 Home

For reference, here’s the link to my minidump and bluescreen capture:
https://ufile.io/f/voub2
S
SnifePvP
10-23-2022, 03:51 AM #1

Hi everyone
Before I begin, I’m a bit concerned because I speak Spanish and communication might not come through clearly. My issue started yesterday when my laptop began showing persistent blue screens with the error code CLOCK_WATCHDOG_TIMEOUT. Recently, I’ve been using multiboot between Windows 11 Home and Linux Mint (though I later removed one of them). The crashes occur randomly, but they tend to happen while playing video games—even when I’m not in a game.

I’ve already created a minidump with the verifier tool, but it didn’t identify which driver was faulty. I’m sharing the minidump so you can help me troubleshoot.

Device details:
- HP VICTUS 15 Gaming Laptop
- CPU: i5-13420H
- RAM: KINGSTON FURY IMPACT 16 GB 3200 MT/s DDR4 (2 modules, ~32GB total)
- Storage: WD_BLACK SN850X 2000GB
- GPU: Nvidia GeForce RTX 3050 6GB Laptop GPU
- OS: Windows 11 Home

For reference, here’s the link to my minidump and bluescreen capture:
https://ufile.io/f/voub2

K
Kynedee
Posting Freak
784
10-24-2022, 11:45 PM
#2
Welcome to the forums, newcomer!
The URL you shared seems to be problematic—both files appear to be invalid in WinBDG and won’t open in MS Paint on Windows 11. Could you please reupload the documents?

Are you running the most recent BIOS for your laptop?
My laptop occasionally crashes unexpectedly, especially when playing video games, even when I’m not gaming.

Can you try using a browser or just watch videos without an internet connection?
The thread has been moved from the Systems section to the Windows 11 section.
K
Kynedee
10-24-2022, 11:45 PM #2

Welcome to the forums, newcomer!
The URL you shared seems to be problematic—both files appear to be invalid in WinBDG and won’t open in MS Paint on Windows 11. Could you please reupload the documents?

Are you running the most recent BIOS for your laptop?
My laptop occasionally crashes unexpectedly, especially when playing video games, even when I’m not gaming.

Can you try using a browser or just watch videos without an internet connection?
The thread has been moved from the Systems section to the Windows 11 section.

H
HotMilkTea
Member
204
10-30-2022, 01:56 PM
#3
The 0x101 bugcheck occurs due to a processor not reacting to a clock synchronisation interrupt. This can happen for two reasons; either some code blocked its response or the CPU simply missed the interrupt entirely (indicating a hardware issue). To investigate this bugcheck, we require the kernel dump, which is located at C:\Windows\Memory.dmp (unless you altered the path). Please upload this file to a cloud service and provide a link. It will be quite large.
H
HotMilkTea
10-30-2022, 01:56 PM #3

The 0x101 bugcheck occurs due to a processor not reacting to a clock synchronisation interrupt. This can happen for two reasons; either some code blocked its response or the CPU simply missed the interrupt entirely (indicating a hardware issue). To investigate this bugcheck, we require the kernel dump, which is located at C:\Windows\Memory.dmp (unless you altered the path). Please upload this file to a cloud service and provide a link. It will be quite large.

O
omrimic30
Member
92
11-04-2022, 07:23 PM
#4
fyi: can't read the dump file in the debugger
(it's not a valid dump file; you might need to upload it to a different vendor server)
O
omrimic30
11-04-2022, 07:23 PM #4

fyi: can't read the dump file in the debugger
(it's not a valid dump file; you might need to upload it to a different vendor server)