Skip to content

0x000000BF: STATUS_ABANDONED_WAIT_63

Windows Error Code Lookup: Decode Windows error codes: Win32, HRESULT (0x80070005), NTSTATUS, Windows Update, msiexec and blue-screen stop codes, with what to check next.

Paste the number from an error dialog, event log, script or setup log: 0x80070005, 80070005, -2147024891, 1603, 0xC0000005, a stop code like 0x7E, a name like E_ACCESSDENIED, or a few words. You get every way Windows could mean that number (an HRESULT often wraps a Win32 error, so 0x80070005 is "Access is denied" too), its parts decoded, and what to check for the common ones. Names and messages come from the Windows SDK headers and Windows' own message tables; see Microsoft's System Error Codes and [MS-ERREF] for the full references.

Try: 0x80070005, 1603, 0xC0000005, 0x800F081F, 0x8024402C, 0x7E, access denied

0x000000BF = 191

NTSTATUS 0x000000BF

STATUS_ABANDONED_WAIT_63

Becomes the Win32 error: 736ERROR_ABANDONED_WAIT_63: ERROR_ABANDONED_WAIT_63

Severity (bits 30-31)0: Success
Customer (bit 29)0: Microsoft
Facility0 (0x000)
Code191 (0x00BF)

Stop code 0x000000BF (blue screen)

MUTEX_ALREADY_OWNED

Open the dump in C:\Windows\Minidump with WinDbg and run !analyze -v to see which driver was involved. Microsoft's bug check reference explains the four parameters for each code.

Win32 error 191 (0xBF)

ERROR_INVALID_EXE_SIGNATURE

Cannot run %1 in Win32 mode.

%1, %2… are where Windows fills in details such as a file or program name.

As an HRESULT (HRESULT_FROM_WIN32): 0x800700BF