15 MOST COMMON STOP ERRORS / BSOD’s IN WINDOWS
STOP 0x000000D1 or DRIVER_IRQL_NOT_OR_EQUAL Probably the most common BSOD ! Occurs when a driver has illegally accessed a memory location while NT is operating at a specific IRQL. This is a driver coding error, akin to trying to access an invalid memory location. Recovery/Workaround:Usually none. But these may help KB810093 , KB316208 & KB810980.
STOP 0x0000000A or IRQL_NOT_LESS_OR_EQUAL A kernel-mode process or driver attempted to access a memory location without authorization. This Stop error is typically caused by faulty or incompatible hardware or software. The name of the offending device driver often appears in the Stop error and can provide an important clue to solving the problem. If the error message points to a specific device or category of devices, try removing or replacing devices in that category. If this Stop error appears during Setup, suspect an incompatible driver, system service, virus scanner, or backup program. This KB314063 may show you the direction.
STOP 0×00000050 or PAGE_FAULT_IN_NONPAGED_AREA A hardware driver or system service requested data that was not in memory. The cause may be defective physical memory or incompatible software, especially remote control and antivirus programs. If the error occurs immediately after installing a device driver or application, try to use Safe Mode to remove the driver or uninstall the program. For more information, see KB894278 & KB183169.
STOP 0x000000C2 or BAD_POOL_CALLER A kernel-mode process or driver attempted to perform an illegal memory allocation. The problem can often be traced to a bug in a driver or software. It is also occasionally caused by a failure in a hardware device. For more information, seeKB265879.
STOP OX000000ED or UNMOUNTABLE_BOOT_VOLUME Occurs if Windows if unable to access the volume containing the boot files. But if you get this message while updating TO Vista, check that you have compatible drivers for the disk controller and also re-check the drive cabling, and ensure that it is configured properly. If you’re reusing ATA-66 or ATA-100 drivers, make sure you have an 80-connector cable, and not the standard 40-connector IDE cable. See KB297185 and KB315403.
STOP 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED The Windows kernel detected an illegal or unknown processor instruction, often the result of invalid memory and access violations caused by faulty drivers or hardware devices. The error message often identifies the offending driver or device. If the error occurred immediately after installing a driver or service, try disabling or removing the new addition.
STOP 0×00000024 or NTFS_FILE_SYSTEM A problem occurred within the NTFS file-system driver. A similar Stop error, 0×23, exists for FAT32 drives. The most likely cause is a hardware failure in a disk or disk controller. Check all physical connections to all hard disks in the system and run Check Disk. KB228888 will help you.
STOP 0x0000002E or DATA_BUS_ERROR Failed or defective physical memory (including memory used in video adapters) is the most common cause of this Stop error. The error may also be the result of a corrupted hard disk or a damaged motherboard.
STOP 0x0000003F or NO_MORE_SYSTEM_PTES Your system ran out of page table entries (PTEs). The cause of this relatively uncommon error may be an out-of-control backup program or a buggy device driver. For more information, see KB256004.
STOP 0×00000077 or KERNEL_STACK_INPAGE_ERROR The system has attempted to read kernel data from virtual memory (the page file) and failed to find the data at the specified memory address. This Stop Error can be caused by a variety of problems, including defective memory, a malfunctioning hard disk, an improperly configured disk controller or cable, corrupted data, or a virus infection. For additional information, click KB228753.
STOP 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP Most likely due to a Hardware failure, like defective memory chips, mismatched memory modules, a malfunctioning CPU, or a failure in your fan or power supply are the probable reasons for this BSOD. Can also occur if you have overclocked your CPU. The message gives more details. For more help see KB137539.
STOP 0x000000D8 or DRIVER_USED_EXCESSIVE_PTES This indicated that a poorly written driver is causing your computer to request large amounts of kernel memory. Troubleshooting suggestions are identical to those found in the STOP 0X3F message. KB256004 will help you
STOP 0X000000EA or THREAD_STUCK_IN_DEVICE_DRIVER Could occur after you install a new video adapter or an updated (and poorly written) video driver. Replacing the video adapter or using a different video driver could help. See KB293078.
STOP 0XC000021A or STATUS_SYSTEM_PROCESS_TERMINATED Occurs if there is a serious security problem with Windows. A subsystem, such as Winlogon or the CSRSS is compromised;or due to a mismatch in system files; or if system permissions have been incorrectly modified. A common cause of this problem is some 3rd-party program. Try to identify any new program which you have installed and uninstall it.
STOP 0XC00000221 or STATUS_IMAGE_CHECKSUM_MISMATCH This indicates a damaged page file; or disk or file corruption; or a faulty hardware. The error will indicate the exact nature and the name of the damaged system file. You may have to use the Windows recovery Environment or a System Restore or Last Known Good Configuration to resolve this issue.
0 Comments:
Post a Comment