INTERRUPT_EXCEPTION_NOT_HANDLED, the blue screen, explained and fixed

This stop code (0x0000003D) means an exception occurred while Windows was processing a hardware interrupt, the urgent signals devices use to demand attention, and no handler was in place to catch it. It is one of the rarer blue screens. The realistic causes are a buggy driver for a device that interrupts frequently (network, storage, USB, audio), recently added hardware, and, further down the list, failing memory or the device itself.

The fix, in order

  1. Remove or disconnect recently added hardware. New USB devices, expansion cards, docks, and drives bring new interrupt-heavy drivers. Run without them and see whether the crash leaves with them.
  2. Update device drivers from manufacturers. Network adapters, storage controllers, audio devices, and USB controllers first, because they interrupt constantly and their drivers run in the interrupt path.
  3. Roll back a driver if the timing fits. Device Manager → device → Properties → Driver → Roll Back Driver, for anything updated just before the crashes began.
  4. Boot into Safe Mode to confirm the class. Hold Shift + Restart → Troubleshoot → Advanced options → Startup Settings → Safe Mode. Stability there keeps the investigation on drivers and attached hardware.
  5. Update the BIOS/UEFI. Interrupt routing (the APIC and ACPI tables) is firmware territory, and makers fix interrupt bugs in BIOS updates.
  6. Test RAM and repair files. Windows Memory Diagnostic, then DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow. Rare codes deserve the standard checks before exotic theories.

If it still happens

Because this code is uncommon, weigh the pattern: crashes tied to one device’s activity (network transfers, audio, a dock) indict that device’s driver or hardware. Crashes with no pattern, after the full driver pass, move to memory and then to the motherboard’s interrupt handling, which realistically means a shop diagnosis with known-good parts.

Common questions

Why is there so little information about this code online? It is genuinely rare compared to the driver and memory codes most people meet. Microsoft documents it in the bug check reference as an interrupt exception with no handler, but few machines ever produce it, so first-hand reports are thin. The driver-and-hardware workup on this page is the standard response regardless.

Is INTERRUPT_EXCEPTION_NOT_HANDLED related to KMODE_EXCEPTION_NOT_HANDLED? Same family, different room. KMODE_EXCEPTION_NOT_HANDLED (0x1E) is an unhandled exception in ordinary kernel-mode code. 0x3D happens specifically during interrupt processing, which is why recently added or frequently interrupting devices get extra suspicion here.

Related errors

KMODE_EXCEPTION_NOT_HANDLED · DRIVER_IRQL_NOT_LESS_OR_EQUAL · SYSTEM_THREAD_EXCEPTION_NOT_HANDLED · DPC_WATCHDOG_VIOLATION