A doozy of a problem

[Crespire]

This one's stumped me, and it finally actually affected my daily routine, so I figure it's about time I get a move on. I will note that my hardware specifications before I dive into the problem.

Intel i7-920
Corsair XMS3 Triple Channel 6GB set
XFX Radeon HD 5870
1TB Hitachi
ASUS P6X58D Premium Motherboard
Windows 7 Professional x64
Catalyst 10.12
(More details in my profile)

Here's the problem:

The computer works fine except sometimes, when I leave my computer to idle for a while, it will become unresponsive. I don't let my computer sleep, but I do have the monitors turn off after 10 min of idle. The problem happens when I try to get out of idle. My monitors turn back on, but display a blank screen (ie, they're not longer in sleep mode, fully on, but displaying nothing). As a result, I can't do anything and have to force a restart. I've tried to C+A+D, but that seems to do nothing either. I have no way of telling if my input is being received.

I've already run a variety of tests. SFC returns no errors. Event view shows no System events before the cold restart, indeed the log leaves off at 1:17:29am (which is when I went to bed), and picks up at 6:51:06am (40 min after I was supposed to wake up to my computer playing some music ).

I'm usually pretty savvy and able to pinpoint the causes of problems, but because this problem seems to happen after I've left my computer idle, I've yet to be able to figure it out. Any help would be appreciated.

 

[yowanvista]

Update your Radeon drivers

 

[Crespire]

Update your Radeon drivers

I just edited that in. As far as I know, I'm running the latest version (10.12).

[edit]
10.12 Catalyst was released on 12/13/2010

 

[yowanvista]

Update your Radeon drivers

I just edited that in. As far as I know, I'm running the latest version (10.12)

Use driver sweeper when installing drivers, older versions usually leave leftovers which might cause conflicts with newer ones
Guru3D - Driver Sweeper

 

[Crespire]

Update your Radeon drivers

I just edited that in. As far as I know, I'm running the latest version (10.12)

Use driver sweeper when installing drivers, older versions usually leave leftovers which might cause conflicts with newer ones
Guru3D - Driver Sweeper

It's worth a shot, I've not yet tried a fresh install of the graphics driver, and at first glance it does seem to be the culprit.