A Blue Screen of Death (BSOD) is Windows’ way of stopping everything before a serious error causes further damage. It looks alarming, but a single BSOD is not usually a sign your PC is dying — it is diagnostic information, and the error code it shows is the key to fixing it. This guide explains what the common codes mean, the fixes you can safely try yourself, and when it is time to have the machine looked at.

Before you start: back up your files

Repeated blue screens can be an early warning of a failing drive. If the PC is still starting, copy your documents, photos and anything else you can’t replace to an external drive or cloud storage before trying any fixes. Our guide to backing up your laptop before a repair walks you through it.

Common causes

Outdated or corrupted drivers, especially graphics and network drivers
Faulty RAM or a loose memory stick
A failing hard drive or SSD
Overheating, which can trigger crashes under load
A recent Windows update or software install that conflicts with existing drivers
Corrupted Windows system files, often after a power cut or forced shutdown
Malware interfering with core Windows processes

Common stop codes and what they usually point to

Stop code	Usual suspect
`MEMORY_MANAGEMENT`	Faulty RAM, or occasionally a driver
`IRQL_NOT_LESS_OR_EQUAL`	A badly behaved driver
`PAGE_FAULT_IN_NONPAGED_AREA`	RAM, a driver or antivirus software
`SYSTEM_SERVICE_EXCEPTION`	Drivers, often graphics
`VIDEO_TDR_FAILURE`	Graphics driver or the graphics card itself
`DPC_WATCHDOG_VIOLATION`	Drivers or SSD firmware
`KERNEL_DATA_INPAGE_ERROR`	The hard drive or SSD, or its cable
`INACCESSIBLE_BOOT_DEVICE`	Drive failure or a storage driver/BIOS setting change
`CRITICAL_PROCESS_DIED`	Corrupted system files or a failing drive
`WHEA_UNCORRECTABLE_ERROR`	Hardware: processor, overheating, power supply or overclocking

For a real example of tracking one of these down, see our case study on Critical Process Died (0xEF).

What to do when you see a BSOD

Let the PC restart on its own — do not force a shutdown unless it is completely frozen.
Note the stop code shown on the blue screen, for example MEMORY_MANAGEMENT or IRQL_NOT_LESS_OR_EQUAL. Taking a photo on your phone is the easiest way.
Think about what changed recently: a new update, program, driver or piece of hardware is often the trigger.
Check Settings → Windows Update and install any pending updates. If updates themselves keep failing, see our guide to fixing failed Windows updates.
Update your graphics driver from the manufacturer’s website (NVIDIA, AMD or Intel) rather than relying on Windows Update alone.
Run Windows Memory Diagnostic (search for it in the Start menu) to rule out faulty RAM.

If Windows keeps crashing before you can do anything

After two or three failed starts, Windows should open its Automatic Repair screen. From there choose Advanced options, where you can:

Uninstall Updates — remove the latest quality or feature update if the crashes started straight after it.
System Restore — roll Windows back to a point before the problem began. Your personal files are not affected.
Startup Settings → Safe Mode — start Windows with only basic drivers, so you can remove a problem driver or program.

Repair damaged Windows files

Corrupted system files are a common cause, and Windows has two built-in tools to repair them. Search for Command Prompt, right-click it, choose Run as administrator, then run these one at a time:

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

Each can take 10–30 minutes. Restart when both have finished. If SFC reports files it could not repair, that is a sign Windows itself may need a repair or reinstall.

How to find the exact error code

If the screen clears before you can read it, open Event Viewer (search in the Start menu), then go to Windows Logs → System and look for a red error entry around the time of the crash. This will show the exact stop code, which you can search for to identify the specific cause.

Windows also saves a small crash report each time, in the C:\Windows\Minidump folder. Free tools such as WhoCrashed or BlueScreenView can read these and will often name the exact driver file responsible.

When a BSOD signals a hardware problem

Get it checked out if:

The same stop code keeps appearing after driver and software fixes
Crashes happen randomly with no clear pattern
The PC also runs unusually hot or loud — see our guide to fixing an overheating laptop
You hear clicking or grinding from the hard drive
Memory Diagnostic reports errors, or sfc keeps finding new damage

On older machines with a mechanical hard drive, blue screens are often the drive starting to fail. Replacing it with an SSD fixes the crashes and makes the computer far quicker — see upgrading to an SSD.

Getting repeated Blue Screens? Computer Repair Bolton can help

If BSODs keep coming back after trying the steps above, we can run proper diagnostics on your RAM, drive and drivers to find the actual cause. Most repairs are a flat £40 labour charge (£50 for Apple), with any parts at cost, and we take a full backup of your data before starting work. Book a repair or drop into the shop at 30 Church Road, Bolton.

Computer Repair Bolton
07538 513 916
support@computer-repair-bolton.co.uk

Blue Screen of Death (BSOD): What It Means and How to Fix It