BSOD Crashes on Initial Startup: Critical Process Died and Clock Watchdog Timeout

[chrismartin]

Hello,
Initially, I oftentimes encounter BSOD while running a game (specifically APEX) in my laptop. Afterwards, upon searching for solutions online, I encountered these commands, one of which is listed above.
I tried to run this command along with these commands after encountering BSOD:
sfc /scannow
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

The commands run without issues. On the other hand, after many hours or so after shutting down my device, I tried to run these commands again (without playing a game whatsoever), but DISM /Online /Cleanup-Image /ScanHealth, DISM /Online /Cleanup-Image /RestoreHealth, I got BSOD.
I tried doing this again, and it causes BSOD after initially opening my laptop. After the BSOD, the command and trying games run without issues.

The BSOD error codes that occurred for the past weeks are as follows:
- Kernel Security Check Failure
- Unexpected Store Exception (Frequent BSOD)
- Kernel Data Inpage Error
- IRQL_NOT_LESS_OR_EQUAL
- System Service Exception Error (Frequent BSOD)
(occurring more recently without running the commands above anymore):
- Critical Process Died (Frequent BSOD)
- Clock Watchdog Timeout

I did bring my laptop to the designated service center, but they told me that there are no issues upon stress testing my device (they checked each component and they told me there are no issues). I doubt that claim that's why I'm really asking for help. Thank you.

• System Manufacturer? Gigabyte
• Laptop or Desktop? Laptop
• Exact model number (if laptop, check label on bottom) G5 GE
• OS ? (Windows 11, 10, 8.1, 8, 7, Vista) Win11
• x86 (32bit) or x64 (64bit)? x64
• What was original installed OS on system? Windows
• Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Pre-installed on system (then reinstalled when brought back to service center)
• Age of system? (hardware) About 3 Months
• Age of OS installation? About 3 Months
• Have you re-installed the OS? Yes, but by the official service center of Gigabyte
• CPU 12th Gen Intel(R) Core (TM) i5-12500H
• RAM (brand, EXACT model, what slots are you using?) Kingston, I don't know the exact model, both slots (DDR4-3200)
• Video Card Intel(R) Iris(R) Xe Graphics and NVIDIA GeForce RTX 3050
• Is driver verifier enabled or disabled? Disabled
• What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth) Windows
• Are you using proxy, vpn, ipfilters or similar software? No
• Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software) No
• Are you currently under/overclocking? Are there overclocking software installed on your system? No

 

[ubuysa]

You're using mismatched RAM. There is one stick of 8GB Crucial RAM (CT8G4SFS832A.M8FR) and one stick of 8GB Kingston RAM (99U5795-003.A00G). Whilst the speeds may appear to be the same many of the other critical timings may not. I suspect you've added an 8GB RAM stick since you've had the laptop? When you add more RAM you really need to ensure that you buy exactly the same part number if you want reliability. Mismatched RAM causes untold problems.

I would suggest you remove the newest 8GB RAM stick (which I suspect is the Crucial?) and see whether the laptop is stable on just the original 8GB stick.

 

[chrismartin]

Thank you. If that's the case, would it be the probable cause for my BSOD? The original RAM stick was there when I bought it, then was upgraded to 16GB by the staff of the store where I bought it. The newer one is the Kingston

I also checked the full details of the memory using cmd, does the difference here can also cause BSOD?

 

[ubuysa]

No, the differences are related to timings. If the new one was the Kingston then remove it and see whether it's stable on just the Corsair.

I'm not claiming that this definitely is the problem, but mismstched RAM is a very common cause of BDODs such as the ones you're experiencing. The first troubleshooting step must be to confirm whether mismatched RAM is the cause by removing the new stick.