|
Hex
|
Exception
Type
|
Exception
|
Description
|
More
Information
|
|
00000000
|
|
EXCEPTION_WAIT_0
|
*1
|
|
|
0000007E
|
ERROR:
STOP
|
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
|
After you
upgrade your computer to Windows XP (or re-install XP), you may
receive the following STOP error message on a blue
screen:
STOP: 0x0000007E (0xC0000005, 0x804E518E, 0xFC938104,
0xFC937E04)
Note: The four parameters in this error message may vary depending
on the cause of the STOP error.
|
http://support.microsoft.com/?kbid=330182
|
|
00000080
|
|
EXCEPTION_ABANDONED_WAIT_0
|
*1
|
http://support.microsoft.com/?kbid=292945
|
|
000000C0
|
|
EXCEPTION_USER_APC
|
*1
|
|
|
00000103
|
|
EXCEPTION_PENDING
|
*1
|
|
|
00000102
|
|
EXCEPTION_TIMEOUT
|
*1
|
|
|
40000005
|
|
EXCEPTION_SEGMENT_NOTIFICATION
|
*1
|
|
|
80000001
|
WARNING
|
EXCEPTION_GUARD_PAGE_VIOLATION
|
Memory
Allocated as PAGE_GUARD by VirtualAlloc() has been accessed.
|
http://msdn.microsoft.com/library/en-us/memory/base/creating_guard_pages.asp
|
|
80000002
|
WARNING
|
EXCEPTION_DATATYPE_MISALIGNMENT
|
The thread
tried to read or write data that is misaligned on hardware that
does not provide alignment. For example, 16-bit values must be
aligned on 2-byte boundaries; 32-bit values on 4-byte boundaries,
and so on.
SetErrorMode() may be used to modify the
system's behaviour and auto-correct such misalignment, albeit at
significantly impaired performance.
Not found on x86 boxes, but may appear on Merced or on CE
units.
|
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/prmd_stp_oweb.asp
|
|
80000003
|
WARNING
|
EXCEPTION_BREAKPOINT
|
A breakpoint
was encountered. You can actually skip to the next instruction now
if you're devious with Exception filters. The OS jumps to a
breakpoint when HeapFree() shows guard
byte corruption or other trouble.
|
http://support.microsoft.com/support/kb/articles/Q230/1/76.asp
|
|
80000004
|
WARNING
|
EXCEPTION_SINGLE_STEP
|
A trace trap
or other single-instruction mechanism signalled that one
instruction has been executed.
The CPU has signalled that one instruction has been executed. Only
of interest to debuggers
|
Microsoft Knowledge Base Article 236155 - MSMQMessage.Body (Get_Body) Operation Fails
|
|
C0000005
|
ERROR
|
EXCEPTION_ACCESS_VIOLATION
|
An attempted
read or write to/from an address to
which that process isn't allowed access. [Or from HeapAlloc() with
invalid parameters/corrupt heap] The thread tried to read from or
write to a virtual address for which it does not have the
appropriate access. Usually this indicates a pointer error of some
sort. This error is an access violation, which means some piece of
software tried to access something (could be hardware, software,
memory address or a file) that for some reason it was not entitled
to do. The offending software did not adequately handle the
exception so the operating system took over and terminated it with
the 0xc0000005 error.
|
http://support.microsoft.com/support/kb/articles/Q240/0/23.ASP
|
|
C0000006
|
ERROR
|
EXCEPTION_IN_PAGE_ERROR
|
The thread
tried to access a page that was not present, and the system was
unable to load the page. –i.e. the program or memory mapped file
couldn't be paged in because it isn't accessible any more. Device
drivers can return this exception if something went wrong with the
read (i.e. hardware problems). For example, this exception might
occur if a network connection is lost while running a program over
the network.
|
http://support.microsoft.com/default.aspx?kbid=327020
|
|
C0000008
|
ERROR
|
EXCEPTION_INVALID_HANDLE
|
The API call
was passed a handle to a kernel object which was invalid -usually
because that handle has already been closed. Use the repair
procedures for XP by booting to the XP O/S disk. Go through until
you get to the repair choice. (hit R).
Try repairing the OS first. If this does not work or you are not
comfortable using recovery console, the only other choice is to
re-install the OS. The way to correct this is by reinstalling
Windows XP. You can do a repair option and all your data and
setting will remain intact. You can find instructions on doing a
repair install here
|
http://www.geekstogo.com/forum/index.php?act=ST&f=5&t=138
|
|
C0000017
|
ERROR
|
EXCEPTION_NO_MEMORY
|
Called by
HeapAlloc() if you specify
HEAP_GENERATE_EXCEPTIONS and there is no memory or heap
corruption..
|
http://support.microsoft.com/?kbid=315351
|
|
C000001D
|
|
EXCEPTION_ILLEGAL_INSTRUCTION
|
The thread
tried to execute an invalid instruction -such as MMX opcodes on a
non MMX system. Branching to an invalid location can cause this
-something stack corruption often causes.
|
|
|
C0000025
|
|
EXCEPTION_NONCONTINUABLE_EXCEPTION
|
The exception
filter returned EXCEPTION_CONTINUE_EXCEPTION when the exception
raised isn't re-startable. The thread
tried to continue execution after a non-continuable exception
occurred.
|
|
|
C0000026
|
|
EXCEPTION_INVALID_DISPOSITION
|
An exception
handler returned an invalid disposition to the exception
dispatcher. Programmers using a high-level language such as C
should never encounter this exception.
Whatever number the exception filter returned, it wasn't a value
the OS knows about.
|
|
|
C000008C
|
|
EXCEPTION_ARRAY_BOUNDS_EXCEEDED
|
The thread
tried to access an array element that is out of bounds, and the
underlying hardware supports bounds checking. x86 family processors do not generate this
exception.
|
|
|
C000008D
|
|
EXCEPTION_FLOAT_DENORMAL_OPERAND
|
One of the
operands in a floating-point operation is denormal. A denormal
value is one that is too small to represent as a standard
floating-point value.
|
|
|
C000008E
|
|
EXCEPTION_FLOAT_DIVIDE_BY_ZERO
|
The thread
tried to divide a floating-point value by zero.
|
|
|
C000008F
|
|
EXCEPTION_FLOAT_INEXACT_RESULT
|
The accuracy
of the last floating point operation is worse than usual as it is
impossible to represent in the float accurately,
|
|
|
C0000090
|
|
EXCEPTION_FLOAT_INVALID_OPERATION
|
Any other
floating-point exception.
|
|
|
C0000091
|
|
EXCEPTION_FLOAT_OVERFLOW
|
The result was
too big to represent
|
|
|
C0000092
|
|
EXCEPTION_FLOAT_STACK_CHECK
|
A floating
point stack overflowed or underflow. This related to the baroque
design of the floating point unit.
|
|
|
C0000093
|
|
EXCEPTION_FLOAT_UNDERFLOW
|
The result was
too small to represent
|
|
|
C0000094
|
|
EXCEPTION_INTEGER_DIVIDE_BY_ZERO
|
Attempted
division by zero
|
|
|
C0000095
|
|
EXCEPTION_INTEGER_OVERFLOW
|
The last
integer operation caused an overflow
Seemingly not raised on an x86 unless an INTO (__asm into;) instruction
is placed in the source.
The result of an integer operation caused a carry out of the most
significant bit of the result.
|
|
|
C0000096
|
|
EXCEPTION_PRIVILEGED_INSTRUCTION
|
The
instruction is not allowed in the current ring (inport, outport
& control register manipulation usually). No fix, other than
'don't do that'
The thread attempted to execute an instruction whose operation is
not allowed in the current machine mode.
|
|
|
C00000FD
|
|
EXCEPTION_STACK_OVERFLOW
|
Stack
overflow. Can occur during errant recursion, or when a function
creates a particularly large array on the stack.
|
|
|
C0000135
|
|
|
The
application failed to initialise properly
|
1. Registry
corruption fixed ion Windows XCP service packs - http://support.microsoft.com/kb/318159
2. Can be
failure to install .Net for application that requires it.
|
|
C000013A
|
|
EXCEPTION_CONTROL_C_EXIT
|
Lets the
debugger know the user hit Ctrl-C. Seemingly for console apps
only.
|
|
|
C00002B4
|
|
EXCEPTION_FLOAT_MULTIPLE_FAULTS
|
*1
|
|
|
C00002B5
|
|
EXCEPTION_FLOAT_MULTIPLE_TRAPS
|
*1
|
|
|
C00002C0
|
|
EXCEPTION_ILLEGAL_VLM_REFERENCE
|
*1
|
|
|
C0000142
|
|
<DLL
Initialisation failure>
|
Raised when
DllMain() returns false (?)
|
|
|
E06D7363
|
|
<Visual C++
exception>
|
The SEH
exception used by the c++ try/catch/throw mechanism in Visual
C++
|
|
