BSoD List
Last Updated on Thursday, 25 March 2010 06:35 Written by admin Tuesday, 2 March 2010 10:06
A short list listing some of the more common BSoDs
STOP 0×0000001E KMODE_EXCEPTION_NOT_HANDLED
Causes
A “STOP 0×0000001E KMODE_EXCEPTION_NOT_HANDLED” error message indicates that an error condition was detected by the kernel and Windows was unable to continue running because of this error condition. The types of problems that can cause a “STOP 0×0000001E KMODE_EXCEPTION_NOT_HANDLED” error message are very similar to the problems that cause a “STOP 0×0000000A” error message, such as bad pointers, invalid addresses and other types of access violations. The STOP 0×0000001E bug check identifies an error that occurred in a section of code where no error handling routines exist.
.
Solution :
Try to replace the driver that is identified in the STOP error message, either with a known good copy from your installation media, or with an updated version from the manufacturer.
Disable the driver that is identified in the STOP error message or any newly installed drivers.
Verify that any new hardware or software is properly installed. Disconnect the new hardware or replace it to see if this resolves the issue.
If you have a video driver that was not supplied with the operating system, try switching to the standard VGA driver or a driver that is compatible with the operating system.
Run any system diagnostics that are supplied by your computer manufacturer, especially a RAM check. If this is a new installation of the hardware or software, contact the manufacturer for any requires updates for drivers or firmware.
Disable all filter drivers, such as remote control software, antivirus programs, backup programs, and so on.
__________________
Stop: 0×0000000A IRQL_NOT_LESS_OR_EQUAL
Causes
This error occurs when a driver uses an incorrect memory address. Other possible causes of this error are an incompatible device driver, a general hardware problem, and incompatible software.
Solution
Look for other hardware issues. Remove any newly installed Hardware. Remove all adapters and disconnect all hardware devices that are not required to start the computer.
Perform a Driver Rollback if incase a driver has been updated for a particular component.
Examine third-party software or drivers.
Use the Last Known Good configuration.
Use the Windows XP System Restore feature is system boots into SAFE MODE.
Repair the Windows XP installation.
__________________
Stop 0×00000218 UNKNOWN_HARD_ERROR
Cause
A Stop 0xc0000218 error message means that a necessary registry hive file could not be loaded. This error message can occur if the file is corrupt or missing.
Solution
Start your computer by running the Recovery Console, run the chkdsk /p command on the drive, and then restart your computer. Test to determine whether the issue is resolved.
Use the Last Known Good configuration.
Reinstall Windows in a separate folder.
__________________
Stop 0×0000021A or STATUS_SYSTEM_PROCESS_TERMINATED
Cause
The Stop 0xC000021A message occurs when Windows XP switches into kernel mode and a user-mode subsystem, such as
Winlogon or the Client Server Runtime Subsystem (CSRSS), is compromised and security can no longer be guaranteed. Because
Windows XP cannot run without Winlogon or CSRSS, this is one of the few situations where the failure of a user-mode service
can cause the system to stop responding
Solution
* Perform a Driver Rollback in case the customer has updated the driver for a specific component.
* Perform a System Restore from Safe Mode with command prompt
* Reinstall the Operating System.
__________________
Stop 0×00000221 or STATUS_IMAGE_CHECKSUM_MISMATCH
Cause
This Stop message indicates driver, system file, or disk corruption problems (such as a damaged paging file).
This message usually means that a driver or a .dll file has become corrupt
Solution
* Perform a Driver Rollback if incase a driver has been updated for a particular component.
* Run any system diagnostics that are supplied by your computer manufacturer, especially a RAM check.
* Perform a System Restore from Safe Mode with command prompt.
* If all Hardware fully functional reinstall Operating System.
__________________
Stop 0×00000024 or NTFS_FILE_SYSTEM
Cause
A problem occurred within NTFS.SYS, the driver file that allows the system to read and write to NTFS file system drives. There may be a physical problem with the disk, or an Interrupt Request Packet (IRP) may be corrupted.
Solution
Run chkdsk /r or chkdsk /f to detect and resolve any file system structural damage.
After you use the Chkdsk tool to repair the corrupted NTFS volume, rename %SystemRoot%\System32\Drivers\Ntfs.old to Ntfs.sys, and then shut down and restart the computer.
Try disabling any virus scanning programs, backup programs, or disk defragmenter tools that constantly monitor your computer.
Run any system diagnostics that are supplied by your computer manufacturer, especially a HDD check.
__________________
Stop 0×0000002E or DATA_BUS_ERROR
Cause
This indicates a system memory parity error, typically caused by failed or defective RAM (including motherboard, Level 2 cache, or video memory), incompatible or mismatched memory hardware, or when a device driver attempts to access an address in the 0×8xxxxxxx range that does not exist (does not map to a physical address). It also can indicate hard disk damage caused by viruses or other problems.
Solution
Look for other hardware issues. Remove any newly installed Hardware.
Run any system diagnostics that are supplied by your computer manufacturer, especially a RAM and HDD check.
Perform a Driver Rollback if incase a driver has been updated for a particular component.
__________________
Stop 0×00000050 or PAGE_FAULT_IN_NONPAGED_AREA
Cause
The Stop 0×50 message indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0×50 messages.
Solution
Look for other hardware issues. Remove any newly installed Hardware.
Run any system diagnostics that are supplied by your computer manufacturer, especially a RAM check.
Perform a Driver Rollback if incase a driver has been updated for a particular component.
__________________
Stop 0×00000077 or KERNEL_STACK_INPAGE_ERROR
Cause
A page of kernel data requested from the pagefile could not be found or read into memory. This message also can indicate disk hardware failure, disk data corruption, or possible virus infection.
Solution
Run any system diagnostics that are supplied by your computer manufacturer.
Run chkdsk /r or chkdsk /f to detect and resolve any file system structural damage.
Use the Windows XP System Restore feature is system boots into SAFE MODE.
Run a current virus-checking program.
If all Hardware fully functional reinstall Operating System.
__________________
Stop 0×0000007A or KERNEL_DATA_INPAGE_ERROR
Cause
A page of kernel data was not found in the pagefile and could not be read into memory. This might be due to incompatible disk or controller drivers, firmware, or hardware.
Solution
Stop 0×7A can be caused by bad sectors in the virtual memory paging file, disk controller error, virus infection, or memory hardware problems.
Run chkdsk /r or chkdsk /f to detect and resolve any file system structural damage.
Run any system diagnostics that are supplied by your computer manufacturer, especially a HDD check.
If all Hardware fully functional reinstall Operating System.
__________________
Stop 0×0000007B or INACCESSIBLE_BOOT_DEVICE
Cause
The Stop 0×7B message indicates that Windows XP Professional has lost access to the system partition or boot volume during the startup process.
Solution
Run any system diagnostics that are supplied by your computer manufacturer, especially a HDD check.
Rebuild the Boot.ini file.
Run chkdsk /r or chkdsk /f to detect and resolve any file system structural damage.
If all Hardware fully functional reinstall Operating System.
__________________
Stop 0×0000007F or UNEXPECTED_KERNEL_MODE_TRAP
Cause
One of three types of problems occurred in kernel-mode: (1) Hardware failures. (2) Software problems. (3) A bound trap (i.e., a condition that the kernel is not allowed to have or intercept). Hardware failures are the most common cause.
Solution
Run any system diagnostics that are supplied by your computer manufacturer, especially a RAM check.
Running the CPU beyond the rated specification, known as “overclocking,” can cause Stop 0×7F or other error messages due to heat buildup. When diagnosing problems on overclocked systems, first restore all clock and bus speed settings to the manufacturer recommended values to determine if this resolves the issues.
Use the Windows XP System Restore feature is system boots into SAFE MODE.
If all Hardware fully functional reinstall Operating System.
__________________
Stop 0×000000C2 or BAD_POOL_CALLER
Cause
The Stop 0xC2 message indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations.
• Faulty Driver or Software.
• Failing or Defective hardware.
Solution
• Perform a Driver Rollback in case the customer has updated the driver for a specific component.
• Perform a System Restore from Safe Mode with command prompt.
• Remove the modem and Repair the OS.
__________________
Stop 0×000000ED or UNMOUNTABLE_BOOT_VOLUME
Cause
The kernel mode I/O subsystem attempted to mount the boot volume and it failed.
File system structural corruption.
Upgrade to Windows XP Professional on systems that use higher throughput ATA disks or controllers with incorrect cabling.
Higher transfer rates when using the incorrect cable type.
Solution
• Run any system diagnostics that are supplied by your computer manufacturer, especially a HDD check.
• Run the CHKDSK /r to repair the File System.
• If the Hardware is fully functional reinstall the Operating System.
__________________
Stop 0×000000F4 KERNEL_DATA_INPAGE_ERROR
Cause
This problem occurs on a computer in which Windows XP or a later operating system is installed on a hard disk that is configured as a subordinate and no other device is connected to the same IDE controller channel (primary or secondary).
Solution
To resolve this behavior, use one of the following methods:
For Parallel Advanced Technology Attachment (PATA) hard disks, configure your disk drive as master only. For Serial Advanced Technology Attachment (SATA) hard disks, connect the hard disk cable to a master channel SATA connector on the motherboard.
Connect another device as a master, such as another disk drive or a CD drive or DVD drive.
Change your PATA and SATA IDE cable even if the cable does not appear worn.
Install Windows on a new hard disk because it is possible that your hard disk or your Windows installation may be corrupted.
I’m having a BSoD, which is not in this database, and it’s very annoying
0×0000007E
ati3duag.dll error
Can somebody explain what could be the problem, because I haven’t found a solution on web (and there are a lot of persons whit the same problem)
Can you give a little more info?
What OS (operating system)?
What kind of computer?
What are you doing when it bsods, playing a game, surfing the web?
sounds like a problem with your video card.
If your able to boot into Windows you can try these:
Run a virus and spyware scan.
Make sure your drivers for your card are up to date.
Do a windows update, there could be a fix for it if its a Windows problems.
If your unable to boot into normal mode, try safe mode.
Info on safe mode can be found here.
http://bsods.com/downloads-and-tools/safe-mode/
MB: ASUS P5E
CPU: Core 2 Duo 3133 MHz
PSU: Enermax Liberty 620w
GPU: ATI HD 4850
Mem: 2×1Ghz Corsair 1066
I tried different OS (Win 7, Win XP SP3). BSoD happens when playing games. On Win 7, it simply crashes on desktop, without giving any blue screen (but it still crashes regularily every 5-10 min in game). On Win XP SP3, I play usually more than 10 min (sometimes even 1 hour), but it stll crashes (BSoD). In the last month I formated comp 4-5 times, and I’m a little bit annoying with doing these things. I found on some forums that there is a remedy for this BSoD, but only on Win XP SP2 (there are 2 critical updates for, what they call, “Squeal of Death”). Now, I cann’t beleive that in SP3 these updates weren’t included, but I remained without any other solution. The last thing to do, before I take my PC in assistence, would be to install Win XP SP2 and try to install these updates.
By the way, I tried various benchmarks for RAM and graphic card (MemTest, SuperPi, FurMark), and no errors found. My graphic card is running without problems in benchmark for hours (not going over 71 degrees on max). And no component is overclocked. And this is a strange thing, because in game it crashes, giving me this driver problem (ati3duag.dll) with a specific sound that repeats in background (thats why they call it Squeal of Death)
Even I tried latest drivers downloaded directly from Sapphire (and not ATI), but there is allways the same problem. On next format I’ll try not to install Avira antivirus or any other antivirus, to see if this is making some conflicts (even this is said to be a possible problem)
XP Pro, SP3, fully patched on a desktop machine running basic office type applications, nothing unusual or strange about the configuration.
Been having an annoying BSOD 50 for several months when running a routine scan with avg, and a search in Regedit often pulled the same error. The machine had to be looked at in depth the other day for a UDB problem, so the BSOD was also investigated. It took a while to find the problem, but in the end, it turned out to be a corrupt record in the registry that was causing it, and it was 100% repeatable.
The specifics were that it was eventually tracked down to being a corrupt (unreadable) record in current user, microsoft/explorer/MRU. It’s slightly worrying that a corrupt record in a registry file can pull a stop crash in Xp after this length of time, at this stage, having spent hours looking for it, I am just glad it’s been tracked down, I had to do sequential step back through the registry doing finds, as none of the registry cleaners I tried, and I tried a lot, were finding this problem!! The real lesson for me is that the apparent link was meaningless, in that the suggested area of error had no real relation to the real problem.