Bugcheck 0x7B

  • Thread starter Thread starter Larry Waibel
  • Start date Start date
L

Larry Waibel

We have a custom single board computer that I was able to boot the XPe
install CD on and run TAP. The components for hardware appear to be what's
on the board. But when I build and try to boot, I get a BSOD 0x7B. How can
I find any more details about which component might be missing/incorrect?
Thanks!
 
Yes, I'd determined that's the stuff to look for. I used TAP and all the components appear
to agree with the hardware that's on the board (I've not been able to install a full XP Pro
on this system; when booting from the install diskettes at about the 3rd diskette it reports
that hal.dll can't be found but I was able to boot from the XPe install CD to run TAP).
There is no secondary IDE in the BIOS and so none in the configuration but all the other
ones appear to be there. The BSOD error just says 'A problem has been detected...' with no
other clues. The stop is (0xF9E47640, 0xC0000034, 0x00000000, 0x00000000). I'm going to
try your XPProEmulation.slx next and see if that works.
 
Larry,

Well.. The XPProEmulation.slx will unlikely help you because it is just software components from database.
You will have to add hardware support by yourself anyway.

Installing XP Pro would actually help more.

Also, make sure you have got the proper disk driver component in your image. Actually, just manually add all three "Disk drive"
components from "Hardware : Devices : Disk drives" category.

In any case you always have KD (kernel Debugger) that will help you to determine what's missing.

Also, check if on the target you've got hardware RAID support in the BIOS that requires software driver. E.g., "Win XP Promise
FastTrak" would be one example.
 
You're right, XPProEmulation didn't help. I put in all three disk drives and the
secondary IDE controller and that also didn't help. I wish I did 'always have the KD...';
I've never used it and so don't have anything setup. I'm getting our techs to make me a
null cable (the serial ports on the board are RJ45 connectors, not DB9 as normal) and I'll
have to cross my fingers they get it wired right. Then I have to figure out what all has
to be done/obtained in order to get setup. I've seen some discussions of it in the
newsgroups but nothing that I'd say is a 'cookbook' to how to do it. Some of the links I
run across are to 'NT' instructions. Is there a recent and detailed step-by-step of how
to get the KD setup someplace? Thanks!

From: "KM" <konstmor@nospam_yahoo.com>
Subject: Re: Bugcheck 0x7B
Date: Tue, 8 Feb 2005 12:11:22 -0800
Newsgroups: microsoft.public.windowsxp.embedded

Larry,

Well.. The XPProEmulation.slx will unlikely help you because it is just software components from database.
You will have to add hardware support by yourself anyway.

Installing XP Pro would actually help more.

Also, make sure you have got the proper disk driver component in your image. Actually,
Click to expand...
just manually add all three "Disk drive"
components from "Hardware : Devices : Disk drives" category.

In any case you always have KD (kernel Debugger) that will help you to determine what's missing.

Also, check if on the target you've got hardware RAID support in the BIOS that requires
Click to expand...
software driver. E.g., "Win XP Promise
 
I tried booting the system from the regular XP Pro installation disk and partway through it
says it didn't find any hard disk drives installed. The system only has an M-Systems
DiskOnChip 2000 with 384MB and 256MB RAM. I thought the DoC installed BIOS extensions and
should be seen by XP? I'm able to boot with a DOS floppy and see it as drive C: without
having to install any special DOS drivers.

From: "KM" <konstmor@nospam_yahoo.com>
Subject: Re: Bugcheck 0x7B
Date: Tue, 8 Feb 2005 12:11:22 -0800
Newsgroups: microsoft.public.windowsxp.embedded

Larry,

Well.. The XPProEmulation.slx will unlikely help you because it is just software components from database.
You will have to add hardware support by yourself anyway.

Installing XP Pro would actually help more.

Also, make sure you have got the proper disk driver component in your image. Actually,
Click to expand...
just manually add all three "Disk drive"
components from "Hardware : Devices : Disk drives" category.

In any case you always have KD (kernel Debugger) that will help you to determine what's missing.

Also, check if on the target you've got hardware RAID support in the BIOS that requires
Click to expand...
software driver. E.g., "Win XP Promise
 
Larry,

Perhaps Win XP Pro might choose not to show you disk with sizes below 1GB.
If you have XPe BSOD 7B then you were able to pass ntldr and boot.in related problems which is good.

Please try to use empty project and then add component "Minlogon Sample Macro" after which you should resolve all dependencies and
make a build (it should work).

Let us know.

Regards,
Slobodan
 
Larry,

I haven't played with DiskOnChip 2000 and don't know whether it requires a boot driver in order to work under XP.
I would expect it does not because it says in a M-Systems tech paper that DiskOnChip includes a BIOS driver that is automatically
recognized and loaded by the PC BIOS (basically you will not need BDK)

You mentioned you got BSOD. This means you passed ntldr (almost the same fact as you saw it working from DOS).
However, you may still need M-Systems tools to partition the DoC: http://www.m-systems.com/content/Developer/OSSupport2.asp?id=23
 
That didn't work and I'm not surprised because the problem is something with the hardware
components, not just the after boot stuff. I'm trying to get the KD installed and setup
and see if that can tell me anything.

From: "Slobodan Brcin \(eMVP\)" <[email protected]>
Subject: Re: Bugcheck 0x7B
Date: Wed, 9 Feb 2005 01:01:07 +0100
Newsgroups: microsoft.public.windowsxp.embedded

Larry,

Perhaps Win XP Pro might choose not to show you disk with sizes below 1GB.
If you have XPe BSOD 7B then you were able to pass ntldr and boot.in related problems which is good.

Please try to use empty project and then add component "Minlogon Sample Macro" after
Click to expand...
which you should resolve all dependencies and
 
I've already used the DoC tools and can use Remote Recover to copy the image files
to it so I don't think that's it.

From: "KM" <konstmor@nospam_yahoo.com>
Subject: Re: Bugcheck 0x7B
Date: Tue, 8 Feb 2005 16:11:58 -0800
Newsgroups: microsoft.public.windowsxp.embedded

Larry,

I haven't played with DiskOnChip 2000 and don't know whether it requires a boot
Click to expand...
driver in order to work under XP.
I would expect it does not because it says in a M-Systems tech paper that
Click to expand...
DiskOnChip includes a BIOS driver that is automatically
 
Okay, I got the debugger and cable setup and can debug the bugcheck and it's pointing
at the ARC path for the boot disk as:

e1050e20 "\ArcName\multi(0)disk(0)rdisk(0)"
e1050e60 "partition(1)"

which is what it should be since that's the first (only) disk. I've emailed M-Systems
to see if they have any ideas. There are two M-Systems components in the configuration
identified by the TAP.

From: "KM" <konstmor@nospam_yahoo.com>
Subject: Re: Bugcheck 0x7B
Date: Tue, 8 Feb 2005 16:11:58 -0800
Newsgroups: microsoft.public.windowsxp.embedded

Larry,

I haven't played with DiskOnChip 2000 and don't know whether it requires a boot
Click to expand...
driver in order to work under XP.
I would expect it does not because it says in a M-Systems tech paper that DiskOnChip
Click to expand...
includes a BIOS driver that is automatically
 
It seems that TAP doesn't detect the M-Systems DoC and the driver that comes standard
with XPe is for an older firmware than I have on the system. I just poked around on the
internet and found something on the M-Systems site that looked promising and downloaded
and added that component (as well as a component for the video driver I found since TAP
wasn't seeing that either) and with those it now boots! Thanks again for all your help!

From: "KM" <konstmor@nospam_yahoo.com>
Subject: Re: Bugcheck 0x7B
Date: Tue, 8 Feb 2005 16:11:58 -0800
Newsgroups: microsoft.public.windowsxp.embedded

Larry,

I haven't played with DiskOnChip 2000 and don't know whether it requires a boot driver in order to work under XP.
I would expect it does not because it says in a M-Systems tech paper that DiskOnChip
Click to expand...
includes a BIOS driver that is automatically
 
Back
Top