SYSTEM_EXIT_OWNED_MUTEX

Code: 0x39 (57)

As HRESULT:

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

As NTSTATUS:

Sev: 0 (STATUS_SEVERITY_SUCCESS)
C: 0 (Microsoft-defined)
Facility: 0x000 (Default)
Code: 0x0039 (57)

Parameters

Parameter	Description
1	The address of the worker routine that caused the error.
2	The parameter passed to the worker routine.
3	The address of the work item.
4	Reserved.

Description

The SYSTEM_EXIT_OWNED_MUTEX bug check has a value of 0x00000039. This indicates that the worker routine returned without releasing the mutex object that it owned.

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.

Cause

The worker routine returned while it still owned a mutex object. The current worker thread will proceed to run other unrelated work items, and the mutex will never be released.

Resolution

A debugger is required to analyze this problem. To find the driver that caused the error, use the ln (List Nearest Symbols) debugger command:

kd> ln address

Where address is the worker routine given in Parameter 1.

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
EventCreate.exe	0x39	78.11011	%1
KernelBase.dll	0x39	78.1	A network adapter hardware error occurred.
cipher.exe	0x39	78.11011	No User found.
dsreg.dll	0x39	1011	Unable to query WinHTTP option %1. Error: %2
dssec.dll	0x39	78.11011	Enumerate entire SAM domain
ehepgres.dll	0x39	7	%1
kernel32.dll	0x39	78.11011	A network adapter hardware error occurred.
nslookup.exe	0x39	78.11011	Addresses:
reagentc.exe	0x39	8.11011	%1: This operation is not supported in audit mode.
sc.exe	0x39	78.11011	RUN PROCESS -- Delay = %1 milliseconds.
webservices.dll	0x39	78.11011	An integer value in the framing format exceeded the maximum value.
wecutil.exe	0x39	78.11011	Windows Event Collector service was configured successfully.
wevtutil.exe	0x39	78.11011	Export events from a log, log file, or using structured query to a file. Usage: wevtutil { epl \| export-log } [/OPTION:VALUE [/OPTION:VALUE] ...] By default, you provide a log name for . However, if you use the /lf option, then you provide the path to a log file for the value. If you use the /sq parameter, then you provide the path to a file containing a structured query. Path to the file where the exported events are to be stored. Options: You can use either the short (for example, /l) or long (for example, /locale) version of the option names. Options and their values are not case-sensitive. /{lf \| logfile}:[true\|false] If true, is the path to a log file. /{sq \| structuredquery}:[true\|false] If true, is the path to a file that contains a structured query. The command might take a long time if selecting many, but not all, events. /{q \| query}:VALUE VALUE is an XPath query to filter the events you want to export. If not specified, all events will be returned. This option is not available when /sq is true. The command might take a long time if selecting many, but not all, events. /{ow \| overwrite}:[true\|false] If true, and the destination file specified in already exists, it will be overwritten without confirmation. Example: The following example exports events from System log to C:\backup\system0506.evtx. wevtutil epl System C:\backup\system0506.evtx
win32k.sys	0x39	78.1	ButtonAlternateFace
win32kbase.sys	0x39	1011	ButtonAlternateFace
15 entries