driver install issue

I have just done a new install of Windows XP on a brand new hard drive.
I have updated all software with Windows Update.
I am installing and updating all drivers.
Everything works except for my sounds card.
I have a Soundblaster Audigy card. I used the original manufacturer install disk as well as downloaded software. It runs through the process and says drivers were installed. When I review in Device Manager, however, it is the only item listed with a yellow question mark: it says "Audio Device on High Defintion Audio Bus" and even when I point to the disk it seems I cannot get this message to disappear.

 

You might try Sound Blaster Audigy Driver for Windows 2000/XP 02.09.0016 at:

http://tinyurl.com/48c5apk

Or Google on Soundblaster Audigy card. "Windows XP", or Sound Blaster Audigy card. "Windows XP".

Please note different results for Sound Blaster, as 1 or 2 words.

Bazza

 

So I uninstalled the items listed in Device Manager.
Then I reinstalled all drivers using the downloaded package.
The sound card works (I have sound) but I am still getting the yellow question marks listed in device manager and I am getting the Windows "new device detected" pop-up windows with startup so something is not completing.

 

Could the entry in Device Manager be an onboard audio device? Did the PC come with the audio card or did you add it later?

Maybe the audio card driver is installed properly but Device Manager sees the onboard audio as not yet installed.

 

BIOS has an option to turn off onboard audio, does that mean I have it?

Audio card was installed by Dell as part of my purchase setup. I am trying to reinstall everything including drivers after a new XP install on a new HD.

 

I tried "uninstalling" the item listed in Device Manager that has the yellow question marks and my sound turned off. So clearly that entry must be the audio card and not onboard audio, yes? I reinstalled the Creative drivers and sound is back, but so are the yellow question marks.

 

What XP Service Pack are you running? I guess it's possible that the Device Manager entry is pointing to the UAA, so try uninstalling the Creative drivers, download and run Driver Sweeper, install the MS UAA driver from here or here, and then reinstall the Creative.

Is this an OEM machine or custom? If OEM, what's the make and model #, Service Tag #s, etc.?

 

XP SP3 just updated from a brand new install. What is the UAA? I will try those steps when I get home tonight, thanks.

Dell XPS400 purchased 2006, Service Tag 9L1N391

 

http://support.microsoft.com/kb/888111. If you're already running SP3, this angle is probably moot, but it's worth a shot to do the uninstall routine mentioned before.

I was hoping that the chipset drivers might be available at Dell, but no luck so far.

 

So I followed all steps. The UAA was unnecessary according to Windows because I am using SP3, as you said. Creative seemed to successfully install.

But I still have that mysterious devise listed in Device Manager called "Audio Device on High Definition Audio Bus." Is there a way I can determine if that is pointing to my sound card or something else?

 

I'm not good at drivers but I would try letting the Intel chipset Utility check your chipset driver is up to date.

http://support.dell.com/support/dow...dateid=-1&formatid=-1&source=-1&fileid=150654

Then you can try this Sigmatel driver which is your onboard audio if I am not mistaken and the likely cause of the problem.

http://support.dell.com/support/dow...dateid=-1&formatid=-1&source=-1&fileid=150155

 

I ran the Intel chipset update. I had done it before, but ran it again just in case.

I tried the Sigmatel driver download and got the error message: "Device Object not present, restart the system and run setup again." I restarted and ran it and got the same message.

 

Sorry, I just don't know enough about drivers.

Maybe Caliban can look at the full list of drivers for your model rather than the limited list that your service tag number brings up. There are two audio drivers but I believe you already have the Creative Labs installed for your sound card.

 

If MB info is needed, here is what Everest found:

Motherboard:
CPU Type DualCore Intel Pentium D 830, 3000 MHz (15 x 200)
Motherboard Name Dell Dell DXP051
Motherboard Chipset Intel Lakeport i945G/P
System Memory 3328 MB (DDR2 SDRAM)
BIOS Type Phoenix (01/08/07)

 

If a mother board driver is installed for a mother board device. Added a new componant. ( "Soundblaster Audigy card" ) The driver for the M/B componant will alway find the M/B componant. Trouble is. It found it on the M/B and wants the driver, hence the error message. If you add a new same type componant and the driver if installed, M/B still sees the M/B installed componant and wants the driver. What you need to do is on the device. Disable it. Not un-install it in as a re-boot. It finds it and wants the driver for it.

 

Have you disabled this yet?

 

Yes, I did, no change.

 

How does your audio sound? Are you using the Creative control panel(s), options, etc.? If so, are they working well?

Any other symptoms or problems with the machine?

 

Everything more or less seems to sound OK. But when I start up Windows there is a "new hardware detected" message i need to cancel three different times.

 

Do you mean the Sigmatel driver or the Creative driver?

 

I pulled the Creative card out of the box. I did the SP2 rollback and installed the UAA and Sigmatel drivers. Card is still out and I have not tried the Creative driver reinstall yet, because on restart I still see the yellow question marks near HD Audio Bus in Device Manager.

 

I finally solved this issue accidentially. I followed every single instruction above and I still got the startup error. I am posting my simple solution here in the hope that someone stumbling upon the same error has the same dumb luck.

So I was busy updating system drivers. I installed the latest drivers for my new EVGA nVidia GT240 video card. With the driver update, packaged together, was a folder "HDAudioWHQLDriver." I finished the update, restarted, and FIXED, no error on startup and everything is working fine.

Thanks for all your previous input

Jeff

 

Good job - in your case, Windows must have been actively seeking the WHQL designation.

Glad you got it sorted, and thanks for the feedback. :major