spacer spacer spacer
  arrow Description
  arrow Key Facts
  arrow Solutions
  arrow Forum Help
  arrow Technical Details
  arrow Vendor Summary
  arrow Research this Issue
  help Solutions Help
Exception Solutions

Alignment fault exception

Fatal exception 0x80000002


A data type misalignment was detected in a load or store instruction.

The processor requires that some instructions use data that is aligned on a specific boundary. For example, when writing a double-word (4 bytes) the processor can require that the first address used has its last two bits set to zero (i.e. aligned on a double-word boundary). This requirement is done for performance reasons.

This exception means that the program did not follow this rule or some kind of data corruption occurred in the program itself.  Most compilers used for Windows development should handle the alignment automatically, but a programmer could have overridden these rules.  

  Key Facts  
Raw Title


occurance meter

  Microsoft Corporation*

* Reporting vendor, unclear who is responsible for the issue.
  Solutions and Fixes  
  Date Votes ratings
Update or Replace Defective Software
    Add    Flag
solution icon

Most exception errors are the result of a software bug. If the faulting program is identified, check if a newer version is available that corrects the issue.

Be aware that in some cases the fault might lie elsewhere, such as an operating system file, driver or other defective software that is running.

solves it indicator
risk indicator
effort indicator
  FaultWire Staff
Posted: 8-Jan-2009
Check Memory
    Add    Flag
solution icon

You may have a defective memory. This is even more likely if it only occurs when the system is cold or hot, but not all the time. Use a memory tester to confirm if it is defective or if you have spare memory, try replacement.

Windows 7 and Vista include a Memory Test program when booting from the Windows Installation DVD. Step-by-step instructions with screen shots are available at Using System Restore on 7/Vista/2008 as part of System Recovery.

Several software products that also provide memory and video diagnostics includes Fix-It Utilities Professional and SystemSuite Professional. Other diagnostic products include Eurosoft's PC Check and Iolo's System Mechanic.

Additional Memory Solutions:

  • Confirm all the memory is of the same type and speed. Many motherboards only work correctly when the memory is installed with matched sets and matched speeds.
  • If you added or changed your memory just before this problem occurred, try reverting to the prior memory configuration to confirm it's the source of the problem.
  • Check that the memory is fully seated in the sockets. Memory sockets often have side latches that need to be upright to indicate the memory is correctly locked in place.
  • Confirm the memory resides in the correct slots on the motherboard. You'll need to refer to the motherboard manual to confirm this. There is little consistency, even within a single vendor. Some systems require that memory is installed as matched pairs, but not always adjacent to each other!
  • It's also possible the memory problem is on the video card, as they often contain additional memory. The video card should be tested and/or try a different video card to see if the problem goes away.
solves it indicator
risk indicator
effort indicator
  FaultWire Staff
Posted: 5-Oct-2008
  Forum Help  
Forums on topic

Check out what others say about this issue and review or add your own comments and solutions!

Go to Forums on topic.
  List Specific Reports  
Reported Exceptions

You may find more information for this issue in our specific exception reports.

View exception reports for 0x80000002.
  Technical Details  
  technical details

This error is initiated by the processor as an Alignment Check, interrupt 17.  This interrupt can only occur in user mode, and never in the kernel running at privilege level 0.

  Vendor Summary  
  Microsoft Corporation (more info...)

Microsoft Corporation Logo



  Research this Issue  
Getting search results...
  Although less informative than our notes here, you can view the Microsoft MSDN source document for a list of the NTSTATUS codes used when Microsoft encounter a problem with an application.  
  While we believe this information up to date and accurate, FAQware is not responsible for any inaccuracies. If you find something that is out of date or inaccurate, please let us know at so we can correct it.