Why does my [=[ PC BSOD **]\] when it's idle or in sleep mode?

Introduction to BSODs and Common Error Codes

The Blue Screen of Death (BSOD) is a critical error screen displayed on Windows operating systems when a system encounters a situation that it cannot recover from. This typically involves hardware failures, system file corruption, or conflicts that stop the OS from continuing normal operations. When your PC crashes with a BSOD, it often generates error codes that can help point you toward the root cause of the issue.

You’ve mentioned that your PC has been crashing with various BSOD error codes, and you’ve already attempted some standard fixes, such as scannow, chkdsk, updating drivers and BIOS, and checking hardware like RAM and SSD. Unfortunately, none of these solutions have worked, leaving you wondering what the next step should be.

Understanding the Error Codes:

From the five BSOD error codes you've listed:

CRITICAL_PROCESS_DIED (ef)

UNEXPECTED_STORE_EXCEPTION (154)

FAULTY_HARDWARE_CORRUPTED_PAGE (12b)

MEMORY_MANAGEMENT (1a)

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)

Let’s break down what these mean and how they relate to possible hardware or software issues.

1. CRITICAL_PROCESS_DIED (ef)

This error typically occurs when a crucial system process fails to start or crashes during operation. The cause could be corrupted system files, misconfigured startup processes, or issues with drivers that affect kernel processes. This can happen when system files required for Windows to boot properly are either missing or corrupted.

Potential Causes:

Corrupted system files

Incorrect or outdated drivers

Malware infection

Disk issues

Fixes:

System File Checker (sfc /scannow): You’ve already tried this, but it's good to rerun in Safe Mode, just in case it missed some files when run under normal conditions.

DISM tool (dism /online /cleanup-image /restorehealth): This can repair Windows images and fix system corruption.

2. UNEXPECTED_STORE_EXCEPTION (154)

This error usually occurs when Windows has difficulty reading from or writing to storage devices like HDDs or SSDs. The issue might stem from a corrupted storage device or improper configuration.

Potential Causes:

Corrupted storage drivers or disk issues

Faulty SSD or HDD

System issues related to the NTFS file system (ntfs.sys is mentioned in your crashes)

Fixes:

Ensure all drivers for your storage devices (especially SSD drivers) are up-to-date.

Run chkdsk on your drives and ensure there are no issues with file system integrity. Run chkdsk /f from Command Prompt and restart your system for it to check for disk errors.

Try running the manufacturer's diagnostic tools for the SSD again. Sometimes, these can provide further insights into issues like firmware problems.

Ensure the SSD is properly connected to the motherboard (re-seat the cables or try a different port).

3. FAULTY_HARDWARE_CORRUPTED_PAGE (12b)

This error indicates that the system has encountered a problem with accessing data in physical memory. It’s commonly linked to issues with RAM, although it can also relate to other hardware components like the motherboard or even the SSD.

Potential Causes:

Faulty or mismatched RAM

Failing storage devices

Hardware conflicts

Corrupted memory pages in virtual memory

Fixes:

You’ve already run the Windows Memory Diagnostics tool and swapped RAM sticks. Try running MemTest86 for more in-depth testing. It’s a comprehensive tool for identifying memory errors.

If you are using dual-channel memory, try using just one stick of RAM (you’ve already done this, but it’s worth emphasizing).

Try reseating the RAM or changing the slots, as sometimes slight contact issues can cause instability.

4. MEMORY_MANAGEMENT (1a)

This is one of the most common error codes related to memory issues, either with RAM or virtual memory management (page file). Although you’ve ruled out memory by running diagnostics, there could be subtle problems with either the RAM modules or how Windows is handling memory.

Potential Causes:

Faulty RAM (even if diagnostics report no errors, it can still be an issue under stress)

Corrupted or improperly configured virtual memory settings (paging file)

Incorrect BIOS settings related to memory or CPU (like memory timing)

Fixes:

Try adjusting your virtual memory settings: Go to System Properties > Advanced system settings > Performance > Settings > Advanced.

Under Virtual Memory, increase the paging file size, especially if your physical RAM is relatively low.

Recheck your BIOS settings. Ensure that memory settings are configured properly. For example, your RAM is running at 4800MHz instead of its rated 5600MHz speed. While this may not be a problem, it’s worth testing if running the memory at its rated speed may resolve issues.

Ensure XMP (Extreme Memory Profile) is either enabled or disabled, depending on your motherboard and RAM compatibility.

5. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)

This error suggests that there is a problem with a system thread (a basic unit of CPU processing). The error can occur if a driver is incompatible, or if the system is struggling to manage threads properly due to hardware issues.

Potential Causes:

Incompatible drivers (especially graphics drivers like for your ASUS ROG Strix Radeon RX 6650)

System thread conflicts due to hardware issues

Corrupted system files

Fixes:

Driver Updates: Since this error often relates to specific drivers, make sure all drivers, especially for the graphics card and chipset, are up-to-date.

Uninstall recent drivers if you’ve recently updated them and the crashes started occurring afterward. You can use Device Manager to roll back drivers or uninstall and reinstall them.

General Troubleshooting Steps

Here are some general troubleshooting steps you can take to pinpoint the issue and hopefully resolve the BSODs:

Update Windows and All Drivers:

Ensure that Windows 11 is fully up-to-date.

Double-check that you’ve installed all the latest drivers for your components, including the chipset, graphics card, and storage devices.

Hardware Diagnostics:

Run MemTest86 to check the RAM for issues.

Re-run chkdsk and DISM commands to rule out disk corruption.

Use CrystalDiskInfo to monitor the health of your SSD.

Check for hardware conflicts in the Device Manager.

Re-seat or Replace Hardware:

Double-check all connections, especially your RAM and SSD. Ensure everything is firmly seated.

If possible, test with known working hardware (e.g., swapping out the SSD, RAM, or GPU with a spare).

Check Power Supply:

Sometimes, BSODs can result from unstable power. Ensure your PSU is of sufficient wattage and not malfunctioning.

BIOS Settings:

Reset your BIOS to default settings, particularly if you’ve overclocked or changed memory settings.

Update your BIOS to the latest version to fix any known stability issues.

FAQ Section

Q1: What is a BSOD?

A BSOD (Blue Screen of Death) is a critical error screen that Windows displays when it encounters a problem it cannot recover from. It is usually related to hardware failures, driver issues, or system corruption.

Q2: What causes BSODs?

BSODs can be caused by a variety of issues, including faulty hardware (RAM, GPU, storage devices), corrupted system files, incompatible drivers, or even overheating.

Q3: How can I fix BSODs?

To fix BSODs, start by running system diagnostics like sfc /scannow, chkdsk, and MemTest86. Update your drivers, BIOS, and firmware, and check for hardware issues like failing RAM or storage devices.

Q4: Should I replace my hardware?

Before replacing hardware, try as many diagnostic steps as possible. You might need to replace faulty components if they repeatedly show up as problematic, but always confirm the root cause first.

Q5: Why does my PC BSOD when it's idle or in sleep mode?

BSODs occurring during idle or sleep mode could indicate issues with power settings, sleep-state drivers, or even hardware problems like failing RAM or SSDs. Ensure all drivers are up-to-date and check your BIOS settings for power management.

Q6: How do I read the error codes from BSODs?

Error codes can be found on the BSOD itself or in the Event Viewer logs. These codes can provide insight into the type of issue, whether it’s related to drivers, memory, storage, or other components.

Q7: Should I contact customer support?

If all troubleshooting steps fail, and you're unable to identify the cause, contacting the customer support team for your PC's manufacturer may be helpful, especially if the device is still under warranty.

Conclusion

In summary, regular BSODs are a sign that something is wrong, and it may take time to identify the root cause, especially when multiple error codes are involved. You’ve already ruled out many common issues, such as faulty RAM and SSDs, which leaves us to consider less obvious culprits like driver incompatibilities, BIOS misconfigurations, or even power supply problems. By continuing to methodically test each part of your system, you can narrow down the cause and fix the problem.