XP embedded blue screen error stop 0x0000007b

XP embedded blue screen error stop 0x0000007b

Translation: Bill Zhong
Date: 2007-8
Academic Exchange, copyright owned by the original

When developing embedded Windows XP embedded, the most common problem is the blue screen. The specific error code is: "Stop 0x0000007b ". although the "tips and Tips" section in the Windows XP embedded advanced usage book lists the solutions for it, developers still encounter this problem due to incomplete explanations.

The cause of the error is: The image lacks the necessary driver. For example, there are several reasons for compaction: it takes time to load Windows xp pro on the target device; the Windows XP prosystem cannot be installed on the target device on the physical/hardware, and winpe(pre-installed environment ;;ta.exe is like a PCI sniffer program. it checks the CPU bus and basic hardware circuit, collects BIOS information, and saves it as a pmq file. tap.exe is the driver used to further detect Windows XP or 2000's registration table. The reason for this problem is ta.exe. it does not collect the components required when the operating system is started.

When an error occurs in my understanding, the OS switches from the real mode to the protection mode. the operating system must load the device from the start machine protection mode. the current PC accesses the device controller through the PCI bridge chip. if the image does not have the correct PCI driver or other disk device drivers, the system displays a blue screen.

Ta.exe does not find some components, as shown below:
PCI standard host CPU Bridge
PCI standard ISA Bridge
Plug and Play software device enumerato
Primary ide Channel
Secondary ide Channel
Disk Drive
Standard dual channel PCI ide Controller
Standard IDE/ESDI hard disk Controller
Some special OEM bus Main Control ide or SATA controller components may also be the cause of the error (culprit)

The best way to collect all the required components is to run tap.exe on the Windows XP protarget machine. another better solution is to take the first cdns of xpeto winpeand run tap.exe. you should note that the winpe system has limitations because the winpe image does not contain all drivers, so winpe won't capture all components like Windows XP Pro. for example, the winpe system does not have a USB or 1394 client driver, but you will get the required components to start the operating system. if you only need MS-DOS, if you can solve this problem, then try the components listed above.

SATA device-a sata device that uses different RAID Controller cards may also stop a 0x7b device. ensure compatibility between the SATA device and controller card versions.

To prove the xpe operating system, you need to use the minlogon sample macro or Winlogon sample macro to compile an image. However, the result of ta.exe is not displayed. these two macro components are the basic components required to compile the image for any system.

 

Due to the limited level, there will be mistakes or errors. Please do not correct them.

 

Original ENGLISH

Sjj embedded micro solutions version 1.3
Copyright 2005 sjj embedded micro Solutions, LLC., All rights reserved.
Www.sjjmicro.com
11/01/06 1
The blue screen stop 0x0000007b error in XP embedded
By Sean D. Liming
Managing Director
Sjj embedded micro Solutions
March 2005
V1.2 updateed: October 2005
V1.3 updated November 2006

One of the most common problems that first-time developers run into is the blue screen stop 0x0000007b error. although the book Windows XP embedded advanced has the solution listed in the tips-and-tricks chapter, the explanation is not as detailed as it cocould be, and developers still run into the problem.

The error is occurring because a driver is missing from the image such as a PCI bus driver, disk driver, or IDE controller driver. many developers start the xpe development process using the DOS version of target analyzer-ta. EXE instead of tap. EXE. there are pending reasons why developers go the TA. EXE route: loading windows xp pro on the target is time consuming, it is physically not possible to install Windows xp pro on the target, or running winpe is not possible. ta. EXE is like a PCI sniffer program. it will check the CPU bus, basic hardware ICS, and
BIOS to gather information for the pmq file. tap. EXE goes a little further by checking Windows XP's or 2000's registry to see what drivers have been loaded by the OS. the issue is with TA. EXE. ta. EXE doesn' t gather all the components needed to boot the operating system.

My understanding is that the error occurs when the OS is switching from real mode to protected mode. the OS is loading the drivers necessary to access the boot drive in protected mode. today's PCs access the Drive Controller via PCI bridge chips. if the correct PCI driver or other disk device drivers are not in the image, the system will blue screen.

Some of the missing components ta. EXE doesn't find might be the following:

PCI standard host CPU Bridge
PCI standard ISA Bridge
Plug and Play software device enumerator
Primary ide Channel
Secondary ide Channel
Disk Drive
Standard dual channel PCI ide Controller
Standard IDE/ESDI hard disk Controller
Microsoft ACPI-compliant system (if the system is an ACPI compliant system, I. e.
Contains the ACPI multiprocessor PC, ACPI uniprocessor PC, or advanced configuration and Power Interface (ACPI) PC components)

A specific OEM bus master ide or SATA Controller component might also be the culprit. You will have to review you board manufactures documentation and driver CD for more information.

The best way to gather all the necessary components is to install Windows xp pro on the target systems and run tap. EXE. the next best solution is to use xpe's CD1 and boot to winpe and run tap. EXE. you shoshould note that there are limitations with winpe, since not all the drivers are in the winpe image, thus tap under winpe wocould not capture all the components that tap under Windows xp pro wowould capture. for example USB or 1394 client drivers are not in winpe, But you wocould get the components needed to boot the OS. if you only have MS-DOS, then try adding the components listed above to see if that solves the problem.

SATA drives-there have been reports that mixing different version of SATA drives with different RAID Controller cards can also lead to a stop 0x7b condition. make sure the Controller versions on the SATA drive and the controller card are compatible.

If all else fails and to prove that xpe runs on the system, build an image using either minlogon sample macro or Winlogon sample macro components and don't include the TA. EXE results. these two macro component have the basic components to build an image that will run on any system.

Windows is a registered trademark of Microsoft Corporation. v