I recently Custom reinstalled Windows 7 64 bit and the OS fails to detect the soundcard. The previous installation did recognize the card. It's on old card (a Creative SB X-Fi Fatal1ty PCI). When hovering over the sound icon on the taskbar it reports that "no audio output device is installed". Oddly enough, Aida64 Extreme reports the card as being there. The Bios settings are no different than previously. Device Manager shows a 'Multimedia Audio Controller' but it will not install drivers. I reinstalled the chipset drivers after the OS reinstall so that can't be the problem. I've reseated the soundcard in the three PCI slots and presume that is not the problem as the red light on the card is on as usual. Cheers.
-
Still running Windows 7 or earlier? Support for Windows 7 ended on January 14th 2020. Please review the thread here for more details.
Soundcard not detected by Windows 7.
- Thread starter WayneR
- Start date
What do you mean by "custom" reinstall?
And what prompted the reinstallation?
Why not? Do you get an error? And what driver are you trying to install?
And what prompted the reinstallation?
Why not? Do you get an error? And what driver are you trying to install?
The "custom install" is the full Windows install. I tried an upgrade or repair install but it failed. I was having a number of issues such as CHKDSK constantly correcting errors and other issues such as windows color management not working. I attempted a repair or upgrade install but it failed probably due to updates it identified.
I was trying to install the drivers for my soundcard but the new Windows installation does not detect the soundcard. Unless the soundcard is detected the Creative soundblaster drivers can't be installed. This is a fairly widespread problem it seems. I have used the soundcard for several years and I'm pretty sure it's not damaged. I have set up onboard Realtek audio as a temporary solution until I can get the soundcard up and running.
I was trying to install the drivers for my soundcard but the new Windows installation does not detect the soundcard. Unless the soundcard is detected the Creative soundblaster drivers can't be installed. This is a fairly widespread problem it seems. I have used the soundcard for several years and I'm pretty sure it's not damaged. I have set up onboard Realtek audio as a temporary solution until I can get the soundcard up and running.
On one of my old systems, I had to turn off the onboard sound in the bios before Windows would detect the 3rd party add-in card. Others, it did not matter.
The fact that you've been using it before the re-install says this is probably not the case.
Are all of the service packs installed?
The fact that you've been using it before the re-install says this is probably not the case.
Are all of the service packs installed?
Are you referring to service pack 1? That is the only service pack installed. Previously, even if onboard sound was enabled the soundcard would appear in Device Manager and the drivers would install. The soundcard has always been tricky to get working though. I will turn off the onboard sound in the bios again (tomorrow) and see whether the card is detected.
Well, to me, that is just an install, or a "fresh" install, not "custom". But that's not important for this.
What is (maybe) is why? CHKDSK correcting errors [once] is one thing. "Constantly" correcting errors is another. That suggests your drive is failing.
I've managed to install the sound card. I found a 'Product Identification Module Update' in the Creative Drivers section. It states that "This update resolves the hardware/device detection issue for Creative Sound Blaster® X-Fi™ and X-Fi Titanium series of audio devices in Microsoft® Windows® 7". I ran this update and it didn't appear to do anything but when I ran the driver software again it detected the soundcard this time. Old legacy hardware is tricky and often requires a few attempts to get it to work. Until I ran this module the soundcard was not even recognized by its own software or Win7 for that matter.
Bill mentioned a potential hard drive failure but I've run various drive testing software and the drive is in good shape. If the drives start to fail I will know that ahead of time. CHKDSK can be affected by many issues in old installations. I'm relieved to have resuscitated the Soundblaster. The Realtek audio was pretty good but the soundcard edges it out in high fidelity and customization. Thanks to those who offered advice. Cheers.
Bill mentioned a potential hard drive failure but I've run various drive testing software and the drive is in good shape. If the drives start to fail I will know that ahead of time. CHKDSK can be affected by many issues in old installations. I'm relieved to have resuscitated the Soundblaster. The Realtek audio was pretty good but the soundcard edges it out in high fidelity and customization. Thanks to those who offered advice. Cheers.
Glad you fixed it and thanks for taking the time to let us know!
I am glad you got your problem resolved. Thanks for posting that solution.
As far as drive diagnostics, the only one (besides CHKDSK) I would trust is the one found on your drive maker's website.
At any rate, I sure would make sure you have a good backup of anything on that drive you do not want to lose.
Yes, but only once! That is, once exposed to that old installation, and once it corrects those problems, that should be it. It is not normal for it to "constantly" find and correct problems. Those problems should NOT recur.
As far as drive diagnostics, the only one (besides CHKDSK) I would trust is the one found on your drive maker's website.
At any rate, I sure would make sure you have a good backup of anything on that drive you do not want to lose.
It likely was. Check Disk looks for, among other things, corrupt data. That's software. Corrupt data is also a "symptom" of the actual problem. So, the question then becomes, "what corrupted the data?" Malware? A power hiccough? A failing or damaged drive? Gremlins?
In any case, once the corrupted data is corrected, it should not recur. If the "symptom" recurs, the problem is still there.
Great!
I did have an instance of a "Floxif" Trojan some time ago but managed to disinfect the system. The damage done by this Trojan might have contributed to the problems identified by CHKDSK. The drive format and reinstallation of Windows was a necessity after that. Cheers.