Giáo trình Bảo trì và khắc phục sự cố phần cứng máy tính

n in 
pool header. 
Address 
being freed 
This value 
is always 
zero 
This value is 
always zero 
0x0000009
A 
Attempt to 
allocate was 
marked 
MUST_SUCCE
ED. 
Pool type Size of 
allocation 
in bytes 
Allocation's 
pool tag 
0x0000009
B 
The current 
thread 
attempted to 
allocate a pool 
with a tag of 
Pool type Size of 
allocation 
in bytes 
Caller’s 
address 
Bảo trì và khắc phục sự cố phần cứng máy tính Tài liệu dành cho học viên 
VSIC Education Corporation – Tác giả: Huỳnh Lê Bảo Thiện 72
zero. 
0x0000009
C 
The current 
thread 
attempted to 
allocate a 
pool with a 
tag of "BIG." 
Pool type Size of 
allocation 
in bytes 
Caller’s 
address 
Troubleshooting the Stop 0xC2 Error 
The following sections list the most common sources for this Stop error and suggest some 
troubleshooting solutions. 
Driver, system services, and firmware issues 
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/DVD mastering 
tools. 
Hardware issues 
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. 
Software compatibility issues 
If you encounter a Stop 0xC2 message while upgrading to Windows Server 2003, the 
problem might be caused by 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 Server 2003, contact the 
hardware manufacturer to obtain compatible updates. 
Stop 0xCE or 
DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_O
PERATIONS 
This Stop message indicates that a driver failed to cancel pending operations, deferred 
procedure calls, and worker threads before exiting. 
Interpreting the Stop 0xCE Message 
This Stop message has four parameters, as listed in Table 10.26. 
Bảo trì và khắc phục sự cố phần cứng máy tính Tài liệu dành cho học viên 
VSIC Education Corporation – Tác giả: Huỳnh Lê Bảo Thiện 73
Table 10.26 Parameters for the Stop 0xCE Message 
Parameter Description 
Parameter 1 Memory address referenced. 
Parameter 2 • Type of access: 
• 0x00000000 = read operation 
• 0x00000001 = write operation 
Parameter 3 If non-zero, the address of the instruction that 
referenced the incorrect memory location. 
Parameter 4 This parameter is reserved (set aside for future use). 
Troubleshooting the Stop 0xCE Error 
The following section describes the most common source for this Stop error and suggests 
a troubleshooting solution. 
Driver and system services issues 
Stop 0xCE messages can occur after installing faulty drivers or system services. If a driver 
is listed by name, disable, remove, or roll back that driver to confirm that this resolves the 
error. If it does, contact the manufacturer about a possible update. Using updated software 
is especially important for backup programs, multimedia applications, antivirus scanners, 
DVD playback, and CD/DVD mastering tools. 
Stop 0xD1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL 
The Stop 0xD1 message indicates that the system attempted to access pageable memory 
using a kernel process IRQL that was too high. Drivers that use improper addresses 
typically cause this error. The problems that cause Stop 0xD1 messages share similarities 
with those that generate Stop 0xA errors, in that they can be caused by invalid memory 
and access violations. 
Interpreting the Stop 0xD1 Message 
This Stop message has four parameters, as shown in Table 10.27. 
Table 10.27 Parameters for the Stop 0xD1 Message 
Parameter Description 
Parameter 1 Memory referenced 
Parameter 2 IRQL at time of reference 
Parameter 3 • Type of access: 
• 0x00000000 = read operation 
• 0x00000001 = write operation 
Parameter 4 Address that referenced memory 
Troubleshooting the Stop 0xD1 Error 
The following section describes the most common source for this Stop error and suggests 
a troubleshooting solution. 
Driver and system services issues 
Stop 0xD1 messages can occur after you install faulty drivers or system services. If a 
driver is listed by name, disable, remove, or roll back that driver to confirm that this 
Bảo trì và khắc phục sự cố phần cứng máy tính Tài liệu dành cho học viên 
VSIC Education Corporation – Tác giả: Huỳnh Lê Bảo Thiện 74
resolves the error. If it does, contact the manufacturer about a possible update. Using 
updated software is especially important for backup programs, multimedia applications, 
antivirus scanners, and CD/DVD mastering tools. 
Stop 0xD8 or DRIVER_USED_EXCESSIVE_PTES 
The Stop 0xD8 message typically occurs if your computer runs out of PTEs because of a 
driver that requests large amounts of kernel memory. 
Interpreting the Stop 0xD8 Message 
Depending on the configuration of your system, the number of parameters returned might 
vary, as shown in Table 10.28. 
Table 10.28 Parameters for the Stop 0xD8 Message 
Parameter Description 
Parameter 1 If this parameter has a nonzero value, it contains the 
name of the driver that caused the Stop error. 
Parameter 2 If the first parameter has a nonzero value, this 
parameter contains the number of PTEs used by the 
driver that is causing the error. 
Parameter 3 This parameter represents the total free system 
PTEs. 
Parameter 4 This parameter represents the total system PTEs. 
Troubleshooting the Stop 0xD8 Error 
For suggestions about resolving problems related to inadequate PTEs, see “Stop 
0x0000003F or NO_MORE_SYSTEM_PTES” earlier in this chapter. 
Stop 0xEA or THREAD_STUCK_IN_DEVICE_DRIVER 
A device driver problem is causing the operating system to pause indefinitely. Typically, 
this problem is caused by a display driver waiting for the video hardware to enter an idle 
state. This might indicate a hardware problem with the video adapter or a faulty video 
driver. 
Interpreting the Stop 0xEA Message 
This Stop message has four parameters, as listed in Table 10.29. 
Table 10.29 Parameters for the Stop 0xEA Message 
Parameter Description 
Parameter 1 Pointer to the thread object that is caught in an infinite loop. 
Parameter 2 Pointer to a DEFERRED_WATCHDOG object. This pointer 
is useful when you use a kernel debugger to find out more 
information about this problem. 
Parameter 3 The name of the driver that caused the Stop error. 
Parameter 4 When viewing the Stop message in the kernel debugger, this is 
the cumulative number of times the 0xEA bug check was 
intercepted. When viewing the Stop message on the computer 
screen, this parameter is always 0x00000001. 
Bảo trì và khắc phục sự cố phần cứng máy tính Tài liệu dành cho học viên 
VSIC Education Corporation – Tác giả: Huỳnh Lê Bảo Thiện 75
Troubleshooting the Stop 0xEA Error 
The following section describes the most common source for this Stop error and suggests 
a troubleshooting solution. 
Driver and system services issues 
Stop 0xEA messages can occur after you install faulty drivers (especially video drivers) or 
system services. If a driver is listed by name, disable, remove, or roll back that driver to 
confirm that this resolves the error. If it does, contact the manufacturer about a possible 
update. Using updated software is especially important for backup programs, multimedia 
applications, antivirus scanners, DVD playback, and CD/DVD mastering tools. 
Stop 0xED or UNMOUNTABLE_BOOT_VOLUME 
The kernel mode I/O subsystem failed in its attempt to mount the boot volume. This error 
might also occur during an upgrade to Windows Server 2003 on operating systems that 
use higher-throughput ATA disks, or controllers with incorrect cabling. In some cases, 
your operating system might appear to work normally after you restart. 
Interpreting the Stop 0xED Message 
This Stop message has two parameters, as listed in Table 10.30. 
Table 10.30 Parameters for the Stop OxED Message 
Parameter Description 
Parameter 1 Device object of the boot volume. 
Parameter 2 Status code from the file system describing why it 
failed to mount the volume. 
Parameter 3 This parameter is reserved (set aside for future use). 
Parameter 4 This parameter is reserved (set aside for future use). 
Troubleshooting the 0xED Stop Error 
The following section describes the most common source for this Stop error and suggests 
a troubleshooting solution. 
Disk controller and throughput issues 
Verify that your computer firmware, disk controller, and cabling support the storage 
system. For example, using an 80-wire cable is optional for transfer rates up to and 
including 33.3 megabytes per second, but is mandatory for higher transfer rates. The 
additional grounded pins are required to prevent data loss. Verify that the cables and hard 
disks are connected according to the hard disk manufacturer’s specifications. 
Some firmware enables you to force higher transfer rates even when you are using the 
incorrect cable type. Your firmware might issue a warning but allow the startup process to 
proceed. To avoid problems, do not change the default firmware settings for ATA cable 
detection. 
Other suggestions 
Problems that cause Stop 0xED errors might also cause Stop 0x6B and Stop 0x7B errors. 
For more information about Stop 0x7B errors, see “Stop 0x0000007B or 
INACCESSIBLE_BOOT_DEVICE” earlier in this chapter.