Sager NP8662: Red Screen upon Awakening from Sleep

Hi,

I've owned my Sager NP8662 for just over two years and two months now, and I've just recently started having an issue with the system.

When I put it to sleep, everything goes along fine, but upon pressing the power on button to get the laptop active again, I've been getting a brief flash of a purely red screen for a fraction of a second before I see my desktop screen again.

Just now, the red screen lasted for ~1.5 or 2 seconds before the laptop returned to full function, so I'm a little concerned. Do any other users have experience with this kind of issue?

For reference:

The notebook's specs:

Sager NP8662
Intel Core 2 Duo P9700 @ 2.8GHz
nVidia GTX 260M
4GB DDR2 1066MHz RAM
Windows Vista Home Premium

Additionally, the graphics card had an overclocked (650/1625/910) and overvolted (1.05V) 'EXTRA' setting, so when gaming it would receive more juice and work harder than normal, but I pushed the clocks down to stock (550/1375/900) and the 'EXTRA' voltage down to 0.95V recently to prolong the notebook's life, as I'd been getting 'Graphics driver has failed' errors when gaming, which indicate GPU failure as I've been led to understand. Those errors have since disappeared. Furthermore, the laptop has been on a Zalman NC2000 turned to maximum from the day I bought it, to ensure safe and cool operation. Between the underclock/undervolt and cleaning out the insides of the laptop (particularly near the fan), I've gotten max gaming temps down from 80C to 70C. Everything idles at roughly 45C.

Note that all other clock/voltage settings, used when browsing, video watching, or anything other than gaming have remained unchanged from stock values for the entirety of the laptop's life.

 

I don't know much regarding forum etiquette, but I'm seriously concerned here and any help would be tremendously appreciated. (Hence, the bump.) If PM'ing an experienced user would be better, please let me know (via PM or post) and I'll do that instead of clogging the forum.

 

just a shot in the dark, but have you had any luck with updated drivers?

 

I updated my graphics drivers to nVidia's 285.62 WHQL maybe a week or so before I started noticing this issue, actually, and I don't think there have been any further updates since then afaik.