0x0000003D fixes: find the cause and stop crashes fast
What does 0x0000003D mean in Windows?
0x0000003D is the Windows bug check for INTERRUPT_EXCEPTION_NOT_HANDLED. In plain terms, Windows hit an exception while handling an interrupt and stopped to prevent further damage. My first fix step is to sort the crash by timing: if it happens before login, I go straight to WinRE and Safe Mode in Windows; if it started after a driver or update change, I reverse that change first.
That timing check matters because 0x0000003D is usually faster to solve as a driver, update, startup, or corruption problem than as a generic “BSOD.” This guide decodes the stop code, shows what the parameters can and cannot tell you, and maps the shortest safe repair path for Windows 10 and 11. If you need broader crash context, see our Windows BSOD troubleshooting guide.
Bug Check 0x3D in plain English
Bug Check 0x3D has the value 0x0000003D, and Microsoft names it INTERRUPT_EXCEPTION_NOT_HANDLED in its debugger reference. (Microsoft Learn)
For a Windows user, the practical reading is simpler: something running close to the kernel hit an exception during interrupt handling, and Windows stopped because it could not recover safely. In my repair work, that usually sends the first check toward a recent driver change, an update that changed startup behavior, or corruption that appears during boot activity.
What the four bug check parameters can tell you
The four parameters are clues, not a full diagnosis. Without a dump file, they narrow the path. With a minidump and WinDbg !analyze, they can point to the driver or module worth testing next, and Microsoft documents !analyze as the debugger extension used to display bug check information and help determine root cause. If you have dumps ready, our WinDbg crash dump guide pairs well with this stop code workflow. (Microsoft Learn)
| Parameter | Practical meaning | What it can tell you without a dump | What it cannot tell you alone |
|---|---|---|---|
| Parameter 1 | Usually the exception record pointer | Confirms the crash stored exception details | The exact bad driver name |
| Parameter 2 | Context record when available | Shows there may be CPU state to inspect later in WinDbg | Whether the fault came from storage, graphics, or networking by itself |
| Parameter 3 | Implementation-specific data | May help compare repeated crashes for pattern matching | A safe fix choice on its own |
| Parameter 4 | Implementation-specific data | Can help confirm the crash is repeating in the same path | A final diagnosis without the dump, timing, and recent-change history |
Microsoft’s debugger reference says the parameters may include an exception record and a context record, with parameter 2 used for the context record when available. For non-programmers, that means the blue screen parameters become useful when you pair them with crash timing, minidumps, and recent system changes. (Microsoft Learn)
According to Bug Check 0x3D – Windows Drivers — The stop code value is 0x0000003D. (source)
What causes stop code 0x0000003D?
The first cases I chase are driver faults and startup-change failures, especially when the blue screen began right after a driver install, device swap, BIOS-adjacent utility install, or Windows Update. If the timing does not line up with a recent change, I move next to system-file or file-system repair, then to dump analysis and deeper recovery.
Ranked causes to test first
- Driver faults after recent installs, updates, or device changes. Focus on storage, chipset, display, network, printer, and security-related drivers. Check Device Manager for yellow exclamation marks and recent hardware.
- Windows Update or startup-change failures. If crashes begin during update install, after a cumulative update, or right after login, treat rollback and recovery as the shortest path.
- System file or file-system damage.
SFC /scannowandCHKDSKbelong here, not as the first move for every case. MiniTool includes both SFC andCHKDSKamong its fixes, with the examplechkdskc: /f /r /x. (minitool.com) (minitool.com) - Lower-frequency kernel-path trouble. When the same stop code returns after rollback, Safe Mode testing, clean boot, SFC, and
CHKDSK, use minidumps and WinDbg before making bigger changes.
0x0000003D triage map
Use crash timing to choose the first repair step. Before login, go to WinRE and boot into Safe Mode. Right after a driver or update change, reverse that change first. If there is no clear trigger, check system files, the file system, and minidumps instead of bouncing between random fixes.
The fastest safe fix depends more on when the crash happens than on the stop code name itself. A boot crash, a login crash, an idle crash, and an update-install crash each need a different first move. I treat this as a routing problem, then test one branch at a time.
0x0000003D triage map
| Crash timing | Likely cause | Next action |
|---|---|---|
| Before login or during a reboot loop | Boot-start driver, update rollback failure, startup corruption | Open WinRE, start Safe Mode, then remove the last driver or update change |
| At login or right after the desktop appears | Recent driver update, vendor utility, startup service | Use Safe Mode, Device Manager rollback, or System Restore |
| Only when idle or under background load | Third-party service, security suite, RGB or motherboard utility | Run a Clean Boot and re-enable services in batches |
| During Windows Update or first reboot after update | Broken quality update, changed driver package, failed servicing state | Uninstall the latest update from WinRE or Settings, then retry Windows Update |
| Random repeats with minidumps available | Specific driver or kernel module | Open the newest dump in WinDbg and run !analyze |
| No recent changes, plus disk or NTFS errors in logs | System file or file-system corruption | Run SFC first, then CHKDSK in Windows |
- Crash before login, or reboots too fast to reach desktop
Best next action: Enter WinRE first. From the sign-in screen, hold Shift and select Power > Restart, or interrupt boot until recovery opens. Then go to Troubleshoot > Advanced options > Startup Settings > Restart > Safe Mode. - Crash at login or right after desktop loads
Best next action: Start with Safe Mode. If Safe Mode holds, use Device Manager, System Restore, or update rollback before trying normal boot again. - Crash only when idle, after a few minutes, or under background load
Best next action: Use a Clean Boot. Run msconfig > Services tab > check Hide all Microsoft services > Disable all. Then disable startup apps in Task Manager > Startup apps. - Crash during update install or on the first reboot after an update
Best next action: Use WinRE or Settings to uninstall the latest update, or use System Restore if a restore point exists. - Parameter 1 and Parameter 2 present, and minidumps exist
Best next action: Open the dump in WinDbg and run !analyze. That is the shortest path to the likely module name. (Microsoft Learn) - No recent changes, but Event Viewer shows disk or NTFS errors near the crash
Best next action: Runsfc /scannowfirst, thenchkdskc: /f /r /x from an elevated Command Prompt. Expect a reboot prompt for the disk check.
Did a driver or device change trigger 0x0000003D?
If the blue screen started after new hardware, a driver update, or a vendor utility install, test that recent change first. In practice, I look for the last thing added or updated, then check Device Manager for the matching device class, warning icons, rollback options, and timestamps before I touch unrelated drivers.
Check Device Manager and reverse the recent change
- Open Device Manager: press Windows + X and select Device Manager.
- Expand the categories most tied to this stop code path: Display adapters, Network adapters, Storage controllers, System devices, and any recently added printer or USB device.
- Look for a yellow exclamation mark. If present, right-click the device and select Properties to review status.
- If the crash began right after a driver update, right-click the device > Properties > Driver > Roll Back Driver.
- If rollback is unavailable, select Uninstall device, restart, and let Windows reload the prior driver path. MiniTool also suggests updating outdated drivers and using Safe Mode where needed.
- If the suspect is a printer path and the machine shows a print-queue problem instead of a blue screen, stopping the Print Spooler, clearing Windows\System32\spool\Printers, restarting the service, and reinstalling the printer driver are reported by bleepingcomputer.com.
Use WinDbg when the bad module is not obvious
- Open File Explorer and check
C:\Windows\Minidumpfor recent dump files. - Open the dump in WinDbg.
- Run !analyze. Microsoft says this debug extension displays bug check information and helps determine the root cause. For a step-by-step walkthrough, use our WinDbg guide for BSOD dump analysis. (Microsoft Learn)
- Compare the module named in the analysis with the device category changed most recently.
Is 0x0000003D happening during boot, login, or right after Windows Update?
If 0x0000003D hits before login, go to WinRE first. If it starts right after a cumulative update or on the first reboot after patching, uninstall the latest update before you spend time on deeper repairs. Crash timing is one of the fastest ways I cut down the search list.
