none
Infamous BSOD Stop 7B Error

    Question

  • Hello all. Could someone please help me solve this issue.

    Here is my situation, I have an XPe image created from FP2007 that is
    relentless to boot from an AHCI enabled drive. It will boot all day
    long running in Basic mode but when I enable AHCI I get the infamous
    Stop 7B bug check.

    Here is a little background of the system I am configuring and what I
    have tried. The motherboard is an Asus P5B-VM with the G965 chipset,
    2gig RAM, Core duo, JMicron SATA.

    First off I imported the SATA drivers into custom component and then
    into my database with no errors being displayed throughout its creation
    in Component Designer. Then I imported the PMQ into TD which picked up
    the SATA component and all of its dependencies. Satisfied the
    dependencies and built the image with no errors. Time for deployment. I
    partitioned and formated the target drive using the oem drivers buy a
    custom PE and the F6 during install and still no errors everything
    looks good. Reboot.... Stop 7B! So I hooked up the trusty ole Kernel
    Debugger and got some more info.

    Microsoft (R) Windows Debugger  Version 6.5.0003.7
    Copyright (c) Microsoft Corporation. All rights reserved.

    Using 1394 for debugging
    Opened \\.\DBG1394_INSTANCE10
    Waiting to reconnect...
    Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
    Kernel Debugger connection established.
    Symbol search path is:
    C:\WINDOWS\Symbols;srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
    Built by: 2600.xpsp.050301-1521
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
    System Uptime: not available

    *** Fatal System Error: 0x0000007b
                           (0xF789E524,0xC0000034,0x00000000,0x00000000)

    Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been
    invoked.

    A fatal system error has occurred.

    Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
    Loading Kernel Symbols
    ..........................
    Loading unloaded module list

    Loading User Symbols
    ***************************************************************************­****
    *
          *
    *                        Bugcheck Analysis
          *
    *
          *
    ***************************************************************************­****

    Use !analyze -v to get detailed debugging information.

    BugCheck 7B, {f789e524, c0000034, 0, 0}

    Probably caused by : ntkrnlmp.exe ( nt!IopMarkBootPartition+113 )

    Followup: MachineOwner
    ---------

    nt!RtlpBreakWithStatusInstruction:
    804e2a42 cc               int     3
    0: kd> !analyze -v
    ***************************************************************************­****
    *
          *
    *                        Bugcheck Analysis
          *
    *
          *
    ***************************************************************************­****

    INACCESSIBLE_BOOT_DEVICE (7b)
    During the initialization of the I/O system, it is possible that the
    driver
    for the boot device failed to initialize the device that the system is
    attempting to boot from, or it is possible for the file system that is
    supposed to read that device to either fail its initialization or to
    simply
    not recognize the data on the boot device as a file system structure
    that
    it recognizes.  In the former case, the argument (#1) is the address of
    a
    Unicode string data structure that is the ARC name of the device from
    which
    the boot was being attempted.  In the latter case, the argument (#1) is
    the
    address of the device object that could not be mounted.
    If this is the initial setup of the system, then this error can occur
    if
    the system was installed on an unsupported disk or SCSI controller.
    Note
    that some controllers are supported only by drivers which are in the
    Windows
    Driver Library (WDL) which requires the user to do a custom install.
    See
    the Windows Driver Library for more information.
    This error can also be caused by the installation of a new SCSI adapter
    or
    disk controller or repartitioning the disk with the system partition.
    If
    this is the case, on x86 systems the boot.ini file must be edited or on
    ARC
    systems setup must be run.  See the "Advanced Server System
    Administrator's
    User Guide" for information on changing boot.ini.
    If the argument is a pointer to an ARC name string, then the format of
    the
    first two (and in this case only) longwords will be:
        USHORT Length;
        USHORT MaximumLength;
        PWSTR Buffer;
    That is, the first longword will contain something like 00800020 where
    20
    is the actual length of the Unicode string, and the next longword will
    contain the address of buffer.  This address will be in system space,
    so
    the high order bit will be set.
    If the argument is a pointer to a device object, then the format of the
    first
    word will be:
        USHORT Type;
    That is, the first word will contain a 0003, where the Type code will
    ALWAYS
    be 0003.
    Note that this makes it immediately obvious whether the argument is a
    pointer
    to an ARC name string or a device object, since a Unicode string can
    never
    have an odd number of bytes, and a device object will always have a
    Type
    code of 3.
    Arguments:
    Arg1: f789e524, Pointer to the device object or Unicode string of ARC
    name
    Arg2: c0000034
    Arg3: 00000000
    Arg4: 00000000

    Debugging Details:
    ------------------

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0x7B

    LAST_CONTROL_TRANSFER:  from 805360c7 to 804e2a42

    STACK_TEXT:
    f789e08c 805360c7 00000003 f789e3e8 00000000
    nt!RtlpBreakWithStatusInstruction
    f789e0d8 80536b9e 00000003 00000000 80087000
    nt!KiBugCheckDebugBreak+0x19
    f789e4b8 805371b2 0000007b f789e524 c0000034 nt!KeBugCheck2+0x574
    f789e4d8 806ca58f 0000007b f789e524 c0000034 nt!KeBugCheckEx+0x1b
    f789e640 806b7f0b 80087000 00000000 80087000
    nt!IopMarkBootPartition+0x113
    f789e690 806adf9d 80087000 f789e6ac 00034000
    nt!IopInitializeBootDrivers+0x4ba
    f789e838 806af023 80087000 00000000 897e5788 nt!IoInitSystem+0x712
    f789edac 80574128 80087000 00000000 00000000
    nt!Phase1Initialization+0xac7
    f789eddc 804efc71 806ae7d0 80087000 00000000
    nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

    FOLLOWUP_IP:
    nt!IopMarkBootPartition+113
    806ca58f 8d85e4feffff     lea     eax,[ebp-0x11c]

    SYMBOL_STACK_INDEX:  4

    FOLLOWUP_NAME:  MachineOwner

    SYMBOL_NAME:  nt!IopMarkBootPartition+113

    MODULE_NAME:  nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  42251085

    STACK_COMMAND:  kb

    FAILURE_BUCKET_ID:  0x7B_nt!IopMarkBootPartition+113

    BUCKET_ID:  0x7B_nt!IopMarkBootPartition+113

    Followup: MachineOwner
    ---------

    I will post the !devnode 0 1 shortly.

    Has anyone had any problems using AHCI or Native Command Queuing
    issues? Is AHCI supported in XPe? Does this sound like a Sata driver
    problem or a ntloader issue? Any help would be greatly appreciated.

    Cheers

    PH

    Thursday, January 25, 2007 4:57 AM

Answers

  • The AHCI driver needs to be in the image if the SATA disk is configured AHCI. If the ACHI driver is not present with SATA set for AHCI, you will get STOP 7B. The AHCI driver INF file will have to be imported to create a custom component.

    -Sean
    www.sjjmicro.com / www.seanliming.com, Book Author - XP Embedded Advanced, XPe Supplemental Toolkit, WEPOS / POS for .NET Step-by-Step
    Monday, October 19, 2009 7:23 PM
    Moderator

All replies

  • Here is all of the debugger output. Any help would be greatly appreciated.

     


    Microsoft (R) Windows Debugger  Version 6.5.0003.7
    Copyright (c) Microsoft Corporation. All rights reserved.

    Using 1394 for debugging
    Opened \\.\DBG1394_INSTANCE10
    Waiting to reconnect...
    Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
    Kernel Debugger connection established.
    Symbol search path is: C:\WINDOWS\Symbols;srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
    Built by: 2600.xpsp.050301-1521
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
    System Uptime: not available

    *** Fatal System Error: 0x0000007b
                           (0xF789E524,0xC0000034,0x00000000,0x00000000)

    Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
    Loading Kernel Symbols
    ..........................
    Loading unloaded module list

    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7B, {f789e524, c0000034, 0, 0}

    Probably caused by : ntkrnlmp.exe ( nt!IopMarkBootPartition+113 )

    Followup: MachineOwner
    ---------

    nt!RtlpBreakWithStatusInstruction:
    804e2a42 cc               int     3
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    INACCESSIBLE_BOOT_DEVICE (7b)
    During the initialization of the I/O system, it is possible that the driver
    for the boot device failed to initialize the device that the system is
    attempting to boot from, or it is possible for the file system that is
    supposed to read that device to either fail its initialization or to simply
    not recognize the data on the boot device as a file system structure that
    it recognizes.  In the former case, the argument (#1) is the address of a
    Unicode string data structure that is the ARC name of the device from which
    the boot was being attempted.  In the latter case, the argument (#1) is the
    address of the device object that could not be mounted.
    If this is the initial setup of the system, then this error can occur if
    the system was installed on an unsupported disk or SCSI controller.  Note
    that some controllers are supported only by drivers which are in the Windows
    Driver Library (WDL) which requires the user to do a custom install.  See
    the Windows Driver Library for more information.
    This error can also be caused by the installation of a new SCSI adapter or
    disk controller or repartitioning the disk with the system partition.  If
    this is the case, on x86 systems the boot.ini file must be edited or on ARC
    systems setup must be run.  See the "Advanced Server System Administrator's
    User Guide" for information on changing boot.ini.
    If the argument is a pointer to an ARC name string, then the format of the
    first two (and in this case only) longwords will be:
        USHORT Length;
        USHORT MaximumLength;
        PWSTR Buffer;
    That is, the first longword will contain something like 00800020 where 20
    is the actual length of the Unicode string, and the next longword will
    contain the address of buffer.  This address will be in system space, so
    the high order bit will be set.
    If the argument is a pointer to a device object, then the format of the first
    word will be:
        USHORT Type;
    That is, the first word will contain a 0003, where the Type code will ALWAYS
    be 0003.
    Note that this makes it immediately obvious whether the argument is a pointer
    to an ARC name string or a device object, since a Unicode string can never
    have an odd number of bytes, and a device object will always have a Type
    code of 3.
    Arguments:
    Arg1: f789e524, Pointer to the device object or Unicode string of ARC name
    Arg2: c0000034
    Arg3: 00000000
    Arg4: 00000000

    Debugging Details:
    ------------------


    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0x7B

    LAST_CONTROL_TRANSFER:  from 805360c7 to 804e2a42

    STACK_TEXT: 
    f789e08c 805360c7 00000003 f789e3e8 00000000 nt!RtlpBreakWithStatusInstruction
    f789e0d8 80536b9e 00000003 00000000 80087000 nt!KiBugCheckDebugBreak+0x19
    f789e4b8 805371b2 0000007b f789e524 c0000034 nt!KeBugCheck2+0x574
    f789e4d8 806ca58f 0000007b f789e524 c0000034 nt!KeBugCheckEx+0x1b
    f789e640 806b7f0b 80087000 00000000 80087000 nt!IopMarkBootPartition+0x113
    f789e690 806adf9d 80087000 f789e6ac 00034000 nt!IopInitializeBootDrivers+0x4ba
    f789e838 806af023 80087000 00000000 897e5788 nt!IoInitSystem+0x712
    f789edac 80574128 80087000 00000000 00000000 nt!Phase1Initialization+0xac7
    f789eddc 804efc71 806ae7d0 80087000 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    FOLLOWUP_IP:
    nt!IopMarkBootPartition+113
    806ca58f 8d85e4feffff     lea     eax,[ebp-0x11c]

    SYMBOL_STACK_INDEX:  4

    FOLLOWUP_NAME:  MachineOwner

    SYMBOL_NAME:  nt!IopMarkBootPartition+113

    MODULE_NAME:  nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  42251085

    STACK_COMMAND:  kb

    FAILURE_BUCKET_ID:  0x7B_nt!IopMarkBootPartition+113

    BUCKET_ID:  0x7B_nt!IopMarkBootPartition+113

    Followup: MachineOwner
    ---------

    0: kd> !devnode 0 1
    Dumping IopRootDeviceNode (= 0x89808ee8)
    DevNode 0x89808ee8 for PDO 0x89808020
      InstancePath is "HTREE\ROOT\0"
      State = DeviceNodeStarted (0x308)
      Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0x898089e0 for PDO 0x89808b28
        InstancePath is "Root\RDPDR\0000"
        ServiceName is "rdpdr"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0x89808680 for PDO 0x898087c8
        InstancePath is "Root\RDP_KBD\0000"
        ServiceName is "TermDD"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0x89808440 for PDO 0x89808588
        InstancePath is "Root\RDP_MOU\0000"
        ServiceName is "TermDD"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0x89808200 for PDO 0x89808348
        InstancePath is "Root\SYSTEM\0000"
        ServiceName is "swenum"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0x897ccee8 for PDO 0x897cc030
        InstancePath is "Root\SYSTEM\0001"
        ServiceName is "update"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0x897ccbb0 for PDO 0x897cccf8
        InstancePath is "ROOT\ACPI_HAL\0000"
        ServiceName is "\Driver\ACPI_HAL"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
        DevNode 0x897cb4a0 for PDO 0x897cc988
          InstancePath is "ACPI_HAL\PNP0C08\0"
          ServiceName is "ACPI"
          State = DeviceNodeStarted (0x308)
          Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0x8979fc10 for PDO 0x897a31f8
            InstancePath is "ACPI\GenuineIntel_-_x86_Family_6_Model_15\_0"
            ServiceName is "intelppm"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
          DevNode 0x89786608 for PDO 0x897ca030
            InstancePath is "ACPI\GenuineIntel_-_x86_Family_6_Model_15\_1"
            ServiceName is "intelppm"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
          DevNode 0x89769c60 for PDO 0x897b51d0
            InstancePath is "ACPI\PNP0A08\0"
            ServiceName is "pci"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0x89750d78 for PDO 0x89807818
              InstancePath is "PCI\VEN_8086&DEV_29A0&SUBSYS_00000000&REV_02\3&11583659&0&00"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0x89750c58 for PDO 0x89807638
              InstancePath is "PCI\VEN_8086&DEV_29A1&SUBSYS_00000000&REV_02\3&11583659&0&08"
              ServiceName is "pci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0x89782b40 for PDO 0x89806030
                InstancePath is "PCI\VEN_1002&DEV_7249&SUBSYS_0B121002&REV_00\4&2b9c2f50&0&0008"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_NOT_CONFIGURED
              DevNode 0x897b6238 for PDO 0x89782c88
                InstancePath is "PCI\VEN_1002&DEV_7269&SUBSYS_0B131002&REV_00\4&2b9c2f50&0&0108"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_NOT_CONFIGURED
            DevNode 0x89750b38 for PDO 0x897a29e0
              InstancePath is "PCI\VEN_8086&DEV_2834&SUBSYS_81EC1043&REV_02\3&11583659&0&D0"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_NOT_CONFIGURED
            DevNode 0x89750a18 for PDO 0x897a2800
              InstancePath is "PCI\VEN_8086&DEV_2835&SUBSYS_81EC1043&REV_02\3&11583659&0&D1"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_NOT_CONFIGURED
            DevNode 0x897508f8 for PDO 0x89786bd0
              InstancePath is "PCI\VEN_8086&DEV_283A&SUBSYS_81EC1043&REV_02\3&11583659&0&D7"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_NOT_CONFIGURED
            DevNode 0x897507d8 for PDO 0x89786898
              InstancePath is "PCI\VEN_8086&DEV_284B&SUBSYS_81EC1043&REV_02\3&11583659&0&D8"
              ServiceName is "HDAudBus"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
            DevNode 0x897506b8 for PDO 0x897cbcf8
              InstancePath is "PCI\VEN_8086&DEV_283F&SUBSYS_00000000&REV_02\3&11583659&0&E0"
              ServiceName is "pci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0x89750598 for PDO 0x897cb9c0
              InstancePath is "PCI\VEN_8086&DEV_2847&SUBSYS_00000000&REV_02\3&11583659&0&E4"
              ServiceName is "pci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0x897c9ee8 for PDO 0x897a2330
                InstancePath is "PCI\VEN_197B&DEV_2363&SUBSYS_81E41043&REV_02\4&18cd42ce&0&00E4"
                ServiceName is "JRAID"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
              DevNode 0x897c9dc8 for PDO 0x89807030
                InstancePath is "PCI\VEN_197B&DEV_2363&SUBSYS_81E41043&REV_02\4&18cd42ce&0&01E4"
                ServiceName is "pciide"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
                DevNode 0x897eb610 for PDO 0x8974f470
                  InstancePath is "PCIIDE\IDEChannel\5&e79960f&0&0"
                  ServiceName is "atapi"
                  State = DeviceNodeStarted (0x308)
                  Previous State = DeviceNodeEnumerateCompletion (0x30d)
                DevNode 0x897eb4f0 for PDO 0x897eba08
                  InstancePath is "PCIIDE\IDEChannel\5&e79960f&0&1"
                  ServiceName is "atapi"
                  State = DeviceNodeStarted (0x308)
                  Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0x89750478 for PDO 0x897cb688
              InstancePath is "PCI\VEN_8086&DEV_2849&SUBSYS_00000000&REV_02\3&11583659&0&E5"
              ServiceName is "pci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0x897828c0 for PDO 0x897c9818
                InstancePath is "PCI\VEN_10EC&DEV_8168&SUBSYS_81AA1043&REV_01\4&24cafebd&0&00E5"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_NOT_CONFIGURED
            DevNode 0x89750358 for PDO 0x89806cf8
              InstancePath is "PCI\VEN_8086&DEV_2830&SUBSYS_81EC1043&REV_02\3&11583659&0&E8"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_NOT_CONFIGURED
            DevNode 0x89750238 for PDO 0x898069c0
              InstancePath is "PCI\VEN_8086&DEV_2831&SUBSYS_81EC1043&REV_02\3&11583659&0&E9"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_NOT_CONFIGURED
            DevNode 0x897b7008 for PDO 0x89806688
              InstancePath is "PCI\VEN_8086&DEV_2832&SUBSYS_81EC1043&REV_02\3&11583659&0&EA"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_NOT_CONFIGURED
            DevNode 0x897b7ee8 for PDO 0x89805cf8
              InstancePath is "PCI\VEN_8086&DEV_2836&SUBSYS_81EC1043&REV_02\3&11583659&0&EF"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_NOT_CONFIGURED
            DevNode 0x897b7dc8 for PDO 0x898059c0
              InstancePath is "PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_F2\3&11583659&0&F0"
              ServiceName is "pci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0x8979fd78 for PDO 0x89786450
                InstancePath is "PCI\VEN_104C&DEV_8023&SUBSYS_808B1043&REV_00\4&1faf5ea3&0&08F0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_NOT_CONFIGURED
            DevNode 0x897b7ca8 for PDO 0x89805688
              InstancePath is "PCI\VEN_8086&DEV_2810&SUBSYS_00000000&REV_02\3&11583659&0&F8"
              ServiceName is "isapnp"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0x897b6970 for PDO 0x897823d8
                InstancePath is "ISAPNP\ReadDataPort\0"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0x897b6850 for PDO 0x897822c0
                InstancePath is "ACPI\PNP0000\4&14c67d85&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_NOT_CONFIGURED
              DevNode 0x897b6730 for PDO 0x897821a8
                InstancePath is "ACPI\PNP0200\4&14c67d85&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_NOT_CONFIGURED
              DevNode 0x897b6610 for PDO 0x89783b90
                InstancePath is "ACPI\PNP0100\4&14c67d85&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_NOT_CONFIGURED
              DevNode 0x89768008 for PDO 0x89783a78
                InstancePath is "ACPI\PNP0B00\4&14c67d85&0"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0x89768ee8 for PDO 0x89783960
                InstancePath is "ACPI\PNP0800\4&14c67d85&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_NOT_CONFIGURED
              DevNode 0x89768dc8 for PDO 0x89783848
                InstancePath is "ACPI\PNP0C04\4&14c67d85&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_NOT_CONFIGURED
              DevNode 0x89768ca8 for PDO 0x89783730
                InstancePath is "ACPI\PNP0501\1"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_NOT_CONFIGURED
              DevNode 0x89768b88 for PDO 0x89783618
                InstancePath is "ACPI\PNP0700\4&14c67d85&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_NOT_CONFIGURED
              DevNode 0x89768a68 for PDO 0x89783500
                InstancePath is "ACPI\PNP0C02\2e"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_NOT_CONFIGURED
              DevNode 0x89768948 for PDO 0x897833e8
                InstancePath is "ACPI\PNP0C02\10"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_NOT_CONFIGURED
              DevNode 0x89768828 for PDO 0x897832d0
                InstancePath is "ACPI\ATK0110\1010110"
                ServiceName is "MTsensor"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
              DevNode 0x89768708 for PDO 0x897b6f18
                InstancePath is "ACPI\PNP0103\4&14c67d85&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_NOT_CONFIGURED
              DevNode 0x897685e8 for PDO 0x897b6e00
                InstancePath is "ACPI\PNP0401\4&14c67d85&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_NOT_CONFIGURED
              DevNode 0x897684c8 for PDO 0x897b6ce8
                InstancePath is "ACPI\PNP0C02\0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_NOT_CONFIGURED
              DevNode 0x897683a8 for PDO 0x897b6bd0
                InstancePath is "ACPI\PNP0303\4&14c67d85&0"
                ServiceName is "i8042prt"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
              DevNode 0x89768288 for PDO 0x897b6ab8
                InstancePath is "ACPI\PNP0F03\4&14c67d85&0"
                ServiceName is "i8042prt"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
            DevNode 0x897b7b88 for PDO 0x897c9630
              InstancePath is "PCI\VEN_8086&DEV_2820&SUBSYS_81EC1043&REV_02\3&11583659&0&FA"
              ServiceName is "pciide"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0x897e84c0 for PDO 0x897e8a08
                InstancePath is "PCIIDE\IDEChannel\4&525cdf1&0&0"
                ServiceName is "atapi"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0x897a1008 for PDO 0x897e8838
                InstancePath is "PCIIDE\IDEChannel\4&525cdf1&0&1"
                ServiceName is "atapi"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0x897b7a68 for PDO 0x897cdb28
              InstancePath is "PCI\VEN_8086&DEV_283E&SUBSYS_81EC1043&REV_02\3&11583659&0&FB"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_NOT_CONFIGURED
            DevNode 0x897b7948 for PDO 0x897cd7f0
              InstancePath is "PCI\VEN_8086&DEV_2825&SUBSYS_81EC1043&REV_02\3&11583659&0&FD"
              ServiceName is "pciide"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0x89805878 for PDO 0x897b7560
                InstancePath is "PCIIDE\IDEChannel\4&2af91a6&0&0"
                ServiceName is "atapi"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0x897cb370 for PDO 0x89782718
                InstancePath is "PCIIDE\IDEChannel\4&2af91a6&0&1"
                ServiceName is "atapi"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0x897b7828 for PDO 0x89805200
              InstancePath is "ACPI\PNP0C01\a"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_NOT_CONFIGURED
            DevNode 0x897b7708 for PDO 0x897cd580
              InstancePath is "ACPI\PNP0C02\11"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0x89769b40 for PDO 0x897b54a0
            InstancePath is "ACPI\PNP0C01\1"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0x89769908 for PDO 0x89769110
            InstancePath is "ACPI\PNP0C0C\aa"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0x897697e8 for PDO 0x89769f18
            InstancePath is "ACPI\FixedButton\2&daba3ff&0"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0x8979eee8 for PDO 0x89768190
        InstancePath is "ROOT\Ftdisk\0000"
        ServiceName is "Ftdisk"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0x8974fee8 for PDO 0x8979e2b8
        InstancePath is "ROOT\dmio\0000"
        ServiceName is "dmio"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
    0: kd> !object help
    *** ERROR: Module load completed but symbols could not be loaded for jraid.sys
    *** Invalid address argument specified
    0: kd> lm
    start    end        module name
    804d7000 806fd000   nt         (pdb symbols)          c:\websymbols\ntkrnlmp.pdb\1F623A3A03514FBA84802D392AFDDE182\ntkrnlmp.pdb
    806fd000 8071dd00   hal        (pdb symbols)          C:\WINDOWS\Symbols\dll\halmacpi.pdb
    baf2b000 baf45580   Mup        (pdb symbols)          C:\WINDOWS\Symbols\sys\mup.pdb
    baf46000 baf72a80   NDIS       (pdb symbols)          C:\WINDOWS\Symbols\sys\ndis.pdb
    baf73000 bafff480   Ntfs       (pdb symbols)          C:\WINDOWS\Symbols\sys\ntfs.pdb
    f746b000 f7481780   KSecDD     (pdb symbols)          C:\WINDOWS\Symbols\sys\ksecdd.pdb
    f7482000 f7499800   SCSIPORT   (pdb symbols)          C:\WINDOWS\Symbols\SYS\scsiport.pdb
    f749a000 f74b1480   atapi      (pdb symbols)          C:\WINDOWS\Symbols\sys\atapi.pdb
    f74b2000 f74d7700   dmio       (pdb symbols)          C:\WINDOWS\Symbols\sys\dmio.pdb
    f74d8000 f74f6880   ftdisk     (pdb symbols)          C:\WINDOWS\Symbols\sys\ftdisk.pdb
    f7597000 f75c4d80   ACPI       (pdb symbols)          C:\WINDOWS\Symbols\sys\acpi.pdb
    f75c5000 f75d5a80   pci        (pdb symbols)          C:\WINDOWS\Symbols\sys\pci.pdb
    f75f7000 f75ffc00   isapnp     (pdb symbols)          C:\WINDOWS\Symbols\sys\isapnp.pdb
    f7607000 f7611500   MountMgr   (pdb symbols)          C:\WINDOWS\Symbols\sys\mountmgr.pdb
    f7617000 f7621d80   jraid      (no symbols)          
    f7627000 f7635e80   ohci1394   (pdb symbols)          C:\WINDOWS\Symbols\sys\ohci1394.pdb
    f7637000 f7644000   1394BUS    (pdb symbols)          C:\WINDOWS\Symbols\SYS\1394bus.pdb
    f7647000 f764fe00   disk       (pdb symbols)          C:\WINDOWS\Symbols\sys\disk.pdb
    f7657000 f7663200   CLASSPNP   (pdb symbols)          C:\WINDOWS\Symbols\SYS\classpnp.pdb
    f7707000 f770b900   PartMgr    (pdb symbols)          C:\WINDOWS\Symbols\sys\partmgr.pdb
    f770f000 f7715200   PCIIDEX    (pdb symbols)          C:\WINDOWS\Symbols\SYS\pciidex.pdb
    f7897000 f789a000   BOOTVID    (pdb symbols)          C:\WINDOWS\Symbols\dll\bootvid.pdb
    f7987000 f7988d00   kdcom      (pdb symbols)          C:\WINDOWS\Symbols\dll\kd1394.pdb
    f7989000 f798a100   WMILIB     (pdb symbols)          C:\WINDOWS\Symbols\SYS\wmilib.pdb
    f798b000 f798c700   dmload     (pdb symbols)          C:\WINDOWS\Symbols\sys\dmload.pdb
    f7a4f000 f7a4fd00   pciide     (pdb symbols)          C:\WINDOWS\Symbols\sys\pciide.pdb
    f7b1b000 f7bde400   dmboot     (pdb symbols)          C:\WINDOWS\Symbols\sys\dmboot.pdb

    Thursday, January 25, 2007 5:48 PM
  • Hi Ph,

    Looking at the response from the newgroup, I see a lot of suggestions. I wanted to explain some of the boot process to remove the confusion on the 7B bugcheck.

    There are two phases of the boot that you are seeing.

     

    NTLDR. This portion reads the boot.ini. NTLDR has the capability to do basic reads. It loads ntoskrnl.exe and boot critical drivers then passes control to the kernel (ntosknrl.exe).

    NTOSKRNL.EXE: Completes the boot process, using the drivers loaded by ntldr. 7B bugchecks occur in the kernel.

     

    You mentioned your registry key for your boot critical devices is the same as xp pro. Ie start=0 indicating a boot driver. This makes sure the driver was loaded by ntldr and passed to ntosknrl.exe.

    So that leads me to suspect it's during pnp when ntoskrnl has control.

     

    Now, during PNP operation in the kernel, a special key is used to help with device enumeration. (HKLM\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase)

     

    Can you check if your special hardware is found in XP pro but not XPe in this key?

      

    -milong

    Monday, January 29, 2007 8:27 PM
  • Although I have not fixed the original problem I seem to have found a
    work-around. Here goes...

    My original problem consisted of not being able to boot to the AHCI
    enabled SATA port on the motherboard. For some reason XPe could not
    read the volume during the initial FBA boot, believe me I tried
    everything. Anyway my workaround goes as such.

    First off I partitioned and formated the target drive connected to the
    AHCI enabled SATA port on the motherboard. Next I transferred the
    image to the target drive then powered off. At this point before
    whenever I tried to reboot to that AHCI SATA port I would fail
    miserably with a STOP 7B bug-check. Woow Wooow Woooow! So after
    transfering the image I powered down and disconnected the drive from
    the AHCI SATA port and connected the drive to on of the other non AHCI
    ports with AHCI still enabled in the BIOS, turned the power back on
    and... no 7B and no AHCI. Once FBA is finished I shutdown the
    computer, unplug the drive from the non-AHCI SATA port and plug it
    back into the AHCI enabled SATA port and power back on, whats this...
    no 7B... AHCI enabled.

    Can anyone explain that?

    I have re-run the kernel debugger and see that the drivers actually
    load when they are suppose to and everything seems to be working fine
    so I guess that will work for now.

    Thanks everyone for the help and suggestions.

    PH

    Tuesday, January 30, 2007 11:40 PM
  • This last post really help me figure out the issue that I was having with a Dell Opti 755.  I had to image a drive to it and got the BlueScreen-o-Death (with the prev mentioned stop erros).  All I did to resolve the issue is go to the bios and disable the AHCI, and change it to the alternative which was ATA.  The PC booted up perfectly fine.  I'll see if I can enable the AHCI once I install all the dell drivers properly in the Windows OS. 
    Does anyone know what benefits the AHCI has?
    Friday, February 1, 2008 7:04 PM
  •  

    I have been having the same issue on a dell optiplex 755 myself. I had to reimage the machine and now while the other drive configurations work (such as legacy and ata), the new AHCI provides the above 7b stop error.
    Friday, May 16, 2008 8:00 PM
  • You will need the AHCI driver in the image in order for the system to boot.

     

    -Sean

     

     

    Saturday, May 17, 2008 3:42 AM
    Moderator
  • As Sean stated, you will need to add/create the AHCI Driver component before this will work.

     

    -P

    Monday, May 19, 2008 3:38 PM
  •  

     

    You could try installing a full XP Pro build on the device, then use DevCon (link below) to install the AHCI drivers for your chipset.  Then, see if the system boots.  If yes, then repeat the process on XPe.  Your bug check and call stack indicates that Kernel Mode PnP did not set up the boot critical disk stack correctly.   I suspect that the ACHI drivers were not correctly componentized (start type = 0, critical device database entries, etc) when converted to the SLD.    Using the Kernel Debugger, you could also dump the loaded driver modules to see what boot critical drives you are missing.  Again, on a full build of XP Pro, if that works, you can view the boot critical stack with DevCon or Device Manger (view by connection).

    Ideally you would want to configure the component correctly via Component Designer to avoid the work around.  A good component to look at is the USB Boot 2.0 component since it’s adds boot critical drivers to the boot stack and shows the required CDD and Service registry keys required to boot.  The same would apply to ACHI for boot.  

    http://support.microsoft.com/kb/311272

    Tuesday, May 20, 2008 8:11 PM
  • In my Toshiba laptop the sATA disk can be configured as AHCI or Compatibility. In AHCI mode I got the same error 7B when trying to install Windows XP.
    I changed it in BIOS to Compatibility and everything worked OK.
    • Proposed as answer by Apache92 Thursday, July 8, 2010 1:42 PM
    Monday, October 19, 2009 6:27 PM
  • The AHCI driver needs to be in the image if the SATA disk is configured AHCI. If the ACHI driver is not present with SATA set for AHCI, you will get STOP 7B. The AHCI driver INF file will have to be imported to create a custom component.

    -Sean
    www.sjjmicro.com / www.seanliming.com, Book Author - XP Embedded Advanced, XPe Supplemental Toolkit, WEPOS / POS for .NET Step-by-Step
    Monday, October 19, 2009 7:23 PM
    Moderator
  • Thanks all ... This really helped me ... I too have Dell OptiPlex 755 and it suddenly started giving the STOP 7B error. The fix that worked for me is to change the drive to ATA rather than AHCI ... It worked like a wonder.

    Thanks to all once again.

    Monday, March 14, 2011 8:58 AM
  • In my Toshiba laptop the sATA disk can be configured as AHCI or Compatibility. In AHCI mode I got the same error 7B when trying to install Windows XP.
    I changed it in BIOS to Compatibility and everything worked OK.

      This worked for me. Switched hdd in BIOS from AHCI to IDE and it works now.
    Thursday, June 14, 2012 9:24 PM