Windows error 0x0000005E, 94

Detailed Error Information

OBJECT_INITIALIZATION_FAILED[1]

This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0x5E: OBJECT_INITIALIZATION_FAILED.

HRESULT analysis[2]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.
FlagsSeveritySuccess

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[2][3]
DescriptionThe default facility code.[2][3]
Error Code94 (0x005e)

Questions

26votes
2answers

Debugging C++ library with Android Studio

I'm working on an Android project which uses a Java class that is a wrapper on a C++ library. The C++ library is a company internal library and we have access to its source code, but in the Android project it is only dynamically linked, so it is used only [...] read more
android
c++
android-studio
java-native-interface
android-studio-3.0
6votes
1answer

Trouble displaying C# stack trace in WinDbg

I have a handle leak in a C# program. I'm trying to diagnose it using WinDbg using !htrace, roughly as presented in this answer, but when I run !htrace -diff in WinDbg I'm presented with stack traces that don't show the names of my C# functions (or even my .net [...] read more
c#
windbg
stack-trace
handle-leak
1vote
0answers

application creating muant handles and never frees them

My c++ application is creating mutant handles. I couldn't find where the handle is being created, so I used Windbg and with !htrace. It doesnt give the exact function name. All my symbol files are loaded and the application is built in debug mode. !htrace shows open handles but the [...] read more
windbg
handle
resource-leak
0votes
1answer

Syntax for passing a user-defined variable as a command option

With LLDB version 8 I'm trying to dump the code bytes for a function "fh", using the memory read command, using variables to calculate the length: (lldb) expr unsigned $addr = (unsigned) fh (lldb) expr unsigned $next_addr = (unsigned) fi (lldb) expr unsigned $len = $next_addr - $addr (lldb) p/x [...] read more
lldb
0votes
2answers

Windows Server debugging: view User Mode Stack in WDM Kernel Mode Driver Breakpoint

I'm debugging a WDM Kernel driver IOCTL using Visual Studio Kernel Mode Debugger via pipe Serial connection to a Hyper-V VM running Windows Server 2012 R2. Once I hit a breakpoint inside the Driver IOControl is it possible to view the user mode call stack? At the moment I can [...] read more
windows
stack
driver
wdm

Comments

Leave a comment

(plain text only)

Sources

  1. https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
  2. https://msdn.microsoft.com/en-us/library/cc231198.aspx
  3. winerror.h from Windows SDK 10.0.14393.0

User contributions licensed under CC BY-SA 3.0