WIN32 Exception/ Access Violation Errors
Win32 Exception/Access Violation Errors
Back to "How To Interpret Fatal Error Messages"
Exception Code Label Description
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.
A breakpoint was encountered.
A trace trap or other single-instruction mechanism signaled that one instruction has been executed.
The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
The thread tried to access a page that was not present, and the system was unable to load the page. For example, this exception might occur if a network connection is lost while running a program over the network.
The thread tried to execute an invalid instruction.
The thread tried to continue execution after a noncontinuable exception occurred.
An exception handler returned an invalid disposition to the exception dispatcher. Programmers using a highlevel language such as C should never encounter this exception.
The thread tried to access an array element that is out of bounds and the underlying hardware supports bounds checking.
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.
The thread tried to divide a floating-point value by a floating-point divisor of zero.
The result of a floating-point operation cannot be represented exactly as a decimal fraction.
This exception represents any floatingpoint exception not included in this list.
The exponent of a floating-point operation is greater than the magnitude allowed by the corresponding type.
The stack overflowed or underflowed as the result of a floating-point operation.
The exponent of a floating-point operation is less than the magnitude allowed by the corresponding type.
The thread tried to divide an integer value by an integer divisor of zero.
The result of an integer operation caused a carry out of the most significant bit of the result.
The thread tried to execute an instruction whose operation is not allowed in the current machine mode.
The thread used up its stack.
Web Page Designed By