Windows error 0x00000286, 646

Detailed Error Information

NOT_SAFE_MODE_DRIVER[1]

MessageThe driver was not loaded because the system is booting into safe mode.
Declared inwinerror.h

This appears to be a raw Win32 error. More information may be available in error 0x80070286.

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][1]
DescriptionThe default facility code.[2][1]
Error Code646 (0x0286)

Possible solutions

6

iOS app developed in Xcode 4.5 runs fine on iOS 6 but crashes on iOS 5

ios
xcode
ios5
ios6
xcode4.5
  1. It's possible you're using features only available in iOS 6 such as AutoLayout. Open your interface files and make sure AutoLayout is unchecked:
    enter image description here
    This AutoLayout toggle can be found in the utilities inspector (pane on the right side of Xcode) and then under the first tab of the Utilities Inspector (the File Inspector). You can also change the Document Versioning Deployment setting to the lowest iOS version your app supports. After doing so, Xcode will show warnings for features in your interface that are deprecated or may not be supported on some iOS versions.

  2. Yes, of course you can develop apps for earlier versions of iOS with Xcode 4.5. Just make sure that your deployment target is set correctly in your project settings.

  3. DrummerB's Suggestion for 3 & 4 should work well:

    I don't think that's going to help. Maybe you could try running bt in the debug console when your app crashes to get a trace.

Also, to improve upon DrummerB's answer, it is okay to use iOS 6 classes / APIs but you must check for their availability before using them:

if ([UIClassName class] != nil) {
    //UIClassName is available, you can now set it up
} else {
    //UIClassName is not available, use a different class or prompt the user
}
answered on Stack Overflow Oct 20, 2012 by Samuel Spencer • edited Jan 3, 2013 by Samuel Spencer
4

iOS app developed in Xcode 4.5 runs fine on iOS 6 but crashes on iOS 5

ios
xcode
ios5
ios6
xcode4.5
  1. You're probably using an iOS 6 API. Maybe you're using Auto-Layout. Check in all of your xib files that you disabled Auto-Layout. See this answer.
  2. It's certainly possible to develop iOS 5 apps with Xcode 4.5. You have to set the deployment target accordingly (which you did) and not use any iOS 6 features or APIs.
  3. & 4: I don't think that's going to help. Maybe you could try running bt in the debug console when your app crashes to get a trace.
answered on Stack Overflow Oct 20, 2012 by DrummerB • edited May 23, 2017 by Community
1

Python IDLE crash only on second monitor. Tcl/Tk compatibility issue?

python
macos
tkinter
python-idle

I found a simple fix.

In IDLE:

Options Menu > Configure Extensions > CallTips > set to FALSE

Then restart IDLE.

Took much research to find that super simple solution... the problem is caused not by an error in IDLE but by an error in the mac's Tcl/Tk code specifically when calltips are called in external monitors above the default monitor.

answered on Stack Overflow Nov 17, 2017 by Maxim Lott
1

LLDB print out NSException name or class from library

ios
xcode
debugging
lldb

Select the stack frame for objc_exception_throw and then enter this command:

(lldb) po *(id *)($esp + 4) // reason
(lldb) po *(id *)($esp + 12) // name
answered on Stack Overflow May 29, 2014 by Ken Kuan
0

iOS app developed in Xcode 4.5 runs fine on iOS 6 but crashes on iOS 5

ios
xcode
ios5
ios6
xcode4.5

I ran into a similar problem building with Xcode 4.5 - it cleared up with xCode 4.5.1

Hope this helps.

answered on Stack Overflow Nov 2, 2012 by jbbenni
0

iOS Simulator Stalls

xcode
macos
ios-simulator

Removing folder

Developer-3.2.6

has solved the problem.

Thanks Ned Deily for your answer

answered on Stack Overflow Sep 10, 2012 by Carl Thomas

Comments

Leave a comment

(plain text only)

Sources

  1. winerror.h from Windows SDK 10.0.14393.0
  2. https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0