How to troubleshoot specific STOP Errors - Techist - Tech Forum

Go Back   Techist - Tech Forum > Computer Software > Microsoft Windows and Software
Click Here to Login
Reply
 
Thread Tools Display Modes
 
Old 12-09-2008, 09:05 AM   #1 (permalink)
Call me Mak or K
Mod Emeritus
 
KSoD's Avatar
 
Join Date: Sep 2004
Location: C:\
Posts: 35,647
Default How to troubleshoot specific STOP Errors

The general troubleshooting steps outlined in the previous section apply to all STOP errors. Details provided by specific STOP errors, however, can help you narrow down the cause of the error and get to a solution quickly. This section lists the most common STOP error codes, with suggested troubleshooting actions and external resources for additional information.

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.

STOP 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED

The Windows XP 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 0x00000024 or NTFS_FILE_SYSTEM

A problem occurred within the NTFS file-system driver. A similar STOP error, 0x23, 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 the Check Disk utility (Chkdsk.exe) using the instructions outlined in "Checking Disks for Errors," page 1237.

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 0x0000003B or SYSTEM_SERVICE_EXCEPTION

This is a Windows Executive character-mode STOP message. It indicates an exception was raised in a system service which was not handled by the system service. If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows.

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. Knowledge Base article 256004, "How to Troubleshoot 'STOP 0x0000003F' and 'STOP 0x000000D8' Error Messages in Windows 2000," (How to troubleshoot "STOP 0x0000003F" and "STOP 0x000000D8" error messages in Windows Server 2003, Windows XP, and Windows 2000), describes modifications to the Windows registry that may resolve the problem.

STOP 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA

A hardware driver or system service requested data that was not in memory, causing an exception error. 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.

STOP 0x00000074 or BAD_SYSTEM_CONFIG_INFO

This issue may occur if one or more of the Random Access Memory (RAM) modules that are installed in your computer is damaged or if the RAM configuration is incompatible. Remove 1 RAM module before each restart to find which is the bad module.

STOP 0x00000077 or KERNEL_STACK_INPAGE_ERROR


The system 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.

STOP 0x00000079 or MISMATCHED_HAL

No, this message has nothing to do with Hal, the paranoid computer in the classic film 2001: A Space Odyssey. Instead, this message identifies a mismatch between the Windows XP hardware abstraction layer (HAL) and the Windows XP system files. This error most often occurs on ACPI machines, when ACPI BIOS settings are changed unexpectedly. To disable or reenable ACPI features, reinstall Windows XP after making changes in the BIOS. For more details, read Knowledge Base article 237556, "How to Troubleshoot Windows 2000 Hardware Abstraction Layer Issues" (How to Troubleshoot Windows 2000 Hardware Abstraction Layer Issues

STOP 0x0000007A or KERNEL_DATA_INPAGE_ERROR

This STOP error has the same underlying cause as 0x77 errors: A page of kernel data was not found in virtual memory (the page file). This might be due to incompatible disk or controller drivers or hardware problems, such as an improperly terminated SCSI device, bad blocks on the hard disk, or a conflict with the BIOS or other firmware on a disk controller. Run the Windows XP Check Disk utility as detailed in "Checking Disks for Errors," page 1237. If the disk manufacturer has a more comprehensive disk utility, use it to do a thorough check of each physical hard disk on the system.

STOP 0x0000007B or INACCESSIBLE_BOOT_DEVICE

Windows XP was unable to locate the system partition or boot volume during the startup process. This problem may occur after repartitioning disks, adding new disks, or upgrading a disk controller and its drivers. In that case, entries in the Boot.ini file no longer point to the correct partitions. If the error occurs after upgrading the disk controller, verify that the new hardware is configured properly. Then start your system with the Windows XP CD, log on to the Recovery Console, and use the Bootcfg command to scan for available Windows installations and repair the Boot.ini file automatically.

STOP 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP

Hardware failure is the most common cause of this error. You are most likely to see this STOP error if you have defective memory chips, mismatched memory modules, a malfunctioning CPU, or a failure in your fan or power supply that causes overheating. The error is especially likely to occur on systems where the CPU has been tweaked to run past its rated speed, a process known as "overclocking." The first parameter immediately after this STOP error number identifies the specific cause of the error, as explained in Knowledge Base article 137539, "General Causes of STOP 0x0000007F Errors."

STOP 0x0000009F or DRIVER_POWER_STATE_FAILURE

A driver is currently in an inconsistent or invalid power state after shutting down, suspending to Standby or Hibernate mode, or resuming from either of those modes. This error is not limited to hardware drivers. It can also be caused by file-system filter drivers, such as those installed by antivirus programs, backup utilities, and remote control programs. The name of the offending driver file often appears in the STOP error. As a troubleshooting technique, try uninstalling unsigned hardware drivers or the software that uses the named driver. Knowledge Base article 266169, "How to Troubleshoot Problems with Standby Mode, Hibernate Mode, and Shutting Down Your Computer in Windows 2000," (How to Troubleshoot Problems with Standby Mode, Hibernate Mode, and Shutting Down Your Computer in Windows 2000), provides additional suggestions for resolving this type of error.

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. You can find detailed debugging instructions for this error in Knowledge Base article 265879, "How to Debug 'Stop 0xC2' or 'Stop 0x000000C2' Error Messages."

STOP 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL

This is one of the most common Stop errors. The error typically occurs when a driver tries to access an improper memory address. Check for unsigned drivers, and be especially suspicious of recently installed or updated antivirus programs, disk utilities, and backup programs, which may install a faulty file-system filter driver.
For more information see Knowledge Base articles 810093, 316208, 317216, and 810980, Windows Vista Inside Out - Redirect, Windows Vista Inside Out - Redirect, Windows Vista Inside Out - Redirect, and Windows Vista Inside Out - Redirect.

STOP 0x000000D8 or DRIVER_USED_EXCESSIVE_PTES

If a poorly written driver causes your computer to request large amounts of kernel memory, you may run out of page table entries (PTEs) and see this error message. The underlying cause of the error and troubleshooting suggestions are identical to those found in the STOP 0x3F message.

STOP 0x000000EA or THREAD_STUCK_IN_DEVICE_DRIVER

You may see this error message after you install a new video adapter or an updated (and poorly written) video driver that causes the system to pause indefinitely while waiting for the video hardware. To resolve the problem, replace the video adapter or use a different video driver.

STOP 0x000000ED or UNMOUNTABLE_BOOT_VOLUME

Windows XP was unable to gain access to the volume containing boot files. If you see this STOP message while attempting to upgrade a system to Windows XP, verify that you have compatible drivers for the disk controller and check the drive cabling to make sure it is configured properly. If you're using ATA-66 or ATA-100 drivers, make sure you have an 80-connector cable, not a standard 40-connector IDE cable. See the troubleshooting suggestions for STOP 0x7B errors as well. In some cases, this error will spontaneously correct itself after you restart your system.

STOP 0x000000F2 or HARDWARE_INTERRUPT_STORM

This hardware-related STOP error can be extremely frustrating to experience and even more vexing to troubleshoot. The Windows XP kernel detects an interrupt storm when a device fails to release an interrupt request (IRQ). This failure is usually caused by a poorly written device driver or a bug in firmware. To isolate the problem, try to determine which device is associated with the file name listed in the driver information section of the STOP message. Then use Device Manager or the System Information tool to identify other devices using the same IRQ, as described in "Viewing and Changing Resource Assignments," page 149. Remove all the devices identified as using that IRQ and add them back, one at a time, until the problem recurs.

STOP 0xC000021A or STATUS_SYSTEM_PROCESS_TERMINATED

This message indicates a serious security problem with Windows XP—a user-mode subsystem, such as Winlogon or the Client Server Runtime Subsystem (Csrss.exe), is compromised. The most common cause of this problem is a third-party program, and the solution is usually to remove that program. This error can also occur if a backup set has been partially restored,
causing a mismatch in system files, or if system permissions have been incorrectly modified so that the System account no longer has permission to access system files and folders.

STOP 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH

File or disk corruption problems (including a damaged page file) and faulty hardware are the most common causes of this type of STOP error. The message usually includes the name of the damaged file at the end of the symbolic error name or on a line by itself; you might be able to restore the file from the Windows XP CD using Recovery Console. Restoring the Last Known Good Configuration might also help to resolve this problem.

*NOTE*

For a full list of all STOP error code visit this MSDN Site.
__________________

__________________
I do not accept support questions via EMail, PM, IM or my G+ page!

Phone: LG Optimus G Pro
Running: Stock JB from LG with Nova Launcher

KSoD is offline   Reply With Quote
Old 12-09-2008, 09:16 AM   #2 (permalink)
Wizard Techie
 
Lexluethar's Avatar
 
Join Date: Jul 2008
Location: 127.0.0.1
Posts: 4,708
Send a message via AIM to Lexluethar
Default Re: How to troubleshoot specific STOP Errors

+1, that is freaking awesome Mak, this will be printed and on my fav's now!

Great work.
__________________

__________________
-Vista SME
Lexluethar is offline   Reply With Quote
Old 12-09-2008, 12:38 PM   #3 (permalink)
Chillin Techie
 
Join Date: Nov 2004
Location: USA
Posts: 11,861
Default Re: How to troubleshoot specific STOP Errors

bad_pool_header is related to your wireless card. disabling it or installing the latest driver or rolling back to the previous should fix it.

Bsod containing ati.sys or nv and sys in it, related to your video cards.

How to fix the UNMOUNTABLE_BOOT_VOLUME error.

MS post that 80, 40 pin things to waste people time. for one your bios will alert you if that happen and second, it would have never boot right in the first place.

UNMOUNTABLE_BOOT_VOLUME is corrupted file and or bad sectors on your hard disc

Use Spinrite 6.0.

GRC*|*Hard drive data recovery software**

I fix this error all of the time with it. spinrite tries to recover the bad sectors or jacked up data and if they can't they moved the data from that sector and then hide that sector from being accessed


now if spinrite takes a long time to run and you have a fast computer, you might want to buy another hdd and clone it over to there because the hdd sectors are badly damaged in that case. I fixed at least 50-100 computers this way. I had 2 instance where the hdd was to badly damage for spinrite to fix
__________________
The Ultimate Hard Drive Utility PowerMax 4.23. (It now has the ability to clean a Boot Sector virus on the quick erase option.)
The best browser Netscape 8
Have you accidently delete something? Look here (trial. the better one) and here(free)
EricB is offline   Reply With Quote
Old 12-09-2008, 07:58 PM   #4 (permalink)

Triforcer
 
Baez's Avatar
 
Join Date: Sep 2005
Location: Toronto, Canada
Posts: 6,987
Default Re: How to troubleshoot specific STOP Errors

Very nice list mate. You create this yourself or find it somewhere else?
__________________


Baez is offline   Reply With Quote
Old 12-09-2008, 09:32 PM   #5 (permalink)
Chillin Techie
 
Join Date: Nov 2004
Location: USA
Posts: 11,861
Default Re: How to troubleshoot specific STOP Errors

1.IRQL_NOT_LESS_OR_EQUAL in simple terms mean program conflict and or bad ram

2.MACHINE_CHECK-EXCEPTION mean your cloning program didn't clone the hdd properly. use another program

3.the error code "The bios in this system is not fully ACPI compliant. you must update your bios from the vendor or at hardware-update.com" and update your bios doesn't work

this means that you have issues in your advance power management (apm) in the bios. disable it if you can.
__________________
The Ultimate Hard Drive Utility PowerMax 4.23. (It now has the ability to clean a Boot Sector virus on the quick erase option.)
The best browser Netscape 8
Have you accidently delete something? Look here (trial. the better one) and here(free)
EricB is offline   Reply With Quote
Old 12-09-2008, 09:55 PM   #6 (permalink)
Call me Mak or K
Mod Emeritus
 
KSoD's Avatar
 
Join Date: Sep 2004
Location: C:\
Posts: 35,647
Default Re: How to troubleshoot specific STOP Errors

Quote:
Originally Posted by Baez View Post
Very nice list mate. You create this yourself or find it somewhere else?
Created from various sources that i have seen over the years.
__________________
I do not accept support questions via EMail, PM, IM or my G+ page!

Phone: LG Optimus G Pro
Running: Stock JB from LG with Nova Launcher

KSoD is offline   Reply With Quote
Old 12-09-2008, 10:25 PM   #7 (permalink)
Chillin Techie
 
Join Date: Nov 2004
Location: USA
Posts: 11,861
Default Re: How to troubleshoot specific STOP Errors

I start teaching myself how to figure them out about 4 years ago
__________________
The Ultimate Hard Drive Utility PowerMax 4.23. (It now has the ability to clean a Boot Sector virus on the quick erase option.)
The best browser Netscape 8
Have you accidently delete something? Look here (trial. the better one) and here(free)
EricB is offline   Reply With Quote
Old 12-09-2008, 10:49 PM   #8 (permalink)
Call me Mak or K
Mod Emeritus
 
KSoD's Avatar
 
Join Date: Sep 2004
Location: C:\
Posts: 35,647
Default Re: How to troubleshoot specific STOP Errors

I know most of them know. Between learning these and how to read minidump files has proven real useful.
__________________
I do not accept support questions via EMail, PM, IM or my G+ page!

Phone: LG Optimus G Pro
Running: Stock JB from LG with Nova Launcher

KSoD is offline   Reply With Quote
Old 12-12-2008, 02:19 AM   #9 (permalink)
Chillin Techie
 
Join Date: Nov 2004
Location: USA
Posts: 11,861
Default Re: How to troubleshoot specific STOP Errors

smrt.sys - address something something

encoder board conflict. I got this trying to run to 2 completely different tv tuners
__________________
The Ultimate Hard Drive Utility PowerMax 4.23. (It now has the ability to clean a Boot Sector virus on the quick erase option.)
The best browser Netscape 8
Have you accidently delete something? Look here (trial. the better one) and here(free)
EricB is offline   Reply With Quote
Old 12-12-2008, 03:31 AM   #10 (permalink)
Master Techie
 
eyeCpc's Avatar
 
Join Date: Apr 2007
Posts: 2,074
Default Re: How to troubleshoot specific STOP Errors

Here's some additional references to add here.

TROUBLESHOOTING
WINDOWS STOP MESSAGES
Troubleshooting Windows STOP Messages

Windows Error Advisor
Computer Support - Registry Errors - Windows Errors - Get Help today from the best Windows blog on the planet!

Windows XP Stop Errors
Windows XP Stop Errors

Troubleshooting Windows Explorer Errors
Troubleshooting Windows Explorer Errors - HelpWithWindows.com

When trying to find information on any specific error you'll often run into a list of sites trying to sell some registry program instead! I figured you could use something else here.
__________________

eyeCpc is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Decoding STOP Errors KSoD Official TF Tutorials 0 12-06-2008 11:06 PM
Help stop Uwe Boll Harper Off Topic Discussion 37 04-30-2008 12:18 AM
Frequent Windows STOP Errors Looby Laptops and Notebooks 5 02-06-2008 10:54 AM
Internet Issues/Errors, Networked Apps Failing Cunjo Microsoft Windows and Software 9 12-03-2007 03:26 AM
Major STOP errors, can't reinstall Windows, please help. putty Microsoft Windows and Software 3 09-20-2007 10:45 PM



Copyright 2002- Social Knowledge, LLC All Rights Reserved.

All times are GMT -5. The time now is 12:33 PM.


Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.