Status
Not open for further replies.

russianlion

Distinguished
Dec 18, 2006
29
0
18,530
Installed Vista Premium 2 days ago over XP on a fairly high end system. have had some hard drive warning messages and this other strange problem...I cant come out of sleep mode. I always wind up having to have to reset as all I get is a blank screen.

Never had this happen before and I don't really know where to start. Any ideas?
 

denster

Distinguished
Aug 18, 2005
158
0
18,680
This is not necessarily a new issue. I have had this same problem with XP. Not much on the web or microsoft in the past that I have found in terms of help on this subject. Looks as though Microsoft is heavily addressing this with their focus on Vista. However it has to do with ACPI settings if you want to look that up. And also what the capabilities of your motherboard are. I.E. Some BIOS versions only support certain functions of power management modes. You will have to do a little research on http://www.microsoft.com/whdc/system/pnppwr/powermgmt/default.mspx and on your BIOS / Motherboard specs. to find out exactly.


http://www.acpi.info/


http://www.acpi.info/spec.htm


http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface
 

Nonymous

Distinguished
May 27, 2004
199
0
18,690
You didn't say what kind of video card. There was a problem with the beta nvidia drivers causing the video to not resume when the PC was woken up. The screen would remain blank. Not sure if it was fixed in the recently released (last week) certified drivers or not.
 

davidinsarasota

Distinguished
Oct 10, 2006
61
0
18,630
I'm having issues with coming out of sleep as well. Could need a driver update as was mentioned earlier, I have an EVGA GTS 8800 and I am reluctant to download the new driver untill I have had some more time on the new pc.

Anyway, the tower kicks back on but the monitors stay dark, so I cant really tell where the malfunction is.
 

Nonymous

Distinguished
May 27, 2004
199
0
18,690
I am reluctant to download the new driver untill I have had some more time on the new pc.
So you're running the beta driver and not the new certified driver? The beta driver *definitely* causes this problem. Can't say the certified driver fixes it (i don't know), but if you have the beta driver, then no need to question the problem further.
 
Status
Not open for further replies.