Scratchyness

[MaMMa]

My hard drive ( WD 74GB raptor ) just died and before that, when i listed to my emu 0404 and start up a new program, the song I would be listening to would lag and delay for a split second.

I just got my new/refurb hard drive and everything is back to normal except when I listen to it now, it lags a lot worse and scratchy lots more now. I can not have this! Please help, would could be going wrong?

System Specs

AMD 2500+ @ 2.5 ghz
3 X 512 Corsair XMS 3500
Emu 0404 ~> Tributaries RCA to RCA ~> MisterX SubGilmore ~> HD280 Pro
Audigy 2 zs
Winxp SP2 w/ all updates

Its skipping bad! It hurts my ears

 

[skitlets]

I have a feeling it's a problem with ram caching. Try running memtest to make sure all 3 sticks of ram are good, especially since 3 sticks taxes the memory bux a lot more than just 2.

 

[MaMMa]

I've ran memtest on these bad boys for 7 hours about a month ago, I guess I should try it agian. I Just did prime95 for 10 hours and no issues

Gonna try memtest now

 

[sgrossklass]

[ignore]

 

[sgrossklass]

Sounds like it might be a SATA controller driver issue - if there are any newer matching ones out (need not be from the same board manufacturer, just the chip must be the same - I guess it's a Promise PDC20378 or something, they used to be rather popular when southbridges did not feature integrsted SATA yet), try those. I don't think SATA drives can run in PIO mode, but it may not be a bad idea to watch CPU usage during drive access. Additionally, make sure the SATA controller does not share a PCI INT line with the sound card (I don't know how sensitive the 0404 is).

 

[MaMMa]

So your saying I should update my SATA controller drivers? I just got the latest one from windows update, but I'll try on from sis themselves later when I get home, Thanks!

 

[sgrossklass]

Hmm, SiS SATA, is that southbridge integrated? But then I'm not aware of any common SiS chipset for socket A with native SATA support. Which board would that be?
BTW, I wouldn't really trust Windows Update in terms of having the most current drivers.

 

[MaMMa]

I've used both windows drivers and the Silcone 3114 and the one from my manufacture's website.

The problem still there. I called WD and they are sending me another one

o yea, i have a DFI Lanparty NFII Ultra rev. B

 

[maarek99]

I had that same issue. I fixed it by changing my ide controller which was a maxtor pci card. Is it possible to update the firmware on your sata controller? Or update your motherboards bios?

 

[sgrossklass]

Quote:

Originally Posted by maarek99 I had that same issue. I fixed it by changing my ide controller which was a maxtor pci card.

That was the old Promise driver issue affecting 2.00 build 29 through 39. With a current driver (.42, from Maxtor in this case, not that new actually) the card would most likely have worked well. We have a total of two original Promise Ultra100 TX2s and one Ultra66 in use here, all with the latest drivers for the U100TX2 (2.00 build 42), and there are no problems with sound crackling. However, when I happened to try build 39 at one point, the problem was very apparent.

As for why the Sil3114 would cause crackling, perhaps the sound card is sharing an INT line with the thing? Or is the APIC in use (look out for interrupts >15 in device manager), which is known to create odd problems on nForce2 boards?

 

[MaMMa]

Quote:

Originally Posted by sgrossklass That was the old Promise driver issue affecting 2.00 build 29 through 39. With a current driver (.42, from Maxtor in this case, not that new actually) the card would most likely have worked well. We have a total of two original Promise Ultra100 TX2s and one Ultra66 in use here, all with the latest drivers for the U100TX2 (2.00 build 42), and there are no problems with sound crackling. However, when I happened to try build 39 at one point, the problem was very apparent. As for why the Sil3114 would cause crackling, perhaps the sound card is sharing an INT line with the thing? Or is the APIC in use (look out for interrupts >15 in device manager), which is known to create odd problems on nForce2 boards?

So the problem is identified, is there a fix for this?