|
"Troubleshooting Guide for STOP Errors"
(Source:"Google-searching", http://support.microsoft.com/
& http://support.intel.com/)
Stop 0x0000000A or IRQL_NOTT LESS_OR_EQUAL
This error is typically caused by faulty or incompatible hardware or
software attempting to access a memory location without
authorization.
Suspect an incompatible driver, system service, virus scanner, or
backup program.
Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED
There is insufficient disk space on the drive on which you installed
Windows. There is an outdated or incompatible third-party driver (or
drivers) installed on your computer.
There are system BIOS incompatibilities
Free disk-space. Update drivers. BIOS settings /or Update
Stop 0x00000024 or NTFS_FILE_SYSTEM
The problem points to a NTFS file-system driver or a FAT32 driver
for 0x23
FAT32: Check all physical connections to hard disks, Rename the %SystemRoot%\System32\Drivers\Ntfs.sys
file to Ntfs.old, “chkdsk driveletter: /f “from
Recovery Console, rename %SystemRoot%\System32\Drivers\Ntfs.old to
Ntfs.sys, and then shut down and restart the computer.
NTFS (Win2K): Boot with Win98 BootDisk, insert the Windows 2000
installation CD-ROM change to the CD_ROM:\Support\Bootdisk folder,
and then run Makeboot.exe or
Makebt32.exe to create the four Windows 2000 Setup disks, Using
Notepad, modify the Txtsetup.sif file on the first Setup disk you
created (In the [FileSystems.Load] section,
locate the line that begins with "ntfs.", Insert a
semicolon (;) at the beginning of the line, as shown in the
following example: [FileSystems.Load]
fat =
fastfat.sys
;ntfs =
ntfs.sys
Save your changes.
Recovery Console, chkdsk driveletter: /p , exit.
Stop 0x0000002E or DATA_BUS_ERROR
This error may result from a corrupted hard disk, damaged MOBO, or
failed or defective physical memory
Stop 0x0000003F or NO_MORE_SYSTEM_PTES
This occurs when your system runs out of page table entries (PTEs)
Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA
This may be caused by defective physical memory or incompatible
software which caused a hardware driver or service request for data
that was not in memory.
If the error occurred after installing a device driver or
application, try using Safe Mode and removing the driver or program.
Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR
This error can be caused by defective memory, a malfunctioning HD,
an improperly configured disk controller or cable, corrupted data,
or a virus infection when an attempt was made to read kernel data
from virtual memory and failed to find the data at the memory
address.
Stop 0x00000079 or MISMATCHED_HAL
This error occurs when there is a mismatch between the hardware
abstraction layer (HAL) and the WinXP system files. It is often
experienced on ACPI machines when ACPI
BIOS settings are changed unexpectedly.
Reinstall WinXP after making changes in the BIOS
Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR
This error may be due to an incompatible disk or controller drivers
or hardware problems.
Run the windows XP check disk utility or use a more comprehensive
disk utility obtained from the disk manufacturer.
Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE
WinXP can not locate the system partition or boot volume. This error
may occur after repartition or upgrading of the disk controller. The
boot.ini file may no longer point to the correct partitions or the
hardware may not be configured properly
Try the Recovery Console and use the Boofdfg command to repair the
Boot.ini file.
Boot from WindowsXP CD and "Repair" the Windows.
Stop 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP
This error is most commonly caused by a hardware failure.
Defective or mismatched memory, a malfunctioning CPU, or overheating
can cause this failure
Stop 0x0000009F or DRIVER_POWER_STATE_FAILURE
This error is caused by an inconsistent or invalid power state after
shutting down, suspending to Standby or Hibernate modes. The name of
the offending driver file often appears in the Stop message.
Check to make sure that your computer and all installed devices are
on the Hardware Compatibility List (HCL). Check for drivers that are
not designed for use with Windows.
You can use the Sigverif.exe tool to do this. Check for driver
updates that may be available for your hardware. Update any software
that uses filter drivers (for example,
antivirus, remote control, and backup software). Remove any
non-critical devices and software to help isolate the device or
software that is causing the error. Install Windows in a new folder.
Add drivers one by one, and restart the computer after each
addition, to try to locate the driver that is causing the error.
Stop 0x000000C2 or BAD_POOL_CALLER
This occurs when a kernel-mode process or driver attempts to perform
an illegal memory allocation and is generally do to a driver or
software bug
Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL
(0x00000040, 0x00000002, 0x00000000, 0xfc96a9dc)
a) This common error occurs when a driver tries to access an
improper memory address.
b) This problem may occur because the OHCI endpoint is unable to
find the transfer descriptor in the list.
To resolve this problem, obtain the latest service pack for Windows
XP. Check for unsigned drivers, recently installed or updated
antivirus programs, disk utilities, and backup programs.
Stop 0x000000D8 or DRIVER_USED_EXCESSIVE_PTES
A poorly written driver may have caused your computer to request
large amounts of kernel memory and you may have run out of page
table entries (PTES).
Stop 0x000000EA or THREAD_STUCK_IN_DEVICE_DRIVER
A new video adapter or an updated but poorly written video driver
may cause your system to pause indefinitely while waiting for the
video hardware.
Remove the adapter or use a different driver
Stop 0x000000ED or UNMOUNTABLE_BOOT_VOLUME
WinXP was unable to gain access to the volume containing boot files.
If you are attempting an upgrade, verify that you have compatible
driver for the disk controller and check the drive cabling. For
ATA-66 and ATA-100 drivers make sure you have an 80 connector cable.
Try the Recovery Console and use the Boofdfg command to repair the
Boot.ini file.
Stop 0x000000F2 or HARDWARE_INTERRUPT_STORM
This error shows up when the WinXP kernel detects an interrupt storm
when a device fails to release an interrupt request (IRQ)
This is commonly caused by a poorly written device driver or a bug
in firmware. Try to isolate the problem by determining which device
is associated with the file name listed in the driver information.
Try removing all devices identified as using the IRQ and add them
back, one at a time.
Stop 0x000021A or STATUS_SYSTEM_PROCESS_TERMINATED
This indicates there is a serious security problem or a user mode
subsystem problem, such as Win logon or the Client Server Runtime
Subsystem (Csrss.exe)
The most common cause is a third party program which should be
removed or if a backup set has been partially restored, causing a
mismatch in sytem files or if the System account no longer has
permission to access the sytem 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. The message may contain
the name of the damaged file
Try using the Recovery Console, Last Known Good Configuration, or
re-installing WinXP
Stop 0xc000026C Þ Stop 0xc0000221 [Unable to load device driver]
".sys" file is missing or corrupted or/and User32.dll file
is missing or corrupted
a) From Recovery Console:
cd windows\system32\drivers
ren device_driver_name.sys device_driver_name.bak
copy "cd-rom":\i386 device_driver_name
b) From Recovery Console:
cd windows\system32
ren user32.dll user32.bak
expand cd-rom :\i386\user32.dl_ c:\windows \system32\user32.dll
STOP 0x00000074 or BAD_SYSTEM_CONFIG_INFO
When you try to start your computer from the Windows XP CD-ROM, you
may receive the following error message: The following file is
corrupted: toside.sys
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 the memory modules that are installed in your computer, but
leave enough RAM to start your computer and run Windows, and then
restart your computer. If the issue is not resolved, remove a
different memory module. Check the BIOS settings /or Update.
STOP 0x0000001D or STOP 0x000000A Stop Error Occurs in Ndis.sys
When you change the IPX frame type for your network connection from
Auto Detect to any other IPX frame type, you may receive a
"STOP 0x0000001D" or "STOP 0x000000A"
Stop error that occurs in Ndis.sys.
This problem may occur if you installed the NWLink IPX/SPX/NetBIOS
Compatible Transport protocol on your computer and you are using the
Driver Verifier Manager to troubleshoot your Ndis.sys driver's
Special Pool feature.
A supported fix is now available from Microsoft, but it is only
intended to correct the problem that is described in this article.
{http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS}
STOP 0x0000008E Error Message Occurs in Wdmaud.sys
Many components have advance logging or debugging features that are
used only by developers. In this particular situation, a logging or
debugging feature that was causing
the "STOP 0x0000008E" error message has been corrected.
To resolve this problem, obtain the latest service pack for Windows
XP
Stop 0xc0000218 UNKNOWN_HARD_ERROR or Stop: 0xc0000218 {Registry
File Failure}
The registry cannot load the hive (file):
\SystemRoot\System32\Config\SYSTEM or its log or alternate.
It is corrupt, absent, or not writable
This behavior can occur if a necessary registry hive file cannot be
loaded because the file is corrupted or missing. Registry files can
be damaged because of hard disk corruption or some other hardware
problem. This behavior can also occur if the driver has damaged the
registry data while loading into memory, or if the memory where the
registry is loading has a parity error. In the latter case, turn off
the external cache and check the memory chips.
Attempt to start the computer by using the "Load Last Known
Good" configuration. To do this, when Windows loads, press the
SPACEBAR when the Load Last Known Good message
appears. Restore the registry files by using Recovery
Console. Reinstall Windows into a separate folder, restore the
registry hives that are found in the
SystemRoot%\System32\Config folder [If Windows is stored on a
partition formatted with the FAT file system, you can restore the
files by using files from another computer
and copying the registry hive files into the Windows folder.],
Low-Level Format for “Bad-Sectors”
Stop 0xc0000244
If you turn on the CrashOnAuditFail option, Windows XP may stop
responding (hang) with stop code 0xC0000244 during the startup
process. This problem occurs if you turn on the CrashOnAuditFail
option and you are auditing for policy changes.
To resolve this problem, obtain the latest service pack for Windows
XP.
Stop 0xCA
If you insert two of the same SmartMedia cards in two of the same
Antec SmartCard PCMCIA readers in Windows XP, you may receive a
"Stop 0xCA" error message that indicates that a fatal Plug
and Play error has occurred. The computer may also stop responding
(hang). Atapi.sys does not make the Plug and Play IDs of the Antec
SmartMedia readers unique because they return the same serial number
for different
physical entities.
To resolve this problem, obtain the latest service pack for Windows
XP.
STOP 0x00000073 ((0x00000001, 0xc000017d, 0x00000002, 0xfc96fcc0)
CONFIG_LIST_FAILED
(Q330006)
This Stop error indicates that one of the core Windows system hives
(the SAM hive, the SECURITY hive, the SOFTWARE hive, or the DEFAULT
hive) cannot be linked in the Windows registry. However, this error
does not mean that the hive is damaged or that it was not loaded
successfully.
To troubleshoot this issue, use the four parameters that are
enclosed in brackets
{0xc000017d:STATUS_NO_LOG_SPACE} is one of the most typical
causes of this error.
This parameter indicates that Windows does not have enough hard disk
space available on the system drive. Free some disk space on your
system drive to resolve this issue.
{0xC000009A:STATUS_INSUFFICIENT_RESOURCES} is another typical
cause of this error.
This parameter means that there are not enough available resources
to complete the API, which most likely indicates that Windows does
not have enough memory (physical memory or page file memory). In
rare cases, this parameter may mean that the Windows kernel is
running out of paged-pool memory.
Stop 0x000000A5 When You Are Installing Windows XP
This behavior can occur if Windows has detected that the BIOS in the
computer is not fully compliant with Advanced Configuration and
Power Interface (ACPI).
To resolve this behavior, contact the manufacturer of your computer
to obtain a BIOS that is fully ACPI compliant. To work around this
behavior, manually install the Standard
PC hardware abstraction layer (HAL): Restart the computer to restart
Setup, when Setup starts again, press F7 (not F6) when you see the
"Press F6 if you need to install a
third-party SCSI or RAID driver" screen. Windows
automatically disables the installation of the ACPI HAL and installs
the Standard PC HAL
*** Fatal System Error: 0x000000C4 (0x00001003, 0xF7DE4F50,
0xA0C9AFE0, 0x809F6AE8)
This issue may occur if Norton Antivirus is installed on the
computer and the Deadlock Detection feature in Driver Verifier is
turned on. This is not a bug in Norton Antivirus. However if other
drivers hit this problem, it is probably a bug in that driver and
must be fixed. If you only turn off ioverifictation, you hide the
deadlock problem which may result in the system deadlocking in the
future.
To resolve this issue, turn off Deadlock Detection in Driver
Verifier (Click Start, click Run, and then type verifier. After
Driver Verifier Manager starts, click Display Existing Settings, and
then confirm that Deadlock Detection is turned on. Click Back. Click
Create Custom
Settings, and then click Next. Click Select Individual settings from
a full list, and then click Next. Click the settings that you want
to turn on, make sure the Deadlock Detection check box is not
selected, and then click Next.
Click the drivers that you want to verify, and then click Next or
Finish if you choose all drivers on your computer. Restart the
computer.
After you restore a full backup of a Windows XP installation, you
may receive the following Stop error message: STOP: 0xc0000139
Entry Point Not Found
The procedure entry point LdrEnumerateLoadedModules could not be
located in the dynamic link library Ntdll.dll.
After you receive this error message, the computer may automatically
restart. After this error message occurs, you may not be able to
start the computer in Safe mode.
"The procedure entry point LdrEnumerateLoadedModules could not
be located in the dynamic link library Ntdll.dll”
WinXP Repair (You must be able to start your computer from the
Windows XP CD to run Windows Setup). After the repair process has
been completed, install Windows XP SP1.
After you repair your Windows XP installation, you may have to
reactivate your copy of Windows XP.
This problem does not occur if you use the Automated System Recovery
(ASR) Wizard to create the backup, and then restore the backup by
using ASR.
After you start a computer where the video adapter has the TV tuner
or video capture feature, the computer may generate the following
error message on a blue screen:
STOP: 0x000000CE (0xHEXNUM1, 0xHEXNUM2, 0xHEXNUM3, 0xHEXNUM4) in
DXAPI.SYS
"DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS"
This issue can occur if a Windows 2000 version of a device driver
replaces the Windows XP version of the device driver. This
replacement can happen without your knowledge if you install DVD or
TV tuner software or programs from an older CD-ROM that installs
drivers that are not designed for Windows XP.
To work around this issue, reinstall updated DirectX device drivers
that are designed to work with Windows XP.
STOP: 0x0000009C (0x00000004, 0x00000000, 0xb2000000,
0x00020151)"MACHINE_CHECK_EXCEPTION"
System bus errors. Memory errors that may include parity or Error
Correction Code (ECC) problems. Cache errors in the processor or
hardware. Translation Lookaside Buffers (TLB)
errors in the processor. Other CPU-vendor specific detected hardware
problems. Vendor-specific detected hardware problems. This behavior
occurs because your computer processor detected an unrecoverable
hardware error and reported it to Windows XP. To do so, it used the
Machine Check Exception (MCE) feature of Pentium processors or the
Machine Check Architecture (MCA) feature of some Pentium Pro
processors. Running the processor or mainboard beyond its
specifications. Noisy power, overstressed power strips, outmatched
power supplies and failing power supplies can destabilize your
computer. Extreme thermal conditions caused by the failure of
cooling devices such as fans. Damaged memory, or memory that is not
the correct type for your computer. If you recently changed the
memory configuration, revert to the previous configuration to
determine what is wrong.
0x00000076 (PROCESS_HAS_LOCKED_PAGES)
0x000000CB (DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS)
This problem may occur if the redirector driver (Rdbss.sys) does not
release the locked user pages when the original input/output (I/O)
request packet (IRP) is canceled.
A supported fix is now available from Microsoft, but it is only
intended to correct the problem that is described in this article.
Only apply it to systems that are experiencing this specific
problem. This fix may receive additional testing. Therefore, if you
are not severely
affected by this problem, Microsoft recommends that you wait for the
next Windows 2000 service pack 5 or Windows XP SP2 that contains
this fix.
To resolve this problem immediately, contact Microsoft Product
Support Services to obtain the fix.
{The hotfix for Windows XP includes the following files: Mrxsmb.sys
& Rdbss.sys}
{The hotfix for Windows 2000 includes the following files:
Mrxsmb.sys & Rdbss.sys}
STOP: 0x0000006B (0x0000003A, 0x00000002, 0x00000000, 0x00000000)
PROCESS1_INITIALIZATION_FAILED
When you try to repair your Windows XP installation or when your
computer first restarts after you upgrade to Windows XP. This issue
may occur if the Roxio GoBack program is installed in your computer.
(The GoBack program is also included with the Norton SystemWorks
program)
To resolve this issue, cancel Windows XP Setup, remove GoBack, and
then restart
Windows XP Setup.
http://www.roxio.com/en/support/index.jhtml
http://www.symantec.com/techsupp/consumer.html
------------------------------------------------------
-From INTEL ("Troubleshooting for the IA Platform")-
To isolate the cause of the STOP error, do the following: Make sure
that you have the most current BIOS. Make sure that you have the
newest Windows Service Pack. Turn your PC off and take out all cards
except the video card and SCSI card if you are booting from the SCSI
drive. After the OS is installed, shut down the computer and plug in
one card at a time, boot the OS and installed the drivers for that
card. If you get the error message again, try to update the driver.
Check to make sure the system is not using non-parity memory in a
parity based system or mixing of parity/non-parity memory. Run
diagnostic software and test the RAM in the computer. Try removing
or swapping out
controllers, cards or other peripherals. Check to see if the RAM
modules are the same speed and that they are compatible with each
other. Disable memory caching. Replace
the RAM. Try a different motherboard. Try a different processor or
processors. The video driver is bad, corrupted, missing, or
disabled. Try starting your computer in safe mode or Enable VGA mode
and trying removing the driver and reinstalling the driver. Remove
any newly added hard drives or controllers. If you are using a SCSI
adapter, obtain the latest Windows driver form the adapter vendor.
In addition, try to disable sync negotiation, check termination and
check the SCSI Ids of the devices. If you are using IDE devices,
define the on-bard IDE part to Primary only. Check the
Master/Slave/Only settings for the IDE devices. Remove all Ide
devices except for the hard disk. Run CHKDSK. The file system could
be corrupt. If Windows cannot run CHKDSK, you might have to move the
drive to another computer running Windows 2000 or Windows XP and run
the CHKDSK command on that drive. Restart your computer. At the
startup screen, press F8 for the Advanced Startup option, and select
Last Known Good Configuration. Check for viruses on your computer.
The Hardware Abstraction Layer is incorrect for the machine. This
usually occurs when one machine mixes single and dual processor
configuration files. In Windows NT, restart the install and when the
message “Windows NT is examining the hardware” appears, press
F5. Choose your computer type from the list that appears and
continue with the installation. In Windows 2000, you should begin
the installation process again and install a clean copy of OS.
Repartition and reformat your hard drive from scratch and install
Windows. Remove any recently installed software, including backup
utilities or disk-intensive applications such as defragmenting,
virus protection and backup utilities. If the motherboard and hard
drive support Ultra DMA-66 or faster, enter the BIOS CMOS program
and disable the Ultra DMA and set the PIO to mode 4 for that
channel. Then after Windows is installed, try the Ultra DMA to see
if Windows is stable. Be sure to use the 40-pin, 80 conductor cable.
Make sure the SCSI controller and SCSI cable is connected correctly.
Check for Resource Conflicts for your SCSI card. The system has
multiple processors, but they are asymmetric in relation to one
another. To be symmetric, all processors must be the same type and
level (same type, cache size and frequency with compatible
stepping). In addition, make sure the processor supports
multiprocessing.
|
