RE: XP SP2: Only Safe Mode doesn't work - normal system start works pe



"Oliver Breitfelder" wrote:

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
---
http://www.nasstec.co.uk
.

Relevant Pages

  • Re: Vista killed my HP DV7
    ... on Vista x64 issues. ... When I booted on Friday evening I got a Windows Defender error asking ... also occasionally BSOD, especially when trying to enter Windows Update. ... didn't get a BSOD I got, no price for guessing, another error message ...
    (microsoft.public.windows.vista.general)
  • Virus?Hardware?Other?
    ... window I had before the BSOD I uninstalled the software I ... I tried reinstalling Windows XP to repair it. ... referenced to in the Error message above. ... Is this a virus only affecting my user profile? ...
    (microsoft.public.scripting.virus.discussion)
  • RE: 0x0000007e stop error
    ... Without the Complete error message like Stop 0x00000050 in Win32k.sys I ... that XP setup could gather new drivers for the new hardware. ... I'm trying to setup Windows XP ... After that you could do a repair install, ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Stop error during gameplay.
    ... You receive a "Stop 0xD1" error message in the Netbt.sys driver on your Windows 2000-based computer ... adapter miniports or NDIS drivers do not have to indicate NDIS_STATUS_CLOSING, and when possible, drivers that do so must be corrected. ... - When you use a Philips PhilCam730 Webcam on a computer that is running Microsoft Windows 2000 Professional Service Pack 3 or Service Pack, you may receive the following Stop error message: ...
    (microsoft.public.win2000.general)
  • Re: BSOD pause
    ... Can someone post how exactly to pause a BSOD? ... There's no way to "pause" the reboot at the blue screen without first getting into Windows to set the option for the boot to halt at the error. ... To get the error message from the blue screen (a.k.a. the BSOD -- ...
    (microsoft.public.windowsxp.hardware)