Apology: Stop 7B question

[Henry Markov]

I know that questions about Stop 7B at FBA are not appreciated and that there is
a "hints" article with some suggestions. However I am evaluating a relatively
new single board computer that uses a HanceRapids chip set and other video and
network devices that have no inherent support in the XPe/SP1 or XP Pro
distributions. I can build a completely functional XP Pro system by using
vendor supplied XP drivers for the new devices but the corresponding XPe drivers
lead me to a Stop 7B. I verified through manufacturer and device codes that all
the drivers needed for boot are present in the XPe configuration. Is there any
methodical way to identify the problem given that everything looks correct at a
high level?

 

[KM]

Henry,

You can always use KD (Kernel Debugger) to find our more info about the 7B.
Also, take a look at the DDK 7B page - it has more info and hints that the known 7B tip page.

What's about installing XP Pro on the target? I did not quite get it from your message.
If you can install it, you can capture a lot of information from there about the boot drivers you got (TAP, Device Manager,
registry, etc.).

Or, does your target have a CD-ROM so that you could boot WinPE? You mentioned it is a new board you are trying but who knows.

 

[Henry Markov]

1. The DDK Bug Check 7B page says "this error always occurs while the system is
starting. This will often happen before the debugger connection is established,
making debugging difficult or impossible." Is this statement not true for XPe
Stop 7B? I haven't tried it because of this warning and the fact I know nothing
about using it.

2. The same page suggests examination of the data pointed to by parameter 1 of
the Stop 7B message. What tool does one use for this examination?

3. Yes I installed XP Pro on the same target and I didn't see anything critical
missing when comparing Device Manager to my XPe configuration. I don't know
enough about registry organization to know how examining the XP Pro registry can
help.

4. Yes I can boot WinPE but how does that help me?

Henry

 

[Slobodan Brcin \(eMVP\)]

Hi Henry,

1. This error occur only at time when system tries to access to system partition for first time. (Before file system is loaded).
You can use debugger to break at any point, even point after the 7B is enough for diagnostic driver stack.

If you want to break in to system before any driver is loaded (there is no purpose in this case for this).
You can add /BREAK switch in boot.ini
System will issue int 3 and wait for debugger to connect. before continuing load.

Regards,
Slobodan

 

[Henry Markov]

Where is kd.exe? According to Jon Fincher's Third-Party Tools for Windows XP
Embedded" article it can be downloaded from
http://go.microsoft.com/fwlink/?LinkId=16273. That link says that it should be
in the Windows XP SP1 DDK which as an MSDN subscriber I downloaded and installed
however kd.exe is not one of the utilities. A lot of other web searching has
similarly led me to dead ends. A current pointer to kd.exe and an explanation
about how I use it with XPe to get info about a Stop 7B would be greatly
appreciated.

 

[KM]

Henry,

If you have installed DDK, you likely got "\Program Files\Debugging Tools
for Windows" directory. Take a look there and find either kd.exe or
windbg.exe. Those two are most interesting to you now.

In case you don't have it, download and install it from here:
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
And you may also need symbols:
http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx

Again, I refer to DDK's "Bug Check 0x7B: INACCESSIBLE_BOOT_DEVICE" page.
there is a lot of info on how to use KD to troubleshoot it.
You may wan to use "!devnode 0 1" and "!analyze -v commands".
Also, read this thread for helpful info:
http://groups.google.com/[email protected]&rnum=1

KM

Where is kd.exe? According to Jon Fincher's Third-Party Tools for Windows XP
Embedded" article it can be downloaded from
http://go.microsoft.com/fwlink/?LinkId=16273. That link says that it should be
in the Windows XP SP1 DDK which as an MSDN subscriber I downloaded and installed
however kd.exe is not one of the utilities. A lot of other web searching has
similarly led me to dead ends. A current pointer to kd.exe and an explanation
about how I use it with XPe to get info about a Stop 7B would be greatly
appreciated.

correct at a high level?

 

[KM]

Henry,

3-4) When you capture PMQ file using TAP on the target from XP Pro or WinPE
and then import it with CD, do you see any errors (missing driver items,
etc.)?

KM

1. The DDK Bug Check 7B page says "this error always occurs while the system is
starting. This will often happen before the debugger connection is established,
making debugging difficult or impossible." Is this statement not true for XPe
Stop 7B? I haven't tried it because of this warning and the fact I know nothing
about using it.

2. The same page suggests examination of the data pointed to by parameter 1 of
the Stop 7B message. What tool does one use for this examination?

3. Yes I installed XP Pro on the same target and I didn't see anything critical
missing when comparing Device Manager to my XPe configuration. I don't know
enough about registry organization to know how examining the XP Pro registry can
help.

4. Yes I can boot WinPE but how does that help me?

Henry

correct at a high level?