Tip & How-To about Microsoft Windows Vista Home Premium with Service Pack 1: Windows
General Troubleshooting of STOP Error Messages:
If you can’t find a specific reference to your problem, running through the following checklist stands a good chance of resolving the problem for you. This checklist is also usually the best approach to troubleshooting some specific Stop messages, such as 0x0A and 0x50.
Examine the “System” and “Application” logs in Event Viewer for other recent errors that might give further clues. To do this, launch EventVwr.msc from a Run box; or open “Administrative Tools” in the Control Panel then launch Event Viewer.
If you’ve recently added new hardware, remove it and retest.
Run hardware diagnostics supplied by the manufacturer.
Try enabling Windows Error reporting (if you are able to logon using safe mode)
Make sure device drivers and system BIOS are up-to-date.
If you’ve installed new drivers just before the problem appeared, try rolling them back to the older ones.
Open the box and make sure all hardware is correctly installed, well seated, and solidly connected.
Confirm that all of your hardware is on the http://www.microsoft.com/hcl/default.asp. If some of it isn’t, then pay particular attention to the non-HCL hardware in your troubleshooting
Check for viruses.
Investigate recently added software.
Powerflee the computer and try rebooting the computer.
Examine (and try disabling) BIOS memory options such as caching or shadowing.
Look for any hotfix released on Microsoft Site.
NOTE: When a STOP message occurs, Windows can create a debug file for very detailed analysis. To do this, it needs a workspace equal to the amount of physical RAM you have installed. If you resize your Win XP pagefile minimum to less than the size of your physical RAM, you will get an advisory message that your system may not be able to create a debugging information file if a STOP error occurs. My advice is to go ahead with this change if you want, but simply remember the limitation so that you can change it back if you need to troubleshoot STOP messages. Some general troubleshooting principles are suggested in the Resource Kit for approaching STOP messages overall.
It indicates a mismatch of thread and asynchronous procedure call (APC) indexes. The most common reason to see this message is if a file system has a mismatched number of KeEnterCriticalRegion compared to KeLeaveCriticalRegion.
It indicates that a device queue was expected to be busy, but was not.
It indicates a null of nonproper subset affinity.
It indicates an invalid data access trap
It indicates a problem with an owned mutex or a mutex with a process already attached.
It indicates a problem with an owned mutex or an unclean asynchronous procedure call (APC) state.
It indicates a level not within the software range
It indicates an attempt to remove a device not at the dispatch level.
It indicates an IRQL that was expected to be greater or equal, but was not.
It indicates an attempt to release an unowned spin lock
It indicates an attempt to release a thread by a mutex non-owner.
It indicates a trap from an unknown cause.
It indicates the thread reaper list is corrupted (the reaper list was signaled, but no threads were present on the list).
This problem occurs because a coding error in the Http.sys file causes stack corruption
This indicates that the last chance exception service was called from kernel mode.
This indicates that a failure occurred creating a handle to represent a client ID
This indicates that a failure occurred deleting a handle to represent a client ID
This indicates that a failure occurred while referencing an object by what should have been a referenced pointer.
Router incorrectly set the packet fragmentation bit on a browser broadcast datagram packet. The Tcpip.sys driver attempts to reassemble this packet and causes pool memory corruption.
It indicates that a kernel-mode asynchronous procedure call (APC) was found pending during thread termination. The first parameter is the address of the APC found pending during exit. The second parameter is the thread's APC disable count. And the third parameter is the current IRQL (interrupt request level). If the thread's disable count is non-zero, it is the source of the problem: the current IRQL should be 0. If it is not, a driver's cancellation routine returned at an elevated IRQL.
It indicates that quota was returned to a process, but that process was not using the amount of quota being returned.
This indicates a generic file system problem.
It indicates a FAT file system problem.
It indicates an NTFS file system problem
It indicates a named pipe file system problem.
This indicates a CD-ROM file system problem.
Posted by Hashir... on
Mar 04, 2011 | HP Photosmart 3210 Printer
Nov 03, 2010 | HP LaserJet CM1017 MFP All-In-One Color...
Oct 26, 2010 | HP LaserJet P3005d Printer
Jan 28, 2010 | Samsung (SH-M522C/BEBN) CD-RW/DVD-ROM...
1,091 people viewed this tip
Usually answered in minutes!