Windows error 0x0000011D, 285

Detailed Error Information

EVENT_TRACING_FATAL_ERROR[1]

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

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 Code285 (0x011d)

Questions

0votes
0answers

Confused about Y86 assembly code memory storage

I've been using an online compiler but I'm not sure why the memory is being split the way it is It's coming out as: 00a8 0000001d 00ac 01000000 when 00a8 should just hold the whole hex value as 0000011d. .pos 0 irmovl $1, %eax # int i = 1 irmovl [...] read more
memory
y86
0votes
1answer

MonoTouch Fatal Crash once deployed

I've found that I'm getting an error once I've deployed a solution to iPhone 4s which is causing the app to crash without raising any errors within MonoTouch. I'm handling the UIApplication.Main and writing to error log any exceptions, and none are being raised. I've tracked it down to a [...] read more
xamarin.ios

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