Blue Screen? Don’t Panic — Let’s Fix It
8 Simple Steps to Troubleshoot a Windows BSOD
You are using your computer normally and suddenly...
BOOM. Blue screen.
Sad face. Weird code. Windows restarts.
The Blue Screen of Death, or BSOD, looks scary, but it is usually Windows stopping the system after a critical error.
The important thing is not to start changing random settings.
We need clues.
The process is simple:
Identify → Investigate → Test → Fix → Verify
Step 1 — Get the Stop Code
When the blue screen appears, look for the Stop Code.
Example:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Take a picture or write it down.
That code can point toward drivers, memory, storage, system files, or hardware.
Without it, troubleshooting becomes much closer to guessing.
Step 2 — What Changed?
Ask:
“When did this start?”
Then:
“What changed before it started?”
Maybe you installed:
- New software
- A Windows update
- A driver
- New RAM or hardware
If the crashes started immediately after one of those changes, that gives us a strong direction.
Troubleshooting is often just reducing the number of possible causes.
Step 3 — Boot Into Safe Mode
Safe Mode starts Windows using only essential drivers and services.
Go to:
Troubleshoot → Advanced Options → Startup Settings → Restart
Then select Safe Mode.
If the computer works in Safe Mode but crashes normally, the problem may involve a driver, startup program, service, or recently installed software.
We are not fixing the problem yet.
We are isolating it.
Step 4 — Check the Drivers
Drivers allow Windows to communicate with hardware, and a bad driver can cause system crashes.
Press:
Win + R
Type:
devmgmt.msc
Open Device Manager and look for yellow warning icons.
You may need to:
Update driver
or, if the crashes started after an update:
Roll Back Driver
Newer does not always mean better.
Step 5 — Check Windows Update
Go to:
Settings → Windows Update → Check for updates
Microsoft regularly releases fixes for stability, drivers, and compatibility problems.
Install important updates, restart, and then test the computer again.
The important part is:
Change → Test → Verify
Step 6 — Check Event Viewer
Windows records system events that can help us understand what happened before the crash.
Press:
Win + R
Type:
eventvwr.msc
Then go to:
Windows Logs → System
Look for Critical or Error events around the time of the BSOD.
The timestamp matters.
Your computer may have hundreds of warnings, but we want the ones that happened around the crash.
Step 7 — Test Hardware and System Files
If drivers and software do not reveal the problem, start checking hardware.
Memory
Run:
mdsched.exe
This opens Windows Memory Diagnostic.
Storage
Open Command Prompt as Administrator:
chkdsk C: /f /r
Windows files
Run:
SFC /scannow
If SFC cannot repair everything:
DISM /Online /Cleanup-Image /RestoreHealth
Then run SFC again.
At this point we are checking:
RAM → Storage → Windows files
Step 8 — Recovery Options
If the computer is still crashing, Windows Recovery gives us stronger options.
Go to:
Troubleshoot → Advanced Options
You may use:
Startup Repair System Restore Uninstall Updates
And, if necessary:
Reset This PC
But I would not start with Reset This PC.
Resetting Windows before troubleshooting is kind of like replacing the whole door because the key is not turning.
It might work...
But maybe we should figure out the actual problem first.
Side warning:
“RESET THIS PC = LAST RESORT, NOT STEP ONE.”
Final Thoughts
One thing I like about troubleshooting is that you do not always need to know the answer immediately.
You need a process.
Ask:
What happened? What changed? What evidence do I have? What can I test?
Then change one thing at a time.
Test it.
Document it.
Verify the result.
That is useful for Blue Screens, but it is also the same mindset used across IT Support.
Usually the computer gives you a clue.
You just have to know where to look.
> SYSTEM STABILITY. RESTORED.
Matrix OS // IT Solutions pauloramsdell.com