Audio driver no go no matter what!

[ell]

I have just performed a clean install of vista 32bit home pre. No matter what I can't get the audio driver to install right, I've downloaded the driver from hp, the audio driver error is:

This device cannot find enough free resources that it can use. (Code 12)

If you want to use this device, you will need to disable one of the other devices on this system.


two two issues I have here
Name: High Definition Audio Controller
Description: High Definition Audio Controller
Manufacturer: Microsoft
Device ID: PCI\VEN_10DE&DEV_07FC&SUBSYS_2A64103C&REV_A1\3&2411E6FE&0&48
PNP Device ID: PCI\VEN_10DE&DEV_07FC&SUBSYS_2A64103C&REV_A1\3&2411E6FE&0&48
Service: HDAudBus
Class GUID: {4d36e97d-e325-11ce-bfc1-08002be10318}and one of the two standard dual pci ide controllers has an issue:


Name: Standard Dual Channel PCI IDE Controller
Description: Standard Dual Channel PCI IDE Controller
Manufacturer: (Standard IDE ATA/ATAPI controllers)
Device ID: PCI\VEN_10DE&DEV_056C&SUBSYS_2A64103C&REV_A1\3&2411E6FE&0&40
PNP Device ID: PCI\VEN_10DE&DEV_056C&SUBSYS_2A64103C&REV_A1\3&2411E6FE&0&40
Service: pciide
Class GUID: {4d36e96a-e325-11ce-bfc1-08002be10318}

Audio works fine in linux live cd, this driver stuff can drive me crazy sometimes! ideas?

 

[phaZed]

Sounds like the chipset drivers are not installed or are not installed correctly. Another possibility is a failing board/controller.

 

[NYJimbo]

This device cannot find enough free resources that it can use. (Code 12)

Go to device manager and then click on "view resources by connection" or whatever they call it and look at the IRQ usage, scroll through, you might have to go far to find the PCI devices. See if anything is clashing. If so you might have to install a newer driver as the existing drivers might be using same IRQ's and not allowing PNP to rule. Poke around in there but if you still cant find anything get the latest drivers for both, dont just use MS drivers, check the dates too.

ps - what is the make and model of machine. Might help for this diag.

 

[bertie40]

Unusual in a fresh install. Is that "fresh" fresh, or fresh with a couple of program's installed.

Has a full windows update been performed ?

Have the main chipset drivers been installed first ?

Service packs ?

Full set of motherboard drivers ie, from a CD ?

Is the BIOS current ?

Unplugged any other cards ?
Regards.

 

[FoolishTech]

probably a dumb suggestion, but do you have a setting for PNP OS in the BIOS and is it enabled?

If not, agreed a BIOS update and chipset drivers are a concern.

 

[bertie40]

Could you please supply a few more details. PC manufacturer, motherboard manufacturer etc. etc.

 

[bertie40]

Could you please supply a few more details.
PC manufacturer ?
Motherboard manufacturer ?
Is the sound card a plugin?
Chipset manufacturer ?

Have you googled the motherboard?

Does an established problem exist ?
etc. etc.

Shoe size ?
Inside leg measurement. Stuff like that.

 

[ell]

Could you please supply a few more details.
PC manufacturer ?
Motherboard manufacturer ?
Is the sound card a plugin?
Chipset manufacturer ?

Have you googled the motherboard?

Does an established problem exist ?
etc. etc.

Shoe size ?
Inside leg measurement. Stuff like that.

Well, I'm a sz 10...but I got impatient and threw win 7 on it cuz it was my own bench pc and I couldn't find anyway in device manager in stupid vista would show me where I could change the conflict address or even see who the culprit was. I know its a driver because I did a full reinstall and there was sound just fine until a pile of other drivers got installed then on reboot, no sound and the conflict error. I'm thinking the Dual Channel PCI IDE Controller driver I installed all the drivers I could find for the model on hp. I disabled the ones I suspected and still couldn't get it installed. Wish there was a tool that would just point to the culprit or conflict.

 

[NYJimbo]

...but I got impatient and threw win 7 on it cuz it....

But you didn't learn anything from this. I know you got impatient but you would have learned so much from this issue that you could have used in the future. It's situations like this where you dig into something and not only resolve the immediate issue at hand but also learn other things like how to understand all the stuff inside things like the Device manager that you might not normally have a reason to poke around in. Vista DOES have all you need to find the conflict and you had a controlled environment, you knew it worked before the drivers but not after. Well, if PLAN B works, it works, but I think you missed out on some valuable learning.

 

[ell]

But you didn't learn anything from this. I know you got impatient but you would have learned so much from this issue that you could have used in the future. It's situations like this where you dig into something and not only resolve the immediate issue at hand but also learn other things like how to understand all the stuff inside things like the Device manager that you might not normally have a reason to poke around in. Vista DOES have all you need to find the conflict and you had a controlled environment, you knew it worked before the drivers but not after. Well, if PLAN B works, it works, but I think you missed out on some valuable learning.

I know, I wish I could have hung with it longer, this is why I got into this business! I had to get my bench pc working with stuff coming in, I'm chalking it up to my vista image, which I will be using again on other systems so I may run across the issue again!