What a blue screen actually means
A blue screen of death, or BSOD, looks alarming, but it is really Windows protecting itself. When the system hits a problem it cannot safely recover from, usually a driver misbehaving or a hardware fault, it stops everything and crashes deliberately rather than risk corrupting your data. A one-off blue screen is rarely something to worry about. Repeated ones are Windows telling you there is an underlying problem that needs finding.
The key to fixing a BSOD is that the screen itself hands you a clue: the stop code. That code points to the category of problem, which turns a frightening crash into something you can actually investigate. This guide shows you how to read that clue and then work through the most common causes in order, from quick software repairs to the hardware tests that catch failing memory and drives.
The common causes behind blue screens
Almost every BSOD traces back to one of these:
- Driver conflicts. A faulty, outdated, or recently updated driver, especially graphics or network, is the single most common cause.
- Faulty RAM. Bad memory produces repeated blue screens that often seem random and unpredictable.
- Corrupt system files. Damaged Windows files can trigger crashes until they are repaired.
- A failing drive. A hard drive or SSD with errors can cause BSODs, particularly with storage-related stop codes.
- A recent change. New software, a Windows update, or new hardware installed just before the crashes began is a prime suspect.
- Overheating. A system running too hot can crash to a blue screen under load.
Work through the steps in order. The stop code from step one will often tell you which of these to focus on.
Troubleshooting Steps
Read the stop code
This is your most important clue, so start here. The stop code tells you roughly what Windows was doing when it crashed, which narrows the search dramatically before you change anything.
- Common codes include CRITICAL_PROCESS_DIED, MEMORY_MANAGEMENT, and IRQL_NOT_LESS_OR_EQUAL
- Take a photo of the screen or note the exact code before the PC restarts
- Search that code once you have it, as it points you to the likely cause
A code with MEMORY in it points toward RAM, while many others point toward drivers. If your PC restarts too fast to read the code, the Event Viewer method in the next step will recover it.
Recover the stop code with Event Viewer
If your PC restarts too quickly to read the blue screen, you can still find the stop code afterwards. Windows logs every crash, and Event Viewer is where you read that log back, so you are not left guessing about what happened.
- Press Start, type Event Viewer and open it
- Go to Windows Logs → System
- Look for red Error or Critical entries around the time the crash happened
- Note the source and the stop code shown, which give you something specific to search
For a friendlier read of the same crash data, the free tool WhoCrashed analyses the underlying dump files and tells you in plain language which driver or component was most likely responsible.
Think about what changed recently
BSODs very often begin right after something on the system changes. Identifying that change is frequently the fastest route to a fix, because reversing it solves the problem directly.
- Did the crashes start after a Windows update?
- Did you install new software recently?
- Did you add or change any hardware?
- If yes to any of these, that change is the prime suspect, so try reversing it first
Repair corrupt system files
Corrupted Windows files are a common trigger for blue screens, and Windows has a built-in tool that repairs them without touching your data. This is a safe, sensible early step.
- Right-click Start and select Terminal (Admin) or Command Prompt (Admin)
- Type the following and press Enter:
sfc /scannow- Let it finish, which can take several minutes
Run DISM to repair the Windows image
If the file check finds problems it cannot fix on its own, DISM repairs the deeper Windows image that those files are restored from. The two tools work as a pair.
- In the same admin Terminal, run:
DISM /Online /Cleanup-Image /RestoreHealth- Let it complete, then restart and run sfc /scannow once more
Update or roll back drivers
Drivers are the most common cause of blue screens, so this step resolves a large share of cases. If the crashes started after an update, rolling a driver back is as important as updating one.
- Right-click Start and open Device Manager
- Check Display adapters and Network adapters first, as these cause the most trouble
- Right-click each and choose Update driver
- If the crashes began after a recent update, open the device's Properties, go to the Driver tab, and use Roll Back Driver instead
Test your RAM
Faulty memory is one of the most common causes of repeated blue screens, particularly with a MEMORY_MANAGEMENT stop code. Windows has a built-in tester that checks it for you.
- Press Start and type Windows Memory Diagnostic
- Choose to restart now and check for problems
- Windows scans the RAM on boot and reports any errors
If it finds errors, the affected stick usually needs replacing, which is typically a quick and inexpensive fix.
Check the drive's health
A failing hard drive or SSD can cause blue screens, especially when the stop code relates to storage. Checking the drive for errors rules this in or out.
- Open Command Prompt (Admin)
- Run the following:
chkdsk /f /r- You will likely need to schedule it for the next restart, so accept and reboot
If it reports bad sectors, back up your important files straight away and treat the drive as needing replacement.
Remove recently installed programs
Some software installs its own drivers or background services that can clash with Windows and trigger crashes. If the blue screens line up with a recent install, this is worth a look.
- Press Windows + R and type appwiz.cpl
- Sort the list by installation date
- Uninstall anything added around the time the blue screens started
When blue screens mean a hardware problem
If the crashes continue after working through these steps, the cause is most often hardware, and the two usual culprits are failing RAM and a failing drive. Both are serious in the sense that they can lead to data loss if ignored, but both are also straightforward and usually affordable to replace once identified. The priority if you are getting frequent blue screens is to back up anything important now, before a failing component takes your data with it. Pinning down exactly which part is at fault often means swapping in known-good components to test, which is the kind of diagnosis that is much easier with spare parts on hand.
If blue screen errors keep happening after these steps, it usually points to a deeper issue such as faulty hardware, a stubborn driver conflict, or system instability. These rarely resolve on their own and can lead to data loss if left unchecked. If you are in Johannesburg or Gauteng and the problem keeps returning, you are welcome to get in touch and have it diagnosed properly.
Get It Diagnosed →