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.
Anti-Virus Software.
Software incompatiblity.
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.
0x00000001: APC_INDEX_MISMATCH
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.
0x00000002: DEVICE_QUEUE_NOT_BUSY
It indicates that a device queue was
expected to be busy, but was not.
0x00000003: INVALID_AFFINITY_SET
It indicates a null of nonproper subset
affinity.
0x00000004: INVALID_DATA_ACCESS_TRAP
It indicates an invalid data access
trap
0X00000005: INVALID_PROCESS_ATTACH_ATTEMPT
It indicates a problem with an owned mutex or a mutex with a process already
attached.
0x00000006: INVALID_PROCESS_DETACH_ATTEMPT
It indicates a problem with an
owned mutex or an unclean asynchronous procedure call (APC) state.
0X00000007: INVALID_SOFTWARE_INTERRUPT:
It indicates a level not within
the software range
0x00000008: IRQL_NOT_DISPATCH_LEVEL
It indicates an attempt to remove a
device not at the dispatch level.
0x00000009: IRQL_NOT_GREATER_OR_EQUAL
It indicates an IRQL that was
expected to be greater or equal, but was not.
0x00000010: SPIN_LOCK_NOT_OWNED
It indicates an attempt to release an
unowned spin lock
0x00000011: THREAD_NOT_MUTEX_OWNER
It indicates an attempt to release a
thread by a mutex non-owner.
0x00000012: TRAP_CAUSE_UNKNOWN
It indicates a trap from an unknown cause.
0x00000013: EMPTY_THREAD_REAPER_LIST
It indicates the thread reaper list is corrupted (the reaper list was
signaled, but no threads were present on the list).
0x00000014: CREATE_DELETE_LOCK_NOT_LOCKED
This problem occurs because a
coding error in the Http.sys file causes stack corruption
0x00000015:LAST_CHANCE_CALLED_FROM_KMODE
This indicates that the last
chance exception service was called from kernel mode.
0x00000016: CID_HANDLE_CREATION
This indicates that a failure occurred
creating a handle to represent a client ID
0x00000017: CID_HANDLE_DELETION
This indicates that a failure occurred
deleting a handle to represent a client ID
0x00000018: REFERENCE_BY_POINTER
This indicates that a failure occurred
while referencing an object by what should have been a referenced pointer.
0x00000019: BAD_POOL_HEADER
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.
0x00000020: KERNEL_APC_PENDING_DURING_EXIT
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.
0x00000021: QUOTA_UNDERFLOW
It indicates that quota was returned to a
process, but that process was not using the amount of quota being returned.
0x00000022: FILE_SYSTEM
This indicates a generic file system problem.
0x00000023: FAT_FILE_SYSTEM
It indicates a FAT file system problem.
0x00000024: NTFS_FILE_SYSTEM
It indicates an NTFS file system problem
0x00000025: NPFS_FILE_SYSTEM
It indicates a named pipe file system
problem.
0x00000026: CDFS_FILE_SYSTEM
This indicates a CD-ROM file system problem.
×