Code Blue Screen Windows XP & Solutions

When Windows XP detects a problem that can not be repaired, Windows XP will display the STOP Message (Message STOP). This message is a message of damage in the form of text that provides information on the condition occurs.

STOP Message sometimes refer to BSOD (Blue Screen of Death) that contain specific information that can help you diagnose and allows you to fix problems detected by the Windows kernel.

Note: This list is not comprehensive and are not intended to resolve any errors / damage. This list is a guide for each message and the possible causes and solutions. With a basic understanding of error messages will also be easier for you to communicate with technical support.

The following list:

1. Stop 0×0000000A or IRQL_NOT_LESS_OR_EQUAL
Information:
Message Stop 0 × 0000000A indicates that a kernel-mode process or driver tried to access a memory location but do not have permission (license), or the kernel IRQL (interrupt request level) is too high. Kernel-mode process can access only other processes that have IRQL less than or equal to his own.
This Stop message usually occurs because of an error or not kompatibelnya (not suitable) hardware and software. Could also occur because the BIOS settings are not right.

Solution:
- Message Stop 0 × 0000000A may appear after installing the driver, system service, or firmware is wrong. If the Stop message lists a driver, disable, remove, or roll back (restore the driver to a version that works well) the faulty driver. If you disable or delete the drivers solve the problem, contact the device manufacturer (hardware) is problematic for possible driver updates are available.
- This Stop message also may occur because of defective hardware or problems. If the Stop message indicates a particular category of devices (video or disk adapters, for example), try out or replace the hardware to determine if the correct hardware is the source of the problem.
- If you are experiencing this Stop message when updating Windows XP to sp1, 2, or 3, the possibility of problems due to an incompatible driver, system service, virus scanner, or backup. To prevent this, before you perform the update of Windows, your hardware configuration features a minimum, and remove all third-party drivers (additional) and system services (including antivirus). After the Windows update is complete, contact your hardware manufacturer to obtain compatible updates to the version service pack (sp) Windows XP PC.
- If you are not sure of the three messages above, try reset the BIOS settings you come back.

2. Stop 0×0000001E or KMODE_EXCEPTION_NOT_HANDLED

Information:
Message Stop 0 × 0000001E indicates that the Windows XP kernel detected an illegal or processor instructions that are not known. The cause of this Stop message 0 × 0000001E similar to the cause of the message Stop 0 × 0000000A, namely because of access violations and invalid memory. Usually error-handler (handler error) by default from Windows XP will overcome this problem if there are no error-handling routines in the instruction code is executed.

Solution:
- Message Stop 0 × 0000001E generally occurs after installing a damaged driver or system service, or maybe there is a problem in hardware (such as memory and IRQ conflicts). If the Stop message lists a driver, disable, remove, or roll back (restore the driver to a version that works well) the faulty driver. If you disable or delete the drivers solve the problem, contact the device manufacturer (hardware) is problematic for possible driver updates are available.
- If the message include the Stop Win32k.sys file, the source of possible damage is the program "a remote-control" third-party. If similar programs were installed, you may be able to disable it through safe mode. If not, use Recovery Console to manually delete the file system service that causes the problem.
- Problems can also be caused by incompatible firmware. Most problems ACPI (Advanced Configuration and Power Interface) can be improved by updating with the latest firmware.
- Another possibility for disk space is not sufficient when installing an application or perform certain functions that require more memory. You can delete files that are not required to obtain disk space. Use Disk Cleanup to increase disk space. Through the Recovery Console, remove temporary files (files with the extensions. Tmp), files, Internet cache files, application backup files, and files. Tmp generated by Chkdsk.exe or Autochk.exe. You can also choose to install the application on another hard drive with more space or can also move data from a full hard drive to hard drive with more space.
- This Stop message also may be caused by a memory leak (memory leak) from the application or service that does not release memory correctly. Poolmon (Poolmon.exe) to help you isolate the components that kernel memory leak. For more information about the handling of memory leaks see Microsoft Knowledgebase article Q177415 (http://support.microsoft.com/kb/177415): "How to Use Poolmon to Troubleshoot Kernel memory leaks" and Q298102 (http://support.microsoft .com/kb/298102): "Finding Pool Tags Used by Third Party Files Without Using the Debugger".

3. Stop 0×00000024 or NTFS_FILE_SYSTEM
Information:
Message Stop 0 × 00000024 indicates that there is a problem in Ntfs.sys (driver file that allows the system to read and write to NTFS file system drives). Similar Stop message, 0 × 00000023, indicates there is a problem in the file system FAT16 or FAT32 (File Allocation Table).

Solution:
- SCSI hardware malfunctions and ATA (Advanced Technology Attachment) or the driver may also affect the system's ability to read and write to the disk and cause errors. If using a SCSI hard drive, check cables and the problem stops (termination problem) between the SCSI controller and disk. Periodically check Event Viewer for error messages related to SCSI or FASTFAT in the System log or Application log in Autochk (Right click on My Computer, choose Manage, in the Computer Management - System Tools, select Event Viewer).
- Check the tool you normally use to monitor your system constantly (such as antivirus, backup programs, or the Disk Defragmenter program) is already compatible with Windows XP. Some disk or adapter is bundled with diagnostic software that you can use to test hardware.

The way to test hard disk or volume integrity:
Method 1:
1. Open a command prompt (Start - Run - type cmd)
2. Run the Chkdsk tool, which will detect and attempt to resolve the structure of the corrupted system files, by typing in the command prompt: chkdsk drive: / f

Method 2:
1. Double-click My Computer and select the disk you want checked.
2. On the File menu, select Properties.
3. Select the Tools tab.
4. On the Error-checking box, click Check Now.
5. In Check disk options, check the Scan for and attempt recovery of bad sectors. Option Automatically fix file system errors can also be checked.

If the volume you select is in use, a message will appear and ask whether to delay disk error checking until you restart the computer. After the restart, disk error checking runs and the volume being checked will not be used during the process. If you can not restart the computer because of an error, use safe mode or Recovery Console.

If you are not using the NTFS file system, and the system partition is formatted with the FAT16 file systems or FAT32 (File Allocation Table), the information LFN (Long File Name) can be lost if hard disk tools through a command prompt running MS-DOS. Command prompt that appears when using a startup floppy disk or when using the command prompt option in the boot multiple systems that use FAT16 or FAT32 partitions with Microsoft Windows 95 OEM Service Release 2 (OSR2), Microsoft Windows 98, or Microsoft Windows Millennium Edition (Me) which installed. Do not use tools other operating systems to Windows XP partition.

- Nonpaged pool memory might be depleted which can cause the system to stop. You can solve this problem by adding RAM, which will increase the quantity of nonpaged pool memory available to the kernel.

Related Articles