error 0x0000007B on installation

  • Thread starter Thread starter eminescu
  • Start date Start date
E

eminescu

Hello,

I'm stuck with the error in the subject trying to install XP prof *sp2*;
here's my hardware:

motherboard: asus m2n4-sli with nForce chipset
cpu athlon: 64 3500+ AM2
hd: maxtor 300GB PATA primary master (no RAID)
graphic card: sapphire ati 1600 pro
RAM: 512*2MB dual channel

and the step I followed:

1. I installed XP in a brand new 30GB partition (disc left
unpartitioned elsewhere) *without* loading any driver with F6
2. I receive a BSOD with 0x0000007B after the first restart (i.e. before
reaching the graphical installation)
3. same as point 1 but this time loading the two drivers provided by
the MB manufacturer (nVidia storage and nVidia RAID, even if I don't
have RAID)
4. first reboot and graphical install went fine
5. next reboot I receive the same error as point 2

Looks like that at the second reboot windows forgot the drivers I put with
F6 (is it because it tries to use its own?)

I upgraded the BIOS to the latest, and checked the RAM with memtest86.

Any suggestion?


Thanks

-
Matteo Lanza
 
eminescu said:
Hello,

I'm stuck with the error in the subject trying to install XP prof *sp2*;
here's my hardware:
Click to expand...

Is that the complete and total content of the error message? Just
error 0x0000007B with nothing else mentioned whatsoever?

We need the complete *verbatim* text of the actual error message,
including any text comments, parameter codes, and/or file or module
names.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
error 0x0000007B with nothing else mentioned whatsoever?

We need the complete *verbatim* text of the actual error message,
including any text comments, parameter codes, and/or file or module
names.
Click to expand...

Basically it's similar to this one:

http://www.juliuzz.com/shot.jpg

except mine is in italian. There is no file/module name, only the four
parameters beetween parentheses, which is the only thing that probably
changes from the screenshot (unfortunately I'm not near the computer
right now).
To reproduce the BSOD I have to press F8 and select the "disable reboot
on error" option, otherwise the system simply reboots.

An interesting fact is that the HD led stays completely off for a few
seconds while windows boots (tries to), then before the BSOD it
switches on and stays "fixed", even after reboot. I have to "manually"
switch the computer off and on, otherwise the system wouldn't even pass
the BIOS start phase.
Good luck
Click to expand...

I'll need it!! :-)
 
eminescu said:
Basically it's similar to this one:

http://www.juliuzz.com/shot.jpg

except mine is in italian. There is no file/module name, only the four
parameters beetween parentheses, which is the only thing that probably
changes from the screenshot (unfortunately I'm not near the computer
right now).
To reproduce the BSOD I have to press F8 and select the "disable reboot
on error" option, otherwise the system simply reboots.

An interesting fact is that the HD led stays completely off for a few
seconds while windows boots (tries to), then before the BSOD it
switches on and stays "fixed", even after reboot. I have to "manually"
switch the computer off and on, otherwise the system wouldn't even pass
the BIOS start phase.
Click to expand...

The "reboot on error" setting is, in my opinion, worse than useless on
a home or small business computer although it might repeat might have
some value in a large corporate or network environment where there is
a full time professional computer support staff.

I therefore suggest that you shut it off permanently. Use Control
Panel - System - Advanced and click on the Settings button in the
Startup and Recovery (bottom) section. In the Startup and Recovery
window click on the checkbox for "automatically restart to clear it
then click on Apply and OK as needed to exit.

The following general comments regarding STOP 0x0000007B:
INACCESSIBLE_BOOT_DEVICE are from MVP Jim Eshelman's web page for STOP
errors at http://www.aumha.org/win5/kbestop.htm
"Windows lost access to the system partition or boot volume during the
startup process. Typical causes: Installing incorrect device drivers
when installing or upgrading storage adapter hardware, or a virus."

Some additional information about this error can be found at
http://msdn.microsoft.com/library/d..._7ad69779-4ee3-42da-8543-4b22946f8aad.xml.asp

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
Back
Top