INTERRUPT_EXCEPTION_NOT_HANDLED

Code: 0x3d (61)

As HRESULT:

S: 0 (Success)
C: 0 (Microsoft-defined)
N: 0 (Not an NTSTATUS value)
Facility: 0x000 (FACILITY_NULL: Default)
Code: 0x003d (61)

As NTSTATUS:

Sev: 0 (STATUS_SEVERITY_SUCCESS)
C: 0 (Microsoft-defined)
Facility: 0x000 (Default)
Code: 0x003d (61)

Parameters

Parameter	Description
1	Exception Record (When Available)
2	Context Record (When Available)
3	0
4	0

Description

The INTERRUPT_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000003D. This indicates that the exception handler for the kernel interrupt object interrupt management was not able to handle the generated exception.

Important
This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

Resolution

The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause.

Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.

Associated Modules

Module	Code	Found in	Description
EhStorAuthn.exe	0x3d	7	Device initialize to manufacturer state fail
EventCreate.exe	0x3d	78.11011	%1
KernelBase.dll	0x3d	78.1	The printer queue is full.
cipher.exe	0x3d	78.11011	No recovery certificate found.
dsreg.dll	0x3d	1011	Unable to set WinHTTP call back function. Notification flags: %1. Error: %2
dssec.dll	0x3d	78.11011	Create inbound forest trust
ehepgres.dll	0x3d	7	%1
hvloader.dll	0x3d	11	Hypervisor launch failed; Minimum CPUID leaves required by the hypervisor are not supported on the system.
hvservice.sys	0x3d	10	Hypervisor launch failed; Minimum CPUID leaves required by the hypervisor are not supported on the system.
kernel32.dll	0x3d	78.11011	The printer queue is full.
nslookup.exe	0x3d	78.11011	unknown query class: %1
reagentc.exe	0x3d	11	Recovery test mode is currently active.
webservices.dll	0x3d	78.11011	The length of the buffered protocol record exceeded the quota.
wevtutil.exe	0x3d	78.11011	Install event publishers and logs from manifest. Usage: wevtutil { im \| install-manifest } [/OPTION:VALUE [/OPTION:VALUE] ...] File path to an event manifest. All publishers and logs defined in the manifest will be installed. To learn more about event manifests and using this option, consult the Windows Eventing SDK on Microsoft Developers Network (MSDN) at http://msdn.microsoft.com. Options: You can use either the short (for example, /rf) or long (for example, /resourceFilePath) version of the option names. Options and their values are not case-sensitive. /{rf \| resourceFilePath}:VALUE ResourceFileName attribute of the Provider Element in the manifest to be replaced. The VALUE should be the full path to the resource file. /{mf \| messageFilePath}:VALUE MessageFileName attribute of the Provider Element in the manifest to be replaced. The VALUE should be the full path to the message file. /{pf \| parameterFilePath}:VALUE ParameterFileName attribute of the Provider Element in the manifest to be replaced. The VALUE should be the full path to the parameter file. Example: The following example installs publishers and logs from the myManifest.man manifest file. wevtutil im myManifest.man /rf:^%systemroot^%/System32/wevtutil.exe
win32k.sys	0x3d	78.1	MenuHilight
win32kbase.sys	0x3d	1011	MenuHilight
16 entries