please dont rip this site Prev Next

EXCEPTION_RECORD info  Overview  Group

The EXCEPTION_RECORD structure describes an exception.

typedef struct _EXCEPTION_RECORD { // exr 

    DWORD ExceptionCode; 

    DWORD ExceptionFlags; 

    struct _EXCEPTION_RECORD *ExceptionRecord; 

    PVOID ExceptionAddress; 

    DWORD NumberParameters; 





Specifies the reason the exception occurred. This is the code generated by a hardware exception, or the code specified in the RaiseException function for a software-generated exception. Following are the exception codes likely to occur due to common programming errors:




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 an array element that is out of bounds and the underlying hardware supports bounds checking.


A breakpoint was encountered.


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.


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 floating-point 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 execute an invalid instruction.


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 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.


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.


The thread tried to continue execution after a noncontinuable exception occurred.


The thread tried to execute an instruction whose operation is not allowed in the current machine mode.


A trace trap or other single-instruction mechanism signaled that one instruction has been executed.


The thread used up its stack.

Another exception code is likely to occur when debugging console processes. It does not arise because of a programming error. The DBG_CONTROL_C exception code occurs when Ctrl+C is input to a console process that handles Ctrl+C signals and is being debugged. This exception code is not meant to be handled by applications. It is raised only for the benefit of the debugger, and is raised only when a debugger is attached to the console process.

Specifies the exception flags. This member can be either zero, indicating a continuable exception, or EXCEPTION_NONCONTINUABLE indicating a noncontinuable exception. Any attempt to continue execution after a noncontinuable exception causes the EXCEPTION_NONCONTINUABLE_EXCEPTION exception.
Points to an associated EXCEPTION_RECORD structure. Exception records can be chained together to provide additional information when nested exceptions occur.
Specifies the address where the exception occurred.
Specifies the number of parameters associated with the exception. This is the number of defined elements in the ExceptionInformation array.
Specifies an array of additional 32-bit arguments that describe the exception. The RaiseException function can specify this array of arguments. For most exception codes, the array elements are undefined. For the following exception code, the array elements are defined as follows:

Exception code

Array contents


The first element of the array contains a read-write flag that indicates the type of operation that caused the access violation. If this value is zero, the thread attempted to read the inaccessible data. If this value is 1, the thread attempted to write to an inaccessible address.

The second array element specifies the virtual address of the inaccessible data.

See Also

EXCEPTION_DEBUG_INFO, EXCEPTION_POINTERS, GetExceptionInformation, RaiseException, UnhandledExceptionFilter 

See also:

file: /Techref/os/win/api/win32/struc/src/str07_12.htm, 12KB, , updated: 2000/4/7 12:20, local time: 2022/5/23 01:03,

 ©2022 These pages are served without commercial sponsorship. (No popup ads, etc...).Bandwidth abuse increases hosting cost forcing sponsorship or shutdown. This server aggressively defends against automated copying for any reason including offline viewing, duplication, etc... Please respect this requirement and DO NOT RIP THIS SITE. Questions?
Please DO link to this page! Digg it! / MAKE!


After you find an appropriate page, you are invited to your to this massmind site! (posts will be visible only to you before review) Just type a nice message (short messages are blocked as spam) in the box and press the Post button. (HTML welcomed, but not the <A tag: Instead, use the link box to link to another page. A tutorial is available Members can login to post directly, become page editors, and be credited for their posts.

Link? Put it here: 
if you want a response, please enter your email address: 
Attn spammers: All posts are reviewed before being made visible to anyone other than the poster.
Did you find what you needed?

  PICList 2022 contributors:
o List host: MIT, Site host, Top posters @20220523
* Page Editors: James Newton, David Cary, and YOU!
* Roman Black of Black Robotics donates from sales of Linistep stepper controller kits.
* Ashley Roll of Digital Nemesis donates from sales of RCL-1 RS232 to TTL converters.
* Monthly Subscribers: Gregg Rew. on-going support is MOST appreciated!
* Contributors: Richard Seriani, Sr.

Welcome to!