Check to be sure you have adequate disk...

The system disk (typically C:) may be full. We recommend at least 1 GB of free disk space be left on the Windows system drive at all times. To get additional space:

• Remove deleted files (right-click on the trash-bin and select Empty recycle bin)
• Remove unneeded files, such as browser cached files.
• Move files to another drive or media
• Compress or Zip large files to take up less space
• Transfer the system to a new larger drive

Several software products that can help clean and remove unneeded files are Fix-It Utilities Professional and SystemSuite Professional. If you need to move or copy a partition or entire drive, you could use Partition Commander or similar product.

If you are unable successfully boot into Windows because of the fatal error, Windows has an option to reload registry information from the last successful boot. To revert to the last successful boot:

1. Reboot the computer.
2. Near the end of the BIOS messages or graphic, but well before anything appears from Windows, press the F8 key. You may only have a few seconds to get the right spot to press F8 before it attempts to go into Windows. If the BIOS complains about a pressed key or asks you to go into BIOS setup, you've pressed F8 too soon (Don't go into BIOS setup).
3. When successful, you should see a black screen with white text "Windows Advanced Options". Use the up or down arrow keys to highlight Last Known Good Configuration and press Enter.

Check if you are using the latest hardware drivers, especially the chipset and video drivers. Older drivers are a common contributor to BSoD issues.

You can use a product like Driver Genius or Radar Sync to verify you have the latest drivers and help keep all your drivers up-to-date. If you're comfortable with driver installations, you can individually find and install current drivers.

A some of the most popular driver download sites:

• CPU and Chipset Drivers: AMD, Intel, Via
• Video Drivers: ATI, Intel, Nvida
• Computer and other hardware manufacturers

Check with the PC manufacturer if you're using the latest BIOS or not. If not, update to the current version.

A few of the manufacture's download or support links for a motherboard/BIOS update:

If the BIOS is current, it's possible bad BIOS parameters are causing the problem, especially if the memory or CPU settings are overclocked. The BIOS parameters are stored in CMOS memory. The best way to reset the BIOS parameters is to remove the CMOS battery. To do this:

1. Unplug the PC, and open the case.
2. Locate the battery on the motherboard - typically a silver coin cell.
3. Remove the battery and note if the plus side is up or down, so you can reinstall it later the same way.
4. Wait at least 1 minute and reinstall the battery.
5. Attach power and power up. Typically a BIOS warning message will indicate CMOS was corrupted or changed and it may require you to go into the BIOS setup to set the time and date.
6. Proceed to boot Windows and see if this fixes the issue.

Some BIOSes have options to enable/disable caching and/or shadowing. If the options are available, disable caching and shadowing. Most newer (2005+) systems do not have these options. There are many BIOS makers and customized versions of the BIOS, so you may have to enter BIOS setup and look a bit to find these options. Typically you press a key like Esc, Del, F1, or F2 before Windows starts (almost right after you reboot) to enter BIOS setup. Consult your computer manual for details. The setup key can also be found in our BIOS access list.

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

The Windows error handler did not catch an exception by a kernel-mode program.

After the Stop code will be 4 hex values: {Parameter 1, Parameter 2, Parameter 3, Parameter 4}.

Parameter 1 is the The exception code that was not handled. Common codes include:

0x80000002	STATUS_DATATYPE_MISALIGNMENT - An unaligned data reference was encountered.
0x80000003	STATUS_BREAKPOINT - A breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.
0xC0000005	STATUS_ACCESS_VIOLATION - A memory access violation occurred. (Parameter 4 of the bug check is the address that the driver attempted to access.)

Parameter 2 is address where the exception occurred.

Parameter 3 is the first Parameter of the exception.

Parameter 4 is the second Parameter of the exception.