If you are a victim of BLUE SCREEN/ Death of computer. The main reason is hardware and software mutual incompatibility. So you should do first these steps if after that problem still persists go on error specific solution.
General recommendations:
a.) Remove or replace any new hardware you have installed.
b.) Try to remove antivirus which you have installed. If anyhow you are able to reach and access appwiz.cpl “Add or Remove Programs”. If you have CD/DVD ROM you put corresponding windows CD in that drive and while its installing the hardware settings during system setup just click SHIFT + F10. you will get access to command prompt. From there open control panel and you may restore your system or remove antivirus.
c.) It may caused by incorrect BIOS settings, so just reset your BIOS settings in that case.
d.) This problem may also due to RAM. So first remove your RAM and then again place it in its slot.
DRIVER_IRQL_NOT_LESS_OR_EQUAL or Stop 0x000000D1
This message indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error.
Possible Solutions:
This message can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error.
THREAD_STUCK_IN_DEVICE_DRIVER or Stop 0x000000EA
A device driver problem is causing the system to pause indefinitely. Typically, this problem is caused by a display driver waiting for the video hardware to enter an idle state. This might indicate a hardware problem with the video adapter or a faulty video driver.
Possible Solutions:
This message can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error
IRQL_NOT_LESS_OR_EQUAL or Stop 0x0000000A
kernel interrupt request level (IRQL). A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own. This Stop message is typically due to faulty or incompatible hardware or software.
Possible Solutions:
While upgrading to Windows XP, the problem might be due to an incompatible driver, system service, virus scanner, or backup. Go for General recommendations as above.
.
KMODE_EXCEPTION_NOT_HANDLED or Stop 0x0000001E
The Stop 0x1E message indicates that the Windows XP kernel detected an illegal or unknown processor instruction. This default Windows XP error handler typically intercepts these problems if error-handling routines are not present in the code itself.
Possible Solutions:
Stop 0x1E messages typically occur after installing faulty drivers or system services, or they can indicate hardware problems, such as memory and IRQ conflicts. If a Stop message lists a driver by name, disable, remove, or roll it back to correct the problem. If disabling or removing applications and drivers resolves the issue, contact the hardware manufacturer about a possible update.
Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.
NTFS_FILE_SYSTEM or Stop 0x00000024
The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to NTFS file system drives. A similar Stop message, 0x23, exists for the file allocation table (FAT16 or FAT32) file systems.
Possible Solutions:
To test hard disk or volume integrity
Method 1:
1. In the Run dialog box, in the Open box type:
cmd
2. Start the Chkdsk tool, which detects and attempts to resolve file system structural corruption. At the command prompt type:
chkdsk drive: /f
Method 2:
1. Double-click My Computer, and then select the hard disk you want to check.
2. On the File menu, click Properties.
3. Click the Tools tab.
4. In the Error-checking box, click Check Now.
5. In Check disk options, select the Scan for and attempt recovery of bad sectors check box. You can also select the Automatically fix file system errors check box.
If the volume you are checking is in use, a message asks whether you want to delay disk error checking until the next time you restart your computer. After you restart, disk error checking runs and the volume chosen is not available to run other tasks during this process. If you cannot restart the computer due to the error, use safe mode or Recovery Console.
This problem may also due to RAM. So add RAM memory may allow more space for paging and you may get rid of it.
DATA_BUS_ERROR or Stop 0x0000002E
The cause is typically 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 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.
Possible Solutions:
just do general recommendations (at top of post). If even problem persists
Go to service center or any hardware repair shop.
NO_MORE_SYSTEM_PTES or Stop 0x0000003F
This problem may be due to more memory allocation for kernal programs. Or due to system Page Table Entries (PTEs) are depleted or fragmented due to the system performing a large number of input/output (I/O) actions.
Possible Solutions:
Here you can increase the no. of Page Table Entries, for that you have to change in registry. The registry editor bypasses standard safeguards, allowing settings that can damage your system, or even require you to reinstall Windows. If you must edit the registry, back it up first...
To increase the number of PTEs allocated in the registry
1. In the Run dialog box, and in the Open box, type: regedit
2. In the registry editor, navigate to the subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
Session Manager\Memory Management.
3. Double-click on PagedPoolSize and SystemPages to view the value for each entry.
4. If PagedPoolSize is not zero, assign a value of 0.
5. If SystemPages is not zero, assign a value of 40000 for systems with 128 MB (or less) of memory, or 110000 for systems with 128 MB to 256 MB of memory. For systems with more memory, do not increase the SystemPages value above 110000 without contacting Microsoft technical support.
6. Click OK, and then close the registry editor.
7. Restart your computer.
PAGE_FAULT_IN_NONPAGED_AREA or Stop 0x00000050
Due to request of data that is not in memory. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages.
Possible Solutions:
If you added new hardware recently, 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.
Or you just disable or update your latest driver suit. You may choice to restore system.
KERNEL_STACK_INPAGE_ERROR or Stop 0x00000077
This message indicates that a page of kernel data requested from the paging (virtual memory) file could not be found or read into memory. This Stop message can also indicate disk hardware failure, disk data corruption, or possible virus infection.
Possible Solutions:
This problem is due to virtual memory, so restart you system may fix this problem. If still your system persists problem perform general recommendations (on top of post).
Still problem persists go for check of your motherboard of drives failure.
MISMATCHED_HAL or Stop 0x00000079
This message indicates that the hardware abstraction layer (HAL) and the kernel type for the computer do not match. This error most often occurs when ACPI firmware settings are changed. For example, you might install Windows XP on an x86-based computer with the firmware ACPI enable option enabled and later decide to disable it. This error can also result when mismatched single and multi-processor configuration files are copied to the system.
Possible Solutions:
Just don’t waste your time to again reset your setting, you better need to re-install OS.
KERNEL_DATA_INPAGE_ERROR or Stop 0x0000007A
Possible Solutions:
The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
INACCESSIBLE_BOOT_DEVICE or Stop 0x0000007B
Windows XP has lost access to the system partition or boot volume during the startup process. Installing incorrect device drivers when installing or upgrading storage adapter hardware cause this error.
It may be due to storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows XP Professional.
Possible Solutions:
If you know edit boot.ini file. Or go with recovery manager. Repair your OS will solve this problem.
UNEXPECTED_KERNEL_MODE_TRAP or Stop 0x0000007F
A condition that the kernel is not allowed to have or intercept (also known as a bound trap). Its due to software problems and Hardware failures.
Possible Solutions:
It is due to defective, malfunctioning, or failed memory hardware. So run diagnosis or repair system.
DRIVER_POWER_STATE_FAILURE or Stop 0x0000009F
Due to bad power setting of drives.
Possible Solutions:
so change the power setting. You may correct it from BIOS.
ATTEMPTED_WRITE_TO_READONLY_MEMORY or Stop 0xBE
Due to forced attempt to write on ReadOnly memory.
Possible Solutions:
Restart your system.
BAD_POOL_CALLER or Stop 0xC2
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.
• By allocating a memory pool that does not exist.
• By attempting to free a memory pool that is already free.
• By allocating or freeing a memory pool at an IRQL that was too high.
This Stop message is typically due to a faulty driver or software.
Possible Solutions:
This message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem
DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS or Stop 0x000000CE
This Stop messages indicates that a driver failed to cancel pending operations before exiting.
Possible Solutions:
This message can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error.
UNMOUNTABLE_BOOT_VOLUME or Stop 0x000000ED
The kernel mode I/O subsystem attempted to mount the boot volume and it failed. 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. In some cases, your system might appear to work normally after you restart.
Possible Solutions:
If using higher throughput ATA disks and controllers, those capable of data transfer rates above 33.3 megabytes per second, replace the standard 40-pin cable with an 80-pin cable. Using an 80-pin cable is optional for transfer rates up to and including 33.3 megabytes per second, but is mandatory for higher transfer rates. The additional grounded pins are required to avoid data loss.
Some firmware enables you to force higher transfer rates even when you are using the incorrect cable type. Your firmware might issue a warning but allow the startup process to proceed. Restore the default firmware setting for ATA cable detection.
STATUS_IMAGE_CHECKSUM_MISMATCH or Stop 0xC0000221
This Stop message indicates driver, system file, or disk corruption problems (such as a damaged paging file). Faulty memory hardware can also cause this Stop message to appear.
Possible Solutions:
You can use Driver Rollback or System Restore from safe mode, to restore a previous driver. You can also use Windows XP Professional recovery features such as the Last Known Good Configuration startup option, Backup, or Automated System Recovery to restore a previous working configuration. After restoring from backup media, you might need to reapply service packs or hotfixes, depending on when the backups were made.
if still problem persists re-install Operating system or go to repair center for diagnosis.
