• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Windows XP doesn't detect Audigy 2

burningrave101

[H]F Junkie
Joined
Sep 9, 2003
Messages
11,825
I just got done installed my new Audigy 2 ZS Gamer and i started up the machine and windows xp doesn't detect anything and i can't install the creative drivers off the disk because it says it doesn't detect a sound blaster audigy 2 installed on this machine. Up until now i had been using the on-board Realtek AC97 audio. I disabled the AC97 detect under on-board features in my BIOS and i uninstalled the AC97 drivers in ADD/REMOVE Programs. But it still doesn't detect anything when i reboot. I'm downloading the newest creative drivers as we speak. What do i need to do to get it recognized?
 
This is really starting to piss me off. I called Creative tech support and they just told me to try different PCI slots and if windows still doesn't recognize it then i probably have a bad card and need to RMA. I've tried three different PCI slots and none of them have worked.

WHY WONT THIS STUPID THING DETECT!!!
 
Actually i'm starting to think its not. I've seen alot of people that have the same problem as me, and on the exact board i'm using and i think it has to do with IRQ conflicts and the PCI bus not working right or something. I have my two raptors in RAID0 on the Silicon Image chip on my board and that is suppost to go through the PCI bus and that could be conflicting. The ICH5R chip is suppost to be faster so i'm switching over to that now. I've also seen people say they had to IRQ force their card to get it to work and some said they had to re-install windows before it detected. I'm going to try some things out and let you guys know what happens.

http://www.motherboard-forum.com/gigabyte/index.html
 
Try two BIOS settings.
Force ESCD update ENABLED
Disable unused PCI clock DISABLED
 
Mister X said:
Try two BIOS settings.
Force ESCD update ENABLED
Disable unused PCI clock DISABLED

As far as i know i dont have ither one of those options in my BIOS settings.

I just finished moving my RAID0 array to the ICH5R controller and re-installed windows xp but its still not detecting my Audigy card :(.

I've seen quite a few people have this problem and they seemed to all have different solutions to their problem yet none of them have worked for me so far.
 
Just an update for you guys. I fixed the problem. The card is most definitely not dead which is the good news and the problem i was having was the cause of several IRQ conflicts. Creative cards dont play well with lots of on-board devices and my board has ALOT and it should for $200 :p.

Anyways i re-installed windows, disabled a bunch of on-board stuff i wasn't using and got the Audigy 2 to recognize without problems in PCI slot #3.

I got quite a bit of help on this from the tomshardware forums along with the motherboards.org forums.

Here is a good thread for those of you that dont already know which PCI slots are best to use for which devices to try and avoid IRQ conflicts.

http://www.motherboards.org/forums/viewtopic.php?t=45374&highlight=irq

I was an IRQ nOOb up till last night :p.

Anyways, now the only device its sharing the same IRQ number with is my USB 2.0 Host Controller and so far it hasn't been a problem. I can probably assign the sound card its own IRQ in my BIOS though if i have further issues.

I'm glad this conflict happened and i had to go searching other forums to get advice because i just found out about a month ago i flashed my BIOS to a Rev. 1.0 version of my board instead of 2.0 lol. I was running F10 when i should of been running FH. Luckily though i managed to get it flashed back without problems using @BIOS in windows. Q-Flash wouldn't do it. It kept giving me an error. Q-Flash works fine now though and i updated my main and backup BIOS.
 
Back
Top