0x00000080 NMI_HARDWARE_FAILURE Fixes and Checks for Windows

0x00000080 is an NMI_HARDWARE_FAILURE blue screen: Windows got a non-maskable hardware alert, so I look at hardware and firmware before drivers. If you start with software fixes, you waste time and can miss a bad DIMM, PSU, motherboard, or PCIe card. Remove the newest hardware or driver change first, then see whether the crash comes back.

This guide is part of our Windows BSOD stop codes: full list and fixes series.

What 0x00000080 means in Windows

Bug Check 0x80 has the value 0x00000080, and Microsoft labels it NMI_HARDWARE_FAILURE. NMI means non-maskable interrupt, a hardware-level signal that skips normal software handling. That is why this stop code differs from an app crash or a routine driver error. It points straight at a hardware fault, though the exact cause is often hard to pin down from the code alone (per Microsoft support). (Microsoft Learn)

Before you reboot, record the stop code, whether the machine was under load, and any driver or module names on screen. If the screen shows a dump file path, save that too. I use those details later when I compare the crash against memory, power, or add-in card tests.

What information to note before the reboot

1. Write down the stop code exactly as shown: 0x00000080.
2. Note whether the crash happened during boot, idle, or load.
3. Record any recent BIOS, RAM, GPU, storage, or USB changes.
4. Take a photo of the blue screen if any module name or file path appears.

What usually causes 0x00000080?

The usual suspects are recently added hardware, unstable memory, power delivery faults, add-in cards, and heat problems. The code does not rank them for you, because many hardware faults can trigger the stop and the exact cause is often hard to determine (per Microsoft support). That is why I isolate parts instead of guessing.

Intermittent failures often point to power or heat: the system may run for a while, then fail when load changes. Permanent failures usually repeat at the same point in startup, or fail even after the same part is moved to another slot or test system. Timing matters. It is one of the few clues that separates a weak component from a bad connection.

Likely causes from most to least common

• Recently installed hardware or a driver change
• Unstable or mismatched memory modules
• Loose or failing power delivery hardware
• Nonessential add-in cards
• Heat buildup, fan failure, or blocked airflow

Should I remove recently installed hardware for 0x00000080?

Yes. Remove any hardware or drivers installed recently before deeper testing, because that is the fastest first-pass isolation step Microsoft calls out (per Microsoft support). Test one item at a time and keep a change log. If the crash stops after removal, leave that part out and verify it in another machine or with known-good hardware before you put it back.

1. Shut down completely.
2. Unplug AC power and discharge the system.
3. Remove one newly added internal card or peripheral only.
4. Boot and note whether the crash returns.
5. Repeat with the next newest item, one change at a time.
6. If a removal fixes the crash, keep that part out until it can be tested elsewhere.

Recently installed hardware or driver rollback path

If the part is a device driver rather than a card, open Device Manager, right-click the device, and choose Properties > Driver > Roll Back Driver or Uninstall Device. Reboot after each change. For storage, GPU, Wi-Fi, and chipset drivers, keep the test window simple: one change, one boot, one result.

Can bad RAM cause bug check 0x80?

Yes. Bad or mismatched memory can trigger the crash, especially when the installed modules are not the same type or when one stick fails only in a specific slot. Microsoft advises checking that memory modules are of the same type (per Microsoft support). Use a one-stick, one-slot test order and record every result.

1. Power off, unplug, and remove all but one memory module.
2. Install that module in the primary slot recommended by the board manual.
3. Boot and run Windows Memory Diagnostic from the Start menu.
4. If needed, run a longer pass with memtest86 from bootable media.
5. Move the same stick to the next slot and repeat.
6. Write down the exact stick, slot, pass/fail result, and error count.

If one stick fails in every slot, replace that module first. If the same slot fails with multiple sticks, suspect the motherboard slot or memory channel. If every module passes alone but fails together, mixing may be the issue.

Check power hardware next

Power faults can trigger intermittent crashes that look random at first. Inspect the main power connectors, the CPU power lead, and any PCIe power connectors for looseness, heat damage, or bent pins. If the system clicks, rattles, or a drive makes mechanical noise, disconnect secondary drives and retest. A noisy drive can be a separate fault or a clue that power is unstable under load (reported by windowscentral.com).

1. Shut down and unplug the PC.
2. Reseat the 24-pin ATX connector and CPU power connector.
3. Check PCIe power plugs on GPU or add-in cards.
4. Inspect for scorch marks, melted plastic, or bent contacts.
5. Detach secondary drives if there is clicking or rattling.
6. Swap in known-good power hardware or move to bench testing if the crash persists.

When the failure happens only under load, or only after a warm-up period, power delivery and heat move up the list. A PSU that looks fine at idle can still fail when current demand rises.