0xPC Error Codes Look up a code
One safety rule: if a message shows a phone number to call, it is a scam: Microsoft never does that. Check any warning in 5 questions.

Home › Blue and Black Screen Stop Codes › WHEA_UNCORRECTABLE_ERROR (0x124): The Hardware Error Windows Can't Fix Itself

0x124Stop Codes

WHEA_UNCORRECTABLE_ERROR (0x124): The Hardware Error Windows Can't Fix Itself

By Editorial Team · · 9 min read ✓ Checked against Microsoft documentation

In plain English

WHEA_UNCORRECTABLE_ERROR with stop code 0x124 usually means Windows has reported a hardware fault that it could not recover from. If you want the wider stop-code list, start with the full blue and black screen stop code guide, but for this error the safest path is hardware first, not Windows repair first.

First safe step

Before you run scans or reinstall anything, check the simple physical causes: shut the PC down, let it cool, and check heat, power cables, battery or charger fit on a laptop, recently added parts, drive connections, and any overclock or undervolt settings you changed in BIOS or software.

Try these in order, cheapest first

Hardware first. Software fixes come last on this page.

1Heat, power, reseat, undo tuningFree
2Find the failing part
3Test one part at a timeFree
4Software steps last

WHEA_UNCORRECTABLE_ERROR with stop code 0x124 usually means Windows has reported a hardware fault that it could not recover from. If you want the wider stop-code list, start with the full blue and black screen stop code guide, but for this error the safest path is hardware first, not Windows repair first.

Before you run scans or reinstall anything, check the simple physical causes. Start by shutting the PC down, letting it cool, and checking heat, power cables, battery or charger fit on a laptop, recently added parts, drive connections, and any overclock or undervolt settings you changed in BIOS or software.

This error often points to the CPU, RAM, storage, graphics card, motherboard, or power supply. If your crashes started after a memory upgrade, you may also need the RAM-check page for memory-related crashes. If the real clue is that Windows suddenly cannot see the boot drive, use the drive-loss stop code page when storage is the real clue.

What WHEA_UNCORRECTABLE_ERROR (0x124) means

WHEA_UNCORRECTABLE_ERROR with code 0x124 means Windows received a hardware error report and could not recover from it safely. WHEA stands for Windows Hardware Error Architecture. In plain English, something at the hardware or firmware level looked bad enough that Windows stopped the PC to prevent more damage or data loss.

That makes this stop code different from many blue screen errors that are often caused by a bad driver, a broken update, or damaged system files. Software can still play a part, but 0x124 usually points first to the CPU, RAM, storage, graphics card, motherboard, firmware, or the power feeding those parts.

The pattern around the crash matters. If your screen goes black, flickers, or recovers before the blue screen appears, check the graphics-driver crash page if the screen blanks and recovers before the stop code. If the stronger clue is repeated memory corruption or random app crashes between blue screens, start with the RAM-check page for memory-related crashes. If Windows suddenly cannot see the boot drive, use the drive-loss stop code page when storage is the real clue.

On this page, the first checks stay hardware-first because that is the safest place to start with 0x124. The next section begins with the quick checks that matter most before you spend time on deeper Windows repair steps.

1 Start with the fastest hardware checks Free

  1. Start with heat. Turn the PC off, let it cool for 10 to 15 minutes, then check whether the vents are blocked with dust or whether a fan has stopped spinning or started making a grinding noise. If the crash happens during games, video editing, or anything that pushes the graphics card, also keep in mind the graphics-driver crash page if the screen blanks and recovers before the stop code.
  2. Next, check power. Make sure the power cable is fully seated at both ends, the laptop charger is the correct one for that model, and the surge protector or power strip is not failing. On a laptop, test once on charger power and once on battery power if you can. On a desktop, a weak power supply can cause WHEA_UNCORRECTABLE_ERROR under load, especially after a new graphics card or extra drive was added.
  3. If the PC is a desktop, or a laptop with easy service access, turn it fully off, unplug it, and reseat the parts most likely to work loose: RAM sticks, the graphics card, and SATA or power cables to the drive. Remove each part, then fit it back firmly. If one RAM stick seems to be the clue, or crashes started after a memory upgrade, jump to the RAM-check page for memory-related crashes. If the drive disappears, Windows suddenly cannot boot, or the BIOS stops seeing the SSD, use the drive-loss stop code page when storage is the real clue.
  4. Last, undo recent tuning changes before you test again. Load default BIOS settings if you recently changed CPU overclock, XMP or EXPO memory profiles, GPU overclock, undervolt, or power limits. If this started right after a firmware change, go back one step at a time instead of changing five things at once. If the PC is too unstable to stay running, use Safe Mode boot steps only to help you reach shutdown or recovery screens, not as the main fix for 0x124.
Open desktop PC with a hand reseating a RAM stick and visible dust near the cooling fans | PC Error Codes

✓ Crash gone? You can stop here.

2 Find the part that is actually failing

Look at when 0x124 happens. If it appears while gaming, rendering, installing a big game, or doing anything that pushes the CPU or GPU hard, heat or power is still the leading suspect. If it happens at idle, during startup, or a few minutes after waking from sleep, think more about a bad stick, slot, cable, drive, or motherboard fault.

Recent changes matter more here than they do with many other stop codes. A new RAM stick, a second SSD, a graphics card swap, a BIOS update, or even moving the PC can leave one part slightly out of place. One bad RAM stick or one bad motherboard slot can do it, which is why this can overlap with the RAM-check page for memory-related crashes when the crashes cluster around memory-heavy work.

Watch the screen behavior before the restart. If the display goes black, flickers, freezes, then comes back before the blue screen, the graphics side moves up the list, and you may want the graphics-driver crash page if the screen blanks and recovers before the stop code. If the PC vanishes straight to a restart under load, with fans suddenly loud or the system shutting off fast, that pattern fits overheating or unstable power more than a normal Windows file problem.

Storage can still be the real fault even though this code sounds broader. A failing SSD, a loose SATA cable, a weak NVMe connection, or a drive that disappears for a moment can surface as WHEA_UNCORRECTABLE_ERROR. If you also see boot trouble, missing drives in BIOS, very slow file access, or the PC sometimes cannot find Windows at all, check the drive-loss stop code page when storage is the real clue.

3 What to test next if the PC still crashes Free

If the PC can stay on for 10 to 20 minutes, run the built-in memory and drive checks next. In Windows, search for Windows Memory Diagnostic, restart, and let it test. Then check the system drive's health in the maker's app if you have one, or watch for read errors, freezes, and files that suddenly fail to open. If memory clues are getting stronger, use the RAM-check page for memory-related crashes. If the drive disappears, boot loops, or Windows suddenly cannot find itself, go to the drive-loss stop code page when storage is the real clue.

Go into the BIOS or UEFI and load default settings. That matters even if you never meant to overclock, because XMP, EXPO, auto-boost settings, undervolts, and board presets can all make a system pass light use and still crash with 0x124. After loading defaults, save, restart, and test the PC again with the same task that usually triggers the crash.

If the machine is stable at default settings, only then does it make sense to update BIOS, SSD firmware, chipset drivers, or graphics drivers one at a time. Change one thing, test, then move to the next. If the screen goes black, comes back, and only later ends on a blue screen, that fits the graphics-driver crash page if the screen blanks and recovers before the stop code better than a general hardware fault. If crashes started right after a Windows patch or driver update, check what to do first after a crash that followed an update.

Stop testing and get service if the PC will not stay on long enough to finish checks, if it crashes in BIOS, if you smell burning, or if new parts fail in more than one slot or cable path. Those signs point away from a simple Windows repair. If you need a way to start with fewer drivers before making one last software-side check, use these Safe Mode boot steps.

UEFI BIOS screen showing an option to load default settings on a Windows PC | PC Error Codes

4 When software steps make sense after the hardware checks

If the hardware checks did not expose the fault, software steps can help, but keep them narrow. Start with anything that changed right before the crashes, especially a Windows update, BIOS update, graphics driver, storage driver, or chipset package. If the blue screen started right after Patch Tuesday or a manual update, read what to do first after a crash that followed an update before you remove several things at once.

If Windows still starts, roll back one recent driver or uninstall one recent update, then test again. If normal startup crashes too fast, use Safe Mode boot steps so you can remove the last change with less load on the system. If the stop code changes after that, follow the new clue, for example the RAM-check page for memory-related crashes, the drive-loss stop code page when storage is the real clue, or the graphics-driver crash page if the screen blanks and recovers before the stop code.

Skip deep Windows repair work if the signs still point away from Windows. A PC that crashes in BIOS, shuts off under load, freezes during a clean install, or keeps throwing 0x124 after defaults, memory checks, and drive checks is more likely to need a part swap or bench testing. The same goes for burning smell, fan failure, visible board damage, battery swelling in a laptop, or power loss that cuts the machine off completely.

At that point, the best next step is to stop changing multiple settings and write down what changed before the first crash. Note any new part, update, BIOS flash, power event, or temperature pattern, and whether the crash happens at startup, idle, or load. That short timeline helps a repair shop test the right part first, and it helps you avoid circling through Windows fixes that do not match this stop code.

Windows Advanced Startup screen showing startup repair and Safe Mode options for post-crash troubleshooting | PC Error Codes

Frequently asked questions

I saw 0x124 once. Do I need to replace a part?

Not yet. One crash after a heat spike or a loose connection may not repeat once that cause is fixed. Back up important files, work through the checks in order, and act on a pattern of repeat crashes, not a single event.

Will reinstalling Windows fix WHEA_UNCORRECTABLE_ERROR?

Usually no. A reinstall does not repair failing RAM, storage, power, or cooling, and crashes during or after a clean install point back to hardware. Try a reinstall only after the hardware checks and basic tests look sound.

The short version

If WHEA_UNCORRECTABLE_ERROR (0x124) keeps coming back after the heat, power, seating, and default-settings checks, treat that pattern as the answer. The fault has survived the steps that fix loose parts and unstable tuning, so it is more likely a part that is failing than a Windows setting you missed.

Write down when it crashes, what changed just before the first crash, and what you have already tested, then take that note to a repair shop if the crashes continue. That record saves time and money, and it stops you from replacing parts or reinstalling Windows on a guess.

Different number on screen?

Type it exactly as it appears and get the plain-English answer.

Look up a code

Pop-up telling you to call?

That is a scam. Microsoft never asks you to phone a number.

Check it in 5 questions