System Builder Tip: Vista Install - Stop Error 0x0000009F - FIXED!!!

DRIVER_POWER_STATE_FAILURE

Hmmmm, KB Troubleshooting a Stop 0x9F Error in Windows XP nope.

KB Troubleshooting STOP 0x9F Error Messages in Windows, again nope.

KB You receive a Stop 0x9F error when you wake a Windows Vista-based computer that is connected to an IEEE 1394-based device definitely doesn't cut it either as the BSOD happens during install.

The setup is a brand new Intel D945GTP, Pentium D, and Kingston RAM. Most BIOS settings and on board components are disabled with the exception of the video. Two revisions of this board did it: the GTPL and the GTPLKR.

At least this time the Stop Error stayed there and the thing didn't reboot on me. When it kept rebooting, all I saw was the blue flash. After the reboot into setup it would do it again in exactly the same spot. Just a tad bit frustrating.

Not sure what I am going to do as there is little info out there on it other than the KB articles already cited.

Looks like Microsoft doesn't have this one licked yet! :(

For you system builders, be wary of quoting on a system with Vista before you have tested the configuration. Things like this could be costly to your business and your client's trust in you.

UPDATE 2007-02-23: Okay, a lot of hits on this one. I will dig deeper to see if I can discover a work-around.
If anyone comes up with the solution, please comment!

UPDATE 2007-03-08: I picked up an ATI FireMV 2200 PCI-E low profile capable video card so as to bypass the onboard video. I till get the BSOD.

I am a little stumped. Going to check and see if we can update the BIOS and go from there.

UPDATE 2007-03-23: Spoke with Intel Desktop Board Technical Support about this issue this evening. The tech recommended I try a different media disk. So, off goes the OLP Ultimate version, and on goes the OEM Business version.

The system still blue screened. Different error this time, and I could not catch it as the screen went blank as soon as the last line peeled off the screen.

But, after trying a little bit of a different tact for searching, Vista Install Error Log, I came up with Vista Install Freeze Problem on Microsoft's Forum.

Instead of booting into Windows PE (did not know/realize that I could - heh still learning ;)) I took the drive over to our Data Mule station and slaved it up. Did a search for logs on the failed Vista install and came up with:

2007-03-24 00:14:37, Error [windeploy.exe] Failure occured during online installation. Online installation cannot complete at this time.; hr = 0x8007000a

This came from the setuperr.log that was in C:\Windows\Panther\UnattendGC.

Then from setupact.log also in the same directory:

2007-03-24 00:12:27, Info [windeploy.exe] ------------------------------------------------
2007-03-24 00:12:27, Info [windeploy.exe] WinDeploy.exe launched with command-line []...
2007-03-24 00:12:27, Info [windeploy.exe] Setup has not completed, adding pending reboot.
2007-03-24 00:12:27, Info [windeploy.exe] Found no unattend file.
2007-03-24 00:12:27, Info [windeploy.exe] Found generalization state [0x4], setup.exe completion flag [False] --> launching setup.exe.
2007-03-24 00:12:27, Info [windeploy.exe] Launching [C:\Windows\system32\oobe\setup.exe]...
2007-03-24 00:14:37, Info [windeploy.exe] ------------------------------------------------
2007-03-24 00:14:37, Info [windeploy.exe] WinDeploy.exe launched with command-line []...
2007-03-24 00:14:37, Info [windeploy.exe] Setup has not completed, adding pending reboot.
2007-03-24 00:14:37, Info [windeploy.exe] Setup was launched during Safe mode.
2007-03-24 00:14:37, Error [windeploy.exe] Failure occured during online installation. Online installation cannot complete at this time.; hr = 0x8007000a
2007-03-24 00:14:49, Info [windeploy.exe] Flushing registry to disk...
2007-03-24 00:14:50, Info [windeploy.exe] Flush took 656 ms.
2007-03-24 00:14:50, Info [windeploy.exe] WinDeploy.exe exiting with code [0x8007000a]

Both of the above errors were the last log files to be touched by the OS just before it died.

And then, from the setupapi.dev.log in the C:\Windows\inf directory we have the following:

inf: {Install Inf Section [i945G0] exit (0x00000000)}
inf: {Install Inf Section [i945G0.Hw]}
inf: Empty section
inf: {Install Inf Section [i945G0.Hw] exit (0x00000000)}
dvi: {Writing Device Properties}
dvi: Provider name=Intel Corporation
dvi: DriverDate 08/21/2006
dvi: DriverVersion=7.14.10.1103
dvi: Class name=Display
dvi: Manufacturer=Intel Corporation
dvi: Matching DeviceID=pci\ven_8086&dev_2772
dvi: Strong Name=igdlh.inf:Intel.Mfg:i945G0:7.14.10.1103:pci\ven_8086&dev_2772
dvi: {Writing Device Properties - Complete}
inf: {Install Inf Section [i945G0.Services]}
inf: AddService=ialm,0x00000002,ialm_Service_Inst (igdlh.inf line 115)
inf: ServiceType=1 (igdlh.inf line 127)
inf: StartType=3 (igdlh.inf line 128)
inf: ErrorControl=0 (igdlh.inf line 129)
inf: ServiceBinary=C:\Windows\system32\DRIVERS\igdkmd32.sys (igdlh.inf line 131)
inf: LoadOrderGroup=Video (igdlh.inf line 130)
dvi: Add Service: Modified existing service 'ialm'.
inf: {Install Inf Section [i945G0.Services] exit(0x00000000)}
dvi: {Install DEVICE exit (0x00000000)}
dvi: Writing common driver property settings.
dvi: DriverDescription=Intel(R) 82945G Express Chipset Controller 0 (Microsoft Corporation - WDDM)
dvi: DeviceDisplayName=Intel(R) 82945G Express Chipset Controller 0 (Microsoft Corporation - WDDM)
dvi: {Restarting Devices} 00:13:07.671
<ins>
àà‡uæým ý  àà7Š+ÔŸ Ú@

Those last characters demonstrate something unhappy in the install process me thinks. And this kinda points to what I have a hunch about: Intel delivered some sort of driver for the Vista image for the 945G chipset that doesn't seem to be working.

They worked on the 965 chipset because it is current, and a lot of new systems would be going out on it. That seems to me to be logical at this point from a business point of view, but, what about those of us who are still supplying 945 chipset based systems?

So, I am waiting for the Intel rep to call back so that I can let him know that the install failed on a different Vista DVD media set.

To cap it all off, here is what I have done so far (keep in mind that setup has started from ground zero with each combination:

• Swapped hard drives
• Tried an Adaptec 1210SA RAID controller
• Turned off all of the BIOS settings for any peripheral device or service
• Originally 2 x 512 MB Kingston
• 2 x 1 GB Kingston
• 1 of each stick of 512 MB or 1 GB Kingston
• Turned on all BIOS settings + added ATI FireMV 2200 PCI-E video
• Turned off all BIOS settings with the above ATI
• Different Pentium D CPU
• Different PSU
• Different optical drive
• USB optical drive versus IDE
• Unplug every connector except keyboard and video + all BIOS settings off
• Updated the BIOS!!!
• Different BIOS revisions

Obviously this is not the complete list. But, it gives you an idea of the amount of time I have put in trying to figure this one out.

I don't see it as a waste of time, I see it as a challenge! :D

And, once I have exhausted all possible avenues, I will let it go. But, for now, there are a couple more to go yet including an RMA for this board.

But, before the above happens, I also have the 64 bit OLP version of Vista Ultimate. I think I might as well give it a whirl while waiting for the SBS setup to finish for an install we are doing tomorrow! :D

Hmmmm...I caught sight of the offending driver briefly: something like igdkme....sys ... That kinda says Intel Graphics ??? 64 bit install dies at the same spot too. :(

UPDATE 07-03-24: WHOOO HOOO!!!!

I finally got Vista Ultimate 32 bit to install on this board! Intel just released a BIOS update for the board that fixed compatibility issues.

It sure did! :D

Sometimes, patience and persistence does pay off and makes the whole struggle worth it!

Thanks to Ben over at Intel Desktop Board Support who helped me with some suggestions along with the recommendation to check out the newly released BIOS.

So, to you System Builders, if you are having Stop issues, bet on the system board and a needed BIOS update for compatibility!

Now, on to some testing for Aero compatibility and Assessment Scores.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists