Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.
JSI Tip 0733. Resolving STOP 0x00000077 and 0x0000007A messages.
Jerold Schulman
September 25, 1998
1 Min Read
The subject STOP messages are related to the inability of Windows NT to load a pagefile record into memory due to either a software or hardware failure. They possible causes are:
- A bad block.
- Improper termination on a SCSI device.
- Bad cabling from the controller to the disk.
- A disk controller error.
- Exhausting the non-paged pool resources.
The value of the second hexadecimal paramater may help you pinpoint the actual cause of the error:
Value | M e a n i n g |
|---|---|
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. |
If you know someone who has the MSDN DDK, the NTSTATUS.H file has additional status codes.
About the Author
You May Also Like
.png?width=700&auto=webp&quality=80&disable=upscale)