Shutdown by power switch with MinLogon

M

Mike Warren

Hello,

I have an image I am happy with except the computer will not shutdown
by pressing the power switch.

The only computer component that I can get to work without a BSOD
on boot is "Standard PC" even though XPPro uses "Advanced
Configuration and Power Interface (ACPI) PC". This may be the root of
my problem.

I have included "ACPI Power Button" and "ACPI Fixed Feature Button"
without success.

I have searched through many messages on Google Groups with the same
problem and it seems there was a bug but it is now fixed.

The problem exists with both "Command Shell" and "Task Manager Shell".

If I execute FBA.exe -shutdown the computer will not power off but displays
"It is now safe to turn off your computer" message.

I even tried adding "Disk Dump Drivers" component because someone said
that had cured the problem for him.

WinLogon images I have created previously for this same hardware have
worked correctly but too many unwanted components are pulled in if I use
WinLogon.

Does anyone have a suggestion of what to do next?

-Mike
 
K

KM

Mike,

Since your BIOS supposrts ACPI, you will have to make ACPI HAL working on your image.
This will fix the power switch issue.

What BSOD you got with ACPI component in configuration?
Did you get the image built from TAP output imported?

KM
 
M

Mike Warren

Hi Konstantin,
Since your BIOS supposrts ACPI, you will have to make ACPI HAL
working on your image. This will fix the power switch issue.

Ok, that's what I thought.
What BSOD you got with ACPI component in configuration?

0x0000007B (0xF8950528,0x0000034,0x00000000,0x00000000)
Did you get the image built from TAP output imported?

Importing TA output causes the same error and I haven't tried TAP
since moving to Minlogon. I'll try that again.

-Mike
 
S

Slobodan Brcin \(eMVP\)

Hi Mike,

Make sure that you add components like:
Microsoft ACPI-Compliant System
Microsoft ACPI-Compliant Embedded Controller
Advanced programmable interrupt controller
Plug and Play Software Device Enumerator

And of course components requred to boot from your disk medium. (For disk, pci, ide controler)

This is not related to shell components but to driver components. Please give us more details of your boot medium so we might help
you. And also BSOD number error would be nice.
If I execute FBA.exe -shutdown the computer will not power off but displays
"It is now safe to turn off your computer" message.

ACPI kernel should help you with that. Just add single or multi processor component.
What QFE's do you use. MS fixed some power problems in new minlogon image.
Also look at how you can use WM_POWERBROADCAST on minlogon in your application to catch button press. Then you can do shutdown.

http://groups-beta.google.com/group...RBROADCAST&qt_g=1&searchnow=Search+this+group

HTH,
Slobodan
 
S

Slobodan Brcin \(eMVP\)

K

KM

Mike,
0x0000007B (0xF8950528,0x0000034,0x00000000,0x00000000)

You are missing a critical device component. Include IDE channels, PCI Bus, disk drive components (include all 3 disk components).

http://msdn.microsoft.com/embedded/community/community/tips/xp/stoperr7b/default.aspx

Or you can do a quick trick - in your current working image that is based on Standard PC HAL, disable the Standard PC component and
add ACPI one (make sure to use the proper one, you can check it with TAP output). Resolve dependencies, rebuild and re-deploy the
new image.
Importing TA output causes the same error and I haven't tried TAP
since moving to Minlogon. I'll try that again.

TA will provide you output that is likely missing some critical components. In my case, for instance, it was IDE Channels that TA
did not pick up.

And, of course, check :
http://groups-beta.google.com/group...crosoft.public.windowsxp.embedded&q=7B&qt_g=1

Konstantin
 
M

Mike Warren

Hi Slobodan,

I understand the error but all I do is swap "Standard PC" with any of the
following:

ACPI Multiprocessor PC
ACPI Uniprocessor PC
Advanced Configuration an Power Interface (ACPI) PC

Doing only this one thing causes the image to go from working correctly
except for the power switch problem to generating the BSOD on first boot.

The computer is a standard ACPI PC mainboard (AOpen) with one IDE HDD
and one IDE DVDROM drive.

I have already included all the components you mentioned in your other message.
Make sure that you add components like:
Microsoft ACPI-Compliant System
Microsoft ACPI-Compliant Embedded Controller
Advanced programmable interrupt controller
Plug and Play Software Device Enumerator

And of course components requred to boot from your disk medium. (For disk,
pci, ide controler)
You can remove most non critical component for boot from TAP results.

I'll try TAP again shortly.
Or you can use standard drivers that will work on all devices of
certain type.

This is exactly what I am trying to achieve.
 
S

Slobodan Brcin \(eMVP\)

Hi Mike,

Add:
- ACPI Multiprocessor PC
-Microsoft ACPI-Compliant System
-Microsoft ACPI-Compliant Embedded Controller
-Advanced programmable interrupt controller
-Plug and Play Software Device Enumerator
- All three Disk Driver components.
- Direct Memory access controler
- FAT
- FAT Format
- Motherboard resources
- Mount Manager
- Numeric Data processor.
- PCI Bus
- Both PnP components.
- Processor
- System CMOS real time clock
- Sytem timer.
- PCI standard host CPU Bridge
- PCI Standard PCI-toPCI bridge
- PCI Standard RAM controler
- Programable Interrupt controler.
- PCI Stadnard EISA bridge
- PCI Standard ISA bridge
- Standard Dual Channel PCI IDE Controller.
- Standard IDE/ESDI Hadr disk controler

HTH,
Slobodan
 
K

KM

Mike,
I understand the error but all I do is swap "Standard PC" with any of the
following:

ACPI Multiprocessor PC
ACPI Uniprocessor PC
Advanced Configuration an Power Interface (ACPI) PC

Doing only this one thing causes the image to go from working correctly
except for the power switch problem to generating the BSOD on first boot.

This is wierd. Especially considering the fact that you were running XP Pro on the target with ACPI HAL.

Any chance of connecting to the target with KD?
The computer is a standard ACPI PC mainboard (AOpen) with one IDE HDD
and one IDE DVDROM drive.

I have already included all the components you mentioned in your other message.



I'll try TAP again shortly.


You won't necessarily have to re-deploy the new image but rather compare the images to see what components you were missing.

And one more way to include necessary components - get TAP running on any ACPI desktop computer. Then just grab the list of
components from the output (or most important components) and implement it in your image. This may be the fastest way.

KM
 
M

Mike Warren

Konstantin,
Or you can do a quick trick - in your current working image that is
based on Standard PC HAL, disable the Standard PC component and add
ACPI one (make sure to use the proper one, you can check it with TAP
output). Resolve dependencies, rebuild and re-deploy the new image.

That's exactly what I'm trying to do.

I just tried a test with TAP. I started with a blank configuration, imported
devices.pmq and resolved all dependencies. This image gives the same 7B
error. I'm now really lost. This is the procedure I originally used for testing
with SP1. I'm now using SP2.

-Mike
 
K

KM

Mike,
I just tried a test with TAP. I started with a blank configuration, imported
devices.pmq and resolved all dependencies. This image gives the same 7B
error. I'm now really lost. This is the procedure I originally used for testing
with SP1. I'm now using SP2.

Do you mean SP1 TAP based image (ACPI) worked on the same target without problem?

If it is not what you meant, can you try it with SP1? Although if you don't have a separate dev machine with SP1 installed, you are
going to have to go back to SP1 on the main dev machine :-(

Also, you mentioned XP Pro.. Was it SP1 or SP2 XP Pro?

KM
 
M

Mike Warren

Konstantin,
Do you mean SP1 TAP based image (ACPI) worked on the same target
without problem?

Unfortunately, it wasn't very scientific. I have been just "mucking around"
with XPe while waiting for SP2. Now I've got SP2, I have to get serious.
One of my successful images was created with that procedure on SP1.

I have 3 units of our target machine here now. One has XP Pro SP1,
one is unformatted and the third one is what I'm testing with.
If it is not what you meant, can you try it with SP1? Although if you
don't have a separate dev machine with SP1 installed, you are going
to have to go back to SP1 on the main dev machine :-(

Two of the components Slobodan listed were not in my image. When I added
them I was able to get past first boot but it stopped on the same 7B error on each
boot after that.

I think I'll try a simpler config starting with Slobodans list. If that doesn't work
I'll upgrade the XPPro machine to SP2 and try again.

-Mike
 
S

Slobodan Brcin \(eMVP\)

Hi Mike,
Two of the components Slobodan listed were not in my image. When I added
them I was able to get past first boot but it stopped on the same 7B error on each
boot after that.

Which two component did help you? It might be important.
Also it is highly uncommon that after you go trough FBA your image stop booting. What disk type do you use for booting?
I think I'll try a simpler config starting with Slobodans list. If that doesn't work
I'll upgrade the XPPro machine to SP2 and try again.

This won't help you. XPe tools are working fine for you on SP1 so you may leave it be since it will not have an impact on XPe image
that you create.

Regards,
Slobodan
 
M

Mike Warren

Hi Slobodan,
Which two component did help you? It might be important.
Also it is highly uncommon that after you go trough FBA your image
stop booting. What disk type do you use for booting?

Standard IDE/ESDI Hard Disk Controller
PCI Standard RAM controller

I'm using a basic IDE HDD with 2 partitions. The first partition is 500MB
and marked active. The second is about 200GB. Both are formated with
NTFS.
This won't help you. XPe tools are working fine for you on SP1 so you
may leave it be since it will not have an impact on XPe image that
you create.

I tried this but still have the 7B error on second boot.
Here is more detail in case you can see something that will give you a clue.

Created a new config.
Added all the components on your list plus NTFS.
I then auto resolved dependencies. This required adding "Command Shell"
and "English Language Support"
I connected the target system hard drive to my dev machine through a USB/IDE
adaptor.
Performed a quick NTFS format on the 500MB partition of the target drive.
Copied the files from my image folder to the 500MB partition of the drive.
Stopped the USB/IDE adaptor.
Removed drive and fitted to target using an IDE cable directly to the motherboard.
Booted target.

-Mike
 
M

Mike Warren

Hi Slobodan,
So in last attempt you did not used any of components provided by TA/TAP,
right? This is good since you now know at least that inf files pulled by
these components is not causing failure.

That's right.
Also what chipset do you use. Or what platform?

It is a AOpen MX4SGI-4DN2 and uses the Intel 865G chipset.

http://asia.aopen.com.tw/Products/mb/MX4SGI-4DN2;MX4SGI-4DN2(P).htm
Do you have an RS-232 or 1394 cable for establishing remote debugging from
your targed machine? This would give you insight where is the problem.
In windbg just type.
1. !devnode 0 1
2. !analyze -v

And send us these results.

I have never used KD or windbg before and am having problems getting it to
work. Here are the results:

kd> !devnode 0 1
Error retrieving address of IopRootDeviceNode

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: f8950524, Pointer to the device object or Unicode string of ARC name
Arg2: c0000034
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x7B
LAST_CONTROL_TRANSFER: from 8053771f to 804e30d9
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f89500d8 8053771f 00000004 00000000 80087000 nt!DbgBreakPointWithStatus+0x4
f89504b8 80537832 0000007b f8950524 c0000034 nt!KeDeregisterBugCheckReasonCallback+0xbc8
f89504d8 806ce5b4 0000007b f8950524 c0000034 nt!KeBugCheckEx+0x1b
f8950640 806bcefb 80087000 00000000 80087000 nt!KeFindConfigurationNextEntry+0x115fd
f8950690 806b2f69 80087000 f89506ac 00034000 nt!KeFindConfigurationEntry+0x4fd2
f8950838 806b3fea 80087000 00000000 81fc8958 nt!SeTokenObjectType+0x16089
f8950dac 80576b24 80087000 00000000 00000000 nt!SeTokenObjectType+0x1710a
f8950ddc 804eed86 806b3797 80087000 00000000 nt!PsCreateSystemThread+0x70
00000000 00000000 00000000 00000000 00000000 nt!KeInitializeTimerEx+0x1eb

FOLLOWUP_IP:
nt!KeDeregisterBugCheckReasonCallback+bc8
8053771f 8b4dfc mov ecx,[ebp-0x4]
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KeDeregisterBugCheckReasonCallback+bc8
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 41107faa
STACK_COMMAND: kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
 
K

KM

Mike,

Did you set the symbol path?

You can set to something like :
srv*c:\websymbols*http://msdl.microsoft.com/download/symbols

Follow instruction from thin link : http://www.microsoft.com/whdc/devtools/debugging/symbols.mspx
After the proper setup you will get more detail and readable results.

KM

Hi Slobodan,
So in last attempt you did not used any of components provided by TA/TAP,
right? This is good since you now know at least that inf files pulled by
these components is not causing failure.

That's right.
Also what chipset do you use. Or what platform?

It is a AOpen MX4SGI-4DN2 and uses the Intel 865G chipset.

http://asia.aopen.com.tw/Products/mb/MX4SGI-4DN2;MX4SGI-4DN2(P).htm
Do you have an RS-232 or 1394 cable for establishing remote debugging from
your targed machine? This would give you insight where is the problem.
In windbg just type.
1. !devnode 0 1
2. !analyze -v

And send us these results.

I have never used KD or windbg before and am having problems getting it to
work. Here are the results:

kd> !devnode 0 1
Error retrieving address of IopRootDeviceNode

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: f8950524, Pointer to the device object or Unicode string of ARC name
Arg2: c0000034
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x7B
LAST_CONTROL_TRANSFER: from 8053771f to 804e30d9
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f89500d8 8053771f 00000004 00000000 80087000 nt!DbgBreakPointWithStatus+0x4
f89504b8 80537832 0000007b f8950524 c0000034 nt!KeDeregisterBugCheckReasonCallback+0xbc8
f89504d8 806ce5b4 0000007b f8950524 c0000034 nt!KeBugCheckEx+0x1b
f8950640 806bcefb 80087000 00000000 80087000 nt!KeFindConfigurationNextEntry+0x115fd
f8950690 806b2f69 80087000 f89506ac 00034000 nt!KeFindConfigurationEntry+0x4fd2
f8950838 806b3fea 80087000 00000000 81fc8958 nt!SeTokenObjectType+0x16089
f8950dac 80576b24 80087000 00000000 00000000 nt!SeTokenObjectType+0x1710a
f8950ddc 804eed86 806b3797 80087000 00000000 nt!PsCreateSystemThread+0x70
00000000 00000000 00000000 00000000 00000000 nt!KeInitializeTimerEx+0x1eb

FOLLOWUP_IP:
nt!KeDeregisterBugCheckReasonCallback+bc8
8053771f 8b4dfc mov ecx,[ebp-0x4]
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KeDeregisterBugCheckReasonCallback+bc8
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 41107faa
STACK_COMMAND: kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
 
M

Mike Warren

Hi Konstantin
Did you set the symbol path?

You can set to something like :
srv*c:\websymbols*http://msdl.microsoft.com/download/symbols

Follow instruction from thin link :
http://www.microsoft.com/whdc/devtools/debugging/symbols.mspx After
the proper setup you will get more detail and readable results.


Thanks, that helps. Is this any better?

kd> !devmode 0 1
No export devmode found

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INACCESSIBLE_BOOT_DEVICE (7b)
During the initialization of the I/O system, it is possible that the driver
.... <snip> ...
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: f8950524, 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 80536753 to 804e30d9
STACK_TEXT:
f895008c 80536753 00000004 ffdff408 00000000 nt!RtlpBreakWithStatusInstruction
f89500d8 8053771f 00000004 00000000 80087000 nt!KiBugCheckDebugBreak+0x19
f89504b8 80537832 0000007b f8950524 c0000034 nt!KeBugCheck2+0xa75
f89504d8 806ce5b4 0000007b f8950524 c0000034 nt!KeBugCheckEx+0x1b
f8950640 806bcefb 80087000 00000000 80087000 nt!IopMarkBootPartition+0x113
f8950690 806b2f69 80087000 f89506ac 00034000 nt!IopInitializeBootDrivers+0x4ba
f8950838 806b3fea 80087000 00000000 81fc8958 nt!IoInitSystem+0x712
f8950dac 80576b24 80087000 00000000 00000000 nt!Phase1Initialization+0xac7
f8950ddc 804eed86 806b3797 80087000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

FOLLOWUP_IP:
nt!IopMarkBootPartition+113
806ce5b4 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: 41107faa
STACK_COMMAND: kb
BUCKET_ID: 0x7B_nt!IopMarkBootPartition+113
Followup: MachineOwner
---------
 
M

Mike Warren

Oops,

I didn't even notice I had typed !devmode instead of !devnode.

-Mike

kd> !devnode 0 1
Dumping IopRootDeviceNode (= 0x81febdd8)
DevNode 0x81febdd8 for PDO 0x81febf10
InstancePath is "HTREE\ROOT\0"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81feb8e8 for PDO 0x81feba30
InstancePath is "Root\ACPI_HAL\0000"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb0370 for PDO 0x81fea6f8
InstancePath is "ACPI_HAL\PNP0C08\0"
ServiceName is "ACPI"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fe8250 for PDO 0x81fd11b0
InstancePath is "ACPI\GenuineIntel_-_x86_Family_15_Model_3\_0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81fe8130 for PDO 0x81fd41a8
InstancePath is "ACPI\PNP0C0C\2&daba3ff&0"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb2258 for PDO 0x81f78e40
InstancePath is "ACPI\PNP0A03\1"
ServiceName is "pci"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81f99628 for PDO 0x81fe9cb8
InstancePath is "PCI\VEN_8086&DEV_2570&SUBSYS_00000000&REV_02\3&13c0b0c5&0&00"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81f99508 for PDO 0x81fe9ad8
InstancePath is "PCI\VEN_8086&DEV_2571&SUBSYS_00000000&REV_02\3&13c0b0c5&0&08"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81f993e8 for PDO 0x81fe98f8
InstancePath is "PCI\VEN_8086&DEV_24D2&SUBSYS_042DA0A0&REV_02\3&13c0b0c5&0&E8"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81f992c8 for PDO 0x81fe95c0
InstancePath is "PCI\VEN_8086&DEV_24D4&SUBSYS_042DA0A0&REV_02\3&13c0b0c5&0&E9"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81f991a8 for PDO 0x81fe8e50
InstancePath is "PCI\VEN_8086&DEV_24D7&SUBSYS_042DA0A0&REV_02\3&13c0b0c5&0&EA"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81f98008 for PDO 0x81fe8b18
InstancePath is "PCI\VEN_8086&DEV_24DE&SUBSYS_042DA0A0&REV_02\3&13c0b0c5&0&EB"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81f98ee8 for PDO 0x81fe87e0
InstancePath is "PCI\VEN_8086&DEV_24DD&SUBSYS_040AA0A0&REV_02\3&13c0b0c5&0&EF"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81f98dc8 for PDO 0x81fe84a8
InstancePath is "PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_C2\3&13c0b0c5&0&F0"
ServiceName is "pci"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fd2ee8 for PDO 0x81fd38a0
InstancePath is "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1f7dbc9f&0&20F0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81fd2dc8 for PDO 0x81fd3568
InstancePath is "PCI\VEN_14F1&DEV_2F00&SUBSYS_200414F1&REV_01\4&1f7dbc9f&0&28F0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81fd2ca8 for PDO 0x81fd3230
InstancePath is "PCI\VEN_8086&DEV_1050&SUBSYS_04AFA0A0&REV_02\4&1f7dbc9f&0&40F0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81f98ca8 for PDO 0x81f78270
InstancePath is "PCI\VEN_8086&DEV_24D0&SUBSYS_00000000&REV_02\3&13c0b0c5&0&F8"
ServiceName is "isapnp"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81f883f8 for PDO 0x81f88030
InstancePath is "ISAPNP\ReadDataPort\0"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81f882d8 for PDO 0x81fd2190
InstancePath is "ACPI\PNP0C02\1"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81f881b8 for PDO 0x81f88f18
InstancePath is "ACPI\PNP0000\4&26dd0f47&0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81fd0008 for PDO 0x81f88e00
InstancePath is "ACPI\PNP0200\4&26dd0f47&0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81fd0ee8 for PDO 0x81f88ce8
InstancePath is "ACPI\PNP0100\4&26dd0f47&0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81fd0dc8 for PDO 0x81f88bd0
InstancePath is "ACPI\PNP0B00\4&26dd0f47&0"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fd0ca8 for PDO 0x81f88ab8
InstancePath is "ACPI\PNP0800\4&26dd0f47&0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81fd0b88 for PDO 0x81f889a0
InstancePath is "ACPI\PNP0C04\4&26dd0f47&0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81fd0a68 for PDO 0x81f88888
InstancePath is "ACPI\PNP0501\2"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81fd0948 for PDO 0x81f88770
InstancePath is "ACPI\PNP0400\1"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81fd0828 for PDO 0x81f88658
InstancePath is "ACPI\PNP0C02\2"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81fd0708 for PDO 0x81f88540
InstancePath is "ACPI\INT0800\4&26dd0f47&0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81f98b88 for PDO 0x81fb1e50
InstancePath is "PCI\VEN_8086&DEV_24DB&SUBSYS_042DA0A0&REV_02\3&13c0b0c5&0&F9"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81f98a68 for PDO 0x81fb1b18
InstancePath is "PCI\VEN_8086&DEV_24D1&SUBSYS_042EA0A0&REV_02\3&13c0b0c5&0&FA"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81f98948 for PDO 0x81fb17e0
InstancePath is "PCI\VEN_8086&DEV_24D3&SUBSYS_042DA0A0&REV_02\3&13c0b0c5&0&FB"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81fb2138 for PDO 0x81fea9f0
InstancePath is "ACPI\PNP0C01\2&daba3ff&0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81f97008 for PDO 0x81f97688
InstancePath is "ACPI\PNP0C0B\2&daba3ff&0"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81f97150 for PDO 0x81fe91f0
InstancePath is "ACPI\ThermalZone\THRM"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb2ee8 for PDO 0x81fe90d8
InstancePath is "ACPI\FixedButton\2&daba3ff&0"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb3ee8 for PDO 0x81fb3030
InstancePath is "Root\Ftdisk\0000"
ServiceName is "ftdisk"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb3ca8 for PDO 0x81fb3df0
InstancePath is "Root\LEGACY_ACPIEC\0000"
ServiceName is "ACPIEC"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb3a68 for PDO 0x81fb3bb0
InstancePath is "Root\LEGACY_KSECDD\0000"
ServiceName is "KSecDD"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb3828 for PDO 0x81fb3970
InstancePath is "Root\LEGACY_MOUNTMGR\0000"
ServiceName is "MountMgr"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb35b0 for PDO 0x81fb36f8
InstancePath is "Root\LEGACY_PARTMGR\0000"
ServiceName is "PartMgr"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb3370 for PDO 0x81fb34b8
InstancePath is "Root\LEGACY_PCI\0000"
ServiceName is "pci"
State = DeviceNodeRemoved (0x312)
Previous State = DeviceNodeStarted (0x308)
Problem = CM_PROB_DEVICE_NOT_THERE
DevNode 0x81fb3130 for PDO 0x81fb3278
InstancePath is "Root\LEGACY_VGASAVE\0000"
ServiceName is "VgaSave"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81feaee8 for PDO 0x81fea030
InstancePath is "Root\SYSTEM\0000"
ServiceName is "swenum"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81feaca8 for PDO 0x81feadf0
InstancePath is "Root\SYSTEM\0001"
ServiceName is "update"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
 
S

Slobodan Brcin \(eMVP\)

Hi Mike,

You should have posted this as txt file attachment, but nevertheless.

pciide did not initialized for some reason :-(

You might want to send us setupapi.log that was made during the FBA.

Also info that was not written to setupapi.log during second boot can be read from remote debugger if you tell windows to send diag
to debugger.
http://msdn.microsoft.com/library/d..._66a07114-953e-49aa-bebf-f9b4ca60a6dd.xml.asp

This all sound too strange. (Ability to pass FBA, and then in second boot XPe wont work)

Regards,
Slobodan
 
K

KM

I was about to point out the same failing lines but Slobodan already sent a message :)

DevNode 0x81fb3370 for PDO 0x81fb34b8
InstancePath is "Root\LEGACY_PCI\0000"
ServiceName is "pci"
State = DeviceNodeRemoved (0x312)
Previous State = DeviceNodeStarted (0x308)
Problem = CM_PROB_DEVICE_NOT_THERE

System Bus Extender is not there.
pciide.sys or pciidex

Mike, do you have a PCI IDE Controller component? Most likely you do since you were able to pass FBA at least once.
If you got "Standard Dual Channel PCI IDE Controller" you will get both pciide.sys and pciidex.sys.

If you still have similar platform running XP Pro, check what System Bus Extender is runinng there: pciide.sys or else?

KM
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top