Microsoft KB Archive/130801

= Common Causes of STOP Messages 0x00000077 and 0x0000007A =

Article ID: 130801

Article Last Modified on 2/20/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows XP Professional
 * Microsoft Windows XP Home Edition
 * Microsoft Windows NT Advanced Server 3.1
 * Microsoft Windows NT Server 3.5
 * Microsoft Windows NT Server 3.51
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT Workstation 3.1
 * Microsoft Windows NT Workstation 3.5
 * Microsoft Windows NT Workstation 3.51
 * Microsoft Windows NT Workstation 4.0 Developer Edition
 * Microsoft Windows NT Advanced Server 3.1

-



This article was previously published under Q130801



SUMMARY
STOP Messages 0x00000077 and 0x0000007A are related kernel traps that are caused when the operating system tries to load a page into memory from the paging file on the hard disk, but cannot access the page because of either a software or hardware failure.

If you experience this issue more than one time, contact your computer or hard disk vendor.



MORE INFORMATION
The following are all common causes of STOP Messages 0x00000077 and 0x0000007A:


 * The paging file contained a bad block.
 * If the page file is on a SCSI device, the trap could have been caused by improper termination.
 * Bad cabling from hard disk to controller.
 * An error on the disk controller.
 * Running out of non-paged pool resources on the server.

Frequently, the cause of these traps can be determined from the second of the 4 hexadecimal parameters included in the first line of the STOP Message. Value       Meaning --  --- 0xC0000008   STATUS_INVALID_HANDLE, an invalid HANDLE was specified.

0xC000009A  STATUS_INSUFFICIENT_RESOURCES, caused by lack of non-paged pool.

0xC000009C  STATUS_DEVICE_DATA_ERROR, generally due to bad block on the drive.

0xC000009D  STATUS_DEVICE_NOT_CONNECTED, bad or loose cabling, termination, or controller not seeing drive.

0xC000016A  STATUS_DISK_OPERATION_FAILED, also caused by bad block on the drive.

0xC0000185  STATUS_IO_DEVICE_ERROR, caused by improper termination or bad cabling on SCSI devices. These codes are the most common and the ones for which specific causes have been determined. For information about other possible status codes that may be returned, see the NTSTATUS.H file, which is included in the MSDN Development Platform DDK.

Additional query words: prodnt 0x7a 0x77

Keywords: kbother KB130801

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.