Bugcheck 7B -MS ID 6

[Guest]

Hi KM
When I added the ACPI componments to the image the system will become blue screen.(Error message 7B
But if I change to use standard pc componment will not
All of the componments in this image are all the same just difference in ACPI and Standard Pc componment
Could you kindly guide me the way of the soluation

Thanks in advance

Sean

 

[KM]

Sean,

What exactly 7B code do you see? Is it "Inaccessible Boot Device"? If so,
check the tip
http://msdn.microsoft.com/embedded/community/tips/xp/stoperr7b/default.aspx.

Does your target support ACPI HAL? Is the BIOS ACPI compliant?
If you are not sure, try to install XP Pro and see what is supported.
Or run TAP (or TA) on the target.

Usually, 7B means that Windows lost access to the system partition during
the startup process. However, I don't know if there is any other
possibilities to get the BSOD.

KM

PS. Not sure why you are asking me. There are a lot of knowledgeable folks
here who may better answer your questions.

Hi KM ,
When I added the ACPI componments to the image the system will become blue screen.(Error message 7B)
But if I change to use standard pc componment will not.
All of the componments in this image are all the same just difference in

ACPI and Standard Pc componment .

 

[Slobodan Brcin \(eMVP\)]

Do you have components?

Microsoft ACPI-Compliant Embedded Controller
Microsoft ACPI-Compliant System

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Hi KM ,
When I added the ACPI componments to the image the system will become blue screen.(Error message 7B)
But if I change to use standard pc componment will not.
All of the componments in this image are all the same just difference in

ACPI and Standard Pc componment .

 

[Guest]

Hi KM
Thanks your reply so soon
What exactly 7B code do you see? STOP : 0X0000007B (0XF7B95640,0XC0000034,0X00000000,0X00000000
Does your target support ACPI HAL? Yes
Is the BIOS ACPI compliant? Yes
As below componments in my image
*Advance configuration and Power Interface (ACPI) P
*ACPI FA
*ACPI Fixed Feature Butto
*ACPI Power Butto
*ACPI Thermal Zon
*Microsoft ACPI-Compliant Syste
Use tap in my target and reload the pmq file still the same problem
The tips that you offered I already checked
As I told you last time all of the componments in this image are all the same just difference in
ACPI and Standard Pc componment.
I still confuse with this problem
I don't know the info enough or not if you need more please tell me

Thanks a lot
Sea

 

[KM]

Sean,

Did you try Slobodan's suggestion?

Make sure you got these components:
Microsoft ACPI-Compliant Control Method Battery [Version 5.1.2600, R620], [Visibility=1000]
Microsoft ACPI-Compliant Embedded Controller [Version 5.1.2600, R620], [Visibility=1000]
Microsoft ACPI-Compliant System [Version 5.1.2600, R620], [Visibility=1000]

And if you have WMI Core in place:
Microsoft Windows Management Interface for ACPI [Version 5.1.2600, R620], [Visibility=1000]


Also, thy experiment (to make sure your target is ACPI compatible):
Build ACPI image, deploy, get BSOD. Shutdown the target (or reboot it in a different OS if you have a dual boot set up). Access to
the disk offline. Rename hal.dll to halacpi.dll under \windows\system32 dir. Copy hal.dll (Standard PC) to the image's
\windows\system32 directory. Change boot.ini to use /HAL option to switch between different HALs and see if you target boots fine
with halacpi.dll (ACPI) and hal.dll (Standard PC). Most likely, it will only boot with the last one.

Another high level thing to try - XPProEmulation.slx from www.xpefiles.com. Just include your platform (ACPI imported pmq/sld) to
the configuration (it may take a time), build, deploy and see if the issue is still there. It will tell you if the problem is just
about some missing components or more low level.

If it is more low level issue, I'd suggest to switch to KD (Kernel Debugger)/WinDbg to see what exactly is happening when you boot
your target with ACPI compliant platform.

Here is the steps how to set up the WinDbg:

Just download the tool and symbol files from http://www.microsoft.com/whdc/ddk/debugging/default.mspx.
Then follow the leads from
http://support.microsoft.com/defaul...port/kb/articles/q121/5/43.asp&NoWebContent=1 and
http://support.microsoft.com/defaul...port/kb/articles/q151/9/81.asp&NoWebContent=1 (if
you use null modem for remote debugging).
MS Debugging Tools KB is here: http://www.microsoft.com/whdc/ddk/debugging/DBG-KB.mspx.


Hope this helps,

 

[KM]

Sean,

Just remembered one more thing for you to check...

Your system BIOS may be on the "bad BIOS" list (even if the system is
detected as ACPI-compliant). A BIOS appears on the "bad BIOS" list if that
BIOS is known to cause system instability when the ACPI HAL is used. This
instability can range in severity from poor hardware performance to system
lack of response and data loss.

In case of XP Pro, the XP Setup will detect the BIOS, check if it is on the
Good ACPI Bios list and force an ACPI installation. See more info here:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;314088.

I don't know what really happens on XPe when you may have either HAL
component. FBA can't really switch to a Standard PC HAL if it is not
included, right? Therefore, if the BIOS is "bad" and the ACPI HAL is used,
there may appear some system instability.

Check Txtsetup.sif text file (you can find it in XPE Repository but not
belonging to any component, though, or on XP Pro installation CD). There
will be a [GoodACPIBios] section. Try to find your system BIOS in the list.
You will also need ACPIBiosDate entry from [ACPIOptions] section (the
details you will find in the KB mentioned above).

Hope this helps,
KM

 

[Guest]

KM
Thanks your reply so soon
As below is the question metioned before
Did you try Slobodan's suggestion?Add releative ACPI componments .Yes,but the result still 7B
----------------------------------------------------------------------------------------------------------------------------------------
Change boot.ini to use /HAL option to switch between different HALs and see if you target boots fine with halacpi.dll (ACPI) and hal.dll (Standard PC). Most likely, it will only boot with the last one
----------------------------------------------------------------------------------------------------------------------------------------
How to use /HAL option ? I don't understand the command
So I only rename the hal.dll to halacpi.dll and copy the hal.dll(Standard PC) to the image.But result sill 7B
Besides,thanks your reminding I recheck the system bios .It's "good bios
Another high level thing to try - I download the sld file via www.xpefiles.com and by your suggestion.But result still 7B
About the low level issue . I think need times to read the doc and try
Is there more simple way to find out the problem

Appreciate your efforts and help

Sean

 

[Slobodan Brcin \(eMVP\)]

Well few minutes with remote kernel debugger would reveal what is wrong with
your image if you know what to look for.

Try Konstantins first suggestion.

Run TAP.
Import PMQ and ACPI support should be there. And then try this new image to
see if it will boot.
Do not import PMQ to existing project, create new clean project.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

KM,
Thanks your reply so soon.
As below is the question metioned before.
Did you try Slobodan's suggestion?Add releative ACPI componments .Yes,but the result still 7B.
-------------------------------------------------------------------------- ---------------------------------------------------------------
Change boot.ini to use /HAL option to switch between different HALs and

see if you target boots fine with halacpi.dll (ACPI) and hal.dll (Standard
PC). Most likely, it will only boot with the last one.

-------------------------------------------------------------------------- ---------------------------------------------------------------
How to use /HAL option ? I don't understand the command.
So I only rename the hal.dll to halacpi.dll and copy the hal.dll(Standard

PC) to the image.But result sill 7B.

Besides,thanks your reminding I recheck the system bios .It's "good bios"
Another high level thing to try - I download the sld file via

www.xpefiles.com and by your suggestion.But result still 7B.

 

[Guest]

Hi Slobodan
I try another way to slove this Bugcheck 7B problem
Steps as below
1. removed the database and recreat whole new one
2.Import the target pmq file to this new data base

After pmq file importing shown
Database miss this file "Could not find a driver for Hardware Device: ACPI\ASF0001 (ACPI\ASF0001).
Do you know the meanig
But now my image is good with ACPI and work fine

Thanks you and Konstantins's help
Sea

 

[Slobodan Brcin \(eMVP\)]

Hi Sean,

I can't find this hardware id (ASF0001) on my computer. nor in any inf file
in repository
It looks like you should make component from inf files for your chipset.
If you have WinXP on your device you can use devcon or device manager in
advanced view mode to find out what driver is related to this.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[KM]

ASF actually stands for "Alert Standard Format".
See DMTF specification doc for more info:
http://www.dmtf.org/standards/documents/ASF/DSP0114.pdf

KM