What's Actually Going On?

  • Symptom: Windows crashes to a blue screen with a stop code.
  • Cause: A critical system error Windows cannot safely recover from.
  • Risk level: Medium to High - depends on frequency.
A BSOD is Windows protecting itself. When something at kernel level fails - driver, hardware, memory corruption - Windows stops everything to prevent data damage.

Step 1 - Read the Stop Code

Common examples:
  • IRQL_NOT_LESS_OR_EQUAL - Usually driver or RAM issue.
  • CRITICAL_PROCESS_DIED - System file corruption.
  • MEMORY_MANAGEMENT - Often RAM related.

Step 2 - Check Event Viewer

Open Event Viewer and check System logs around the crash time. This can give clues - which driver or process caused the crash. Look for critical errors or warnings. Steps
  1. Press Win + X, select Event Viewer.
  2. Expand Windows Logs > System.
  3. Look for red error icons around the time of the BSOD (Usually Critical errors).

Step 3 - Run System Repairs


sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

What You Should Not Do

  • Ignore repeated BSODs - they rarely fix themselves
  • Update all drivers blindly - can make things worse
  • Assume it is always Windows - hardware is often the real cause
One crash is annoying. Repeated crashes mean investigation is required.

Step 4 - Troubleshooting

Common causes of sudden BSoDs include:
  • Recent hardware changes
  • Driver updates or issues
  • Software conflicts
  • Overheating
  • Corrupted system files
  • BIOS changes (Especially overclocking)

Log kernel dumps

If BSODs persist, configure Windows to create a memory dump for analysis, if it isn't already set up. This can help identify the exact cause of the crash.
  • Open System Properties (sysdm.cpl). Can be opened with Win + R, type sysdm.cpl, and press Enter.
  • Go to the Advanced tab.
  • Under Startup and Recovery, click Settings.
  • Under Write debugging information, select Small memory dump (256 KB) - Usually sufficient for most troubleshooting scenarios.
  • Ensure the dump file location is set to %SystemRoot%\Minidump.
When the next BSOD occurs, it will create a dump file in the specified location. You can analyze this dump file using tools like WinDbg or BlueScreenView to get more insights into the cause of the crash.
  • Win + R and type in %SystemRoot%\Minidump, then press Enter to open the folder containing the dump files.
  • Open the dump file with WinDbg or BlueScreenView to analyze the crash details.
Granted, a lot of this is technical and the information could be hard to read and figure out, but it can be very helpful in diagnosing persistent BSOD issues. But who loves text more than anybody? - AI - So try feeding the dump file text into an AI model for analysis. It can help identify patterns or specific issues that may not be immediately obvious to human analysts. Link for the WinDbg tool: WinDbg Download

Step 5 - Check for Hardware Issues

A BSOD can be caused by hardware failures. Common culprits include:
  • RAM: Use MemTest86+ to check for memory errors.
  • Storage: Check for bad sectors with CrystalDiskInfo or similar tools.
  • GPU: Monitor temperatures and test with stress tools like Furmark.

RAM Testing

Using MemTest86+

As for RAM testing, MemTest86+ is a widely used tool that can help identify memory-related issues. It runs a series of tests on your RAM to check for errors. If you find errors during the test, it may indicate that your RAM is faulty and needs to be replaced. Ensure using MemTest86+, a free open source tool, not the MemTest86 commercial version, which can be misleading and may not provide the same level of testing. Link to the MemTest86+ tool: MemTest86+

Using Windows Memory Diagnostic

Windows also has a built-in memory diagnostic tool that can be used to check for RAM issues. To use it:
  1. Press Win + R, type mdsched.exe, and press Enter.
  2. Choose whether to restart immediately and check for problems or to check for problems the next time you start your computer.
The tool will run a series of tests on your RAM and report any issues it finds. The full report can be found in the Event Viewer under Windows Logs > System, with the source "MemoryDiagnostics-Results".

Important Note

An important note on these Memory Tests: If you find errors, it is often recommended to test each RAM stick individually to identify which one is faulty. However, if you have multiple RAM sticks and they are running in dual-channel mode, testing them individually may not always reveal the issue, as some errors can be intermittent or only occur under certain conditions. In such cases, it may be necessary to test the RAM sticks in different combinations to identify the faulty one. Additionally, if you have multiple RAM sticks, try swapping their positions in the motherboard to rule out issues with the RAM slots. But do note in dual-channel, that the RAM sticks should be installed in the correct slots (usually A1 and B1) for optimal performance, so be sure to check your motherboard manual for the correct configuration. Most importantly: If the test claims faulty RAM, but only sometimes, it could very well be a motherboard issue, not the RAM itself. It could also be the CPU's memory controller, which is integrated into the CPU. In such cases, it may be necessary to test the RAM in another system to confirm whether the issue is with the RAM or the motherboard/CPU.

Step 6 - Update Drivers and BIOS

Outdated or incompatible drivers can cause BSODs. Update critical drivers:
  • Chipset - From your motherboard manufacturer.
  • Graphics - From NVIDIA, AMD, or Intel.
  • Network - From your network card manufacturer.
Also, check for BIOS updates from your motherboard manufacturer, especially if you have newer hardware or are experiencing compatibility issues.

Step 7 - Check for Software Conflicts

Some software can cause conflicts leading to BSODs. Common culprits include:
  • Antivirus software
  • System utilities
  • Recently installed applications
Try uninstalling or disabling these applications to see if the BSODs stop.

Step 8 - Monitor System Temperatures

Overheating can cause BSODs. Use tools like HWMonitor to check your CPU and GPU temperatures. If temperatures are consistently high, consider improving cooling solutions or cleaning dust from your system. Link to HWMonitor: HWMonitor

Final Thoughts

BSODs can be frustrating, but they are a sign that something is seriously wrong. By following these steps, you can diagnose and often fix the underlying issue. If you're not comfortable troubleshooting on your own, consider seeking help from a professional technician. But do know, that in some cases BSOD problems can be like going to the mechanic and saying your car is making a funny noise. Time and money can be spent trying to find the issue, and sometimes it can be a simple fix, while other times it can be a more complex problem that requires replacing parts.