A Blue Screen of Death (BSOD) on a desktop PC displays a specific stop code, like MEMORY_MANAGEMENT or DPC_WATCHDOG_VIOLATION, that identifies exactly which subsystem crashed, and reading that code is the fastest way to a fix rather than guessing. Faulty RAM, driver conflicts, and failing storage drives account for most desktop BSODs.
Read the Actual Stop Code First
Every BSOD displays a stop code, either as text like MEMORY_MANAGEMENT or a hex code like 0x0000001A, usually near the bottom of the blue screen or in a QR code that links to Microsoft's own explanation page. Writing this code down before the system restarts (it often happens too fast to read, so check Event Viewer's Windows Logs > System afterward) tells you which component or driver to investigate first.
Common Stop Codes and What They Usually Mean
- MEMORY_MANAGEMENT or IRQL_NOT_LESS_OR_EQUAL: usually points to faulty RAM or a RAM-driver conflict; run Windows Memory Diagnostic to confirm.
- DPC_WATCHDOG_VIOLATION: often a storage drive or driver issue, especially common after a Windows update changes a storage controller driver.
- CRITICAL_PROCESS_DIED: frequently tied to corrupted system files or a failing drive that can't read a needed file reliably.
- VIDEO_TDR_FAILURE: points to the graphics card driver or the card itself overheating or failing under load.
Run Built-In Diagnostics
- Search Windows Memory Diagnostic in the Start menu and run it, which reboots the PC and tests RAM before Windows fully loads.
- Open Command Prompt as Administrator and run sfc /scannow to check for corrupted Windows system files.
- Run chkdsk C: /f /r (requires a restart) to scan the main drive for bad sectors or file system errors.
- Check Device Manager for any driver showing a yellow warning triangle, and update or reinstall it directly from the manufacturer.
When a Failing Drive Is the Real Cause
BSODs that happen specifically during file-heavy operations, large file copies, software installs, or waking from sleep, point more toward a failing storage drive than RAM or drivers, even though the stop code sometimes looks memory-related. A drive that's beginning to fail can cause the same symptoms as bad RAM because Windows can't reliably read critical system files either way. Our guide on signs your hard drive is failing covers the overlapping symptoms in more detail.
Hardware Causes Software Can't Fix
If Memory Diagnostic, SFC, and CHKDSK all come back clean but BSODs continue, the underlying hardware itself needs physical inspection, whether that's a RAM stick with an intermittent fault that passes basic tests, a dying drive, or overheating components. An SSD upgrade resolves drive-related BSODs permanently while also improving overall speed, and a RAM diagnostic or upgrade handles the memory side.
When to Book a Full Diagnostic
Recurring BSODs with different stop codes each time, rather than the exact same one repeatedly, often indicate a deeper hardware instability issue, sometimes power-related, that's worth a full in-home diagnostic rather than continuing to chase individual error codes one at a time.
