If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Mystery PCI device needs to be installed after roll back to SP3 XP Pro
After rolling back to SP2 with XP Pro I'm getting a message on boot
that a PCI device needs to be reinstalled.I see a yellow X in device manager but it's not clear to me what device it is. I only have 2 PCI cards installed - an Audigy Soundcard and a video card, both of which are working. I'm getting a BSOD when attempting to bring up Pinnacle Studio (video app) and I'm guessing it's related to this. An uninstall and reinstall of Pinnacle Studio didn't help. Trying to do auto install doesn't work. How do I determine what this PCI device is? Thanks. |
Ads |
#2
|
|||
|
|||
Mystery PCI device needs to be installed after roll back to SP3XP Pro
Doc wrote:
After rolling back to SP2 with XP Pro I'm getting a message on boot that a PCI device needs to be reinstalled.I see a yellow X in device manager but it's not clear to me what device it is. I only have 2 PCI cards installed - an Audigy Soundcard and a video card, both of which are working. I'm getting a BSOD when attempting to bring up Pinnacle Studio (video app) and I'm guessing it's related to this. An uninstall and reinstall of Pinnacle Studio didn't help. Trying to do auto install doesn't work. How do I determine what this PCI device is? Thanks. What do you see at the end of the C:\WINDOWS\setupapi.log file ? If something needs to be installed and fails, perhaps the VEN/DEV info is recorded for the device there. The entries are dated, and you're only going to have to look at the last few days worth (since the uninstall), to get a picture of what is going on. If I had to guess, a sound card could have a Firewire port (Pinnacle crash...) or a gameport. I would have thought a Firewire chip would install on its own, but who knows. Even if it's behind a bridge, it should be discovered and loaded. Paul |
#3
|
|||
|
|||
Mystery PCI device needs to be installed after roll back to SP3XP Pro
Don't see anything that I understand where you indicated. Device
manager says "No drivers required or installed for this device". This is what comes up under device instance ID on the Device Manager. PCI\VEN_8086&DEV_293E&SUBSYS_A0021458&REV_02\3&13C 0B0C5&0&D8 |
#4
|
|||
|
|||
Mystery PCI device needs to be installed after roll back to SP3XP Pro
Doc wrote:
Don't see anything that I understand where you indicated. Device manager says "No drivers required or installed for this device". This is what comes up under device instance ID on the Device Manager. PCI\VEN_8086&DEV_293E&SUBSYS_A0021458&REV_02\3&13C 0B0C5&0&D8 That's from an Intel chipset. The 8086 part tells you that. And yet, if I search in a recently downloaded INFINST from Intel, I don't get a hit on that number. In this thread, someone indicates it's related to HDAudio. http://en.community.dell.com/support.../18788125.aspx Same sorta idea here. Now, if I look in an actual UAA hotfix file, I see PCI\CC_0403 as a Device Instance ID in it. If you check your list of Device Instance IDs, that might be there as well. The CC or Class Code is a shorthand for certain standard interfaces (or interface types), and is sometimes used for matching in .inf files. http://forum.notebookreview.com/asus...nd-issues.html ******* My *guess* is: 1) SP3 service pack has built in Microsoft UAA driver. 2) For users of SP1 and SP2, UAA was available via a hotfix. You couldn't install HDaudio unless someone provided you with the Microsoft UAA driver. 3) Things like a RealTek audio driver (and others), include the hotfix in a separate folder. On RealTek, look for "MSHDQFE" as proof of that. Included hotfix files are kb888111w2ksp4.exe, kb888111xpsp1.exe, kb888111xpsp2.exe. At one time, the entire Microsoft package was huge, because it had support for 25 languages, while these approx 700K .EXE files are just one language. I've never heard any complaints about that, so perhaps the localization isn't that important. Note, that there is at least one instance of "getting stuck in a loop" with the UAA driver from Microsoft. In the sense that, you try to (re)install the RealTek driver package, and it doesn't work. And it's related to UAA actually already being present, and it needs to be removed, before a sound driver can be successfully re-installed. Recipe here (gathered from a couple places at the time): http://groups.google.com/group/micro...n&dmode=source So without much to go on (nice positive hits), I'd say reinstall your motherboard audio. If you're not using the motherboard audio at all (speakers are wired to your SoundBlaster add-in card), then just disable HDaudio in the BIOS, and the mess will disappear from Device Manager. Good luck, Paul |
#5
|
|||
|
|||
Mystery PCI device needs to be installed after roll back to SP3XP Pro
Appreciate your input. Here's part of the setupapi.log file that seems
to have references to a driver not loading if it gives any clues. [SetupAPI Log] OS Version = 5.1.2600 Service Pack 2 Platform ID = 2 (NT) Service Pack = 2.0 Suite = 0x0100 Product Type = 1 Architecture = x86 [2011/09/06 03:55:38 2772.140 Driver Install] #-019 Searching for hardware ID(s): ide \cdromasus_drw-2014l1t________________________1.02____,ide \asus_drw-2014l1t________________________1.02____,ide \cdromasus_drw-2014l1t________________________,asus_drw-2014l1t________________________1.02____,gencdrom #-018 Searching for compatible ID(s): gencdrom #-198 Command line processed: "C:\WINDOWS\system32\wuauclt.exe" / RunHandlerComServer #I022 Found "GenCdRom" in C:\WINDOWS\INF\cdrom.inf; Device: "CD-ROM Drive"; Driver: "CD-ROM Drive"; Provider: "Microsoft"; Mfg: "(Standard CD-ROM drives)"; Section name: "cdrom_install". #I023 Actual install section: [cdrom_install]. Rank: 0x00000004. Effective driver date: 07/01/2001. [2011/09/06 04:11:35 776.3 Driver Install] #-019 Searching for hardware ID(s): pci \ven_8086&dev_293e&subsys_a0021458&rev_02,pci \ven_8086&dev_293e&subsys_a0021458,pci\ven_8086&de v_293e&cc_040300,pci \ven_8086&dev_293e&cc_0403 #-018 Searching for compatible ID(s): pci\ven_8086&dev_293e&rev_02,pci \ven_8086&dev_293e,pci\ven_8086&cc_040300,pci\ven_ 8086&cc_0403,pci \ven_8086,pci\cc_040300,pci\cc_0403 #-198 Command line processed: C:\WINDOWS\system32\services.exe #I393 Modified INF cache "C:\WINDOWS\inf\INFCACHE.1". #-166 Device install function: DIF_SELECTBESTCOMPATDRV. #W059 Selecting best compatible driver failed. Error 0xe0000228: There are no compatible drivers for this device. #W157 Default installer failed. Error 0xe0000228: There are no compatible drivers for this device. [2011/09/06 04:11:40 4020.2] #-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line: rundll32.exe newdev.dll,ClientSideInstall \\.\pipe \PNP_Device_Install_Pipe_0.{9A116C33-4170-423B-B968-5846E15F4DC0} #I060 Set selected driver. #-019 Searching for hardware ID(s): pci \ven_8086&dev_293e&subsys_a0021458&rev_02,pci \ven_8086&dev_293e&subsys_a0021458,pci\ven_8086&de v_293e&cc_040300,pci \ven_8086&dev_293e&cc_0403 #-018 Searching for compatible ID(s): pci\ven_8086&dev_293e&rev_02,pci \ven_8086&dev_293e,pci\ven_8086&cc_040300,pci\ven_ 8086&cc_0403,pci \ven_8086,pci\cc_040300,pci\cc_0403 #-166 Device install function: DIF_SELECTBESTCOMPATDRV. #W059 Selecting best compatible driver failed. Error 0xe0000228: There are no compatible drivers for this device. #W157 Default installer failed. Error 0xe0000228: There are no compatible drivers for this device. [2011/09/06 14:11:29 776.3 Driver Install] #-019 Searching for hardware ID(s): pci \ven_8086&dev_293e&subsys_a0021458&rev_02,pci \ven_8086&dev_293e&subsys_a0021458,pci\ven_8086&de v_293e&cc_040300,pci \ven_8086&dev_293e&cc_0403 #-018 Searching for compatible ID(s): pci\ven_8086&dev_293e&rev_02,pci \ven_8086&dev_293e,pci\ven_8086&cc_040300,pci\ven_ 8086&cc_0403,pci \ven_8086,pci\cc_040300,pci\cc_0403 #-198 Command line processed: C:\WINDOWS\system32\services.exe #-166 Device install function: DIF_SELECTBESTCOMPATDRV. #W059 Selecting best compatible driver failed. Error 0xe0000228: There are no compatible drivers for this device. #W157 Default installer failed. Error 0xe0000228: There are no compatible drivers for this device. |
#6
|
|||
|
|||
Mystery PCI device needs to be installed after roll back to SP3XP Pro
Doc wrote:
Appreciate your input. Here's part of the setupapi.log file that seems to have references to a driver not loading if it gives any clues. [SetupAPI Log] .... pci\cc_040300 --- That's the value I see in the Microsoft UAA hotfix installer. You need the Microsoft UAA driver, as well as the sound chip HDAudio driver, to have working motherboard sound. You don't need working motherboard sound if you own a sound card. Just turn HDAudio off in the BIOS if you don't need it. If your motherboard sound, is the only sound you've got, then download the sound driver for the sound chip. When the sound driver sees it is on a SP1 or SP2 WinXP system, it will run and install the appropriate hotfix file. In my other message, I indicated these as examples of the hotfix files. kb888111w2ksp4.exe kb888111xpsp1.exe kb888111xpsp2.exe When you see these in the sound driver folders (when the driver is unzipped), you know the driver is prepared to do the right thing for the owner of an SP1 or SP2 system. Vista and Windows 7, as far as I know, already have UAA, so all they'd need is the device-specific sound driver to finish the job. Your system is complaining about CC_040300, so you need UAA to fix it. ******* When I tried this page... http://support.microsoft.com/kb/888111 I was invited to use a Microsoft Fixit :-) This could very well install UAA for you. Tell us how it works out... http://support.microsoft.com/mats/Au...point=lightbox Paul |
Thread Tools | |
Display Modes | |
|
|