Sound problems with TB Santa Cruz

[bgray77]

I put together the following system over the weekend:

Motherboard: Intel D875PBZLK (no onboard sound)
CPU: P4 2.4CGHz
Memory: (2) Crucial 512MB PC3200 DDR400
Video: Asus GeForce4 Ti4200 128MB
Sound: Turtle Beach Santa Cruz

Everything has run great except for the sound. I am getting skips all the time, even when I am not running any programs. I was previously running a PIII 700MHz with 256MB SDRAM and only got skips when I had 3 or 4 programs running. Does anyone have any suggestions? I have already tried the following:

- Had the most current drivers (4193) from SC website installed. They were not MS certified, so I installed the ones that were (4161). This did not help so I went back to the 4193.

- Checked for IRQ conflicts. None.

- Moved hardware acceleration from full to standard to basic, but no help.

 

[Maleficus]

Operating system?

 

[bgray77]

Originally posted by: Maleficus
Operating system?

Sorry.

Windows XP Pro.

Also, I get this whether I am playing an audio cd from my CD-ROM or if I am playing files from my hard drive.

 

[resinboy]

try to move it to another slot: I know Xp likes to have everything using the same interrupt , but moving the card may help. Don't give up on this card- I was dealing with the Soundbastich driver/ bloatware problem a lot of us had, and that all went away with the Santa Cruz.

 

[bgray77]

I moved it to different slots, but the problem persisted. Wherever I moved it, it kept it on the same IRQ as the onboard LAN connection, a USB controller and a Promise IDE controller card. Finally, I took out the card, enabled Plug and Play O/S in the BIOS setup, and reinstalled the card. This finally put it on its on IRQ. The problem seems to be corrected. Does this solution sound ok/make sense?

 

[Maleficus]

Legitimate Windows XP or *ahem* ?

I know some of the *ahem*'s had problems with cpu utilization and would cause errors such as this.

 

[bgray77]

Originally posted by: Maleficus
Legitimate Windows XP or *ahem* ?

I know some of the *ahem*'s had problems with cpu utilization and would cause errors such as this.

It's legitimate. I bought the XP upgrade through my university.