Windows error 0x00000122, 290

Detailed Error Information

WHEA_INTERNAL_ERROR[1]

This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0x122: WHEA_INTERNAL_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 Code290 (0x0122)

Possible solutions

0

Exception Codes: KERN_INVALID_ADDRESS at 0x0000003d

iphone
addressbook

The best approach to find the cause of the problem depends on whether you are still developing and have the code or whether this is a crash report from iTunes.

While there is a detailed Apple doc on the ARM registers here http://developer.apple.com/library/ios/#documentation/Xcode/Conceptual/iPhoneOSABIReference/Articles/ARMv6FunctionCallingConventions.html it does not really help to locate the problem.

If you have the code and you are still developing I would suggest you need to put NSLogs in the code and/or do some debugging.

If it's a crash report from iTunes the best is to follow Apple's guide on crash report here http://developer.apple.com/library/ios/#technotes/tn2151/_index.html.

This is the main idea as described by Apple:

If you get crash logs off a device through Xcode's Organizer window, then they will be symbolicated for you automatically after a few seconds. Otherwise you will need to symbolicate the .crash file yourself by importing it to the Xcode Organizer. Open the Xcode Organizer, select the “Devices” tab, select “Device Logs” under “LIBRARY” on the top of the sidebar, click the "Import" button and select the .crash file.

Basically, all you need to do in this case is drag and drop the crash report into xCode, but make sure you have the dSym file so xCode can xymbolicate the crash report with the correct version of the build of your app. To do this you need to "build and archive" each distributed app version! ps the video describing all the detail is in session 317...

answered on Stack Overflow Sep 10, 2012 by user387184 • edited Sep 10, 2012 by user387184
0

Decoding Stack Trace error

windows-phone-8

It looks to be related to your creation of a new SpeechRecognizer in the Loaded event of the MainPage.

answered on Stack Overflow Sep 26, 2013 by Matt Lacey

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