Software tower · floor

Blue screen error, and why it is not blue any more

Blue screen error is a name Microsoft itself has stopped relying on. On current Windows 11 the screen is black, the company documents the change and the version it arrived in, and the same page that answers this question lists three different names and two different colours for the same event.

Microsoft’s own page no longer calls it blue

The support page for this error lists the names it goes by: “This is also known as a stop code error, a bug check, a kernel error, or a Blue Screen error, or a Black Screen error, or BSOD.” And it says so plainly: “The screen color and messaging for a stop code error can vary, depending on which version of Windows 11 you are running.”

The change is documented and dated. Announcing the new design, Microsoft wrote: “The screen displays a more readable layout while keeping the technical details visible. This screen appears with a black background.” The update note calls it “a more streamlined interface… during an unexpected restart” and applies it to Windows 11, version 24H2.

Two consequences for anyone searching. A black crash screen is not a different, worse problem than a blue one — it is the same thing renamed and repainted. And there is a third colour with a meaning: “On preview releases of Windows, the screen color can be green, leading to the green screen of death (GSOD).” Green means you are on a preview build.

With the name settled, the useful question is what to do — and on that Microsoft publishes a figure, which is rarer than a list of causes.

The one number that tells you where to look

Microsoft, on what causes these errors: “70% are caused by third-party driver code.”

That figure is worth more than any list of stop codes, because it settles the first question: where to spend your attention. Not the operating system, not a virus, not the disk — something installed alongside Windows that talks to hardware. It also explains why the remedies that feel most thorough, like reinstalling Windows, so often fix the symptom while the same driver waits to be installed again.

Everything else on the screen is there to narrow it down, and it is worth knowing what each part is before the machine restarts itself.

The stop code

the name, not the number

“To help determine the cause of the problem, a stop code, such as PAGE_FAULT_IN_NONPAGED_AREA or MEMORY_MANAGEMENT will appear” on the screen.

It is the one thing worth writing down before restarting.

The module name

when it is known

“The bug check screen displays the stop code error, such as CRITICAL_PROCESS_DIED. When the module name of the currently executing code is known” it is shown too.

Given the 70% figure, that name is the shortest route to the cause.

The percentage

it is saving evidence

“If the system can generate a dump file, you see a display showing the percent complete as the system writes the dump file.”

That counter is not the repair. It is the machine writing down what happened — and a reason to let it finish.

The third card deserves a moment. The percentage counter means the machine is saving the evidence, and interrupting it — by cutting the power because the screen looks stuck — is how a crash becomes unexplainable. On Windows 11 24H2 that wait is much shorter than it used to be: Microsoft says the release “reduced downtime during an unexpected restart to about two seconds for most users”.

And if the seventy per cent figure points at drivers, Windows already ships the tool for testing them.

“The driver verifier manager is built into Windows and is available on all Windows PCs. To start the driver verifier manager, enter verifier” at a command prompt.

Given that Microsoft attributes seventy per cent of these errors to third-party drivers, a tool that stress-tests drivers and is already installed on every Windows machine is the most direct thing on this page. It is also a tool that deliberately provokes crashes, so it belongs on a machine you can afford to restart repeatedly — and Microsoft’s pages on it are written for driver developers, which is worth knowing before starting it.

Two more published details. Where the evidence lands: Microsoft’s troubleshooting page says “The memory dump file is saved at the following locations” and lists them — so the crash you could not read leaves a file you can. And on newer machines the recovery itself has been automated: Microsoft documents it for recent Windows 11 24H2 builds: “quick machine recovery is a feature that enables the recovery of Windows devices” when they cannot start. Microsoft also states that 24H2 “reduced downtime during an unexpected restart to about two seconds for most users”.

So the order that follows from the documentation. Write down the stop code and, if one appears, the module name — those two strings are the whole diagnosis in compressed form. Let the percentage finish so the dump gets written. Then look at drivers first, because that is where Microsoft puts seven of every ten of these errors, and the machine keeps a record of what happened that is linked from the floor on random freezes.

A note on what this page deliberately does not do. It does not list stop codes with causes beside them. Microsoft publishes a reference of them, it runs to hundreds, and reproducing a fraction of it here would be worse than pointing at the whole thing.

A note on the results. Google did not return readable search results while this page was written, so this page makes no claim about what is on Google’s first page for this question.

What this page will not do is tell you which driver is at fault. The module name on the screen and the dump file are the evidence; reading them is a separate job with its own tools.

It will not tell you to reinstall Windows. If the cause is a driver, the reinstall removes the symptom and leaves the driver waiting to be installed again.

And it will not recommend a driver-updater product. The verifier is already on the machine, and the tools that promise to fix drivers automatically are the least tested category in this entire tower.

Where to start

Three ways in. If the screen was black rather than blue, take the first.

“Mine was black, not blue.”: Same thing, repainted — microsoft s own page
“What actually causes these?”: Microsoft publishes a share — the one number
“What should I write down?”: Two strings — the stop code

The colour changed

Microsoft names the error three ways, states that colour and wording vary by version, and documents the black screen arriving in Windows 11 24H2.

A computer that freezes at randomWhat the machine already wrote down, and how to make it record the next one.Open this floor → Windows Update errorsErrors that are not yours to fix, and the space that is not on your drive.Open this floor → A Windows update that failedReading a rollback code, and undoing an update that installed.Open this floor →

Seventy per cent

Microsoft attributes seven of every ten of these errors to third-party driver code, which decides where to look before any list of codes does.

Updating driversWhat a driver is, and what updating or rolling one back actually changes.Open this floor → Graphics driversThe driver most often named in crash reports.Open this floor → Safe modeStarting with third-party drivers out of the way.Open this floor →

What is on the screen

A stop code, sometimes a module name, and a percentage that means the machine is writing the evidence rather than hanging.

Checking hard drive healthThe hardware cause behind some of the remaining thirty per cent.Open this floor → A computer that will not turn onWhen it does not get as far as a crash screen.Open this floor → It powers on but will not bootThe gap before Windows loads, and the codes manufacturers publish to describe it.Open this floor → Backing up your computerWhat makes a driver-level failure an inconvenience instead of a loss.Open this floor →

What this tower will not do

It will not list stop codes with causes beside them. Microsoft publishes a reference running to hundreds; quoting a handful would be worse than pointing at all of it.

It will not name your faulty driver. The module name and the dump file are the evidence, and reading them is a separate job.

It will not tell you to reinstall Windows. Where a driver is the cause, that removes the symptom and keeps the cause.

And it carries no affiliate links, including for driver-updater products, which is what a page ranking for this question would exist to sell. What holds instead is simple: the colour change, the seventy per cent and the contents of the screen above are quoted from Microsoft support pages, its driver documentation and its own announcements, each named where it is used.

Written by Alberto Gulotta

Founder and editor of AI Tools Primer, writing from Palermo, Italy. Thirty-five years of taking computers apart, starting with a Commodore 64 — the long version is on the about page.

Something wrong on this page? Write to aitoolsprimer@gmail.com and it gets fixed.

Written on 23 August 2026.

Independence and limits

No affiliate links and no paid placements anywhere on this site. Nobody pays to appear here, and no company has seen this page before you did.

This is general information, not professional advice. Where a page touches money, health, safety or the law, it names its source and the date it was read — and your situation may still differ. See the privacy page and the cookie policy.