The code is the useful part

Windows drops to a full blue screen with a sad face and a line of capital letters, then restarts on its own. That is a blue screen, or BSOD. Most people's first reaction is that the machine is finished. It usually is not. The blue screen is Windows stopping on purpose to protect itself, and the hardware is intact. The line of code is what tells you why.

The screen often vanishes before anyone can read it. Here is how to get the code back, and what the six most common ones mean.

How to capture a stop code

There are three ways to get it:

  1. Take a photo. The bottom of the blue screen carries a line of capital letters, such as MEMORY_MANAGEMENT, and some builds add a number like 0x0000001A. A phone is the most reliable tool here, because the screen is gone once the machine reboots.
  2. Read the Event Viewer. Right-click the Start button, then Event Viewer, Windows Logs, System. Look for a red error whose source is BugCheck. The full code is in the entry.
  3. Stop the automatic restart. If it blue screens often enough that you never get the photo, open Settings, System, About, Advanced system settings, then Startup and Recovery, Settings. Tick "Write an event to the system log" and untick "Automatically restart". The next blue screen will sit there and wait for you.

What a blue screen actually is. Three causes cover the great majority: a driver conflict, failing memory or storage, and corrupted system files. Software problems you can fix yourself. Hardware problems have to be measured and located. That is why the table below splits every countermeasure into "you can do this" and "this needs a bench".

Six common codes and what to do

Stop code Likely cause What you can do When it needs a repair bench
0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED An incompatible driver, most often a graphics driver, a freshly installed driver, or new hardware Boot into safe mode, uninstall the most recent driver, roll the graphics driver back It still recurs after the driver is gone, which points to hardware or a deeper driver problem
0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL A driver touched an illegal memory address. The driver is almost always the culprit Uninstall recently installed drivers, run sfc /scannow to repair system files Every driver is an official build and it still blue screens: test the memory
MEMORY_MANAGEMENT Faulty or mismatched RAM, or an unstable overclock Drop the overclock. Run Windows Memory Diagnostic, which you can search for from the Start menu. If it reports errors, reseat the modules or test them one at a time The test reports errors repeatedly: replace the memory
IRQL_NOT_LESS_OR_EQUAL A driver or memory address conflict, a close relative of 0xD1 Same as above: roll the driver back, drop the overclock, run the memory test Crashes arrive at random: suspect the memory first
CRITICAL_PROCESS_DIED A critical system process exited abnormally, usually from corrupted system files or bad sectors on the drive Run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth It still recurs after the repair: check the health of the drive
WHEA_UNCORRECTABLE_ERROR A hardware-level error: a CPU overclock, unstable voltage, or damaged hardware Load BIOS defaults, drop the overclock, clean the dust and improve the cooling It still appears at stock clocks: test the CPU, motherboard and memory one by one

General troubleshooting order, from software to hardware:

  1. Think back to what changed before the first blue screen: a new driver, new software, new hardware. Remove it and roll back.
  2. Open Command Prompt as an administrator and run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, to repair system files.
  3. Run Windows Memory Diagnostic. If it reports errors, deal with the memory first.
  4. Remove every overclock and load BIOS defaults.
  5. If it still blue screens more than twice a week after all of that, the fault sits in the hardware layer. Stop reinstalling the system and hoping.

When to stop guessing

Send the machine in if any of these is true:

Locating the fault is the part that takes experience. On the bench we use memory tests, drive diagnostics and swap testing to pin down the failing part, and most faults are pinned down in one visit or half a day. For the full blue screen service and pricing, see blue screen repair. For general desktop work, see desktop repair.

What it costs

Item Price Notes
Diagnosis and assessment RMB 50-150 Tested at the store. We quote first, then repair
Driver conflict or system file repair RMB 80-150 Includes sfc/DISM and a driver rollback
Windows reinstall RMB 150 Desktop and documents are backed up first
Memory replacement (8GB DDR4, for example) RMB 80 labor plus the price of the module Kingston 8GB modules start at about RMB 150
Drive replacement plus system migration RMB 100 labor plus the price of the drive The right job when bad sectors are causing the blue screen

These are Guangzhou Panyu prices for 2026. We test first, quote second, and repair only after you approve.

A real case: five machines, one bad memory kit

In September 2024 a design company in Panyu brought in five desktops. Over the previous month they had blue screened repeatedly between them, mostly on MEMORY_MANAGEMENT and IRQL_NOT_LESS_OR_EQUAL. The customer had already paid an outside shop to reinstall Windows. It did not help. A reinstall only fixes software, and the machines blue screened again within the week.

We went on site and ran memory diagnostics on each machine. The extra module fitted to each machine in this batch was incompatible with the chips on the original modules. We swapped in matched modules, and all five machines returned to normal. The bill was RMB 1,150, covering the site visit, the diagnosis, the memory and a burn-in test. A month of trouble ended in half a day.

Where to find us

We are at No. 3-8 Jinlong Road, Dalong Street, Panyu District, Guangzhou, and we cover both Panyu and Nansha. Phone 18825126836 or 020-39029800, Monday to Saturday, 09:00-18:00.