STOP: 0x0000007B

I am getting the dreaded BSOD 7B error during a first boot from compact flash.

I am attempting to build an XPE bootable image for compact flash on an Intel
DL201GLY motherboard.  This is a new board, with SIS chipset (SIS662 /
SIS964L).  The board has one IDE channel (with an added compact flash
adapter) and no floppy support.

I managed to build an XPE bootable image for a USB memory stick.  When I
boot from USB, Windows does not see anything on the IDE channel.  I've tried
both compact flash and CD-ROM.  On the other hand, the BIOS has no trouble
recognizing either of these devices.

From the USB boot, I ran TAP (not TA) then created a .SLD file from the
resulting .pmq file.  The Component Designer log file contained the following
warnings:

Warning:Could not find a driver for Video Controller (VGA Compatible)
(PCI\VEN_1039&DEV_6330&SUBSYS_D61F8086&REV_04).
Warning:Could not find a driver for Multimedia Audio Controller
(PCI\VEN_1039&DEV_7012&SUBSYS_D61F8086&REV_A0).
Warning:Could not find a driver for Generic volume (STORAGE\Volume).
Warning:Could not find a driver for Generic volume (STORAGE\Volume).
...
Info:Import succeeded with 63 drivers for 67 devices.

(I believe that VEN_1039 refers to Silicon Integrated Systems (SIS).)

The following SIS specific drivers were added to my devices component:

Info:Adding SIS Processor to AGP Controller to the component.
Info:Adding SiS 900-Based PCI Fast Ethernet Adapter to the component.
Info:Adding SiS PCI IDE Controller to the component.
Info:Adding SiS 7001 PCI to USB Open Host Controller to the component.
Info:Adding SiS PCI to USB Enhanced Host Controller to the component.

The following additional PCI/IDE related components were also added:

Info:Adding PCI bus to the component.
Info:Adding CD-ROM Drive to the component.
Info:Adding Disk drive to the component.
Info:Adding PCI standard PCI-to-PCI bridge to the component.
Info:Adding PCI standard host CPU bridge to the component.
Info:Adding PCI standard ISA bridge to the component.
Info:Adding Primary IDE Channel to the component.
Info:Adding Secondary IDE Channel to the component.
Info:Adding Logical Disk Manager to the component.
Info:Adding Volume Manager to the component.

In "KM's" posting to thread "Re: Unable to boot from a XPe NTFS CF" dated

http://msdn2.microsoft.com/en-us/library/ms940177.aspx

When I followed the instructions in that article, I found that all of the
components mentioned were already part of my devices component.

In "Sean Liming's" posting to thread "Re: Unable to boot from a XPe NTFS CF"
dated "5/29/2007 10:24 AM PST" he mentioned the following web page:

http://www.seanliming.com/Docs/XPE%20Stop%200x0000007B%20Error%20V1.3.pdf

The only thing missing from my device configuration that was in Sean's list,
was "Standard IDE/ESDI Hard Disk Controller".  I added that, to no avail.

I even built an image based on Minlogin, which according to the experts has
the "basic components to build an image that will run on any system".  Well,
it doesn't run on this motherboard, and I don't know how it could, since it
only contains a small subset of the components identified by TAP.

Can anyone help?

-Mike

STOP: 0x0000007B

Since there is currently a shortage of experts here I am going to throw
in a random suggestion.

Slobodan suggested the following to me:





--
-Mike

Help me understand the IDE configuration - Is this an IDE to CF adapter on a

Help me understand the IDE configuration - Is this an IDE to CF adapter on a
secondary channel?
Is it possible to boot from a regular IDE/SATA hard drive?

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

Hi Sean,This motherboard has a single IDE channel (single IDE connector) so it

Hi Sean,

This motherboard has a single IDE channel (single IDE connector) so it can
handle at most 2 IDE devices at once.  The CF is installed in an IDE2CF
adapter, (which would normally be connected as the master on the primary
(i.e. only) IDE channel).  There is no SATA connector.

In your article (referenced below), you mention that the best platform to
run TAP from is XP Professional.  That made real sense to me, so I connected
a blank 80 GB hard drive and a CD-ROM drive to the motherboard.

When I attempt to boot the XP setup CD, I get a "Trap 00000006
===EXCEPTION===" message, with a short register dump.  I'm not sure what to
make of that.

Next I augmented my USB boot with every file system I could find, and I
tried running XP setup from XPe booted from USB.  That seemed to work, so I
attempted to install Windows on the hard drive.  Setup copies a bunch of
files to the hard drive, does some initialization, then reboots.  Setup says
to remove any floppy from the A drive before the reboot.  I wasn't sure
whether to take that literally, since there is no floppy adapter on this
board.

If I leave the USB memory stick plugged in, the boot.ini file directs the
boot to "XP Professional Setup", instead of "XP Embedded", as you might
expect.  However, setup basically starts over at the beginning, asking me
what disk partition to install Windows on.  I go through the motions... it
copies files, reboots, and I'm back where I started (i.e. an infinite loop).

If it remove the USB memory stick, I get the following message:

problem.  Could not read from the selected boot disk.  Check boot path and
disk hardware.  Please check the Windows documentation about hardware disk
configuration and your hardware reference manuals for additional information."

Another Catch-22.  I'm guessing that that last error message occurs because
the USB memory stick is "C:" when XPe is booted, then the hard disk becomes

HP has a utility that is supposed to make a USB memory stick look like a
floppy disk.  I'll try that next and see if I can get XP setup to cooperate
better.

-Mike

0x0000007B

I found HP's "Drive Key Boot Utility" at:

http://h18000.www1.hp.com/support/files/serveroptions/us/download/23839.html

Sure enough, it converts a USB memory stick into a bootable floppy disk.

It didn't solve my XP setup problem though, since the XP recovery disk image
that I loaded onto the memory stick doesn't see either my hard drive or my
CD-ROM.  I assume that it's a file system issue, since my USB boot didn't see
either drive until I loaded FAT, CDFS and UDFS.

-Mike

If Windows XP Pro cannot install, then you will not get very far with XPe.

If Windows XP Pro cannot install, then you will not get very far with XPe.
Did the board come with any special drivers that require a F6 during setup
to install?

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

Hi Sean,When I inspected the BOOT.

Hi Sean,

When I inspected the BOOT.INI file on the hard drive on which I had
attempted to install XP, it didn't make any sense to me.

I got past the Windows setup infinite loop by copying NTLDR and NTDETECT.COM
to an empty USB memory stick.  Then I added a generic "first disk, first
partition" BOOT.INI file.  I did a USB reboot, and XP setup ran through to
completion.

It appears that my problem was that XP setup is confused by running it from
a USB memory stick.  I can't reboot this copy of XP Pro without the helper
USB memory stick in place, seemingly to make sure that the drive with XP on
it enumerates as D:.

I ran TAP from XP Pro, and contrary to popular wisdom, I ended up with 4
fewer
devices than when I had run TAP from XPe (USB boot).  That is, 63 devices
instead of 67.  I'm building another copy of XPe using that device component,
but I'm not hopeful.

The D201GLY motherboard did come with a CD, which has 2 drivers on it:


There is an autorun Intel installation program that can be used to install
these components, apparently after Windows is up and running.  The
documentation does not mention loading these drivers during XP setup.

With this newest devices.pmq file, Component Designer reports 5 missing
drivers (one more than before):

Warning:Could not find a driver for Video Controller (VGA Compatible)
(PCI\VEN_1039&DEV_6330&SUBSYS_D61F8086&REV_04).
Warning:Could not find a driver for Multimedia Audio Controller
(PCI\VEN_1039&DEV_7012&SUBSYS_D61F8086&REV_A0).
Warning:Could not find a driver for Hardware Device Storage\Volume
(STORAGE\Volume).
Warning:Could not find a driver for Generic volume (STORAGE\Volume).
Warning:Could not find a driver for Generic volume (STORAGE\Volume).

The "SIS Mirage Graphics" driver corresponds to DEV_6330.  The "SIS
Accelerated Graphics Port" driver does not correspond to DEV_7012, (it's
DEV_1) and I haven't been able to trackdown a matching driver on the SIS
website.

-Mike

Hi MikePciidex.sys and Atapi.sys were already part of my configuration.

Hi Mike

Pciidex.sys and Atapi.sys were already part of my configuration.  I added
couldn't find anywhere to disable PnPID(819)???  I rebuilt my image, and I
still got the STOP: 0x0000007B behavior.

-Mike

I would just install XP Pro on the HDD with no USB flash disk attached.

I would just install XP Pro on the HDD with no USB flash disk attached. XP
Pro install should have reconized the USB flash disk as a removable device.

Video and audio are the only components missing, which is typical. Doesn't
sound like there are any special bus driver components.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

0x0000007B

When I converted a USB memory stick to a virtual floppy disk, it booted as
A:, but the XP recovery image that I installed on the memory stick did not
recognize either the hard drive or the CD-ROM drive.

I didn't seem to have the option of installing XP Pro without the XPe
bootable USB memory stick, since the bootable image on the XP install CD
trapped before it got going.

USB devices are not available in the BIOS boot order, instead there is an
extraordinary option to boot from a USB device before the devices specified
in the boot order.

Normally USB drives are enumerated after the fixed disks.  But when USB boot
is enabled, and one is used as a boot device, the BIOS insists on enumerating
it first.  Hence the USB drive is assigned drive letter C:, instead of being
assigned a drive letter E through Z.  Hence the issue with XP Pro being
installed as disk D, and refusing to boot when enumerated as disk C.

XP setup doesn't seem to provide any means to indicate what it has
determined about the fixed/removable status of the USB memory stick.  After
XP Pro is installed, it does show the USB drive in C: is removable.

In any case, the whims of XP Pro are irrelevant.  Installing XP Pro was only
supposed to be the means to an end.  Running TAP under XP Pro still resulted
in a STOP: 0000007B error.

The two devices which Intel provided drivers for do end up with question
marks inside of Device Manager in XP Pro.  The fact that XP pro runs fine
without those drivers shows that they are irrelevant.  (When I did install
the drivers on XP pro, one of the installs actually failed -- I believe the
PCI device number in the INF file is wrong.)

TAP reports 63 devices, and the resulting XPe image has 94 drivers (.sys
files installed in windows\system32\drivers).  The XP Pro image has 165
drivers.  I assume that one or more of those extra drivers is the cause of my
problem.

Just determining the XPe component or components associated with a few of
those drivers inside of Target Designer is a bit of an ordeal.  Of the two
that I tried, one (vgasave.sys) wasn't even available in any XPe component.

Is there any better way to attack this problem?

-Mike

At this point I would have to play with the unit to see what is going on.

At this point I would have to play with the unit to see what is going on.

Are there any BIOS updates for the system?

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

Yes there was a BIOS update, posted I think July 2nd on Intel's site.

Yes there was a BIOS update, posted I think July 2nd on Intel's site.  The
update description was terse... some issues with some strings not being
filled in and such.  I downloaded and installed the new BIOS.  Nothing really
changed.

I determined that my inability to boot the XP Pro setup CD was a problem
with the CD-ROM drive.  I replaced it, and I was able to load XP Pro so that
it boots off of the C: drive.

I ran tap starting from this "normal" configuration.  The BIOS wouldn't even
boot the resulting image.

As I mentioned in a previous post, I tracked down the components for most of
the drivers that XP Pro loads, that my CF boot wasn't loading, and I added
them to my configuration.  That added about 50 additional drivers.  There was
no real change.  The only difference was that it took a little longer before
the BSOD 7B bug check showed up.

-Mike

To eliminate a variable, I purchased another hard drive and made it bootable.

To eliminate a variable, I purchased another hard drive and made it bootable.
I copied the same XPe image that was crashing with a 7B error, on to the
hard disk.  The image booted fine from the hard disk and FBA completed
normally.

So it appears that my XPe image never had any missing drivers.  The problem
would appear to be caused by either the compact flash medium or the CF2IDE
adapter.

-Mike

Would you mind sharing your final SLX file?

Would you mind sharing your final SLX file?  I am having the same problem as
you (with the same board) but cannot get past the 7B error?

Turns out I was able to solve the problem myself.

Turns out I was able to solve the problem myself.  The issue was that I'm
using XPECMD and was adding the wrong "Disk Drive" component.   See my blog
posting here:
http://hasmanyquestions.wordpress.com/2007/07/13/xp-embedded-gripe/

I finally resolved the problem...

I finally resolved the problem...  It seems to have been a bad compact flash
card and a bad CF2IDE adapter.

After getting past the FBA with a new compact flash card (same brand,
Transcend Industrial DMA) and a new CF2IDE adapter (different brand, ACS), I
put the old/bad CF2IDE adapter back in, and it boots the post-FBA image just
fine.  I'm not sure what to make of that.

I was also able to get a Lexar 2 GB 300X UDMA compact flash to boot, but
only after reformatting it with NTFS using UFDPREP.  I had tried the FAT /
BOOTPREP route, without success.  The Lexar CF is not marked "fixed".

-Mike