computer blue screen of death, troubleshoot, fix computer could not boot probems tip, secrets, guide, solution
Home About Us Reference Product Service Sitemap

Computer Boot Problems Fix: Blue Screen Of Death Code

In this article, we list the common causes and fixes for the Blue Screen.

Attempted Write To Readonly Memory (stop code 0X000000BE)

This error is often out of a faulty driver or service, as is outdated firmware. If the name of a file or service is specified, try uninstalling the software or you can roll back the driver if it has been upgraded.

Bad Pool Caller (stop code 0X000000C2)

The causes and fixes are similar to "Attempted Write To Readonly Memory". Additionally, this error might come from a defective hardware device. If you encounter this message while upgrading to Windows Vista or Windows 7, it may mean that one or more devices in your system are not compatible with these operating systems. What you need to do is to find updated drivers and firmware.

Data Bus Error (stop code 0X0000002E)

The defective memory may be the cause of this problem, which include system RAM, the Level 2 cache, or even the memory on your video card. Other causes of this error may include the hard disk corruption, buggy hardware drivers, or physical damage of the motherboard.

Driver IRQL Not Less Or Equal (stop code 0X000000D1)

The error often is often caused by Drivers programmed to access improper hardware addresses. The fixes are similar to "Attempted Write To Readonly Memory (stop code 0X000000BE)".

Driver Power State Failure (stop code 0X0000009F)

This error often comes from an incompatibility between your computer's power management and one or more installed drivers or services, usually when the computer enters the Hibernate state. With the name of a file or service shown, you can try to uninstall the software or roll back the driver if you upgrade it. You can also try to disable Windows support for power management.

Driver Unloaded Without Cancelling Pending Operations (stop code 0X000000CE)

Find causes and fixes from "Attempted Write To Readonly Memory (stop code 0X000000BE)" described in the above.

Driver Used Excessive PTEs (stop code 0X000000D8)

Find causes and fixes from "No More System PTEs (stop code 0X0000003F)" in the following.

Hardware Interrupt Storm (stop code 0X000000F2)

This error happens when a hardware device, such as a USB or SCSI controller, fails to release an IRQ, a condition typically caused by a buggy driver or firmware. This error can also be caused by incorrectly assigned the same IRQ of two devices.

Inaccessible Boot Device (stop code 0X0000007B)

This error may be seen during Windows startup if Windows cannot read data from the system or boot partitions. Faulty disk controller drivers are often the case, but this problem can also be out of hard disk errors, or even a corrupted boot.ini file. If everything is ok with your drivers and your drive, and boot.ini file is configured properly, you need to check your system BIOS settings.

If you have this error while converting xp to Windows Vista or Windows 7, it may mean that one or more devices in your system are not compatible with these OS. Try disconnecting unnecessary devices and find updated drivers and firmware.

Kernel Data Inpage Error (stop code 0X0000007A)

This error is often caused by virtual memory, most often in the case that Windows wasn't able to read data from - or write data to - the swap file. Possible causes include bad sectors, a virus, improper SCSI termination, bad memory, or physical damage to the motherboard.

Kernel Stack Inpage Error (stop code 0X00000077)

The causes and fixes are similar to the above, "Kernel Data Inpage Error (stop code 0X0000007A)".

Kmode Exception Not Handled (stop code 0X0000001E)

A faulty driver or service like memory and IRQ conflicts, and faulty firmware, is the cause for this error. With the name of a file or service shown, you can try to uninstall the software or roll back the driver if you upgraded it.

If the Win32k.sys file is mentioned in the message, the cause may be third-party remote control software. This error can also be caused by running out of disk space while installing an application or if you run out of memory while using a buggy application with a memory leak.

Mismatched Hal (stop code 0X00000079)

This error happens if the currently installed Hardware Abstraction Layer (HAL) must match the type of computer on which Windows Vista or Windows 7 is installed. For example, if you use a HAL intended for a dual-processor system on a single-processor motherboard, Windows may not start. The best way to fix these problems with the HAL is to reinstall Windows Vista or Windows 7. This error can also be out of out-of-date Ntoskrnl.exe or Hal.dll files.

No More System PTEs (stop code 0X0000003F)

Page Table Entries (PTEs) are used to map RAM as it is divided into page frames by the Virtual Memory Manager (VMM). This error usually means that Windows has run out of PTEs. Aside from the usual assortment of faulty drivers and services that can cause all sorts of problems, this error can also occur if you're using multiple monitors. If you find that you're experiencing this error often, you can increase Windows allocation of PTEs with this procedure:

1. Start --> Run

2. Type regedit

3. Then expand the branches to HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Control\Session Manager\Memory Management.
4. Double-click the PagedPoolSize value, enter 0 for its value data, and click OK.
5. Next, double-click the SystemPages value. If you're using multiple monitors, enter a value of 36000 here. Otherwise, enter 40000 if you have 128 MB of system RAM or less, or 110000 if you have more than 128 MB of RAM.
6. Click OK and then close the Registry Editor.

Note: The change may take effect after restarting Windows.

NTFS File System (stop code 0X00000024)

This error is caused by a problem from ntfs.sys, the driver responsible for reading and writing NTFS volumes. you may see this error If you're using the FAT32 file system,

code 0X00000023).

The causes for this error are a faulty IDE or SCSI controller, improper SCSI termination, an overly aggressive virus scanner, or errors on the disk.

To check out further, open the Event Viewer (eventvwr.msc), and look for error messages related to SCSI or FASTFAT (in the System category), or Autochk (in the Application category).

Page Fault In Nonpaged Area (stop code 0X00000050)

Find out causes and fixes from "Attempted Write To Readonly Memory (stop code 0X000000BE)" described in this article.

Status Image Checksum Mismatch (stop code 0Xc0000221)

Possible causes for this error include a damaged swap file, or a corrupted driver. For additional causes and fixes, please check out "Attempted Write To Readonly Memory (stop code 0X000000BE)" described in this article.

Status System Process Terminated (stop code 0Xc000021A)

This error indicates that there is a problem with either Winlogon.exe or the Client Server Runtime Subsystem (CSRSS). It can also be caused if a user with administrator privileges has modified the permissions of certain system files such that Windows cannot read them. To fix the problem, you need have to install a second copy of Windows Vista or Windows 7, and then repair the file permissions from there.

Thread Stuck In Device Driver (stop code 0X000000EA)

The error is often called "infinite loop" and has lots of causes. What's actually happening is that your video driver has entered an infinite loop because of your video adapter locked up. For fixing this problem, please try the following:

1. Try upgrading your computer's power supply. All your computer's components need sufficient wattage or it may result in a "brown out" of sorts in your system.
2. You need to have the latest driver for your sound card installed. If you already have the latest driver, you can try to roll back to an older driver.
3. You need to have the latest driver for your sound card installed. Also, make sure your sound card is not in a slot immediately adjacent to your video card, lest the resulting interference or heat disrupt the operation of either card.
4. Make sure your video card is properly seated in its AGP or PCI slot. If it's a PCI card, try moving it to a different slot. 5. Check out if your video card and motherboard are physically damaged.
6. Try messing with some of your system's BIOS settings, especially those concerning your AGP slot or video subsystem. For example, if your AGP slot is set to 2x mode, and your video adapter only supports 1x AGP mode, then you'll want to change the setting accordingly.
7. Make sure that the video card of your computer is adequately cooled because overheating can cause your video card's chipset to lock up.
8. Check with the manufacturer of your motherboard for newer drivers for your motherboard chipset.
9. Replacing your system's driver for the Processor-to-AGP Controller. Open Device Manager (devmgmt.msc), expand the System devices branch, and double-click the entry corresponding to your Processor-to-AGP Controller. Select the Driver tab, and click Update Driver to select a new driver.
Unless you can get a newer driver from the manufacturer of your motherboard chipset, try installing the generic "PCI standard PCI-to-PCI bridge" driver shown in the Hardware Update Wizard.
10. If your motherboard has an on-board Ethernet adapter, try disabling the PXE Resume/Remote Wake Up option in your system BIOS.
11. If you're using a dual-processor motherboard, Windows Vista is probably loading a HAL (Hardware Abstraction Layer) for an MPS (Multiple Processor System). Such HALs support the I/O APIC (Advanced Programmable Interrupt Controller), a method of accommodating more than 15 IRQs in a single system. Unfortunately, APIC can cause problems with AGP-based video cards. Also try to change your HAL to "Standard PC".
Unexpected Kernel Mode Trap (stop code 0X0000007F)

The causes of this error are defective memory, physical damage to the motherboard, and excessive processor heat due to overclocking, running the CPU faster than its specified clock speed.

Unmountable Boot Volume (stop code 0X000000ED)

This error indicates that Windows was unable to mount the boot volume, which, if you have more than one drive, is the drive containing Windows. This is usually out of using the wrong cable with a high-throughput IDE controller (more than 33 MB/second); try an 80-pin cable instead of the standard 40-pin cable. Check out "Inaccessible Boot Device (stop code 0X0000007B)" in the above.

©1994 - 2010 Edusoftmax Inc. All rights reserved. Questions? Comments?    Visitors: