I have a real strange situation here. My computer will boot normally into Win2k without 
a problem, but if I try to get into Safe Mode, it spits back a STOP 0x7B error: Inaccessible 
boot device.

I've read many threads about this error but none seem related to my issue. I've tried 
all the fixes and I've even uninstalled software according to those recommendations, 
and still this problem persists.

What happens exactly is that I will attempt a safe mode boot and Windows loads the 
file list up to mup.sys, then I get the bsod with the stop message.

My hardware:
Abit NF7-S2 (nForce2 chipset, AWARD bios)
Athlon XP 3200+
2x 512mb Corsair RAM
Radeon 9800 Pro AGP
AverMedia TV tuner PCI
Sound Blaster Live 5.1
HDD Seagate SATA (boot disk)
HDD Fujitsu IDE
LiteOn CD/DVD RW
Floppy drive
PS/2 keyboard and mouse
Thermaltake 500W PSU

[Reply or follow-up to this message]

Hi Kev:

When you say "I've read many threads about this error . . . "
can we assume you've read the MICROSOFT thread about this
problem, and applied MicroSoft's recommended fix?

http://support.microsoft.com/kb/824288

Jerry

[Reply or follow-up to this message]

No; by "this problem" I meant the one that I actually described, STOP 0x7B, which 
is different from 0x1E. As well, my DFS client is on as per the default, so there's 
no connection to the issue the kb article is describing. And, I don't suspect a problem 
with the mup.sys file itself, but rather with whatever happens after loading it.

But yes, I have read several kb articles related to 0x7B and none of them provided 
a working solution -- most are about general boot problems -- my problem is that 
my computer boots fine EXCEPT in safe mode, and I believe the solution will be somehow 
related to that fact.

[Reply or follow-up to this message]

If you had to use the F6 option to load SATA drivers when you installed W2K, then 
your SATA drive won't be able to boot into safe mode.  The driver that W2K uses is 
a generic one that won't be looking for the non-native controller that most motherboards 
manufacturers were putting on their boards when SATA capability was added.  Not all 
are yet adding SATA as a native capability into the chipset, so that using the F6 
option to load additional drivers wouldn't be necessary.

To get safe more to work, you would have to have the expertise of modifying Windows 
to look for the driver for the SATA controller, instead of the old WIndows default 
driver normally used in safe mode.

Finally, as system files/drivers complete loading, they will be listed on-screen. 
 MUP.SYS isn't the problem.  It is the file/driver that is trying to load after that, 
that will be the problem.  Generally it is video or other hardware that will be the 
problem.

If you had loaded W2K onto the PATA drive controller instead of the SATA, I would 
venture to say that you wouldn't be having this issue.  If you didn't have to use 
F6 for loading SATA drivers, there can still be an issue with the SATA controller 
and the generic driver that will cause the problem also..  :-(







On Tuesday, November 20, 2007 at 6:47 am, kev wrote:

>I have a real strange situation here. My computer will boot normally into Win2k 
without 

>a problem, but if I try to get into Safe Mode, it spits back a STOP 0x7B error: 
Inaccessible 

>boot device.

>

>I've read many threads about this error but none seem related to my issue. I've 
tried 

>all the fixes and I've even uninstalled software according to those recommendations, 

>and still this problem persists.

>

>What happens exactly is that I will attempt a safe mode boot and Windows loads the 

>file list up to mup.sys, then I get the bsod with the stop message.

>

>My hardware:

>Abit NF7-S2 (nForce2 chipset, AWARD bios)

>Athlon XP 3200+

>2x 512mb Corsair RAM

>Radeon 9800 Pro AGP

>AverMedia TV tuner PCI

>Sound Blaster Live 5.1

>HDD Seagate SATA (boot disk)

>HDD Fujitsu IDE

>LiteOn CD/DVD RW

>Floppy drive

>PS/2 keyboard and mouse

>Thermaltake 500W PSU 

[Reply or follow-up to this message]

Dealing with Unwanted Spyware and Parasites

Click Here




http://aumha.org/a/stop.htm



 Are you a wood worker ?,if so  Click Here






On Tuesday, November 20, 2007 at 9:31 am, Jerry wrote:

>Hi Kev:

>

>When you say "I've read many threads about this error . . . "

>can we assume you've read the MICROSOFT thread about this

>problem, and applied MicroSoft's recommended fix?

>

>http://support.microsoft.com/kb/824288

>

>Jerry
 

[Reply or follow-up to this message]

Unlike everybody else, I'm not going to requote. Boot to your windows CD, just as if you were going to install windows, but instead of making a new installation, choose to Repair an existing installation. This will 99.995% fix this problem.

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum