Windows 8 PROBLEM

Crezzlin · 17 Dec 2012 at 00:24

Just put windows 8 my PC and now get the following lines on desktop and metro, but only when I move the mouse or the use IE on desktop mode, so odd.

http://i712.photobucket.com/albums/ww122/crezzlin/IMG_20121216_225113.jpg
http://i712.photobucket.com/albums/ww122/crezzlin/IMG_20121216_225121.jpg
http://i712.photobucket.com/albums/ww122/crezzlin/IMG_20121216_225122.jpg

Has anyone seen this before, could be my GPU, but it works fine under load in any game etc, just has this problem on desktop/metro, but not in any apps or programs. Thanks

Crezzlin · 17 Dec 2012 at 00:40

The PC has been sat for 2 months as its a second computer I used for Photography, I have just put in a new ssd and then windows8, from what I can remember I had no problems in the past with it.. but as you have said the driver maybe the problem, I will try a different win8 driver to see if it fixes it, I've never seen a pc do this apart from a GPU fail but then It wouldn't act like this. Thanks

Crezzlin · 17 Dec 2012 at 01:17

Just changed my driver from 12.10 to 12.11 Beta, no fix but my performace has gone up in 3dmark 11 from 8200 to 9700

Crezzlin · 17 Dec 2012 at 11:12

Thanks guys, I'm running at 2560x1600, I used 2 cables and a Dp to Dvi but made no difference.

Thenewoc, thanks for the link

makes sense but I can't see an easy fix, its like the old 5000 series AMD cards in eyefinty they had a problem like this :s I will try loading a GPU bench in backgroung and see if it stops it for me.. Just at work so can't try it..

Crezzlin · 22 Dec 2012 at 08:54

thenewoc said:
No worries, using 2560 x 1440 with the DVI cable that came with the monitor and 12.11 beta 11 with CAP2's. Think I saw someone create a temp fix by creating a slightly higher than idle clock profile and assign it as the profile to use for 2D in AB. Not tried it yet myself, not sure what would stop it from still down clocking unless selecting it as the 2D profile to use in AB sets it as the lowest it will fall back to. Otherwise I guess it means waiting for a new driver, seems a bit of a co incidents that an older driver didn't use to drop the clock so low. Just wondering if this is only affecting high res users and perhaps fell off AMD's radar if they didn't continue to receive reports of the problem. When I get a moment I will file a bug report.

Cheers. Still can't solve it but I will put up with it