Tue Jan 12, 2010 8:29 pm
I just linked them because other have similar problems too, so far there seems to be no solution. At least not one that i've found yet. But my guess is that this is a driver bug, with the new 5000 series, since i had no problem when i had my 4980.