X-Fi Fatal1ty Sound Card troubles...

[eklock2000]

So I've tried the Creative forums and customer support to no avail. After about 10mins of heavy use (gaming), the squeal appears and only goes away on a reboot. My research has led me to believe it's due to a resource conflict, but the PCI slot is not sharing an IRQ with any other devices?

I'm pretty bummed. This was an expensive card and it seems to happen to a lot of ppl on different mobos? Am I screwed? Any help would be great.

Thanks,

EK2K

System

GA-N680iSLI-DQ6, Rev. 1, F5b
Intel E6850 w/ Zalman 9700
eVGA 8800GTX w/ 163.71 forceware
2Gb - Crucial Ballistix PC2-8000 (BL2KIT12864AA1005)
Corsair CMPSU 620HX ? 620Watts
Antec900
WinXP SP2

 

[AllGamer]

sorry no problem with mine, not sure what's going on in yours.

it could be interference picked up by the other channels, like MIC, or AUX In, or Line In

try muting those 3 options, and see if it goes away

 

[chizow]

Originally posted by: AllGamer
sorry no problem with mine, not sure what's going on in yours.

it could be interference picked up by the other channels, like MIC, or AUX In, or Line In

try muting those 3 options, and see if it goes away

All good suggestions, as muting or closing the loop on unused inputs/outputs can often help with static/hissing/scratching sounds. The OP's problem does sound like a driver/resource problem though and probably ends up with a BSOD or crash. Some things you can try:

1) Update your BIOS. Many board makers have put out specific fixes for the X-Fi.
2) Update your drivers. I had a similar problem with my X-Fi after installing 4GB. Newer drivers fixed the problem. I believe there's a new Beta out for XP.
3) Change PCI slots. Amazing how PCI/IRQ resources can still create conflicts in Windows, but this might help. You can also try changing any PCI/IRQ settings in the BIOS, although I didn't have much luck with this on my current board.
4) Change PCI latency timers. Increase this setting to give the X-Fi control of the PCI bus longer.

 

[AllGamer]

Originally posted by: chizow
3) Change PCI slots. Amazing how PCI/IRQ resources can still create conflicts in Windows, but this might help. You can also try changing any PCI/IRQ settings in the BIOS, although I didn't have much luck with this on my current board.

unfortunately Sad but True, to this day and Age there are still drivers that are not fully IRQ friendly, thus the age old legend of IRQ conflict is way too real for people to dismiss this issue.

ultimately it's the drivers programmers to blame for this, but when you got the hardware, you want to use it no matter what, even if it means doing manual IRQ assignment as the good old practise.

 

[nerp]

I can't believe Creative Labs is still making cards that can encounter IRQ conflicts and produce popping/clicking/hissing problems. Baffling.

 

[chizow]

Originally posted by: nerp
I can't believe Creative Labs is still making cards that can encounter IRQ conflicts and produce popping/clicking/hissing problems. Baffling.

Unfortunately its not all that simple. Like anything in the PC world, everyone has their own agendas and priorities (sup Vista sound stack and onboard/HD audio). Reality of it is that the boardmakers and their BIOS and MS and their OSes are as much as fault as Creative, if not moreso.