Windows BSOD Error 0x0000003D — What It Means & How to Fix It

What Does This Error Mean?

BSOD 0x0000003D (INTERRUPT_EXCEPTION_NOT_HANDLED) means an exception — an unexpected error condition — was raised while the CPU was handling a hardware interrupt, and no error handler was set up to catch it. This is a critical driver bug. The driver was processing a device signal and encountered an error it had no way to recover from, so Windows crashed to protect itself.

Affected Models

Windows 10
Windows 11
Windows 8.1
Windows 7

Common Causes

A device driver has an unhandled exception in its interrupt service routine — the code that runs when the device signals the CPU
A hardware fault is generating malformed or unexpected interrupt signals that the driver cannot process
Corrupted driver files on disk are causing the interrupt handler code to execute incorrectly
A newly installed driver is incompatible with the Windows version's interrupt handling model
Overheating CPU or unstable power delivery is causing intermittent errors during interrupt processing

How to Fix It

Find the responsible driver using WhoCrashed (free from resplendence.com). After a crash, run WhoCrashed — it analyzes your minidump files from C:\Windows\Minidump and tells you the exact driver file (.sys) that caused the crash. Note the driver name.

This step is critical. The driver name tells you which hardware or software to update or remove. Do not skip this step and guess — it will save you a lot of time.
Check your hardware temperatures. Download HWMonitor (free from cpuid.com) and monitor CPU, GPU, and motherboard temperatures during normal use. CPU should stay below 80°C (176°F). If temperatures are high, clean dust from fans and heatsinks, and check thermal paste.

Heat causes intermittent hardware errors that look identical to driver bugs. Always rule out overheating first — it is free to check and often the actual cause.
Update or reinstall the identified driver. Uninstall the current driver through Device Manager (right-click the device > Uninstall device > also check 'Delete the driver software for this device'). Then download and install the latest version from the manufacturer's website.

A fresh driver install is more reliable than an update on top of a potentially corrupted existing driver. The clean uninstall plus reinstall approach fixes corrupted driver files.
Check and reseat all internal hardware connections. Power off and unplug the PC. Open the case and firmly reseat your RAM sticks, GPU, and any PCIe expansion cards. Loose hardware connections can generate erratic interrupt signals.

This is especially worth doing if the PC has been moved recently or if it sits in a dusty environment. Oxidation on card contacts can also cause this — gently clean PCIe contacts with an eraser if they look discolored.
Run the System File Checker to fix corrupted driver files on disk. Open Command Prompt as Administrator and type: sfc /scannow — then press Enter. If it reports 'Windows Resource Protection found corrupt files,' restart and run it again to finish repairs.

Corrupted .sys driver files on disk can cause the interrupt handler code to execute incorrectly. SFC replaces those files from the Windows component store.

When to Call a Professional

If you cannot isolate the responsible driver and the error persists after updates and hardware checks, seek professional help. Kernel-level interrupt debugging requires specialized tools and knowledge. A technician can use WinDbg and kernel debugging to trace exactly where the unhandled exception occurred.

Frequently Asked Questions

What is an interrupt service routine?

When a hardware device needs attention — like a keyboard registering a keypress or a network card receiving data — it sends an interrupt signal to the CPU. The CPU pauses what it is doing and runs a small piece of driver code called an interrupt service routine (ISR) to handle the event. The ISR must run very quickly and cannot make certain types of errors. When it does make an error and there is no exception handler, Windows crashes with this BSOD.

This only happens when a specific USB device is plugged in.

That tells you exactly which driver to target — the driver for that USB device. Go to the device manufacturer's website and check if there is an updated driver. If no update is available, contact the manufacturer's support — this is their bug to fix. In the meantime, avoid using that device on this PC.

My PC is brand new and I am getting this error. What went wrong?

On a new PC, this usually points to a driver conflict between pre-installed software (bloatware) and your hardware. Check Device Manager for any yellow warning icons. Also look in WhoCrashed results for the driver name, then Google it to find out which pre-installed app installed it. Uninstall that app and its drivers, then reinstall only the components you need.