XP SP2: Only Safe Mode doesn't work - normal system start works perfect!?

[Oliver Breitfelder]

Hello guys!

Strange problem with my XP SP2 Pro: Although my normal Windows mode works
perfectly I get a BSOD as soon as I try to start this Windows installation
in Safe Mode.

The STOP error 0x7B appears (0xF78A6524, 0xC0000034, 0x0, 0x0). Referring to
the MS Knowledge Base and other resources on the web this could be caused by
missing or wrong IDE controller drivers. Unfortunately logging of this error
is impossible (no bootlog.txt is created). The only way of narrowing the
problem is: The BSOD happens immediately after the Safe Mode start-up
routine asked for cancelling the loading of drivers sptd and a347bus. By the
way cancelling doesn't solve the BSOD problem...

Checking a bootlog protocol of a normal system start (no safe mode) the
drivers following in the start-up process after sptd and a347bus would be:

pci.sys
isapnp.sys
ohci1394.sys
C:\WINDOWS\System32\DRIVERS\1394BUS.SYS
ACPI.sys
pciide.sys
C:\WINDOWS\System32\DRIVERS\PCIIDEX.SYS
intelide.sys
MountMgr.sys
ftdisk.sys
dmload.sys
dmio.sys
PartMgr.sys

So this really could be some kind of ACPI/IDE problem. Any hint on how to
solve this BSOD in safe mode or even any clou to find out the exact files
causing the problem? I already cleaned all hidden drivers/devices in device
manager and I also cleaned up the windows services. Thanks in advance.


Bye Oliver

 

[Gerry]

Oliver

This is not a boys only club!

Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms795508.aspx

0x0000007B: INACCESSIBLE_BOOT_DEVICE
(Click to consult the online MSDN article.)
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.
Source: http://aumha.org/a/stop.htm

Have you taken the precaution of backing up important data files?

How certain are you that the problem is specific to Safe Mode as these
types of problem are the other way round.

Is there any chance you could have disturbed the cabling to the hard
drive?

What is the computer make and model? How old is it?

Do you have a Windows XP CD and does that CD include the SP2 update?

Try running HD Tune(freeware).

Download and run it and see what it turns up.
http://www.hdtune.com/

Select the Info tabs and place the cursor on the drive under Drive
letter and then double click the two page icon ( copy to Clipboard )
and copy into a further message.

Select the Health tab and then double click the two page icon ( copy to
Clipboard ) and copy into a further message. You can also do a full
surface scan with HD Tune.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[nass]

Hello guys!

Strange problem with my XP SP2 Pro: Although my normal Windows mode works
perfectly I get a BSOD as soon as I try to start this Windows installation
in Safe Mode.

The STOP error 0x7B appears (0xF78A6524, 0xC0000034, 0x0, 0x0). Referring to
the MS Knowledge Base and other resources on the web this could be caused by
missing or wrong IDE controller drivers. Unfortunately logging of this error
is impossible (no bootlog.txt is created). The only way of narrowing the
problem is: The BSOD happens immediately after the Safe Mode start-up
routine asked for cancelling the loading of drivers sptd and a347bus. By the
way cancelling doesn't solve the BSOD problem...

Checking a bootlog protocol of a normal system start (no safe mode) the
drivers following in the start-up process after sptd and a347bus would be:

pci.sys
isapnp.sys
ohci1394.sys
C:\WINDOWS\System32\DRIVERS\1394BUS.SYS
ACPI.sys
pciide.sys
C:\WINDOWS\System32\DRIVERS\PCIIDEX.SYS
intelide.sys
MountMgr.sys
ftdisk.sys
dmload.sys
dmio.sys
PartMgr.sys

So this really could be some kind of ACPI/IDE problem. Any hint on how to
solve this BSOD in safe mode or even any clou to find out the exact files
causing the problem? I already cleaned all hidden drivers/devices in device
manager and I also cleaned up the windows services. Thanks in advance.


Bye Oliver

Hi Oliver,
It is mostly a Driver issue, a basic driver may be or the SCSI cable not
faulty or wrong type.

Missing [SysprepMassStorage] Section Causes STOP 0x7B Error Message on
Windows XP Sysprep Images
http://support.microsoft.com/kb/303786
<Quote::>
This problem may occur after the mass storage drivers are updated to newer
versions on an image that was created by using the System Preparation tool
(Sysprep) -pnp switch. The mass storage drivers are located in the
OemDriversPath as specified in the Sysprep.inf file.

The problem occurs because the -pnp switch only updates a temporary branch
in the registry that
Sysprep creates to mimic the devices that are installed.
The -pnp switch does not update the actual devices in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI registry subkey.
For example, when the –pnp switch is used with Sysprep, the LowerFilter
registry entry that is associated with the older driver is not removed.
Therefore, when you run the Setup program after you copy the image to the new
destination computer, the Setup program tries to load the drivers that are
defined in the LowerFilter registry entry, although the new drivers do not
support this functionality. Therefore, you receive a Stop 0x7B error.
</Quote::>

Try to run the chkdsk /r from the Recovery console and also the Fixmbr:
http://support.microsoft.com/kb/307654/
http://support.microsoft.com/kb/308041


Advanced troubleshooting for "Stop 0x0000007B" errors in Windows XP
http://support.microsoft.com/kb/324103

Run a thorough scan for malware and Viruses on your system.

Open a Notepad, customize or minimize to the taskbar as you will need it
later for this step to copy the error message on it.
Open a run command and type in:
eventvwr.msc click [OK] you will get the Event viewer control Panel.
click on each of these:
Application
System
Security
Look in the right Pane/window for error message with red (X) or Yellow
exclamation mark /!\ , double click each one to get more info about the
causer.
On the Event error properties message you will see:
Up Arrow
Down arrow
Two pages
Click on the two pages to copy the error message then bring up the Notepad
you opened earlier and right click on the first line and select Paste from
the list, this will paste the error message on a Notepad.
Please don't duplicate the error message one of each kind will be sufficient.
HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/kb/308427/en-us

Please we need just the error messages with Red (X) and don't repeat the
error, just one of each kind and post them back in your next post.

Lastly, try to download the Diagnostic tools from your Hard Drive
manufacturer and test the health of your HDD, it my be failing.
HTH.
nass

 

[Oliver Breitfelder]

Oliver

This is not a boys only club!

I am soo sorry: Hello to all the ladies, too! ;-)

Have you taken the precaution of backing up important data files?

Backups of data files exist.

How certain are you that the problem is specific to Safe Mode as these
types of problem are the other way round.

As certain as one can be, I'm afraid. :-( It only happens in Safe Mode. My
normal Windows mode runs absolutely perfect I just want to solve the problem
with Safe Mode.

Is there any chance you could have disturbed the cabling to the hard
drive?

Checked the cables, everythings fine (as far as I can see cable problems
would occur in normal mode, too, but they don't).

What is the computer make and model? How old is it?

Home built Intel E6700 / Asus P5K Dlx / 3GB RAM / 2x Samsung HDDs / 8800
GTS.

Do you have a Windows XP CD and does that CD include the SP2 update?

Yes, the system was once setup with slipstreamed SP2.

Try running HD Tune(freeware).

I checked it, Health is ok, all drive parameters are within normal range. I
am not convinced this could be a hardware problem. Also tried other
utilities - everything is ok with my HDDs.

I haven't used the Safe Mode for motnhs (because just not necessary) and as
normal mode is working flawlessly I didn't even expect a problem in Safe
Mode.

I am thinking of resetting IDE drivers in Windows and let the OS identify
chipset and drivers again. Would that be possible? This coulb possibly fix
Safe Mode, too.
I just want to find out what the difference in hardware support is when
starting normal or safe (means: which drivers are used in safe - others than
in normal mode?)?

Thanks for your help.

Bye Oliver

 

[Oliver Breitfelder]

Hi Oliver,
It is mostly a Driver issue, a basic driver may be or the SCSI cable not
faulty or wrong type.

Missing [SysprepMassStorage] Section Causes STOP 0x7B Error Message on
Windows XP Sysprep Images
http://support.microsoft.com/kb/303786

This info looks interesting although I am not using sysprep or images at
all. But it could be a hint to explore a certain direction. Only thing I
cannot understand is why normal mode works without any problems (writing
this message in normal mode). Only safe mode shows 7B error. Some driver
support seems to be different when booting up in Safe Mode - I must find out
what exactly is different...

Try to run the chkdsk /r from the Recovery console and also the Fixmbr:
http://support.microsoft.com/kb/307654/
http://support.microsoft.com/kb/308041

I'll do this now.

Run a thorough scan for malware and Viruses on your system.

System is clean.

Please don't duplicate the error message one of each kind will be
sufficient.
HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/kb/308427/en-us

Please we need just the error messages with Red (X) and don't repeat the
error, just one of each kind and post them back in your next post.

I checked all errors in event viewer. There were some minor driver issues
not connected to this problem. I solved all of these problems (means: event
viewer log is now clean of red Xs). Safe Mode still shows the 7B stop error.

Lastly, try to download the Diagnostic tools from your Hard Drive
manufacturer and test the health of your HDD, it my be failing.

HDDs are fine.

As this problems seems top be directly connected to IDE i think of resetting
all IDE devices and controllers in windows and let the OS identify them
again. Are there different IDE drivers loaded when starting safe than when
starting normal mode?

Thanks for your help.

Bye Oliver

 

[Oliver Breitfelder]

I also read that when using Safe Mode Windows XP bypasses all thrid party
IDE drivers and starts with it's own drivers. Perhaps that is the point to
work on: Where are the drivers for Safe Mode stored? Perhaps replacing them
with the working IDE drivers from normal mode could solve the BSOD
problem?!? Just a guess...


Bye Oliver

 

[Oliver Breitfelder]

PROBLEM (partly) SOLVED!

Thanks to Gerry & nass for their help! After further research on the web I
found a "golden" hint WHY normal mode works and Safe Mode doesn't:

The registry branch "SafeBoot" that should be located under
HKEY_LM\SYSTEM\CurrentControlSet\Control\ is completely missing!

I imported this branch from another XP Pro installation and safe mode works
now! Unfortunately completely importing the "SafeBoot" branch brings other
problems with Windows themes, VGA drivers, audio drivers and so on... So I
must somheow try to rebuild the SafeBoot branch based on the working normal
mode. Will be quiet a lot of work and i don't know if this can be done
(half-) automatically.


Bye Oliver

 

[nass]

PROBLEM (partly) SOLVED!

Thanks to Gerry & nass for their help! After further research on the web I
found a "golden" hint WHY normal mode works and Safe Mode doesn't:

The registry branch "SafeBoot" that should be located under
HKEY_LM\SYSTEM\CurrentControlSet\Control\ is completely missing!

I imported this branch from another XP Pro installation and safe mode works
now! Unfortunately completely importing the "SafeBoot" branch brings other
problems with Windows themes, VGA drivers, audio drivers and so on... So I
must somheow try to rebuild the SafeBoot branch based on the working normal
mode. Will be quiet a lot of work and i don't know if this can be done
(half-) automatically.


Bye Oliver

Hi Oliver,
That good News that you found the culprit.

By doing this, you got the other settings for that machine and also you
should be careful about this file:
sr.sys, which the FSFilter System Recovery ( System Recovery).

Do you have this subfolders:

[&]Base
[&]Boot Bus Extender
[&]Boot file system
[&]CryptSvc
[&]DcomLaunch
[&]dmboot.sys
[&]dmio.sys
[&]dmload.sys
[&]dmserver
[&]Eventlog
[&]Filter
[&]HelpSvc
[&]Netlogon
[&] PCI Configuration
[&]PlugPlay
[&]System Bus Extender
[&]vds
[&]Vga.sys
[&]vgasave.sys
[&]WinMgmt

I think you will need to perform a Repair/Install for the Operating system,
as the other machine which you imported the Registry may be different is
Hardware settings!.
Repair/ install of XP:
http://michaelstevenstech.com/XPrepairinstall.htm
HTH.
nass

 

[Oliver Breitfelder]

[..]

Do you have this subfolders:

[..]

I'll check for these subfolders.

I think you will need to perform a Repair/Install for the Operating
system,
as the other machine which you imported the Registry may be different is
Hardware settings!.

Fortunately I got a parallel XP installation on the same PC (= same
hardware) for gaming purposes. That's were I "borrowed" the SafeBoot branch
of the registry. The only things that didn't work out correctly were audio
drivers & Windows theme and that's somehow connected to the VGA card I'm
afraid. I'll try some further investigation but at the moment I'm quite
convinced that I can solve this without re-installing oder repair installing
windows.

I am backing up my registry daily and I was capable of finding out that I
"lost" my SafeBoot branch somewhere in October. So I took the 30th September
backup and exported the SafeBoot branch from it. This will work even better
than to copy from the gaming Windows. Small steps but I am proceeding... ;-)
Thanks again.


Bye Oliver