Some Code Blue Screen XP and Solutions

Attempted Write To Readonly Memory (stop code 0X000000BE)
Usually the problem is due to an error in the driver or service. If the file name and the service is specified, try uninstalling the software or driver (rolling back the driver). And browse to the driver in accordance with its Operating System.

Bad Pool Caller (stop code 0x000000C2)
The cause of this problem is similar to the problem of "Attempted Write To Readonly Memory," above. Additionally, this error can also be caused by faulty hardware / disability. If you encounter this message while upgrading to Windows, it may mean that the hardware is not compatible with Windows. Try disconnecting devices, or looking for a suitable driver for his Windwos.


Data Bus Error (stop code 0x0000002E)
This problem is usually caused because there is damage / defects in the hardware, usually a memory. In addition to defects in memory could also be due to damage to the motherboard, hard drive, replace the hardware ..

Driver IRQL Not Less Or Equal (stop code 0x000000D1)
Caused by drivers accessing the hardware address that is not appropriate. Can also be caused by problems such as the "Attempted Write To Readonly Memory," above. See a problem "Attempted Write To Readonly Memory" above.

 Driver Power State Failure (stop code 0X0000009F)
Caused not suitable / compatible between the "computer's power management" with the drivers or services that running. Commonly occurs when the computer do the "hibernation". If the file name and the service is specified, try uninstalling the software or driver (rolling back the driver). Or try to disable 'Windows' support for power management ".

Driver Unloaded Without canceling Pending Operations (stop code 0X000000CE)The cause of this problem is similar to the problem of "Attempted Write To Readonly Memory," above. See a problem "Attempted Write To Readonly Memory" above.
Driver Used Excessive PTEs (stop code 0X000000D)Look at the problem of "No More System PTEs," below.
Hardware Interrupt Storm (stop code 0X000000F2)Problems arise when a hardware (USB or SCSI controller) fails to "remove" an IRQ. Failure is usually caused by problems in the driver. Also this problem can also appear if two devices use the same IRQ.
Inaccessible Boot Device (stop code 0x0000007B)Usually this problem arises at Windows startup if Windows can not read data on the system boot partition. Can also be caused by hard disk errors, flawed boot.ini file (corrupted). If there is no problem on the disk drive, partition and boot.ini file (when the two Operating Systems installed) try to check the BIOS boot settings. If this problem munculketika're doing an upgrade of Windows, it may mean that the hardware is not compatible with Windows. Try disconnecting devices, or looking for a suitable driver for his Windwos.
Kernel Data Inpage Error (stop code 0X0000007A)Problems arise in virtual memory, usually because the windows can not read or write data to the swap file. Possible causes include bad sectors, viruses, defective memory, or even damage the motherboard.
Kernel Stack Inpage Error (stop code 0X00000077)The cause is similar to the problem of "Kernel Data Inpage Error," above.
Kmode Exception Not Handled (stop code 0x0000001E)Usually the problem is due to an error in the driver or service, konfilk IRQ. If the file name and the service is specified, try uninstalling the software or driver (rolling back the driver). This problem can also be caused due to lack of space on the disk during installation.
No More System PTEs (stop code 0X0000003F)The problem arises because Windows shortage of Page Table Entries (PTEs). PTEs are used to perform mapping RAM. Where the mapping is done by the Virtual Memory Manager (VMM). This problem can also arise when you use multiple monitors.If this error often, try to increase the allocation for PTEs in Windows in the following way: I· Open the Registry Editor.· See at: HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager \ Memory Management· Double-click on PagedPoolSize, enter its value 0, click OK.· Then double-click on SystemPages. If using multiple monitors, enter a value of 36000. Also enter a value of 40,000 if the RAM of 128MB or less. If the RAM 128MB or more enter a value of 110 000.• Once finished, click OK, close the Registry Editor and restart the computer. when you're done. Will the change take effect Pls you restart Windows.

NTFS File System (stop code 0x00000024)Error due to the problems reported by Ntfs.sys (driver which serves to read and write NTFS). If it still uses FAT 32 file system, an error message which arise will be similar (stop code 0X00000023). This problem can be overcome by replacing your hard drive.

Page Fault In Nonpaged Area (stop code 0x00000050)The cause of this problem is similar to the problem of "Attempted Write To Readonly Memory," above.

Status Image Checksum Mismatch (stop code 0xc0000221)Possible causes of this error is damage to the swap file, or corrupted drivers.
Solution 1: You can use Driver Rollback or System Restore from safe mode, to restore the previous driver. You can also use Windows XP Professional recovery features such as Last Known Good Configuration startup option, Backup, or Automated System Recovery to restore the previous working configuration. After the restore from backup media, you may need to reapply service packs or hotfixes, depending on when the backups performed.
Solution 2: If the Stop message names a specific file, try replacing it manually with a copy of Windows XP Professional operating system CD in safe mode or Recovery Console. For systems that use FAT16 or FAT32 file system, you have the option to use Windows 98 or Windows Millennium Edition Emergency Boot Disk to access the hard disk.If the original file from the operating system CD has a file name that ends with an underscore (_) character, you can not use a file to a compressed. Recovery Console's Copy command is ideal for copying compressed files because it detects and expands them. If you do not specify a destination file name, you must rename the expanded file with the correct extension before using it. From safe mode or Recovery Console, you can use the Expand command to uncompress and copy files to the destination location. In Recovery Console, the expanded file given the correct name after being copied to the destination location. For more information about Expand Copy or command, see Windows XP Help and Support Centre.
Status System Process terminated (stop code 0Xc000021A)Caused a problem with the Winlogon.exe or the Client Server Runtime Subsystem (CSRSS). Can also be caused by a user with administrator-level change the permissions of a file important files on Windows systems.
Unexpected Kernel Mode Trap (stop code 0x0000007F)This error is generally caused by defective memory, motherboard or damage prossesor high temperatures (usually occurs due to overclocking).
Unmountable Boot Volume (stop code 0X000000ED)Because Windows can not "mount" boot volume. See also the section "Boot Device inaccessible,"
Additional (Update 1):
Unable To Locate Dll (stop code 0 x00000135)Usually caused by a file that has been lost or damaged, or a registry error.Solution: If the document is lost or damaged, usually blue screen will display information relating nam file, you can search for a computer network or other appropriate documents, and to copy the System folder SYSTEM32 subfolders. If the blue screen does not show the file name, the chances of damage are on the registry, use System Restore.
Thread Stuck In Device Driver (stop code x000000EA) is usually caused by the video card (VGA) or caused by its driver.Solution: Install the latest drivers for your video card, otherwise you need to replace the VGA for checking if the failure still occurs.
Bad Pool Caller (stop code 0 x000000C2) Errors drivers trying to enter the memory operations. Usually the driver or software caused by a BUG.Solution: Unplug the RAM, change / move-move its slot.
Video Driver Init Failure (stop code 0 x000000B4) Termination of information that should not start Windows because the graphics-based, so it can not enter into the graphical interface. The problem usually lies in the graphics card, or there is a conflict with the graphics hardware (parallel or serial port).Solution: Go into Safe Mode to see if the problem is resolved, if resolved, please upgrade graphi card latest driver, if still fail, probably caused by graphics cards and parallel port, open the "System Properties" in the hardware -> Device Manager, double- Click the LPT1 port to connect to print the item, the "resource tab" remove / unselect "use automatic configuration", then "input I / O range" of "03BC" to "0378"
BIOS ACPI Error (stop code 0 x000000A5) Usually because the motherboard's BIOS does not support / not support the ACPI specification.Solution: If there is no corresponding BIOS file, then it can install it via Windows 2K/XP CD, when it appears "press F6 if you need to install a third-party SCSI or RAID drivers" press the F7 key, so Windows will automatically prevent the installation of the ACPI HAL, and the installation of the Standard PC HAL.
Machine Check Exception (stop code 0 x0000009C) is usually caused by hardware. In general, occur due to overclocking or hardware problem (memory, CPU, bus, power supply).Solution: When overclocking, the original CPU frequency 请降 (Qing Xiang) will check the hardware.
Kernel Mode Exception Not Handled (stop code 0 x0000008E) Errors in kernel-level applications, but Windows did not catch the error processor. Usually a hardware compatibility error.Solution: Upgrade to the latest driver or BIOS upgrade.
NMI Hardware Failure (stop code 0 x00000080) is usually caused by hardware. (It seems there is an error screen and hardware lblue bond)Solution: If you have recently installed new hardware, off its hardware, replace the slot and then try to install the latest drivers, if problems arise stelah update a driver, please return the original version before, to check whether there is pollution in Goldfinger memory and damage, scanning virus, run "chkdsk / r" to check and repair disk errors, check all the hardware add-in card. If it still fails, contact a professional computer repair company and ask for help.
System Thread Exception Not Handled (stop code 0 x0000007E) system error process, but Windows can not catch the error processor. Many causes, including: hardware compatibility, there is a problem driver or system service system, or some software.Solution: Please use "Event Viewer" to get more information from the root causes of the errors found.
Registry Error (stop code 0 x00000051) Description of a stop code, errors, system configuration manager or managers fault because the hard disk itself has physical damage or file system, so that in the register file read input / output erorr.Solution: Use the "chkdsk / r" to check and repair disk errors.
FTDISK Internal Error (stop code 0 x00000058) Failure as a major driver error.Solution: First try to restart the computer to see whether it can resolve the problem, If not, try "Last Known Good Configuration" to complete.
Critical Service Failed (stop code 0 x0000005E) Beginning very important to identify the system caused.Solution: If you have recently installed new hardware, off its hardware, and open the Internet to check the list if the hardware is compatible with Windows 2K/XP, and then restart your computer, if the blue screen appears, use "Last Known Good Configuration", if it fails, it is recommended to repair or re-install.
Session3 Initialization Failed (stop code 0 x0000006F)This error usually appears at Windows startup, usually the question arises driver or damage arising from the file system.Solution: It is recommended that use of the Windows installation CD to repair the installation of the system.
Process Has Locked Pages (stop code 0 x00000076) is usually due to drivers on completion of the input / output.Solution: First step: Click Start -> Run: regedt32, look for [HKLM \ SYSTEM \ Currentcontrol Set \ Control \ Session Manager \ Memory Management], double-byte value on the right side "TrackLockedPages", value 1.Langkah Second: If the blue screen again, then the error message would be: STOP: 0x0000000CB (0xY, 0xY, 0xY, 0xY) DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS one of the four "0xY" will appear the name of the driver is the problem, repair or uninstall the drivers that muncul.Langkah three: To get into registry, delete "TrackLockedPages" which was added earlier.Multiple IRP Complete Request (stop code 0 x00000044) is usually caused by a hardware device drivers.Solution: Uninstall the new drivers installed.
RDR File System (stop code 0 x00000027) The cause of this error is difficult to assess, but "out of Windows memory management problems" likely will lead to the emergence of this stop code.Solution: If it is caused due to memory management, improve / upgrade the memory (RAM) will solve the problem.