Question BSOD "CLOCK_WATCHDOG_TIMEOUT" crashes ?

[hailew]

My HP Victus 16 gaming laptop has been getting frequent crashes ever since i bought it in specifically games (CPU heavy usually) but not benchmarks. Prime95 ran without issues, no corrupt system files or anything. I sometimes also get WHEA_UNCORRECTABLE_ERROR. No custom overclocking or anything. What could be the issue?
Turning off turbo boost rarely helps either. I sometimes even crash on the base frequency of 2.3 Ghz. Not a RAM issue,I even replaced the sticks.

i7-11800h,
RTX 3060

 

[Colif]

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
   
2. Navigate to C:\Windows\Minidump
   
3. Copy the mini-dump files out onto your Desktop
   
4. Do not use Winzip, use the built in facility in Windows
   
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
   
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
   
7. Then post a link here to the zip file, so we can take a look for you . . .
   

Have you run https://support.hp.com/au-en/help/hp-support-assistant - it can update drivers & possibly bios which can help with WHEA errors

 

[hailew]

HP support assistant alongisde the HP Website itself does pretty much nothing, I've tried both. The crashes themselves leave no minidump files, my folder is completely clean.
The BSOD itself doesn't go above 0% so I think that's why It can't create a memory dump

What are the usual causes for the CLOCK_WATCHDOG_TIMEOUT error on laptops? My GPU and CPU drivers are up to date. Could the BIOS be bad potentially? Ran prime95 again for a couple hours - no errors, memtest was passed

 

[Colif]

clock watchdog is a CPU error.

So no new software from HP means you have newest bios, no missing chipset drivers

lack of dumps - have you changed the page file size or location? that can cause that.
another reason is the drive that they are being created on is the cause of the errors. Hard to create a dump if drive gone away.
can you run speccy and look on drive tab and see if it shows who makes the drive - https://www.ccleaner.com/speccy/download

no dump means Windows error reporting won't have any records. Could look through events leading up to crash, might give a clue.

 

[hailew]

I thought that this was an overheating issue so I tried to undervolt my system, when i was adjusting it and getting BSODs I did get minidump files, so It works fine.

Speccy:

After I booted up in Apex Legends as a test, I idled in the menu for around 5 minutes and my screen froze - I couldn't do anything but I still could move my mouse for around 15 seconds after which I got the error screen or sometimes just a black screen with a reboot following.
Event viewer got 3 identical errors before a unexpected shutdown

Yellow Warning sign

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscDataProtection
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
(Couldn't post image because the website didn't allow it for some reason)

 

[Colif]

if you use imgur, it should accept images. There are some sites it doesn't like

Try running this on drive - https://europe.kioxia.com/en-europe/personal/software/ssd-utility.html

 

[hailew]

No luck with the Utility, SSD is unsupported

 

[Colif]

okay then, try running Crystaldiskinfo (blue icons), it will auto scan drive.

Crystal Dew World

show screenshot.

 

[hailew]

Here's the drive info:

Also, I updated my CPU and GPU drivers to the most recent versions, but my system kept re-installing drivers for my CPU that were old, I fixed it though. Could some other driver cause crashes because of that too?

In a good 80% of the time after i get the CLOCK_WATCHDOG_TIMEOUT or MACHINE_CHECK_EXCEPTION errors I turn off my laptop (it never goes above 0% on the report), i get a CMOS CHECKSUM INVALID 502 error and after that laptop boots up normally