The Blue Screen of Death (BSOD) is Windows telling you it encountered a problem so serious it had to stop everything to prevent damage. Modern BSODs almost always show a stop code — that code is your starting point.
Common BSOD Stop Codes
MEMORY_MANAGEMENT — Points to faulty RAM. Run Windows Memory Diagnostic: press Win+R, type mdsched.exe, restart and let it test overnight.
DRIVER_IRQL_NOT_LESS_OR_EQUAL — A driver is misbehaving. Often happens after a Windows Update or new hardware installation. Boot into Safe Mode and uninstall recent drivers.
CRITICAL_PROCESS_DIED — A core Windows process has crashed. Can be caused by corrupt system files. Run "sfc /scannow" in an elevated Command Prompt.
SYSTEM_SERVICE_EXCEPTION — Usually a driver conflict. Check Event Viewer (search it in the Start menu) under Windows Logs → System for errors matching the crash time.
PAGE_FAULT_IN_NONPAGED_AREA — Hardware problem, often RAM or a failing hard drive. Test both.
How to Read the Minidump File
Every BSOD creates a minidump file at C:\Windows\Minidump. Free tools like WinDbg or WhoCrashed can analyse these files and tell you exactly which driver or process caused the crash — far more useful than guessing.
First Steps to Try
- Update all drivers, especially graphics card drivers
- Run Windows Update fully
- Check for overheating (clean the fans)
- Run a disk check: open Command Prompt as admin, type "chkdsk /f /r C:"
- Test your RAM with Memtest86 (boot from USB)
When BSODs Keep Coming Back
Occasional BSODs after a driver update can resolve themselves. Frequent BSODs — multiple times a week — indicate a hardware problem that won't self-resolve. Continuing to use the computer risks data loss. Give us a call for same-day diagnosis across Melbourne.
Related Services
Local Service Guides