STOP 0x0000007b Error

[David Russcol]

My computer is acting up, and it's really annoying me. Here's the short
version:

I had a working install of XP SP2, but System Restore was not working. I
figured a repair install couldn't hurt, so I used a MSDN SP2 XP CD to do
a repair install. After I did this, the system would, instead of
starting up, throw a BSOD with an 0x7b error (apparently
INACCESSIBLE_BOOT_DEVICE) before it gets to graphical startup. Now, it
goes to graphical startup for a split second before giving the same
error. I did not make any hardware changes or install or remove any
programs before this behavior started.

Here's the long version of things I tried:
Repairing, using a burned XP SP2 CD from MSDN, repeatedly and at various
times
Repairing, using a factory-made XP SP1 CD from MSDN, repeatedly and at
various times
Converted partition from NTFS to FAT32 using PartitionMagic
Copied hard drive to new store-bought hard drive
(Subsequent steps all take place on new drive)
Restored registry from old backup (caused it to go briefly to graphical
startup before throwing same BSOD)
Parallel XP install to different folder - worked fine
Copied registry from new, clean XP install to old install - worked, but
booted to clean install
Converted drive back to NTFS
Wiped drive (zeroed out from Linux LiveCD)
Copied files from backups from about a month ago (about everything
except the registry, which was from last July), and copied other files
other than the windows directory from old hard drive

None of this has helped. I still get the error. I have yet to try going
back to pure backups, but since I didn't restore files from the windows
directory I don't see how that could make a difference.

Does anyone have any suggestions for what might be causing this error,
or how I can fix it?

Thanks.

David

 

[Gerry Cornell]

David

Starting point:
http://aumha.org/win5/kbestop.htm

Can you please post the full text of the Stop Error message.

Disable automatic restart on system failure. This should help by
allowing time to write down the STOP code properly. Right click
on the My Computer icon on the Desktop and select Properties,
Advanced, StartUp and Recovery, System Failure and uncheck
box before Automatically Restart.

Do not re-enable automatic restart on system failure until you have
resolved the problem. Check for variants of the Stop Error message.

There will also be Error Reports in Event Viewer. Please post copies.

You can access Event Viewer by selecting Start, Administrative Tools,
Event Viewer. When researching the meaning of the error, information
regarding Event ID, Source and Description are important.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;308427&Product=winxp

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Double click the button and close Event
Viewer. Now start your message (email) and do a paste into the body of
the message. This will paste the info from the Event Viewer Error Report
complete with links into the message. Make sure this is the first paste
after exiting from Event Viewer.

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[David Russcol]

David

Starting point:
http://aumha.org/win5/kbestop.htm

Can you please post the full text of the Stop Error message.

Disable automatic restart on system failure. This should help by
allowing time to write down the STOP code properly. Right click
on the My Computer icon on the Desktop and select Properties,
Advanced, StartUp and Recovery, System Failure and uncheck
box before Automatically Restart.

Do not re-enable automatic restart on system failure until you have
resolved the problem. Check for variants of the Stop Error message.

There will also be Error Reports in Event Viewer. Please post copies.

You can access Event Viewer by selecting Start, Administrative Tools,
Event Viewer. When researching the meaning of the error, information
regarding Event ID, Source and Description are important.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;308427&Product=winxp

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Double click the button and close Event
Viewer. Now start your message (email) and do a paste into the body of
the message. This will paste the info from the Event Viewer Error Report
complete with links into the message. Make sure this is the first paste
after exiting from Event Viewer.

I've looked at the AumHa page before. I don't know the full error
message off the top of my head, but I do remember the following:
STOP 0x0000007B (0xXXXXXXXX, 0xC0000034, 0x00000000, 0x00000000). Maybe
the first parameter is the most important, I'm not at home right now but
I can look it up later.

I've already set it not to reboot on system failure. But, as Windows
does not start up under any circumstances (not even safe mode), I can't
get to Event Viewer. Is there a way to access that information from DOS,
Linux, or the Recovery Console? Would having a boot log help?

And by the way, I'm not using any fancy RAID drivers or anything.
Regular Intel (I think) IDE controller, plain hard drive, shouldn't
require any special drivers.

Thanks for your help.

David

 

[David Russcol]

I've looked at the AumHa page before. I don't know the full error
message off the top of my head, but I do remember the following:
STOP 0x0000007B (0xXXXXXXXX, 0xC0000034, 0x00000000, 0x00000000). Maybe
the first parameter is the most important, I'm not at home right now but
I can look it up later.

I've already set it not to reboot on system failure. But, as Windows
does not start up under any circumstances (not even safe mode), I can't
get to Event Viewer. Is there a way to access that information from DOS,
Linux, or the Recovery Console? Would having a boot log help?

And by the way, I'm not using any fancy RAID drivers or anything.
Regular Intel (I think) IDE controller, plain hard drive, shouldn't
require any special drivers.

Thanks for your help.

David

OK, so the first part of the error is 0xF79C4528.

I'd appreciate any help you could give.

David

 

[GPG]

OK, so the first part of the error is 0xF79C4528.

I'd appreciate any help you could give.

David

I have the same thing, but the first part of my error is 0xFA2CB528

GPG

 

[Gerry Cornell]

David

What make and model of computer?

Have you thought of trying a Repair Install?

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[David Russcol]

David

What make and model of computer?

Have you thought of trying a Repair Install?

It's a Dell Dimension 4100 desktop. Pentium III, 384 MB RAM. A repair
install was what caused the problem in the first place, but I have done
it several times since.

David