[Crysalis]

thats an IRQ conflict. Try uninstalling drivers, software and the card itself (through device manager), then shut down and take out the card. Start up. Shut down. Put the card in a different PCI slot. Startup

[EricB]

Originally posted by Crysalis
thats an IRQ conflict. Try uninstalling drivers, software and the card itself (through device manager), then shut down and take out the card. Start up. Shut down. Put the card in a different PCI slot. Startup

this solution worked when I had a similar problem with a customer's tv capture card. I just didn't it was an irq conflict

[high_fidelity]

Don't even know if IRQ conflicts are the problem. I have uninstalled and removed the Audigy 2 from my system and have tried recording using and M-Audio Firewire Solo. I am having exactly the same problem!!!

[moisiss]

I have a firepod and use cubase/reason. It was working fine... until I installed a wireless card (my firewire ports are only on a PCI card I installed... not onboard) and I started getting random clicks and cutouts when I was playing the audio back through the firepod. I thought it was an IRQ conflict, so I moved the wireless card into another PCI slot.... but nothing changed. Eventually, I figured out that if I disable the wireless card all of the clicks and cutouts go away.... so now that's what I do if I am doing any recording and or audio playback. It's an extra step to turn it off.... but whatever, it takes about 2 seconds. So mabye try disabling any devices that you aren't using while recording?

Also, I know you said that your CPU isn't under heavy strain... but I have also seen (well, heard really) this happen on big files with lots of tracks and lots of plug-ins going..... although, with a computer as powerful as yours, this shouldn't be a problem unless the session is just HUGE.

I've also heard about this happening if your latency settings are too low? But again, you have a smoking machine... so I can't see this being the problem (I run 3ms latency at 24bit/96kHz on an AMD64 3000+, 512mb RAM, 80 GB 7200 RPM setup and never have any issues).

[joshd]

your wireless card is probably just creating noise on the PCI bus or something.

"when I was playing the audio back through the firepod" does it happen when you play the audio back through anything else? is it the playback or the recording that has the noise?

OP: have you tried any other programs? (its probably easier to quickly check that before fiddling with hardware)

maybe you should try formatting, installing audio drivers, and try recording. if no clicks, install devices one by one, untill the clicking happens again. bingo, you have found what is responsible. (annoying of the clicks are present straight away though, huh? )

[EricB]

After some internet reading (newegg and google), I come to find out that creative just don't like asus or dfi boards(it didn't work on either board in my case). I just bought an m-audio firewire solo and there is no conflicts or glitches with my dfi mobo now.


this guy actually posted a solution to making creative work on a asus board. but you wouldn't want to do it as it has a million steps.

Pros: it works only if it doesnt have any kind of IRQ conflicks. which i have finally figure out how to do it. i run a asus a8n32-sli-deluxe mobo. i use this procedure to fix it: use driver cleaner pro then Download newest Chipset Drivers, but do not install yet * Download and install any BIOS updates * Reboot and enter BIOS * Set what you want, disabling any stuff you never use (whether it be firewire or midi or whatever) * Reboot to Windows * Uninstall all drivers related to sound and video (the b******t apps that go with it too) * Run Driver Cleaner Pro and multi-select all video and sound remotely related to your hardware (I select everything under manufacturer name) * Reboot TO SAFE MODE (keep pressing F8 during reboot until you get the menu choice) * Run Driver Cleaner Pro and clean the same things you just cleaned in normal mode * Select CAB cleaning and clean all CABs it has an option to clean the rest continues in other thoughts>

Cons: creatives tech support is very poor. still waiting on a new driver update. to help out with BSOD=blue screen of death.since the asus mobo have alot of conflicks with creative sound cards. just check out creatives forums you will see what i am chatting bout

Other Thoughts: * Reboot to normal Windows, cancelling out all the search for a driver gumps * Install the newest Chipset Drivers * Reboot, enter and recheck BIOS settings (chipset drivers can sometimes screw with this) * Reboot to Windows * Install latest OnBoard Sound Drivers if seperate from Chipset * Reboot * Set Windows sound applet stuff, test onboard sound. Any pops? Should be fine * Reboot * Install Sound Card DRIVERS (non of that extra c**p) * Reboot * Set Windows sound applet stuff, test both sound sources * Reboot * Recheck sound applet settings, reboot again if you need to set stuff again (it can be difficult to get Win to set some of that in stone) * Now you can install your Video Drivers * Reboot and retest everything * Lastly, I would suggest the latest monthly version of DirectX to be installed then you should either give you a clean and working as you want it system, or give you an indication of where the problem lies, depending on where in the process

11 out of 11 people found this review helpful. Did you? Yes No
Music lovers take note

[high_fidelity]

Ironically, I have now found out that the problem was my M-Audio Firewire Solo which I used for the sole reason of having phantom power on it. I have now bought a mixer which I have plugged directly into my soundblaster Audigy 2 ZS. Whilst the Creative drivers have had to be updated due to all the revisions and updates that microsoft make to their operating system I don't think that Asus boards are the problem as that Asus boards are all I have ever used and creative cards have always worked for me.
I think the issue with the M-Audio Firewire Solo could well be to do with the firmware updates that it does automatically. It works fine with my mac but on all the PC's I have used it on now it has the same problem.

I am upgrading to vista which I will be using in the next few days. I am aware that there are beta drivers available for the SB Audigy 2 ZS so I will let people know how these drivers are with the OS.

Cheers