SYMPTOMS
When you first restart your computer during the upgrade to Windows XP or when
you start Windows XP, you may receive the following error message, where
aaaaaaaa, bbbbbbbb, cccccccc, and dddddddd are hexadecimal numbers that may
vary:
STOP 0x000000ED (0xaaaaaaaa,0xbbbbbbbb,0xcccccccc,0xdddddddd)
UNMOUNTABLE_BOOT_VOLUME
NOTE: If you receive this error message when you restart the computer for the
first time during an upgrade to Windows XP, your original operating system
still works correctly. In some cases, a message appears on the BIOS report
screen that states that the wrong cable is in use, but you may not see this
message on computers that have a fast startup time.
CAUSE
This behavior can occur if either of the following conditions is true:
Your computer uses an Ultra Direct Memory Access (UDMA) hard disk controller,
and the following conditions are true:
You use a standard 40-wire connector cable to connect the UDMA drive to the
controller instead of the required 80-wire, 40-pin cable.
The basic input/output system (BIOS) settings are configured to force the
faster UDMA modes.
The file system is damaged and cannot be mounted.
RESOLUTION
To resolve this behavior, use the appropriate method.
UDMA Controller
If your computer uses a UDMA hard disk controller, use the following
procedures:
Replace the 40-wire cable with an 80-wire UDMA cable.
In the BIOS settings for your computer, load the 'Fail-Safe' default
settings, and then reactivate the most frequently used options such as USB
Support.
Damaged File System
If the second parameter (0xbbbbbbbb) of the Stop error is 0xC0000032, then
the file system is damaged.
If this is the case, restart the computer to the Recovery Console, and then
use the chkdsk /r command to repair the volume. After you repair the volume,
check your hardware to isolate the cause of the file system damage.
To do this, use the following steps:
Start your computer with the Windows startup disks, or with the Windows
CD-ROM if your computer can start from the CD-ROM drive.
When the Welcome to Setup screen appears, press R to select the repair
option.
If you have a dual-boot or multiple-boot computer, select the Windows
installation that you want to access from the Recovery Console.
Type the administrator password when you are prompted to do so.
NOTE: If no administrator password exists, press ENTER.
At the command prompt, on the drive where Windows is installed, type chkdsk
/r, and then press ENTER.
At the command prompt, type exit, and then press ENTER to restart your
computer.For additional information about how to use the Recovery Console in
Windows XP, click the article number below to view the article in the
Microsoft Knowledge Base:
314058 Description of the Windows XP Recovery Console
If this procedure does not work, repeat it and use the fixboot command in
step 5 instead of the chkdsk /r command.
STATUS
This behavior is by design.
MORE INFORMATION
The purpose of this behavior is to prevent potential data loss due to the use
of an incorrect IDE cable for the faster UDMA modes or due to continued
access to a drive on which the file system is damaged.
Note that a variety of issues can cause file system damage, from faulty
hardware to software configuration problems or viruses. You can run Chkdsk /r
at a command prompt to resolve the file system damage, but you may lose some
data.
----------------------------------------
SYMPTOMS
If you are running Windows 2000, you may receive the following error message:
STOP 0x0000001A (parameter, parameter, parameter, parameter)
MEMORY_MANAGEMENT
For example:
Stop 1A (0x00000001, 0x00000043, 0x00024893, 0xffffffff)
The first parameter is 1, therefore the subtype is "The fork clone block
reference count is corrupt. Only occurs on checked builds."
Everything else, must be examined individually.
CAUSE
This issue can indicate the existence of a general memory-management problem.
The error message that is mentioned in the "Symptoms" section of this article
is a Windows 2000 Executive character-mode STOP error message.
RESOLUTION
To resolve this issue, use the appropriate method:
If this is the first time you have started the computer after you install new
hardware, remove the hardware and restart your computer.
View the following Microsoft Hardware Compatibility List Web site to verify
that the hardware and its drivers are compatible with Windows 2000:
http://www.microsoft.com/hcl/default.asp
For more information about your hardware, contact the manufacturer of your
hardware.
If you are installing Windows 2000 for the first time, verify that your
computer meets the Windows 2000 system requirements, including the amount of
RAM and disk space that are required to install the operating system.
If Windows 2000 is loaded and no new hardware has been installed, restart
your computer with the recovery options set to create a dump file. If the
error message that is mentioned in the "Symptoms" section of this article
continues to appear, select the Last Known Good option when you restart your
computer. If there is no Last Known Good configuration, try to use the
Emergency Repair Disk (ERD).
For additional information about Emergency Repair Disks, click the article
number below to view the article in the Microsoft Knowledge Base:
231777 How to Create an Emergency Repair Disk in Windows 2000
For additional information about the Last Known Good configuration and other
Windows 2000 boot options, click the article number below to view the article
in the Microsoft Knowledge Base:
202485 Description of Safe Boot Mode in Windows 2000
++++++++++++++++++++++++++++++++
Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL
The Stop 0xA message indicates that a kernel-mode process or driver attempted
to access a memory location to which it did not have permission, or at a
kernel interrupt request level (IRQL) that was too high. A kernel-mode
process can access only other processes that have an IRQL lower than, or
equal to, its own. This Stop message is typically due to faulty or
incompatible hardware or software.
Interpreting the Message
This Stop message has four parameters:
Memory address that was improperly referenced.
IRQL that was required to access the memory.
Type of access (0x00000000 = read operation, 0x00000001 = write operation).
Address of the instruction that attempted to reference memory specified in
parameter 1.
If the last parameter is within the address range of a device driver used on
your system, you can determine which device driver was running when the
memory access occurred. You can typically determine the driver name by
reading the line that begins with:
**Address 0xZZZZZZZZ has base at <address>- <driver name>
If the third parameter is the same as the first parameter, a special
condition exists in which a system worker routine, carried out by a worker
thread to handle background tasks known as work items, returned at a higher
IRQL. In that case, some of the four parameters take on new meanings:
Address of the worker routine.
Kernel interrupt request level (IRQL).
Address of the worker routine.
Address of the work item.
Resolving the Problem
The following suggestions are specific to Stop 0xA errors. For additional
troubleshooting suggestions that apply to all Stop errors, see "Stop Message
Checklist" later in this appendix.
A Stop 0xA message might occur after installing a faulty device driver,
system service, or firmware. If a Stop message lists a driver by name,
disable, remove, or roll back the driver to correct the problem. If disabling
or removing drivers resolves the issues, contact the manufacturer about a
possible update. Using updated software is especially important for
multimedia applications, antivirus scanners, and CD mastering tools.
A Stop 0xA message might also be due to failing or defective hardware. If a
Stop message points to a category of devices (video or disk adapters, for
example), try removing or replacing the hardware to determine if it is
causing the problem.
If you encounter a Stop 0xA message while upgrading to Windows XP
Professional, the problem might be due to an incompatible driver, system
service, virus scanner, or backup. To avoid problems while upgrading,
simplify your hardware configuration and remove all third-party device
drivers and system services (including virus scanners) prior to running
setup. After you have successfully installed Windows XP Professional, contact
the hardware manufacturer to obtain compatible updates. For more information
about simplifying your system for troubleshooting purposes, see "
Troubleshooting Concepts and Strategies" and "Troubleshooting Startup" in
this book.
For more information about Stop 0xA messages, see the Microsoft Knowledge
Base link on the Web Resources page at
http://www.microsoft.com/windows/reskits/webresources. Search using keywords
winnt, 0x0000000A, and 0xA.
++++++++++++++++++++++++++++++++++++++++++++++++++
Error Message:
STOP: 0x00000026 (parameter, parameter, parameter, parameter)
CDFS_FILE_SYSTEM
Explanation:
This is a Windows 2000 Executive character-mode STOP message. This indicates
a CD-ROM file system problem.
User Action:
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 2000. For information about the hardware, contact the supplier.
If you are installing Windows 2000 for the first time, check the Windows 2000
system requirements, including the amount of RAM and disk space required to
load the operating system. Also, check the Hardware Compatibility List to
verify that the system can run Windows 2000. If Windows 2000 is loaded and no
new hardware has been installed, reboot with recovery options set to create a
dump file. If the message continues to appear, select the Last Known Good
option when you reboot. If there is no Last Known Good configuration, try
using the Emergency Repair Disk. If you do not have an Emergency Repair Disk,
contact your technical support group.
++++++++++++++++++++++++++++++++++++++++++++++
Stop 0xC2 or BAD_POOL_CALLER
The Stop 0xC2 message indicates that a kernel-mode process or driver
incorrectly attempted to perform memory operations in the following ways:
By allocating a memory pool size of zero bytes.
By allocating a memory pool that does not exist.
By attempting to free a memory pool that is already free.
By allocating or freeing a memory pool at an IRQL that was too high.
This Stop message is typically due to a faulty driver or software.
Interpreting the Message
Table C.5 describes the information provided by Stop 0xC2 messages. The value
of the first parameter indicates the type of violation (see the Description
column) and determines the meaning of the next three parameters.
Table C.5 Parameter Listing for Stop Message 0xC2
Parameter 1 Parameter 2 Parameter 3 Parameter 4 Description
0x00000000 This value is always 0 The pool type being allocated The pool tag
being used The caller is requesting a zero byte pool allocation
0x00000001, 0x00000002, or 0x00000004 Pointer to pool header First part of
pool header contents This value is always zero Pool header has been corrupted
0x00000006 Reserved Pointer to pool header Pool header contents Attempt to
free a memory pool that was already freed
0x00000007 Reserved Pointer to pool header This value is always zero Attempt
to free a memory pool that was already freed
0x00000008 Current IRQL Pool type Size of allocation Attempt to allocate pool
at invalid IRQL
0x00000009 Current IRQL Pool type Address of pool Attempt to free pool at
invalid IRQL
0x00000040 Starting address Start of system address space This value is
always zero Attempt to free usermode address to kernel pool
0x00000041 Starting address Physical page frame Highest physical page frame
Attempt to free a non-allocated nonpaged pool address
0x00000042 or 0x00000043 Address being freed This value is always zero This
value is always zero Attempt to free a virtual address that was never in any
pool
0x00000050 Starting address Start offset in pages from beginning of paged
pool Size in bytes of paged pool Attempt to free a non-allocated paged pool
address
0x00000099 Address being freed This value is always zero This value is always
zero Attempt to free pool with invalid address or corruption in pool header
0x0000009A Pool type Size of allocation in bytes Allocation's pool tag
Attempt to allocate must-succeed
Resolving the Problem
The following suggestions are specific to Stop 0xC2 errors. For additional
troubleshooting suggestions that apply to all Stop errors, see "Stop Message
Checklist" later in this appendix.
A Stop 0xC2 message might occur after installing a faulty device driver,
system service, or firmware. If a Stop message lists a driver by name,
disable, remove, or roll back the driver to correct the problem. If disabling
or removing drivers resolves the issues, contact the manufacturer about a
possible update. Using updated software is especially important for
multimedia applications, antivirus scanners, DVD playback, and CD mastering
tools.
A Stop 0xC2 message might also be due to failing or defective hardware. If a
Stop message points to a category of devices (such as disk controllers, for
example), try removing or replacing the hardware to determine if it is
causing the problem.
If you encounter a Stop 0xC2 message while upgrading to Windows XP
Professional, the problem might be due to an incompatible driver, system
service, virus scanner, or backup. To avoid problems while upgrading,
simplify your hardware configuration and remove all third-party device
drivers and system services (including virus scanners) prior to running
setup. After you have successfully installed Windows XP Professional, contact
the hardware manufacturer to obtain compatible updates. For more information
about simplifying your system for troubleshooting purposes, see "
Troubleshooting Concepts and Strategies" and "Troubleshooting Startup" in
this book.
For more information about Stop 0xC2 messages, see the Microsoft Knowledge
Base link on the Web Resources page at
http://www.microsoft.com/windows/reskits/webresources. Search using keywords
winnt, 0x000000C2, and 0xC2.
++++++++++++++++++++++++++
