Everything is good until I put in a PCI envy24 sound card.
With sound card functioning properly, the intel pro100 has an exclamation mark.
One time I uninstalled both devices and rebooted. Windows found the drivers and it all came up working including the intel pro100. Then a reboot and back to the yellow exclamation.
I see alternative button for sound card but is grayed out.
So what would be a way to resolve this?
I'm no expert but the window above that is showing no conflicts is for the sound card. Might have been more helpful to post the same window for the device with the exclamation mark, to see what the conflict is exactly?
In the old days (like 80s) when there were resource conflicts it helped to install the sound card first, by listing it first in autoexec.bat or config.sys (forget which now)... these days they have free programs called something like "Starter Delayer" that let you program in a delay of certain devices so that everything doesn't try to install at once. I don't know if the old rule still holds to let the sound card load first (I think at that time b/c the IRQs etc it could use were limited, and so you wanted it to load first and take what it needed [but I'm sure they are better designed now]), then everything else would make due with what was left.
IAC it would appear your network card p100 and sound card are grabbing for similar addresses or something... maybe installing one of those starter delayer programs that lets you dictate the order things will install at boot would help. Try delaying the sound card to let the network card install first to see if that works.... if not, try the reverse.
I don't know, that's all I got. :)
I can try it.
The properties page for the intel pro100 shows nothing useful, says it has a problem and is not using any resources.
I dont use the pro 100 so if anything was to fail, that would be the one you would want.
This same sound card in a different PC causes other PCI devices to not start, like a tuner card, or sometimes a usb device on the MB.
The sound card works fine, the 5.1 sounds are all there. So i do not understand.
I also booted ubuntu linux on the board and everything works, sound and all 3 NICs, all usbs, tuner, no failures, so problem to me is windows 7, like a driver.
On one pc, I pull out the tuner, and the problem falls onto the usb!
And the sound card driver problem on 3 different pc's all have some kind of failure, tuner, usb, or lan.
It is always device cant start, not using any resources with an exclamation mark.
starter delayer, seems to be about delaying a start up program. From the programs that are installed.
So how about a windows driver initialization? Is a driver a program? It is sort of different.
Autoruns for Windows
Autoruns for Windows
This will tell you what drivers load and in what order.
And I'd try looking for an updated driver for the sound card. It is revealing that everything works fine in Linux... proves all the hardware CAN play nice together, given the proper drivers! I'd also suggest looking for an updated driver for the pc100... that could also be the problem, especially since it couldn't even report what conflict it had.
After installing any new drivers (assuming one or both can be found) if a conflict persists, repeat your procedure of uninstalling the problem device in Device Mgr (do not tick box to uninstall drivers), then click the "scan for new hardware" and let it reinstall... if they can play nice even once it means the problem is in how they are loading at boot up... again, grabbing for the same resources somewhere... and staggering their installation will hopefully solve the problem.
EDIT: The other option is, since you don't use the pro100, just remove it from the machine... or use Dev Mgr to disable it in W7 if you use it in other OSs. But what you are getting is def a resource conflict. That is... the pro100 goes to load and it can't because it needs something another device is already using... so it doesn't load at all and you get the exclamation and "no resources being used"... and same with the sound card causing problems on other machines... it sounds like a bad driver.
Quote