Re: 0x07B BSOD on first boot

You either removed a critical boot device from the configuration or your
machine requires a critical boot device for which there is no driver in the
database. For the second issue you would have had an import error when
importing the PMQ into TD (you can ignore the "General Volume" device
warning).

Do an experiment, re-import the PMQ, watch for errors, then tweak your
configuration but do NOT disable any devices, just let the footprint bloat.
If the 7B goes away then you know you had disabled a critical device
required by your machine. If there is a missing driver component you'll get
an error when importing the PMQ, then you'll need to create a component to
cover this driver, there are articles listed at the link below to help with
this as well. Plus you can check www.xpefiles.com, it's run by Brad Combs.

Read up on the tips articles to help troubleshoot:
http://www.microsoft.com/windows/em.../xp/default.asp

Andy
--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================


"Sam Raslo" <nobody@noplace.net> wrote in message
news:#Pu$ivmbDHA.652@tk2msftngp13.phx.gbl...
> Hi,
> Is there a systematic way to debug a 0x7B BSOD at FBA time? There was no
> FBA log. A broader question is that since I ran tap.exe and then simply
> trimmed some hardware like the sound system and parallel port that were
> irrelevant to my application, why would TD after a good dependency check
> build me an image the results in a BSOD?
>
> Sam
>
>