|
|
Post by Waspman on Jan 2, 2011 23:44:39 GMT -8
|
|
|
|
Post by Waspman on Jan 3, 2011 9:04:38 GMT -8
Other thing is, it's possible either Blizzard will release a patch or nVidia might release a future driver that would fix the problem. But reading that thread, it does look like that would do the trick for you.
Also, what motherboard do you have again? I can't find it.
|
|
|
|
Post by Fayde on Jan 3, 2011 15:55:42 GMT -8
Thanks for the find, almost all of those settings were set differently on mine, so I changed them all and we'll see if it worked tonight.
I'll check later, I'm kinda walking out the door currently. Thanks again.
|
|
|
|
Post by Waspman on Jan 3, 2011 18:37:50 GMT -8
Cool, hope it works.
As for your sound trouble.. I dunno, but I would try removing your audio driver and reinstalling it again (or whatever the newest one is) Should be able to find it just by typing in your motherboard manufacturer in google and then searching for drivers for your specific motherboard. Like I said, I don't know which motherboard you have.
|
|
|
|
Post by Fayde on Jan 4, 2011 10:38:26 GMT -8
So I fixed the sound! When I tried to have Windows update the driver, it came up with nothing, so I decided to look into finding a driver myself. Turns out there is a common Windows 7 Home bug with this problem, and Realtek released a fix for it on their site (which of course does not come up when Windows searches for it).
Good news though, so far the sound has yet to screw up. My computer was on for 2 hours yesterday without being touched and the sound still worked after all that time. I love it when problems are solved lol
|
|
|
|
Post by Waspman on Jan 7, 2011 15:11:25 GMT -8
Cool, glad you got it fixed.
But yeah, I would honestly never update ANY drivers through Windows update. I don't know if it's still true but what Windows update would do is try to detect your devices and then either give you outdated crap or the wrong drivers completely. Always best to get drivers from the actual websites.
|
|
