hensonpaul
asked on
7b stop error when booting xp from the installation disc
Hi there,
I have a PC which will only run in XP pro safe mode.
When I try to boot from the installaion cd it produces a 7b stop error after the initial loads.
In fact any bootable CD has this effect. (I tried W2K disc and ERD Commander)
I thought it may be a boot sector virus so I tried another hard drive, same error.
In despeartion I also changed the CD rom, same errors.
I have looked at a BIOS upgrade but this wont run from safe mode.
So, I am running out of ideas; please help?
Paul.
I have a PC which will only run in XP pro safe mode.
When I try to boot from the installaion cd it produces a 7b stop error after the initial loads.
In fact any bootable CD has this effect. (I tried W2K disc and ERD Commander)
I thought it may be a boot sector virus so I tried another hard drive, same error.
In despeartion I also changed the CD rom, same errors.
I have looked at a BIOS upgrade but this wont run from safe mode.
So, I am running out of ideas; please help?
Paul.
> 0x0000007B: INACCESSIBLE_BOOT_DEVICE <
<quote>
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.
<unquote>
"Windows Stop messages":
http://aumha.org/a/stop.htm
So you could also have a look at your Device drivers ...
<quote>
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.
<unquote>
"Windows Stop messages":
http://aumha.org/a/stop.htm
So you could also have a look at your Device drivers ...
There should be a dump of the state of your system at the time it crashes, and normally located in c:\windows\minidump\
or %systemroot%\minidump\
Can you paste the latest dump(s) in the "Attach Code Snippet" box and we'll take a look. You'll need to rename single minidump files first with a .txt extension, (do not rename the contents of the file). Alternatively zip them before attaching, and rename the .zip to .txt for the attaching (the upload).
You may need to disable auto restart:
Right click My Computer > Properties > Advanced > Startup and Recovery Settings and uncheck Automatically Restart.
If you see no minidump>
Enable Minidump's in Windows XP:
http://www.cakewalk.com/Support/ProblemReporter/minidump.asp
Absence of a Minidump could also be due to deteriorating motherboard capacitors, or an underated or problematic power supply.
or %systemroot%\minidump\
Can you paste the latest dump(s) in the "Attach Code Snippet" box and we'll take a look. You'll need to rename single minidump files first with a .txt extension, (do not rename the contents of the file). Alternatively zip them before attaching, and rename the .zip to .txt for the attaching (the upload).
You may need to disable auto restart:
Right click My Computer > Properties > Advanced > Startup and Recovery Settings and uncheck Automatically Restart.
If you see no minidump>
Enable Minidump's in Windows XP:
http://www.cakewalk.com/Support/ProblemReporter/minidump.asp
Absence of a Minidump could also be due to deteriorating motherboard capacitors, or an underated or problematic power supply.
May be useful>
"Troubleshooting Device Conflicts with Device Manager":
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q310126
Also see if this article is appropriate>
"STOP 0x0000007B: INACCESSIBLE_BOOT_DEVICE" error message when you start your computer from a WinPE CD-ROM or from a Windows Server 2003 CD-ROM by using a USB CD-ROM device:
http://support.microsoft.com/?kbid=839210&sd=RMVP
"Troubleshooting Device Conflicts with Device Manager":
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q310126
Also see if this article is appropriate>
"STOP 0x0000007B: INACCESSIBLE_BOOT_DEVICE" error message when you start your computer from a WinPE CD-ROM or from a Windows Server 2003 CD-ROM by using a USB CD-ROM device:
http://support.microsoft.com/?kbid=839210&sd=RMVP
normally i would say use XP boot CD and go into the recovery console to run CHKDSK /f to check for drive errors & Fixboot to sort partition faults, but if the boot CD function is out of action, Ultimate Boot CD might be your only hope to see if that works to test the rest of your hardware.
the fact that safe mode is working, is a good sign that all is not lost, but that would point to a driver/application loading in normal mode as causing the issue - you could try using MSCONFIG in safe mode (Start, Run and type MSCONFIG), 2nd last tab is the Start tba, which controls everything that loads during and after boot-up - try unticking everything, and build it up from there.
the fact that safe mode is working, is a good sign that all is not lost, but that would point to a driver/application loading in normal mode as causing the issue - you could try using MSCONFIG in safe mode (Start, Run and type MSCONFIG), 2nd last tab is the Start tba, which controls everything that loads during and after boot-up - try unticking everything, and build it up from there.
I think multi() means that the bios will do the initial loading from disk.
Also, I believe that when AHCI is enabled, the bios disables the
normal IDE I/O ports and enables different ones.
Since the bios knows how to read the disks with AHCI enabled,
it gets the initial boot started, but if the driver is not set up
properly in Windows, it will blue screen.
Also, I believe that when AHCI is enabled, the bios disables the
normal IDE I/O ports and enables different ones.
Since the bios knows how to read the disks with AHCI enabled,
it gets the initial boot started, but if the driver is not set up
properly in Windows, it will blue screen.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If evrything passes, I would try removing all of your component down to just the cpu and ram and see if that helps.