How to fix the Windows blue screen step by step

Informatec Digital » Resources » How to fix the Windows blue screen step by step

The dreaded Windows Blue Screen of Death (BSOD) is one of those things that always seems to appear at the worst possible moment: right when you're submitting an assignment, playing a game, or editing a video. Suddenly, the computer freezes, turns blue, displays an error message, and restarts without much explanation. It might seem like a disaster, but the truth is, it can almost always be fixed.

In this guide, you'll find all the practical ways to fix a blue screen in Windows 10 and Windows 11: from the basic steps recommended by Microsoft, Lenovo, Dell, ASUS, and other manufacturers, to advanced diagnostic, repair, and preventative measures. The idea is to have everything that's usually scattered across several official websites in one place.

What exactly is the Blue Screen of Death (BSOD) and what is it telling you?

When a BSOD appears, it means Windows has encountered a critical error from which it cannot recover without risking data corruption. At that point, the system abruptly stops and forces a restart. This is also called a stop error, STOP code, kernel error, or the "blue screen of death."

In modern versions of Windows 10 and Windows 11, you'll see a message like "Your PC ran into a problem and needs to restart ," accompanied by a STOP code such as CRITICAL_PROCESS_DIED, MEMORY_MANAGEMENT, INACCESSIBLE_BOOT_DEVICE, etc. This text and the hexadecimal value (for example, 0x0000007E) are the main clues to understanding the problem.

In addition to that text, Windows typically generates a memory dump file (minidump) with technical information about what was happening just before the crash. Technicians and advanced users can analyze these dumps with tools like Windows Debugger to find the root cause.

Windows 10 and Windows 11 often display a QR code that links to a Microsoft support page with specific information about that stop error. While it doesn't always provide a magic solution, it's a good starting point if the particular code is uncommon.

Most common causes of a blue screen in Windows

Behind a blue screen there's almost never "bad luck," but rather a specific hardware, driver, or software problem . Knowing what usually fails helps a lot in getting to the root cause.

Official sources and practical experience agree that the typical causes are physical failures in equipment components : defective RAM memory, damaged sectors in the hard drive or SSD , CPU or GPU overheating, unstable power supplies or poorly mounted modules.

Another common culprit is corrupted, outdated, or incompatible device drivers . A faulty graphics, network, storage, or audio driver can cause the system to attempt to access memory illegally and trigger a kernel error.

There are also BSODs caused by conflicting or poorly programmed software : third-party utilities, security programs, overclocking tools, applications that clash with the NTFS file system… Even a major Windows update can introduce a one-off bug that causes problems until Microsoft fixes it.

Malware should not be forgotten . A virus that modifies system files, the boot registry, or certain drivers can cause repeated blue screens or prevent Windows from starting normally.

Main STOP codes and what they mean

The error messages that accompany the blue screen are very helpful because they narrow down the type of problem . Some of the most common ones in Windows 10 and Windows 11 are:

• PAGE_FAULT_IN_NONPAGED_AREA (0x00000050)Windows is attempting to access a memory area that does not exist or should not be used. This usually points to... faulty RAM, a problematic driver, or a corrupted NTFS volume.
• IRQL_NOT_LESS_OR_EQUAL (0x0000000A)A kernel-mode controller is accessing memory at an incorrect priority level. This is usually related to... faulty drivers or malfunctioning hardware.
• SYSTEM_SERVICE_EXCEPTION (0x0000003B)A system service throws an exception. This is where the following typically come into play incompatible drivers, software conflicts, or internal Windows errors.
• DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1)A driver attempts to read from or write to an invalid memory address. The suspect is almost always... that specific controller.
• SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x0000007E)A system thread throws an unhandled exception. This is often caused by a obsolete or incompatible driver.
• CRITICAL_PROCESS_DIED (0x000000EF)A critical system process has stopped working. The cause is usually in corrupted system files or unstable hardware.
• MEMORY_MANAGEMENT (0x0000001A): serious errors in memory management, typically due to faulty RAM or memory corruption.
• INACCESSIBLE_BOOT_DEVICE (0x0000007B)Windows cannot access the boot drive during startup. This may be due to Incorrect storage controllers, changes in SATA/RAID mode, bad sectors, or MBR/partition problems.
• UNMOUNTABLE_BOOT_VOLUME (0x000000ED)The system cannot mount the boot volume correctly. This is often corrected by... file system repairs and disk checks.
• WHEA_UNCORRECTABLE_ERROR (0x00000124): Hardware error detected by the WHEA reporting subsystem. It is usually related to temperature, voltage, or damaged CPU/motherboard.
• DPC_WATCHDOG_VIOLATION (0x00000133)A Deferred Procedure Call (DPC) has taken too long. Most often, this is because... problematic storage drivers or third-party controllers.
• VIDEO_TDR_FAILURE (0x00000116 or similar)The GPU stops responding and the TDR mechanism fails to recover it. This indicates problems with graphics drivers or the graphics card itself.
• NTFS_FILE_SYSTEM: points to corruption in the NTFS file system or damaged sectors on the disk.
• BAD_POOL_HEADER (0x00000019)The header of a memory pool has become corrupted. This is often caused by... faulty drivers or low-level software.
• MACHINE_CHECK_EXCEPTION (0x0000009C): Severe hardware error reported directly by the CPU. There is usually physical or energy problems.

Although it may seem like gibberish, you don't need to memorize all these names . The important thing is that, when you see one on the screen, you write it down exactly as it appears so you can look it up in Microsoft documentation, your PC manufacturer's documentation, or diagnostic tools.

Basic steps to try to fix the blue screen

Before getting into anything too complicated, it's worth following a few simple steps recommended by both Microsoft and manufacturers . Surprisingly, many recurring BSODs are resolved with these steps.

1. Remove new hardware and external peripherals

If the blue screen started right after connecting something new, disconnect everything that is not essential : external drives, printers, webcams, USB hubs, etc., and leave only the keyboard, mouse, and monitor.

On desktops and laptops, it's also a good idea to check if you've added new RAM, an additional SSD, or a PCIe card . If so, shut down the computer, remove those components, and try turning it on again to see if the system stabilizes.

2. Force shutdown and discharge of residual energy

When your computer gets stuck on the blue screen or freezes, a simple restart might not be enough. A classic trick, recommended by several manufacturers, is to perform a full power-off with residual power discharge.

To do this, press and hold the power button until the computer shuts down, unplug the power cord or remove the battery if it's a laptop, wait a few seconds, and then press and hold the power button again for 15-20 seconds. Afterward, plug the power back in and start the PC normally.

3. Check the Device Manager

Once you manage to get to the desktop, open Device Manager (right-click on Start > Device Manager) and check if there are any devices with a yellow warning icon.

In those cases, first try updating the driver . If Windows doesn't find anything suitable or the error persists, temporarily disable or uninstall the device to see if the blue screen stops.

4. Make sure there is enough free disk space

Windows and many applications need some free space for temporary files, virtual memory, and maintenance operations. If the disk is almost full, crashes and strange errors are more likely to occur.

The general recommendation is to try to keep at least 10% to 15% of your disk free . If you're significantly below that, it's time to clean things up: uninstall programs you don't use, delete large files, or move them to an external drive or the cloud.

5. Keep Windows fully updated

Just because a specific update introduces a bug doesn't mean you should always ignore it. In most cases, the latest versions of Windows include fixes for stability issues and improvements to hardware handling.

Go to Start > Settings > Windows Update and click Check for updates. Install everything important, and if there are driver updates offered by Windows Update itself, it's usually a good idea to install them as well (especially if they are for the chipset, storage, or graphics).

6. Reset or restore Windows to a previous state

If the problem started after a major update or the installation of a program and it doesn't go away with any of the above, you can resort to Windows restoration and recovery tools.

On one hand, there's System Restore , which lets you revert to a previous restore point (without affecting your documents, but it can affect drivers and system changes). On the other hand, there are the Reset this PC options , which allow you to reinstall Windows while keeping your files or perform a clean installation.

How to boot into safe mode and work from there

When the blue screen appears repeatedly after starting Windows, you need to use Safe Mode to investigate further. This special boot mode loads only the minimum system components.

On most modern computers, you can force entry into the Windows Recovery Environment (WinRE) by interrupting the boot process three times in a row: turn on the computer, wait until you see the Windows logo, and then hold down the power button until it shuts down. The Automatic Repair screen should appear on the third attempt.

From there, go to Advanced options > Troubleshoot > Advanced options > Startup Settings and click Restart. In the list of options that appears when you boot up, choose the option for Safe Mode with Networking (usually F5).

Once in safe mode, the system is usually much more stable because it doesn't load third-party drivers or programs . It's the ideal environment for uninstalling problematic applications, rolling back drivers, scanning for malware, or running file and disk checks.

Recommended diagnostic and repair tools

Windows and major manufacturers (Dell, Lenovo, ASUS, etc.) provide several very useful utilities to help you locate the cause of the BSOD.

RAM memory check

To rule out RAM problems, you can use the built-in Windows Memory Diagnostic tool . Type it into the search bar, open it, and select the option to Restart now and check for problems.

The computer will restart and perform a series of memory tests. If errors appear, it is very likely that one or more RAM modules are faulty , and the solution involves testing the modules one by one or replacing the defective memory.

SFC and DISM scan to repair system files

If you suspect corrupted system files, use the System File Checker (SFC) . Open Command Prompt or PowerShell as administrator and run:

sfc / scannow

This command analyzes and repairs critical Windows files . If problems persist, you can follow up with DISM, which repairs the Windows image.

DISM / Online / Cleanup Image / RestoreHealth

It is important that you have an internet connection during DISM, as it may need to download components from Microsoft servers.

CHKDSK and disk check

To assess the disk's health , use CHKDSK . From a console with administrator privileges, first run:

chkdsk

If it detects errors, run a more complete check with repair using:

chkdsk / r

This will mark and attempt to recover bad sectors. On older disks or those showing signs of physical failure, repeated BSODs related to NTFS or INACCESSIBLE_BOOT_DEVICE are a clear indication that it's advisable to back up your data and plan for a drive replacement.

Event viewer and minidumps

If you want to delve deeper, open Event Viewer (search "Event Viewer" in the Start menu) and navigate to Windows Logs > System. There you can locate critical errors that coincide with the time of the blue screen.

Additionally, the folder where Windows saves minidump files (usually C:\Windows\Minidump) will contain dumps that you can analyze with advanced tools like WinDbg. It's not essential for the average user, but for technicians and advanced users, it's invaluable.

Manufacturer-specific tools (Dell, Lenovo, ASUS…)

Many systems include solutions such as Dell SupportAssist, Lenovo Vantage/Support, ASUS MyASUS , or other utilities that automate part of the diagnostic process.

These tools can run comprehensive hardware tests, analyze blue screen errors , search for correct versions of official drivers, and in some cases, even automatically repair damaged Windows installations or launch manufacturer-specific recovery environments.

Boot errors and BSODs before Windows loads

In some situations, the blue screen appears even before you see the desktop. This usually indicates problems with booting, storage, firmware (BIOS/UEFI) settings , or fast startup.

Startup repair using the Windows Recovery Environment

If Windows fails to boot and displays a Blue Screen of Death (BSOD), you can use the Startup Repair option from within WinRE itself. Remember the trick of interrupting the boot process three times to force entry into the recovery environment.

Once inside, go to Advanced options > Troubleshoot > Advanced options > Startup Repair and let Windows attempt to detect and fix boot problems, damaged boot sectors, or inconsistent settings.

BIOS/UEFI settings and Intel VMD driver

On modern computers with advanced storage controllers (such as Intel VMD ) the INACCESSIBLE_BOOT_DEVICE error is relatively common after a firmware or disk change.

In such cases, many manufacturers recommend entering the BIOS/UEFI settings (usually with F2, Delete or similar when powering on) and changing the VMD option or the SATA/RAID controller mode: for example, from RAID On to AHCI or vice versa, or disabling VMD if it was previously active.

If you change these settings, it's important to note down the original configuration in case you need to revert them. Incorrect changes can cause Windows to stop recognizing the system drive, so it's best to proceed with caution.

Measures to prevent future blue screens

Once the system is stabilized, the goal is to minimize the chances of the BSOD returning at the worst possible moment. There are several best practices that are consistent across Microsoft and manufacturer guides.

First, it's important to keep your BIOS and drivers up to date , but only from reliable sources: official websites of Dell, Lenovo, ASUS, HP, etc., or using their automatic utilities. Avoid "magic driver packs" from dubious websites.

It's also crucial to have a well-ventilated and dust-free system . Overheating is a silent enemy that can cause WHEA_UNCORRECTABLE_ERROR, MACHINE_CHECK_EXCEPTION, and other hardware errors. Check fans, filters, and, if necessary, replace thermal paste on older systems.

At the software level, it's best not to have multiple antivirus programs running simultaneously . Installing two or three security suites at the same time is a recipe for conflicts, performance drops, and strange errors. Stick with one reliable solution, and if you switch, be sure to completely uninstall the previous one.

Another sensible measure is to periodically perform a clean boot (msconfig, hide Microsoft services, disable all others, and turn off startup programs) to check if a third-party service is causing instability. From there, you can reactivate elements one by one until you find the culprit.

And of course, don't forget to back up your important data . Although the BSOD itself doesn't "break" the hardware, the underlying problem can eventually render the drive inaccessible. In extreme cases, companies like Ontrack and similar services offer professional recovery, but it's much more convenient and cheaper to have backups already made.

In short, while the blue screen of death is intimidating, it's ultimately Windows' defense mechanism when something goes seriously wrong. With a little methodology—removing recently installed hardware, using safe mode, checking drivers, memory, and disk, utilizing diagnostic tools, and keeping up with updates—it's perfectly possible to restore system stability and minimize blue screens . Understanding these guidelines will allow you to react calmly the next time your computer decides to turn blue at the worst possible moment.