M
misterjerk2
Just wondering if anyone could shed some light on my problem?
I purchased a genuine ATI Radeon x700Pro 256M (PCIE) in January.
Last week the card started acting up suddenly. I was playing World of
Warcraft for a few hours when the screen suddenly went black. After a
few moments the screen would return only to go black again a few
seconds later. The more I played, the more frequent the problem became.
When I stopped playing the problem continued in windows whenever I
would move a window or something graphical.
If I power off the machine for a few minutes, the problem goes away at
least until I play a 3D game.
I took a look and the GPU doesn't seem to be getting abnormally hot.
But it seems like the card is overly heat sensitive or something.
Can anyone shed some light on this?
I have already downloaded the latest Catalyst drivers (yesterday) and
followed ATIs recommendations here.
http://www.ati.com/online/customercare/solutions/displayissueshtml
Additionaly, I have not made any recent changes to the system that
would have caused this problem, it just started on its own.
To no avail.
mj
I purchased a genuine ATI Radeon x700Pro 256M (PCIE) in January.
Last week the card started acting up suddenly. I was playing World of
Warcraft for a few hours when the screen suddenly went black. After a
few moments the screen would return only to go black again a few
seconds later. The more I played, the more frequent the problem became.
When I stopped playing the problem continued in windows whenever I
would move a window or something graphical.
If I power off the machine for a few minutes, the problem goes away at
least until I play a 3D game.
I took a look and the GPU doesn't seem to be getting abnormally hot.
But it seems like the card is overly heat sensitive or something.
Can anyone shed some light on this?
I have already downloaded the latest Catalyst drivers (yesterday) and
followed ATIs recommendations here.
http://www.ati.com/online/customercare/solutions/displayissueshtml
Additionaly, I have not made any recent changes to the system that
would have caused this problem, it just started on its own.
To no avail.
mj