|
|
 |
|
|
Pages: 1
SB Audigy miraculously becomes emu10kx and will no longer let me install drivers!
(Click here to view the original thread with full colors/images)
Posted by: TheHaunt
My Audigy card has worked flawlessly until yesterday when the computer spontaneously re-detected it. Since then, I have been unable to re-install the drivers provided on my Audigy CD, I keep getting the error "setup could not detect any sound blaster audio card on your system" at which point the installation stops. It still seems to work, as I still have sound, but now under the sound settings dialog, it appears as "emu10kx" instead of "sound blaster audigy". In the device manager under sound and game controllers menu "creative audigy audio processor (WDM)" appears, as well as the game port, but now there also appears to be an entry for "multimedia audio processor"** with a yellow exclamation next to it under "other" . Also, the 1394 net adapter (ie the firewire port) keeps reporting that it cannot start. How can I get windows to recognize the card as "Sound blaster Audigy" instead of "emu10kx" so that I can reinstall the software from the CD? And how can I correct the 1394 error? I ran SFC to see if it was a corrupt file, but it seems to be fine. I'm bloody confused and more than a little frustrated, anyone have a clue? (PS. I've noted that for some it seems to be a mobo compatibility issue, but I've been running this card in this mobo for almost a year without problem.)
[edit]**the extra multimedia audio processor was my onboard sound card which somehow re-enabled itself in bios, i'm not quite sure how that happened, but in any case, disabling it did not solve my emu10kx problem.
Posted by: goranpaa
Hi!
You could try unistalling the emu10kx in Windows device manager.
Then after rebooting XP, should say it have found your Creative card again. And then, try reistall the Creative driver again.
Hardware with exclamation marks. Means the driver is missing.
Try a registry repair software.
Posted by: thtadthtshldntb
Registry repair software seconded. Also, you could not only uninstall the "fake" hardware driver but also completely remove the hardware physically, both without it and then run the registry cleaners again.
BtW, did you upgrade your bios recently, perhaps some onboard audio that had been disabled has become reenabled via the upgrade.
|
|
|
|
|
