Question Bluescreen on my laptop with error CLOCK_WATCHDOG_TIMEOUT

[ElBryan554]

Hi everyone

Before I start, I speak Spanish so communication may fail me, I will tell you my problem, since yesterday my laptop has started to have constant blue screens with the error CLOCK_WATCHDOG_TIMEOUT. The most relevant thing I have done these days on the laptop is to multiboot between windows 11 home and linux mint (I regretted after a few minutes and removed the distribution). Crashing happens randomly, but it usually happens when I'm playing a video game(my laptop crashes even when I'm not playing).

I have already made a minidump with the verifier tool, but the blue screen did not tell me which driver failed, so I attach the minidump to see if you can support me xc

Specs:
HP VICTUS 15 Gaming Laptop

CPU: i5-13420H
Ram: KINGSTON FURY IMPACT 16 GB 3200 MT/s DDR4 (2 modules, 32 ram basically)
SSD/HDD: WD_BLACK SN850X 2000GB
GPU: Nvidia GeForce RTX 3050 6GB Laptop GPU
OS: Windows 11 Home

Minidump and bluescreen capture (blue screen after using verifier) link: https://ufile.io/f/voub2

 

[Lutfij]

Welcome to the forums, newcomer!

I used the URL that you've provided but apparently both files aren't possible to open. The .dmp file shows as invalid on WinBDG and the JPG file isn't opening in MS Paint(Windows 11). Could you reupload the files for us?

Are you on the latest BIOS version for your laptop?

Crashing happens randomly, but it usually happens when I'm playing a video game(my laptop crashes even when I'm not playing).
Using a browser or just any video on the laptop without the internet?

Moved thread from Systems section to Windows 11 section.

 

[ubuysa]

The 0x101 bugcheck happens because a processor failed to respond to a clock synchronisation interrupt. There are two reasons for this; it was prevented from responding (by some rogue code) or it didn't see the interrupt at all (which is a CPU hardware failure).

To debug this bugcheck we need the kernel dump, it's the file C:\Windows\Memory.dmp (unless you changed the location?). Please upload that kernel dump to a cloud service with a link to it here. It will be large.

 

[johnbl]

fyi: unable to read the dump file in debugger
(not a valid dump file, you might want to put it on a different vendors server)