Full Diagnostic Tree & Step-by-Step Overview
What specific BSOD Stop Code or behavior are you experiencing when the computer crashes?
- MEMORY_MANAGEMENT or PAGE_FAULT_IN_NONPAGED_AREA
- IRQL_NOT_LESS_OR_EQUAL, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, or DRIVER_POWER_STATE_FAILURE
- INACCESSIBLE_BOOT_DEVICE or CRITICAL_PROCESS_DIED
- WHEA_UNCORRECTABLE_ERROR or MACHINE_CHECK_EXCEPTION
- I don't know / The PC restarts too fast for me to read the error screen
RAM / Memory Pool Corruption Detection
Solution:
Step-by-Step Memory Diagnostic:
These codes indicate that Windows encountered a critical error while reading or writing to your system RAM or the virtual memory pagefile.
1. Run Windows Memory Diagnostic: Press Win + R, type mdsched.exe, hit Enter, and select Restart now and check for problems.
2. Reseat Your RAM: Power down, unplug the PC, and physically remove your RAM sticks. Wipe the gold contacts gently with a clean eraser, blow out the motherboard slots with compressed air, and snap them firmly back in.
3. Disable XMP/DOCP: Enter your motherboard BIOS/UEFI on startup (usually Del or F2). Find the Memory Overclocking profile (XMP/DOCP) and set it to Disabled / Standard. Unstable overclocks are the #1 cause of this error.
4. Check the Pagefile: If RAM is fine, right-click Start > System > Advanced System Settings > Performance Settings > Advanced > Virtual Memory. Ensure it is set to 'Automatically manage paging file size for all drives'.
Does the BSOD screen mention a specific `.sys` or `.dll` driver file (e.g., nvlddmkm.sys, rtwlane.sys)?
- Yes, it specifically lists a driver file at the bottom of the text.
- No, it just gives the all-caps Stop Code with no specific file mentioned.
Storage Drive & OS Boot Sector Repair
Solution:
Critical Storage Diagnostics:
Windows has lost communication with the drive hosting the operating system, or vital system processes were killed.
1. Boot into WinRE (Recovery Environment): Interrupt the boot process 3 times in a row by holding the power button, or boot from a Windows USB installation media.
2. Run System File Checker (SFC) & DISM: In Advanced Options > Command Prompt, run: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows followed by dism /image:C:\ /cleanup-image /restorehealth.
3. Repair the Disk (CHKDSK): Still in Command Prompt, run chkdsk C: /f /r /x to locate and bypass dead storage blocks. This can take hours on larger drives.
4. Check SATA/NVMe Connections: If you are on a desktop, unplug and replug your storage drive cables. If using an M.2 NVMe SSD, unscrew it, clean the contacts, and firmly reseat it.
Have you recently overclocked your CPU/GPU, or is your PC experiencing high thermal temperatures (overheating)?
- Yes, I recently applied an overclock, undervolt, or turned on XMP/EXPO.
- No, everything is running at stock speeds, but it might be overheating.
Disable Auto-Restart & Read Minidumps
Solution:
How to Catch the Error:
By default, Windows automatically reboots upon hitting a BSOD. You need to disable this to read the code.
1. Disable Automatic Restart: Boot into Safe Mode (or normal Windows if stable enough). Press Win + R, type sysdm.cpl, hit Enter. Go to the Advanced tab, click Settings under *Startup and Recovery*, and Uncheck 'Automatically restart'. Click OK.
2. Analyze the Dump Files: Download a free tool called BlueScreenView by NirSoft or WinDbg from the Microsoft Store. Open the tool, and it will automatically read the files in C:\Windows\Minidump.
3. Identify the Culprit: The software will highlight the exact driver, application, or kernel module that caused the crash in red. Search that exact file online to find out if it belongs to your GPU, Audio interface, or Antivirus software.
Specific Driver Reinstallation
Solution:
Resolving Rogue Drivers:
A specific third-party driver is writing to restricted memory addresses or conflicting with the Windows Kernel.
1. Identify the File:
nvlddmkm.sys / atikmdag.sys = NVIDIA / AMD Graphics Card.rtwlane.sys / ndis.sys = Realtek / Network Wi-Fi Card.ks.sys / portcls.sys = Audio / Webcams.2. Boot into Safe Mode: This prevents the rogue driver from loading.
3. Perform a Clean Install (For GPUs): Download Display Driver Uninstaller (DDU). Run it in Safe Mode to obliterate all traces of the old driver, then reboot and install the newest version directly from NVIDIA/AMD.
4. Uninstall via Device Manager (For Others): Right-click Start > Device Manager. Find the offending device, right-click > Uninstall device (check the box to remove driver software). Reboot and let Windows Update reinstall a stable version.
General Driver Update & System Repair
Solution:
Deep Windows Health Check:
Without a specific file, the crash is generic. We need to repair the OS foundation.
1. Uninstall Third-Party Antivirus: Programs like Norton, McAfee, or Avast hook deep into the kernel and frequently cause IRQL BSODs after Windows Updates. Use their official removal tools to uninstall them temporarily.
2. Run System File Checker: Open Command Prompt as Administrator. Run sfc /scannow.
3. Update Chipset & BIOS: Go to your motherboard manufacturer's website. Download and install the latest Chipset Driver. If the system is somewhat stable, consider updating your BIOS to patch microcode hardware incompatibilities.
4. Use Driver Verifier (Advanced): Open Command Prompt as Admin, type verifier, and hit Enter. Select *Create standard settings* > *Automatically select unsigned drivers*. Reboot. If your PC crashes immediately, it will catch the bad driver in a new dump file. (Note: To turn this off later, boot to Safe Mode and run verifier /reset).
Revert Overclocks & Power States
Solution:
Restore Hardware to Factory Stability:
WHEA (Windows Hardware Error Architecture) indicates the CPU detected a physical hardware desynchronization or voltage drop.
1. Reset BIOS to Defaults: Reboot your PC and rapidly press Del or F2 to enter the BIOS. Press F5 (or locate the 'Optimized Defaults' button). Save and exit (F10).
2. Remove Undervolts: If you are using software like Ryzen Master, MSI Afterburner, or ThrottleStop inside Windows, uninstall them or reset all profiles to zero.
3. Test Stability: Download Prime95 or Cinebench and run a stress test to see if the WHEA error returns at stock settings. If it does, you may have a degraded CPU.
Hardware & Thermal Failure Diagnostics
Solution:
Identifying Failing Components:
WHEA or Machine Check Exceptions at stock settings are severe and point to failing silicon or power delivery.
1. Check Temperatures: Download HWiNFO64. Monitor CPU (Tdie) and GPU (Hotspot) temperatures under load. If they exceed 95°C-100°C, the system is crashing to prevent catching fire. Clean your fans, re-apply thermal paste, and verify your AIO pump hasn't died.
2. Power Supply (PSU) Degradation: Random WHEA reboots during gaming heavily point to a failing Power Supply Unit that can no longer handle transient power spikes. Try swapping the PSU with a known-good unit of equal or higher wattage.
3. Isolate Peripherals: Disconnect *all* non-essential hardware. Unplug extra monitors, USB hubs, webcams, internal PCIe capture cards, and extra SATA hard drives. See if the PC stabilizes to rule out a shorted peripheral.