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)

Possible solutions

1

MonoTouch Fatal Crash once deployed

xamarin.ios

It looks like the heap has become corrupted somehow. I can't find anything immediately wrong in the code you're using, but maybe you can try changing this line:

var pStr = Marshal.AllocHGlobal(length);

to

var pStr = Marshal.AllocHGlobal(length * 2);

to see if that works around the issue.

I might be able to get my hands on an iPhone soon where I can test it.

Update

I've tried this on an iPhone4, and it does not crash. This means that it's probably several different things in your app that plays together to create this crash, and the best way to fix/find it would be to file a bug at http://bugzilla.xamarin.com and attaching your project (you can mark the bug private so only Xamarin employees can see it if your project is closed source).

answered on Stack Overflow Mar 14, 2012 by Rolf Bjarne Kvinge • edited Mar 14, 2012 by Rolf Bjarne Kvinge

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