I hear the computer turn back on and the light is on, but the screen is still black. My mouse and keyboard are unresponsive (can't turn backlight on). I have to do a hard shut down. When it's back on, it's like it woke up from sleep mode, not a fresh restart.
This just started happening today I think so I did a system restore, but the problem persists. The only thing I remember doing today was updating my ATI drivers.
I have the same problem. It started after the sr1 update.
Not a solution but I found a workaround in the meantime. I disabled suspend to ram option in the BIOS. Waking takes a lot longer, but better than nothing.
Perhaps related but....
ON my test machine with working 10 install for over a month now...
As of last update from MS which I allowed to install this morning....
That test machine boots to a black screen after the intial windows load screen with the small window pane and circle shape
load indicator below.
THen the screen goes black.
Nothing I've tried has managed to get a non blanked screen. Monitor insists on going into 'sleep mode' even when I turn it back on.
All was fine prior to allowing MS to essentially brick my machine with this last update.
I managed to get safe mode to work via f8 only ONCE , subsequent reboots fail to get machine to respond to F8
keypress despite my managing to get it to work the first time.
Repair diagnositics via DVD boot failed.
At this stage I gave up and am open to ideas.
Glad I have not installed W10 on my non testing machines.
Update.
I found a solution to the issue I had and posted in this thread a update:
Black screen - Windows 10 Forums
TLDR. Had to change something in BIOS that was fine prior to last Windows 10 Update. / shrug.
Details in that thread. 3rd or so post down.
(P..S. Still keepign Win 10 off my main gaming box for now!0
I have the same problem and do not have a solution for it, but because of my setup have a workaround.. None of the proposed solutions have worked for me. My screen is a TV plugged into the VGA port. After moving the mouse i use the TV's remote to power on the TV and all's fine.
This is a new problem and may be due to a recent Microsoft software update.
Last edited by Trog; 14 Oct 2015 at 13:21. Reason: remove non-applicable content.
same problem as original post...a few observations. This happens when I close the lid and the laptop goes into sleep mode.
Updating BIOS didn't solve my problem.
Trying to revert back to previous Graphics driver didn't work, nor did the update back to most recent available either.
Mouse and Keyboard, enable wake up using this device, didn't work either.
Changed within BIOS the Core C6 status from "enabled" to "disabled" as it states this has something to do with sleep mode, but this didn't work either. Can't locate the suspend RAM option setting in the BIOS to change.
Previously had noticed that it appeared the computer upon wake was more in the type of state I expect when it's connected to a projector or external VGA monitor (blank screen on laptop/viewable screen external). Plugging in a spare monitor, sure enough, showed that the computer was actually on and transmitting a signal, albeit, to the external port. It's like upon waking up, it doesn't know that the built in laptop screen is supposed to receive the signal and sends the transmission to the VGA port instead. If you know the key strokes you can properly shut the computer down even though the screen is blank. CTRL-ALT-DEL, Tab 8 times, enter, arrow down three times and enter (Shut down). Then I can reboot again. But sleep problem persists.
One WEIRD observation, just noticed today. If I manually place the laptop into sleep mode, I do NOT have this issue. The laptop wakes up fine. It's only when I close the lid.
I have to figure this will be solved eventually, but I'm feeling like since my system is outdated and out of warranty, it's not exactly a "stat" issue for Compaq/HP or Microsoft to Fix. What's frustrating is that earlier this summer the Microsoft Update seemed to test my computer for compatibility with upgrading from Windows 7 to 10. So I enrolled and upgraded when it became available. The problem started immediately after the upgrade.
Now that this problem persists, I have since visited the HP/Compaq site only to find out my particular model was never tested.
I'm feeling misled by Microsoft and it's frustrating.
Last edited by paulcstone; 16 Oct 2015 at 09:19. Reason: updated info.
Quote