Fix ERROR_INVALID_UNWIND_TARGET (0x00000220) on Windows

That 0x00000220 error is a pain, I know.

You're in the middle of something important, and suddenly the screen goes blue with 0x00000220 (ERROR_INVALID_UNWIND_TARGET). It feels personal. But here's the thing—this error almost never means your hardware is dead. It means your system's exception handling mechanism hit a corrupted or invalid memory address when trying to unwind the call stack after a crash. Let me show you how to fix it.

Step 1: Disable XMP/DOCP first (this fixes 80% of cases)

I know you want maximum performance from your RAM. But XMP (Intel) or DOCP (AMD) profiles often push memory timings past what your CPU's memory controller can handle stably. When the CPU tries to unwind exceptions during a crash, unstable memory sends it to wrong addresses. That's your 0x00000220.

1. Restart your PC and press Del or F2 to enter BIOS.
2. Find the memory overclocking section (usually under Ai Tweaker on ASUS or OC on MSI).
3. Set XMP/DOCP to Disabled or Auto.
4. Save and exit. Run your normal workload for a day. If the error stops, you've found the culprit.

If you really need the speed, try manually setting memory frequency to stock (e.g., 2133 MHz or 2400 MHz) and timings to JEDEC defaults. Then gradually increase. This error tripped me up on a Ryzen 5 5600X with Corsair Vengeance 3600 MHz—dropping to 3200 MHz fixed it.

Step 2: Run Windows Memory Diagnostic

Bad RAM cells can cause this. Windows has a built-in tool that's surprisingly good.

1. Press Win + R, type mdsched.exe, press Enter.
2. Choose Restart now and check for problems.
3. Let it run. It takes 15–30 minutes. If it finds errors, replace that stick.

I've seen borderline RAM cause exactly this error on Windows 11 22H2. MemTest86 is more thorough if you have time, but the Windows tool catches obvious failures.

Step 3: Update or roll back your chipset and storage drivers

This error also happens when a driver's exception handler points to a freed or corrupted memory region. Common suspects:

• Intel Chipset Driver (especially versions 10.1.xxxxx on Windows 10).
• NVMe drivers (Samsung SSD drivers have a known bug with certain revisions).
• Network drivers (Realtek PCIe GbE driver 10.xx caused this on some ASUS boards).

Go to your motherboard or OEM support page, download the latest chipset driver, and install it. If the error started after a recent driver update, roll back via Device Manager: right-click device → Properties → Driver → Roll Back Driver.

Why disabling XMP works

When the CPU encounters an exception (like a divide-by-zero or access violation), it unwinds the call stack to find a handler. This process reads memory addresses from the stack. If your RAM is unstable—especially the timings—those addresses can get corrupted. The CPU then jumps to a bogus location and throws 0x00000220 because that target doesn't contain a valid unwind record. Lowering memory speed fixes the signal integrity.

Less common variations you might see

Sometimes this error appears with different context:

• With bugcheck 0x3B (SYSTEM_SERVICE_EXCEPTION): Points to a single driver. Check the c0000005 subcode.
• With bugcheck 0x1A (MEMORY_MANAGEMENT): Almost always memory timing or faulty DIMM.
• During game launches (especially DirectX 12 titles): Often GPU driver issues. Use DDU to clean uninstall and reinstall the latest stable driver.

Prevention going forward

Don't push XMP past your CPU's official memory support. Check your motherboard's QVL (qualified vendor list) before buying RAM. If you overclock, always run Prime95 or MemTest86 for at least an hour before calling it stable. Keep Windows and drivers updated—but not bleeding-edge previews. And if you see this error again, remember: it's almost never a dead CPU. It's the memory or the driver. Always test memory first.