Windows XP Blue Screen of Death STOP Codes

Search
Join Free!
q q q q q q q

How it Works

Log in

Home Forums Downloads Help Terms of Use Contact Live Help

Site Message (Message will auto close in 2 seconds) Need a geek? Geeks to Go offers free, quality tech support -- in terms anyone can understand. Volunteers are waiting to help, friendly, technology experts who have knowledge to share, and enjoy helping others. Feel free to browse the site as a guest. However, you must log in to reply to existing topics, or to start a new topic of your own. Other benefits of joining include richer forum features, and removal of all advertising. Learn more in our Welcome Guide Infected? Malware and Spyware Cleaning Guide. What are you waiting for? Click here to join for free today! > Geeks to Go! » Operating Systems » Windows XP™, 2000, 2003, NT

6 Pages

123>» Options Post #1

Windows XP Blue Screen of Death STOP Codes, A list of most BSoD errors and solutions Jul 12 2005, 11:51 cheathawk1 AM

http://www.geekstogo.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519.html (1 of 18)11/19/2009 4:39:31 PM

Having a basic understanding of these error messages enables you to communicate with your technical support professional more effectively too. contact the hardware manufacturer to obtain compatible updates.. http://www. or roll back the driver to correct the problem. This list is NOT exhaustive or meant to resolve EVERY error.com . • A Stop 0xA message might also be due to failing or defective hardware. sometimes referred to as blue screens (BSoD). That is why tying in the error message into www. posting a notice for help on a relevant newsgroup and entering the stop code into the "Microsoft Knowledge Base" can yield help just when you need it! Here is the (long) list: Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL The Stop 0xA message indicates that a kernel-mode process or driver attempted to access a memory location to which it did not have permission. This Stop message is typically due to faulty or incompatible hardware or software. or firmware. A kernel-mode process can access only other processes that have an IRQL lower than. If a Stop message lists a driver by name. virus scanner. or at a kernel interrupt request level (IRQL) that was too high. With all these Stop messages. This list of messages is a guide to individual messages and their possible causes and resolutions. These are text-mode error messages that report information about the condition. contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications. remove. it displays Stop messages. Windows XP Blue Screen of Death STOP Codes Member Posts: 182 From: Vacaville.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519. or equal to.geekstogo. system service. and CD mastering tools.Windows XP Blue Screen of Death STOP Codes I have been seeing quite a few posts regarding the dreaded Blue Screen of Death. disable.. try removing or replacing the hardware to determine if it is causing the problem. system service. their corrasponding codes.google. the problem might be due to an incompatible driver. its own. you can pretty much assume someone else has encountered the problem before you. simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. or backup. If disabling or removing drivers resolves the issues. Possible Resolutions: • A Stop 0xA message might occur after installing a faulty device driver. and recommended solutions. If a Stop message points to a category of devices (video or disk adapters. This is a fairly extensive list of the most common stop errors. After you have successfully installed Windows XP. This list describes these messages and helps you understand and interpret them. CA OS: Windows XP home SP2 When Windows XP detects a problem from which it cannot recover. antivirus scanners. and what the STOP codes mean. • If you encounter a Stop 0xA message while upgrading to Windows XPl. for example). To avoid problems while upgrading. Stop messages.html (2 of 18)11/19/2009 4:39:31 PM . contain specific information that can help you diagnose and possibly resolve the problem detected by the Windows kernel.

If not. see Microsoft Knowledgebase articles Q177415. application backup files.exe) helps you to isolate the components that are causing kernel memory leaks. The problems that cause Stop 0x1E messages share similarities with those that generate Stop 0xA errors in that they can be due to invalid memory and access violations. If disabling or removing applications and drivers resolves the issue. If such software is installed. For more information about troubleshooting memory leaks.geekstogo.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519. or they can indicate hardware problems. the driver file that allows the system to read and write to NTFS file system drives. Possible Resolutions: • Malfunctioning SCSI and Advanced Technology Attachment (ATA) hardware or drivers can also adversely affect the system's ability to read and write to disk. or roll it back to correct the problem. This default Windows XP error handler typically intercepts these problems if error-handling routines are not present in the code itself. antivirus scanners. and so on. such as memory and IRQ conflicts. and CD mastering tools. "Finding Pool Tags Used by Third Party Files Without Using the Debugger. causing errors. If using SCSI hard disks." and Q298102. disable. Periodically check Event Viewer for error messages related to SCSI or http://www." Stop 0x00000024 or NTFS_FILE_SYSTEM The Stop 0x24 message indicates that a problem occurred within Ntfs. Internet cache files. You can also choose to install additional applications to another hard disk with more free space or move data files. Possible Resolutions: • Stop 0x1E messages typically occur after installing faulty drivers or system services. You can free up space by deleting unneeded files. check for cabling and termination problems between the SCSI controller and the disks. use Recovery Console to manually delete the system service file that is causing the problem. paging files. 0x23.sys.exe. If a Stop message lists a driver by name. From Recovery Console. the source of the error might be a thirdparty "remote control" program.tmp file extensions).exe or Autochk. Using updated software is especially important for multimedia applications.Windows XP Blue Screen of Death STOP Codes Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED The Stop 0x1E message indicates that the Windows XP kernel detected an illegal or unknown processor instruction. • Other possible causes include insufficient disk space while installing applications or performing certain functions that require more memory.tmp files generated by Chkdsk. • If the Stop message mentions the file Win32k. exists for the file allocation table (FAT16 or FAT32) file systems. you might be able to disable it by starting the system in safe mode. • The problem might be due to a memory leak caused by an application or service that is not releasing memory correctly. Use Disk Cleanup to increase available disk space. Many Advanced Configuration and Power Interface (ACPI) issues can be resolved by updating to the latest firmware.sys. "How to Use Poolmon to Troubleshoot Kernel Mode Memory Leaks. • Problems can result from system firmware incompatibilities. contact the hardware manufacturer about a possible update. A similar Stop message. remove. Poolmon (Poolmon. and . remove temporary files (those with .html (3 of 18)11/19/2009 4:39:31 PM .

In the Error-checking box. Microsoft® Windows® 98. Double-click My Computer. or Microsoft® Windows® Millennium Edition (Me) installed. and the system partition is formatted with the file allocation table (FAT16 or FAT32) file system. After you restart. click Check Now. • Verify that the tools you use to continually monitor your system. The cause is typically failed or defective RAM (including motherboard. If you cannot restart the computer due to the error. click Properties. If you are not using the NTFS file system. 2. You can also select the Automatically fix file system errors check box. At the command prompt type: chkdsk drive: /f Method 2: 1. Start the Chkdsk tool. 3. 4. Stop 0x0000002E or DATA_BUS_ERROR The Stop 0x2E message indicates a system memory parity error. Some disks and adapters come packaged with diagnostic software that you can use to run hardware tests. use safe mode or Recovery Console. A command prompt appears when using a startup floppy disk or when using the command prompt startup option on multiple boot systems that use FAT16 or FAT32 partitions with Microsoft® Windows® 95 OEM Service Release 2 (OSR2). or failed memory hardware.geekstogo. such as virus scanners. or video memory). which increases the quantity of nonpaged pool memory available to the kernel. backup programs. Possible Resolutions: • Stop 0x2E is typically due to defective. or disk defragmenters are compatible with Windows XP. incompatible or mismatched memory hardware. In the Run dialog box. malfunctioning. which detects and attempts to resolve file system structural corruption. long file name (LFN) information can be lost if hard disk tools are started from an MS-DOS command prompt.html (4 of 18)11/19/2009 4:39:31 PM . To test hard disk or volume integrity Method 1: 1. disk error checking runs and the volume chosen is not available to run other tasks during this process. a message asks whether you want to delay disk error checking until the next time you restart your computer. If the volume you are checking is in use. in the Open box type: cmd 2. In Check disk options. which can cause the system to stop. Click the Tools tab. 5.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519. such http://www. You can resolve this situation by adding more RAM. Level 2 cache. or when a device driver attempts to access an address in the 0x8xxxxxxx range that does not exist (does not map to a physical address). A Stop 0x2E message can also indicate hard disk damage caused by viruses or other problems. select the Scan for and attempt recovery of bad sectors check box.Windows XP Blue Screen of Death STOP Codes FASTFAT in the System log or Autochk in the Application log. Do not use tools meant for other operating systems on Windows XP partitions! • Nonpaged pool memory might be depleted. On the File menu. and then select the hard disk you want to check.

• The problem might also be due to cracks. Possible Resolutions: • Stop 0x3F messages can occur after installing faulty drivers or system services.. Stop 0x0000003F or NO_MORE_SYSTEM_PTES The Stop 0x3F message indicates one or more of the following problems: • The system Page Table Entries (PTEs) are depleted or fragmented due to the system performing a large number of input/output (I/O) actions. and in the Open box. is improperly allocating large amounts of kernel memory. and CD mastering tools. • Stop 0x2E messages can also occur after installing faulty drivers or system services. that you can use to increase the number of PTEs allocated.html (5 of 18)11/19/2009 4:39:31 PM . type: regedit http://www. • The system might not actually be out of PTEs. In the Run dialog box. Using updated software is especially important for backup programs.geekstogo. • Hard disk corruption can also cause this Stop message. Disable the service or application and confirm that this resolves the error. antivirus scanners. Level 2 (L2) SRAM cache. Disable the service or application and confirm that this resolves the error. SystemPages. but a contiguous memory block of sufficient size is not available to satisfy a driver or application request. To increase the number of PTEs allocated in the registry 1. Check for the availability of updated driver or application files and consult the hardware or program documentation for minimum system requirements. If a file name is given. The registry editor bypasses standard safeguards. allowing settings that can damage your system. take the system motherboard to a repair facility for diagnostic testing. or roll back that driver. Caution o Do not edit the registry unless you have no alternative. or defective components on the motherboard. Windows XP Professional provides a registry entry. If you must edit the registry. remove and replace it to determine if it is causing or contributing to the problem.. remove. or roll back that driver. Using updated software is especially important for backup programs. • A faulty device driver is not managing memory properly. antivirus scanners. If a file name is given. contact the hardware manufacturer about a possible update. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519. you need to disable. If all else fails. If so. such as a backup program. scratched traces. If you added new hardware recently. you need to disable. back it up first. and CD mastering tools. multimedia applications. • Another cause is excessive demands for system PTE by applications.Windows XP Blue Screen of Death STOP Codes as memory modules. or video adapter RAM. contact the hardware manufacturer about a possible update. • An application. This situation is more common in server environments. If so. multimedia applications. or even require you to reinstall Windows. remove.

Double-click on PagedPoolSize and SystemPages to view the value for each entry. the stack signature in the kernel stack is missing. L2 RAM cache. Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR The Stop 0x77 message indicates that a page of kernel data requested from the paging (virtual memory) file could not be found or read into memory. In extremely rare cases. Using updated drivers and software is especially important for network interface cards. assign a value of 40000 for systems with 128 MB (or less) of memory. If an updated driver is not available. • Stop 0x50 messages can also occur after installing faulty drivers or system services. and then close the registry editor. You can try to correct this by restarting the computer. or 110000 for systems with 128 MB to 256 MB of memory. multimedia applications. Restart your computer.Windows XP Blue Screen of Death STOP Codes 2. For systems with more memory. attempt to use a driver from a similar device in the same family. assign a value of 0. 4. If the file name is listed. In the registry editor. contact the hardware manufacturer for updates. if printing to a Model 1100C printer causes Stop 0x50 errors. backup programs. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk. disable the recently installed service or application to determine if this resolves the error. using a printer driver meant for a Model 1100A or Model 1000 might temporarily resolve the problem. Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA The Stop 0x50 message indicates that requested data was not in memory. Click OK. If not. This Stop message can also indicate disk hardware failure.html (6 of 18)11/19/2009 4:39:31 PM . remove. video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages. 6. If the first and third parameters are zero. check for cabling and termination issues. The system generates an exception error when using a reference to an invalid system memory address. or roll back that driver.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519. or possible virus infection. antivirus scanners. For example. Possible Resolutions: • If you added new hardware recently. depleted nonpaged pool resources can cause this error. 5. do not increase the SystemPages value above 110000 without contacting Microsoft technical support. An I/O status code of 0xC000009C or 0xC000016A indicates that the requested data could not be found. which is an error typically caused by defective hardware. 7. remove and replace the hardware to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the hardware manufacturer to determine if the component has failed. If a problem with disk http://www. 3.geekstogo. Defective memory (including main memory. you need to disable. navigate to the subkey HKEY_LOCAL_MACHINE\SYSTEM \CurrentControlSet\Control\ Session Manager\Memory Management. and CD mastering tools. video adapters. If this does not resolve the problem. disk data corruption. If SystemPages is not zero. Possible Resolutions: • Stop 0x77 messages can be caused by bad sectors in the virtual memory paging file or a disk controller error. If PagedPoolSize is not zero.

exe respectively. For example. The kernel and HAL files for single-processor and multiprocessor systems are stored on the Windows XP Professional operating system CD using two different file names.exe or Ntkrnlmp. remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed. scratched traces. Autochk.Windows XP Blue Screen of Death STOP Codes integrity exists. Possible Resolutions: • A Stop 0x79 message occurs when the system is using out-of-date Ntoskrnl. This error also occurs when using mismatched files.geekstogo.exe to your system as Ntoskrnl. If Autochk fails to run. such as memory modules. Level 2 (L2) SRAM cache.exe and Ntkrnlmp. • Another cause of Stop 0x77 messages is defective. you can use the Copy command to copy the correct HAL or kernel files from the CD to the appropriate folder on the hard disk. Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR The Stop 0x7A message indicates that a page of kernel data was not found in the paging http://www. restore the original settings used during Windows XP Professional Setup.html (7 of 18)11/19/2009 4:39:31 PM . you can manually perform the integrity check yourself by following the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this list. • The problem might also be due to cracks. a program that attempts to mark bad disk sectors as defective so that they are not used in the future. • Problems that cause Stop 0x77 messages can also cause Stop 0x7A messages. the single and multiprocessor versions of the kernel. This error can also result when mismatched single and multi-processor configuration files are copied to the system. starts automatically. take the system motherboard to a repair facility for diagnostic testing. malfunctioning. see "Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR" later in this list. or video adapter RAM. For example.exe. you can only manually change IRQ settings for non-ACPI (Standard PC HAL) systems. Some x86-based provide the option to toggle ACPI functionality.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519. you must run Setup again (an upgrade installation does not work). If you added new hardware recently. For more information about Stop 0x7A messages. or defective components on the motherboard. Stop 0x00000079 or MISMATCHED_HAL The Stop 0x79 message indicates that the hardware abstraction layer (HAL) and the kernel type for the computer do not match. you must change firmware settings and reinstall Windows XP. This can occur after manual repairs that involve copying incorrect files to the system. such as copying a multiprocessor HAL on to a system using a single-processor kernel (or vice versa). you might install Windows XP on an x86-based computer with the firmware ACPI enable option enabled and later decide to disable it. or failed memory hardware. • If you experience Stop 0x79 messages after changing firmware settings. Because of the numerous registry and system file changes required. If all else fails. To disable or re-enable ACPI. In Recovery Console. This error most often occurs when ACPI firmware settings are changed. Setup copies either Ntoskrnl. Because systems that use the ACPI HAL ignore IRQ assignments stored in firmware. named Ntoskrnl.exe or Hal.dll files.

geekstogo. Possible Resolutions: • Stop 0x7A can be caused by bad sectors in the virtual memory paging file. If Autochk fails to run. indicates bad blocks (sectors) on the hard disk. An I/O status code of 0xC000009C or 0xC000016A indicates that the requested data could not be found. Run diagnostics software supplied by the system manufacturer to determine if the component has failed. or STATUS_DEVICE_NOT_CONNECTED. the cause of this error can be determined from the second parameter. In extremely rare cases. or failed memory hardware. IMPORTANT o You can install disk controller drivers not present on the Windows XP Professional operating system CD by responding to the following prompt shortly after starting Setup: http://www. • 0xC000009D.Windows XP Blue Screen of Death STOP Codes (virtual memory) file and could not be read into memory. or STATUS_DEVICE_DATA_ERROR. • 0xC0000185. the stack signature in the kernel stack is missing. indicates bad blocks (sectors) on the hard disk. indicates improper termination. or two devices attempting to use the same resources. If a problem with disk integrity exists. or STATUS_INSUFFICIENT_RESOURCES. the I/O status code. an error typically caused by defective hardware. or memory hardware problems. You can try to correct this by restarting the computer. defective storage controller hardware. Some common status codes are: • 0xC000009A. you can manually perform the integrity check yourself by following the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this appendix. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk. remove and replace it to determine if it is causing or contributing to the problem. or hardware. such as memory modules. firmware. or STATUS_DISK_OPERATION_FAILED. Frequently. malfunctioning. Consult your hardware or device documentation for more information. select a slower transfer rate if an update is not yet available.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519. virus infection. a problem with SCSI termination. disk controller error. such as higher transfer rates. or improper controller or disk configuration.html (8 of 18)11/19/2009 4:39:31 PM . starts automatically. check for cabling and termination issues. If the first and third parameters are zero. If necessary. Autochk. or video adapter RAM. indicates a lack of nonpaged pool resources. If you added new hardware recently. • 0xC000016A. • Check the hardware manufacturer's Web site for updates to disk adapter firmware or drivers that improve compatibility. Level 2 (L2) SRAM cache. • Another cause of Stop 0x7A messages is defective. Verify that your disks and controller support the same set of advanced features. a program that attempts to mark bad disk sectors as defective so that they are not used in the future. • 0xC000009C. or STATUS_IO_DEVICE_ERROR. or defective disk cabling. indicates defective or loose data or power cables. depleted nonpaged pool resources can cause this error. This might be due to incompatible disk or controller drivers.

or upgrading to a new disk controller might cause the information in the Boot. • Repartitioning disks. • The problem might also be due to cracks. If this Stop message occurs after installing new disks to your system. and when prompted. For more information about Stop 0x77 messages. and you need to provide additional drivers to complete the Windows XP setup successfully. provide the appropriate storage controller driver (ATA or SCSI) supplied by the manufacturer. defective. Stop 0x7B errors could also indicate possible virus infection. • Problems that cause Stop 0x7A messages can also cause Stop 0x77 messages. take the system motherboard to a repair facility for diagnostic testing.geekstogo. verify that the new hardware is functioning and correctly configured. the problem might be due to unsupported disk controller hardware. Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE The Stop 0x7B message indicates that Windows XP has lost access to the system partition or boot volume during the startup process. the controller or driver for the startup device (typically the hard disk) might have failed to initialize the necessary hardware. Values of 0xC000034 or 0xC000000E typically indicate: • Disks or storage controllers that are failing. If this is the case. • Verify that the system firmware and disk controller BIOS settings are correct and that the storage device was properly installed. for example) that are not fully compatible with Windows XP Professional. • Storage-related drivers or programs (tape management software. Periodically check for driver and firmware updates.ini file. follow the hardware manufacturer's instructions when installing drivers. or defective components on the motherboard. or because the file system did not recognize the data on the boot device. drivers for new hardware are not in the Windows XP Professional Driver. In some cases.Windows XP Blue Screen of Death STOP Codes o Press F6 if you need to install a third party SCSI or RAID driver. edit the Boot.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519. If the error occurs during Windows XP Professional setup.cab library. If all else fails. Installing incorrect device drivers when installing or upgrading storage adapter hardware typically causes stop 0x7B errors. see the instructions provided in "Stop 0x00000024 or http://www.ini file or adjust the Boot Manager parameters to allow the system to start. If the error occurs after upgrading the disk controller. see "Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR" earlier in this list. consult your computer's documentation about restoring default firmware settings or configuring your system to autodetect settings. adding new disks. to become outdated.html (9 of 18)11/19/2009 4:39:31 PM . The second parameter is very important because it can indicate whether the 0x7B Stop message was caused by file system issues or problems with storage hardware and drivers. File system initialization might have failed because of disk or controller failure. or improperly configured. For more information about checking hard disk integrity. Possible Resolutions: • During I/O system initialization. scratched traces. If you are unsure. • Hard disk corruption can also cause this Stop message. o Press F6. or Boot Manager.

antivirus scanners.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519. take the system motherboard to a repair facility for diagnostic testing. • Hardware failures. and Shutting Down Your Computer in Windows 2000. and CD mastering tools. see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" later in this list. malfunctioning. If a file is listed by name and you can associate it with an application. • For information about troubleshooting standby and hibernate mode issues. Contact the software manufacturer about possible Windows XP specific updates. If you added new hardware recently. multimedia applications. contact the hardware manufacturer for a possible update. or roll back that driver to to determine if this resolves the error. antivirus scanners. For drivers." http://www. Possible Resolutions: • Stop 0x9F messages can occur after installing faulty applications or drivers or system services. • The problem might also be due to cracks. Hibernate Mode. Stop 0x0000009F or DRIVER_POWER_STATE_FAILURE The Stop 0x9F message indicates that a driver is in an inconsistent or invalid power state.html (10 of 18)11/19/2009 4:39:31 PM . "How to Troubleshoot Problems with Standby Mode. • Problems that cause 0x7B errors might also cause Stop 0xED errors. Using updated software is especially important for backup programs. first restore all clock and bus speed settings to the manufacturer recommended values to determine if this resolves the issues. When diagnosing problems on overclocked systems. disable. For more information about 0xED Stop messages." can cause Stop 0x7F or other error messages due to heat buildup. or failed memory hardware. see KB article Q266169.Windows XP Blue Screen of Death STOP Codes NTFS_FILE_SYSTEM" earlier in this list. drivers. Run diagnostics software supplied by the system manufacturer to determine if the component has failed. If all else fails. and CD mastering tools. remove. • Software problems. • Running the CPU beyond the rated specification. or system services. scratched traces. remove and replace it to determine if it is causing or contributing to the problem. or defective components on the motherboard. If it does. known as "overclocking. multimedia applications.geekstogo. • Stop 0x7F messages can occur after installing incompatible applications. Possible Resolutions: • Stop 0x7F messages are typically due to defective. uninstall the application. Using updated software is especially important for backup programs. Stop 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP The Stop 0x7F message indicates that one of three types of problems occurred in kernelmode: • A condition that the kernel is not allowed to have or intercept (also known as a bound trap).

virus scanner. After you have successfully installed Windows XP. DVD http://www. antivirus scanners. • If you encounter a Stop 0xC2 message while upgrading to Windows XP. remove. Stop 0xC2 or BAD_POOL_CALLER The Stop 0xC2 message indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations in the following ways: • By allocating a memory pool size of zero bytes. • A Stop 0xC2 messages might also be due to failing or defective hardware. the problem might be due to an incompatible driver. or roll back the driver to correct the problem. or roll back that driver to confirm that this resolves the error.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519. If a Stop message points to a category of devices (such as disk controllers. • By allocating or freeing a memory pool at an IRQL that was too high. system service. system service. disable. If a driver is listed by name.geekstogo. If so. Possible Resolutions: • Stop 0xCE messages can occur after installing faulty drivers or system services. Using updated software is especially important for backup programs. try removing or replacing the hardware to determine if it is causing the problem. contact the hardware manufacturer to obtain compatible updates. or backup. multimedia applications. contact the manufacturer about a possible update. simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. If disabling or removing drivers resolves the issues.html (11 of 18)11/19/2009 4:39:31 PM . disable. system service. contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications. disable. DVD playback. If disabling or removing drivers resolves the issues. or firmware. or firmware. If a Stop message lists a driver by name. Stop 0x000000CE or DRIVER_UNLOADED_WITHOUT _CANCELLING_PENDING_OPERATIONS This Stop messages indicates that a driver failed to cancel pending operations before exiting. and CD mastering tools. for example).Windows XP Blue Screen of Death STOP Codes Stop 0xBE or ATTEMPTED_WRITE_TO_READONLY_MEMORY The Stop 0xBE message indicates that a driver attempted to write to read-only memory. DVD playback. remove. Possible Resolutions: • A Stop 0xBE message might occur after installing a faulty device driver. Possible Resolutions: • A Stop 0xC2 messages might occur after installing a faulty device driver. To avoid problems while upgrading. Using updated software is especially important for multimedia applications. • By allocating a memory pool that does not exist. antivirus scanners. and CD mastering tools. This Stop message is typically due to a faulty driver or software. • By attempting to free a memory pool that is already free. remove. If a Stop message lists a driver by name. antivirus scanners. or roll back the driver to correct the problem. contact the manufacturer about a possible update.

see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" earlier in this appendix. remove. DVD playback. contact the manufacturer about a possible update. Possible Resolutions: • Stop 0xD1 messages can occur after installing faulty drivers or system services. Stop 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH http://www. replace the standard 40-pin cable with an 80-pin cable. This error might also occur during an upgrade to Windows XP Professional on systems that use higher throughput ATA disks or controllers with incorrect cabling. If so. If a driver is listed by name. contact the manufacturer about a possible update. Stop 0x000000ED or UNMOUNTABLE_BOOT_VOLUME The kernel mode I/O subsystem attempted to mount the boot volume and it failed. Your firmware might issue a warning but allow the startup process to proceed. This might indicate a hardware problem with the video adapter or a faulty video driver.3 megabytes per second. and CD mastering tools. The additional grounded pins are required to avoid data loss. or roll back that driver to confirm that this resolves the error. and CD mastering tools. your system might appear to work normally after you restart. In some cases.html (12 of 18)11/19/2009 4:39:31 PM .com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519. antivirus scanners. and CD mastering tools. • Problems that cause 0xED errors might also cause Stop 0x7B errors. Stop 0x000000EA or THREAD_STUCK_IN_DEVICE_DRIVER A device driver problem is causing the system to pause indefinitely. antivirus scanners.Windows XP Blue Screen of Death STOP Codes playback. or roll back that driver to confirm that this resolves the error. disable. Using an 80-pin cable is optional for transfer rates up to and including 33. For more information about 0x7B Stop messages. multimedia applications. • Some firmware enables you to force higher transfer rates even when you are using the incorrect cable type. Restore the default firmware setting for ATA cable detection. If so. this problem is caused by a display driver waiting for the video hardware to enter an idle state.geekstogo. Typically. Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL The Stop 0xD1 messages indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. If a driver is listed by name. Possible Resolutions: • Stop 0xD1 messages can occur after installing faulty drivers (especially video drivers) or system services. DVD playback. Using updated software is especially important for backup programs. Possible Resolutions: • If using higher throughput ATA disks and controllers. multimedia applications. disable. Drivers that have used improper addresses typically cause this error. remove. but is mandatory for higher transfer rates. those capable of data transfer rates above 33.3 megabytes per second. Using updated software is especially important for backup programs.

try replacing it manually with a fresh copy from the Windows XP Professional operating system CD using safe mode or Recovery Console.714 From: 127.1 OS: Windows 7 64-bit RTM ratmilk Jul 28 2005. you have the option of using a Windows 98 or Windows Millennium Edition Emergency Boot Disk to access the hard disk.0. system file. you must rename the expanded file with the correct extension before using it. For systems using the FAT16 or FAT32 file system. In Recovery Console. the expanded file is given the correct name after being copied to the destination location.Windows XP Blue Screen of Death STOP Codes This Stop message indicates driver. or disk corruption problems (such as a damaged paging file). You can also use Windows XP Professional recovery features such as the Last Known Good Configuration startup option. to restore a previous driver. If the original file from the operating system CD has a file name that ends with an underscore (_) character. After restoring from backup media. Possible Resolutions: • You can use Driver Rollback or System Restore from safe mode. you cannot use the file until it is uncompressed. 12:46 PM Great information! Pinned.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519. you might need to reapply service packs or hotfixes. If you do not specify a destination file name. For more information about the Copy or Expand commands. depending on when the backups were made. From safe mode or Recovery Console.0. • If the Stop message names the specific file. 04:02 PM Post #3 http://www. you can use the Expand command to uncompress and copy a file to a destination location. The Recovery Console's Copy command is ideal for copying compressed files because it detects and expands them. or Automated System Recovery to restore a previous working configuration.geekstogo. Post #2 Site Administrator Posts: 18. --Chris admin Jul 12 2005. see Windows XP Help and Support Centre.html (13 of 18)11/19/2009 4:39:31 PM . Backup. Faulty memory hardware can also cause this Stop message to appear.

html (14 of 18)11/19/2009 4:39:31 PM . thanks for this. Dhaka OS: XP http://www... Gulshan. Guest_Tony_* Aug 11 2005..great informaiton... can you please keep this up..Windows XP Blue Screen of Death STOP Codes Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL Member Posts: 151 From: Hong-Kong OS: ••••••••••• Can also be caused by incorrect BIOS settings....geekstogo. 11:47 Post #5 AM WOW! What a list! I'll be sure to bookmark that thread in case someone has a blue screen again. Thanks dude Post #6 Member Posts: 94 From: Mohakhlai. Cause i might need it next time when this errors happens with ma mates or my computer.. I needed to knwo some stuff. 01:50 PM Wow.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519. Member Posts: 303 From: South Africa OS: Windows XP Home mm_akash Aug 16 2005. just reset your BIOS settings in that case. 09:29 Post #4 PM Cool. Dark_Side Aug 13 2005.

. 0xb2000000.0x00070f0f cheathawk1 Aug 21 2005.. CA OS: Windows XP home SP2 robmentx Member Posts: 15 OS: xp pro Aug 22 2005.html (15 of 18)11/19/2009 4:39:31 PM . Post #7 Member Posts: 15 OS: xp pro MACHINE_CHECK_EXCEPTION then it goes on to tell me to restart m computer yada yada yada then i get this crap 0x0000009c (0x00000004.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519. am i looking at a total format here guys? cheathawk1 Aug 23 2005. 03:50 PM i keep geting this crap.Windows XP Blue Screen of Death STOP Codes robmentx Aug 21 2005. 07:49 PM Post #10 http://www...microsoft. nothing helped i still get the same error message. 04:42 Post #9 PM ok i reset my bios to standard settings.geekstogo.com/?kbid=329284 PS. it tells of possible solutions. its microsoft based so I'll keep looking for a another scource just in case! --Chris Post #8 Member Posts: 182 From: Vacaville. 10:56 PM Try going to this site. http://support.0x80545ff0.

08:43 PM Post #13 http://www.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519. Go to the device manager (My computer | Control Panel | System | Hardware tab | Device manager) Then check to see if there are any yellow question marks or red "X's" next to any of your devices.Windows XP Blue Screen of Death STOP Codes Ok. Member Posts: 182 From: Vacaville.com/en/response. if the driver is missing then you can select to upgrade or install it.html (16 of 18)11/19/2009 4:39:31 PM .aspx?. 08:13 Post #12 PM try this. and it happens whenever. Member Posts: 182 From: Vacaville. If there are then you can right click on the device with the mark and click properties.. 08:09 PM cheathawk1 Aug 23 2005. 08:07 Post #11 PM no.. i finally got the xp error report and sent it to microsoft they said it was a device driver but did not specify which one let me find the link and ill post it next post here it is http://oca. did you install any new hardware recently? Also.geekstogo. CA OS: Windows XP home SP2 --Chris This post has been edited by cheathawk1: Aug 23 2005.microsoft.. You most likely will not have to reformat your computer.a22f06c4&SID=10 This post has been edited by robmentx: Aug 23 2005. It sound s like a hardware issue to me. This will then give you a brief explination of whats wrong with the device. CA OS: Windows XP home SP2 robmentx Member Posts: 15 OS: xp pro Aug 23 2005. no new hardware. 08:13 PM robmentx Aug 23 2005. what are you doing when this happens? Playing a particular game/app? How long has this been happening? --Chris PS..

geekstogo. And should bring back the BSoD if you get one. i tried that already via the msn suggestions lol Member Posts: 15 OS: xp pro robmentx Aug 23 2005. to do this go to My computer | Control Panel | System | Advanced tab | Startup and recovery settings button | deselect the 'automatically restart on failure' option.Windows XP Blue Screen of Death STOP Codes lol nope no marks anywhere. This should stop your computer from retsarting on its own. 2000. 08:46 PM but instead of the blue screen now i get my computer just restarting all by itself Post #14 Member Posts: 15 OS: xp pro cheathawk1 Aug 23 2005. 2000. CA OS: Windows XP home SP2 « Next Oldest · Windows XP™. NT · Next Newest » Enter Keywords 6 Pages 123>» Search Topic 9 User(s) are reading this topic (9 Guests and 0 Anonymous Users) 0 Members: |-. --Chris Member Posts: 182 From: Vacaville.Windows XP™.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519.html (17 of 18)11/19/2009 4:39:31 PM . NT Go http://www. 08:52 Post #15 PM disable auto-restart. 2003. 2003.

we do not guarantee that they are accurate and they are to be used at your own risk.05:16 PM Tasty_Spoon started . Inc.12:04 AM danseur90 started .03:35 PM LetLoveRule started . | All Rights Reserved | Privacy Policy | Advertising Powered By IP. Inc.com/forum/Windows-XP-Blue-Screen-Death-STOP-Codes-t43519.Windows XP Blue Screen of Death STOP Codes Similar Topics Topic Title Windows XP .last by infowttech 16th November 2009 . 2000. NT 14 / 281 0 / 38 Search Translate this page Time is now: 19th November 2009 . We make every attempt to ensure that the help and advice posted is accurate and will not cause harm to your computer. 2003.geekstogo.last by tspmi888 17th November 2009 . The forum is run by volunteers who donate their time and expertise.last by LetLoveRule Windows XP™. http://www. NT Replies / Views 3 / 1. NT 5 / 1.737 Topic Information 22nd July 2009 .last by Kenny Reigh 5th November 2009 . © 2009 Geeks to Go. However.html (18 of 18)11/19/2009 4:39:31 PM . NT Death STOP Codes Help! Windows XP Blue Screen of Death! Windows XP™.Board © 2009 IPS.03:33 PM Advertisements do not imply our endorsement of that product or service.134 Windows XP Blue Screen of Windows XP™. 2000. 2003. 2000. 2003. 2003. 2000. All trademarks mentioned on this page are the property of their respective owners.03:40 PM infowttech started .Blue Screen of Death? Windows XP Blue Screen of Death Windows XP™.