Mega Sound Problems

2smoothbooth · 4 Dec 2007 at 19:50

Recently when i'm playing music, watching a video or playing a game every couple of minutes or so, the sound becomes garbled for a second then returns to normal. Its a new system which i've just overclocked, i haven't had time to mess around with drivers or adjust the overclocking but came here first just incase someone knows whats going on?
I'm running an [email protected], Gigabyte P35c-DS3R, 2gb OCZ PC6400@900mhz.

ANy advice would be good.

jak731 · 4 Dec 2007 at 19:53

just a stab in the dark but, have you checked if your cpu overclock is stable?

run orthos for a few hours to see if you havent already done so.

2smoothbooth · 4 Dec 2007 at 19:57

i havent ran any stability programs yet :S but i was thinking the same thing. Its the garbled sound you get just before you get blue screened so i'll run orthos see what happens

Dreadi · 4 Dec 2007 at 20:03

stability is a must

2smoothbooth · 4 Dec 2007 at 20:07

thanks for that input dreadi, how long would you say is stable enough? an hour of prime?

jak731 · 4 Dec 2007 at 20:09

try 6 minimum

2smoothbooth · 4 Dec 2007 at 20:13

6!! Will have to put up with it for now and get it on the go when i'm sleeping, waste uni's electricity

jak731 · 4 Dec 2007 at 20:15

i suggest doing it when you can keep an eye on the temps incase it gets too hot

Dreadi · 4 Dec 2007 at 20:18

2smoothbooth said:
thanks for that input dreadi, how long would you say is stable enough? an hour of prime?

with my opty 144 i used to go for 12 minimum, just leave it running over night and hope it doesn't bum out when your asleep

Corasik · 4 Dec 2007 at 20:55

I had a P4 which could run prime for about 14 hours, perfect temps, but would always fail after about 15 hours... Same test failed every time. Dropped the FSB by 1mhz, and it would sail through it.

There is virtually 'no' maximum time that you can quote for guaranteed stability. The longer you can test the better.

Ok some might say, who cares 14 hours stability thats great... Thing is there were some other applications which went unstable, and all problems were gone when the system was clocked down by 1 mhz.

Incase anyone wonders, it was a 2.4ghz P4 which clocked at 3.2Ghz with 100% stability, FSB 266 totally stable, FSB 267 prime failed after 15 hours, and occasional "unexplained" crashes. ( I suspect it was a FSB wall, as no amount of tweaking, voltage increases or messing around with memory multi's ever got the system past 266 stable)

So no, even 6 hours prime testing isnt really enough. Yes you might get lucky, on the other hand you might end up plagued by random crashes, which you will no doubt forever blame on microsofts shoddy programming.

In reality, a system which is 100% stable will very rarely crash.. Windows has been given a very bad reputation for crashing, which is largely unwarrented, and is actually a side effect of some very cheaply built computers, which are actually not 100% stable.

I've had 'Pre built' computers from big name suppliers which couldnt run prime95 for 24 hours without an error.