Stop error 0x0000007A - Tilted Forum Project Discussion Community

Drugbug · 05-25-2004, 12:31 AM

Hi

A client of mine recently ugraded to Windows 2000 from Windows 98. The OS installed perfectly, but as soon as Office 2003 Setup is started, all hell breaks loose. I get the stop error 0x00000007A. I am assuming that it might be attempting to write to unidentified bad sectors on the hdd.

What do you all think of this?

Latch · 05-25-2004, 03:59 AM

Client? hmm.. that means we get a share of the consulting fee :P

M$ KB comes up w/:

Quote:

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.

Read the link for more.

Drugbug · 05-26-2004, 10:18 PM

Thanks. It turned out to be a faulty harddrive.

05-25-2004, 12:31 AM	#1 (permalink)
Drugbug Upright	Stop error 0x0000007A Hi A client of mine recently ugraded to Windows 2000 from Windows 98. The OS installed perfectly, but as soon as Office 2003 Setup is started, all hell breaks loose. I get the stop error 0x00000007A. I am assuming that it might be attempting to write to unidentified bad sectors on the hdd. What do you all think of this?

05-26-2004, 10:18 PM	#3 (permalink)
Drugbug Upright	Thanks. It turned out to be a faulty harddrive.