How to Fix Error Code 0x0000003D (INTERRUPT_EXCEPTION_NOT_HANDLED)

By ErrorFix · Updated October 16, 2026 · 8 min read

What error 0x0000003D means

The blue screen shows the stop code 0x0000003D with the name INTERRUPT_EXCEPTION_NOT_HANDLED. Deep down, Windows relies on interrupts — tiny signals that devices, timers, and drivers use to get the CPU's attention when something needs handling. When the CPU receives an interrupt it cannot process correctly, Windows has no safe way to continue, so it stops everything and shows the blue screen rather than risk corrupting your data. That is why this stop code is fundamentally a hardware-adjacent error: the interrupts themselves come from hardware or low-level drivers, not from an app crashing.

Compared with memory-focused stop codes like 0x0000001A (MEMORY_MANAGEMENT) or 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA), 0x0000003D is rarer and more strongly tied to the processor and its environment. The most common triggers are CPU or RAM running overclocked beyond their stable limits, a failing CPU core, bad memory, overheating, an underpowered power supply, or a buggy chipset driver. The good news is that the fault is usually identifiable with systematic testing, and if an overclock is the cause, the fix is free and takes about five minutes.

Common causes

• CPU or memory overclocking (including XMP/EXPO): the number-one cause. Running the CPU, RAM, or voltages above stock makes interrupt handling unstable, and even "factory" XMP memory profiles count as overclocking.
• Failing CPU or bad RAM: a degraded CPU core or a faulty memory stick can corrupt the interrupt data the processor receives, producing crashes that get worse over time.
• CPU overheating: a loose cooler, dead fan, or dried-out thermal paste lets the CPU throttle and misfire under the load that interrupts place on it.
• Weak or failing power supply: voltage dips from an underpowered or aging PSU can make the CPU misinterpret interrupt signals, especially during gaming or heavy workloads.
• Buggy chipset, graphics, or storage drivers: low-level drivers that interact with the interrupt system can issue interrupt requests the CPU cannot complete when they are outdated or corrupted.

How to fix error 0x0000003D — step by step

Work through these fixes in order. Steps 1 and 2 resolve the error for most people, so do not skip them.

1. Remove any CPU or memory overclocking. Restart the PC and enter the BIOS or UEFI setup, usually by pressing Delete or F2 during startup. Choose Load Optimized Defaults or Load Setup Defaults to disable any CPU, RAM, or voltage overclocking — including XMP or EXPO memory profiles — then save and exit. If you use software overclocking such as Intel XTU or AMD Ryzen Master, open it in Windows and click Restore Defaults or Reset. Overclocking is the single most common trigger for this error, so test the PC at stock speeds for a day before going further.
2. Update chipset and graphics drivers. Press Windows + X and choose Device Manager. Expand System devices and update the chipset and CPU drivers, then expand Display adapters and update your graphics driver. Better still, download the latest chipset driver directly from your motherboard manufacturer's support page, and the latest graphics driver from AMD, Intel, or NVIDIA. Old or buggy drivers can fire interrupts the CPU cannot handle, so choose a clean installation rather than an in-place upgrade when the installer offers it.
3. Disable new or suspect hardware. If the blue screens started after you added something — a USB hub, a Wi-Fi card, an external capture device, a new SSD — unplug it and run the PC for a day without it. Open Device Manager and look for any device with a yellow warning triangle; right-click anything suspicious and choose Disable device. This narrows down whether one specific piece of hardware or its driver is generating the bad interrupts.
4. Test your CPU and RAM for faults. For the CPU, run a stress test such as Prime95 on the Small FFTs setting for 30 minutes and watch for errors or crashes, keeping an eye on temperatures with a monitor like HWMonitor. For the RAM, type Windows Memory Diagnostic in the Start menu, choose Restart now and check for problems, or boot MemTest86 from a USB drive and let it complete at least one full pass. Failing CPU cores and bad memory sticks are the leading hardware causes of 0x0000003D, and these tests find them reliably.
5. Check CPU cooling and power delivery. Shut down the PC, unplug it, and inspect the CPU cooler: a loose mounting bracket, a dead fan, or dried-out thermal paste lets the CPU overheat and misfire under interrupt load. Make sure the 8-pin EPS power cable is fully seated on the motherboard, and check that your power supply has enough wattage headroom for your hardware. An underpowered or failing PSU can cause voltage dips that the CPU interprets as interrupt errors.
6. Update the BIOS and reinstall Windows if needed. If every test passes but the crashes continue, download the latest BIOS or UEFI firmware from your motherboard manufacturer's support page and flash it following their instructions exactly — newer BIOS versions often fix interrupt-handling bugs, especially for newer CPUs on older boards. If the problem survives a BIOS update, back up your files and do a clean install of Windows 10 or 11 to rule out a corrupted system, then test with only essential hardware connected.

Did this fix it? Quick checklist

• The PC runs for a full day at stock BIOS settings with no blue screens
• Chipset and graphics drivers are up to date with clean installs
• Prime95 and a memory test completed with no errors
• CPU temperatures stay within safe limits under load

If the crashes stopped after removing an overclock, the system is stable at stock and you can cautiously re-tune later — but keep a crash log so you know exactly which setting broke things. If tests reveal bad RAM, replace the faulty stick (most memory carries a lifetime warranty). If Prime95 fails at stock settings on a well-cooled system with a good PSU, the CPU itself may be at fault — contact the manufacturer about a warranty claim. As a last resort, a clean Windows install with only essential hardware connected tells you definitively whether the problem is software or hardware.