The Stop 0x7A message indicates that a page of kernel data was not found in the paging (virtual memory) file and could not be read into memory. The causes of this might be incompatible disk or controller drivers, outdated firmware, or a hardware problem.
Interpreting the Stop 0x7A MessageThe parameters for this Stop message have two sets of meanings. The value of parameter 1 determines the meaning of parameters 2, 3, and 4.
If parameter 1 is 0x1, 0x2, or 0x3, the parameters should be interpreted as shown in Table 10.16.
This Stop message has four parameters, as listed below.
Parameters for the Stop 0x7A Message
Parameter Description
Parameter 1 • Lock type value
• 0x00000001
• 0x00000002
• 0x00000003 or PTE address
Parameter 2 Error status (typically an I/O status code).
Parameter 3 If the lock type is 0x00000001 or 0x00000002, this parameter represents the current process.
If the lock type is 0x00000003, this parameter represents the virtual address.
Parameter 4 The virtual address that could not be paged into memory.
If parameter 1 does not have a value of 0x1, 0x2, or 0x3, the parameters listed in Table 10.17 apply.
Secondary Parameters for the Stop 0x7A Message
Parameter Description
Parameter 1 PTE address
Parameter 2 Error status (typically an I/O status code)
Parameter 3 Virtual address
Parameter 4 The virtual address that could not be paged into memory
Frequently, the cause of this error can be determined from the I/O status code (parameter 2).
Common Status Codes for Parameter 2
Status Code Description
0xC000000E: STATUS_NO_SUCH_DEVICE Indicates defective or loose data or power cables, a problem with SCSI termination, or improper controller or disk configuration.
0xC000009A:
STATUS_INSUFFICIENT_RESOURCES Indicates a lack of nonpaged pool resources.
0xC000009C:
STATUS_DEVICE_DATA_ERROR Indicates bad blocks (sectors) on the hard disk.
0xC000009D:
STATUS_DEVICE_NOT_CONNECTED Indicates defective or loose data or power cables, a problem with SCSI termination, or improper controller or disk configuration.
0xC000016A:
STATUS_DISK_OPERATION_FAILED Indicates bad blocks (sectors) on the hard disk.
0xC0000185:
STATUS_IO_DEVICE_ERROR Indicates improper termination, defective storage controller hardware, defective disk cabling, or an IRQ conflict.
For information about other possible status codes that might be returned, see the file Ntstatus.h of the Windows Server 2003 Driver Development Kits (DDK). For more information about the DDK, see the Driver Development Kit link on the Web Resources page at
http://www.microsoft.com/windows/reskits/webresources.Troubleshooting the Stop 0x7A ErrorThe following sections list the most common sources for this Stop error and suggest some troubleshooting solutions.
Hard disk hardware or driver issuesStop 0x7A can be caused by bad sectors in the virtual memory paging file, disk controller error, virus infection, or memory hardware problems. If parameters 1 and 3 are 0, the stack signature in the kernel stack is missing, an error typically caused by defective hardware. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk, check for cabling and termination issues. An I/O status code of 0xC000009C or 0xC000016A indicates that the requested data could not be found. You can try to correct this by restarting the computer.
If a problem with disk integrity exists, Autochk, a program that attempts to mark bad disk sectors as defective so that they are not used in the future, starts automatically. If Autochk fails to run, you can manually perform the integrity check yourself by following the instructions to run Chkdsk provided in “Stop 0x00000024 or NTFS_FILE_SYSTEM” earlier in this FORUM.
Memory hardware issuesAnother cause of Stop 0x7A messages is defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.
Firmware and driver issuesCheck the hardware manufacturer’s Web site for updates to disk adapter firmware or drivers that improve compatibility. Verify that your firmware, disks, and controller support the same set of advanced features, such as higher transfer rates. If necessary, select a slower transfer rate if an update is not yet available. Consult your hardware or device documentation for more information.
Important
You can install disk controller drivers that are not present on the Windows Server 2003 operating system CD by responding to the following message shortly after starting setup: “Press F6 if you need to install a third party SCSI or RAID driver.” When you see this message, press F6, and when prompted, provide the appropriate storage controller driver (ATA or SCSI) supplied by the manufacturer.
Motherboard issuesThe problem might also be caused by cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
