PC won't wake up

If I put my desktop to 'sleep' mode (or if it does it on timer) I cannot
get it to wake up.
If I move the mouse I normally hear the drive motor start then the screen,
but now I hear the motor start, but whatever I do the screen remains black.
The only solution is to turn off, wait 30 secs and start from scratch.

Ideas please.
--
Jim S

On 2018-11-12 7:00 a.m., Jim S wrote:
If I put my desktop to 'sleep' mode (or if it does it on timer) I cannot
get it to wake up.
If I move the mouse I normally hear the drive motor start then the screen,
but now I hear the motor start, but whatever I do the screen remains black.
The only solution is to turn off, wait 30 secs and start from scratch.

Ideas please.

What happens when you press the spacebar rather than move the mouse?


--
SilverSlimer
Minds: @silverslimer

On Mon, 12 Nov 2018 08:45:10 -0500, SilverSlimer wrote:

On 2018-11-12 7:00 a.m., Jim S wrote:
If I put my desktop to 'sleep' mode (or if it does it on timer) I cannot
get it to wake up.
If I move the mouse I normally hear the drive motor start then the screen,
but now I hear the motor start, but whatever I do the screen remains black.
The only solution is to turn off, wait 30 secs and start from scratch.

Ideas please.

What happens when you press the spacebar rather than move the mouse?

The same
--
Jim S

Jim S wrote:
On Mon, 12 Nov 2018 08:45:10 -0500, SilverSlimer wrote:

On 2018-11-12 7:00 a.m., Jim S wrote:
If I put my desktop to 'sleep' mode (or if it does it on timer) I cannot
get it to wake up.
If I move the mouse I normally hear the drive motor start then the screen,
but now I hear the motor start, but whatever I do the screen remains black.
The only solution is to turn off, wait 30 secs and start from scratch.

Ideas please.
What happens when you press the spacebar rather than move the mouse?

The same

Type "reliability" into the Cortana search, and see if any events
in the Reliability Monitor graph, correlate with your "black screen" thing.

You can look in Event Viewer itself, if you have the stomach for it.
You shouldn't have to search very deep, as the event, whatever it
was, might only have been minutes before the latest entries in
Event Viewer.

Bad RAM and driver crashes, should give different symptoms than you
seem to be seeing right now. It really should not go dark like that,
without attempting to restart in less than a minute. I've had some
BSODs here (during my inaccessible boot volume tests), where
it would restart after less than a minute, even when I didn't
want it to. (In the experiment I was doing, it ends up in a
stupid "boot loop" which always failed. You wouldn't want this
to happen if you were on vacation.)

Maybe if you had bad RAM in the kernel/driver area, it could
tip over like that with a black screen. I would think though,
that it's just a driver bug of some sort. Graphics card problems
are supposed to use VPU recover, so a graphics driver problem
doesn't necessarily mean it has to die like that. It might
blink and the screen become visible a second or two later.

Paul

Jim S wrote:

SilverSlimer wrote:

What happens when you press the spacebar rather than move the mouse?

The same

Is it a wired keyboard? If so do the caps/num/scroll lock keys toggle
the appropriate LEDs after the wake-up? If so it might just be a
failure of the monitor to come out of sleep mode ...

On Mon, 12 Nov 2018 16:23:51 +0000, Andy Burns wrote:

Jim S wrote:

SilverSlimer wrote:

What happens when you press the spacebar rather than move the mouse?

The same

Is it a wired keyboard? If so do the caps/num/scroll lock keys toggle
the appropriate LEDs after the wake-up? If so it might just be a
failure of the monitor to come out of sleep mode ...

Thanks guys. I found this
https://www.drivereasy.com/knowledge...windows-10/#F3
I unticked 'faststartup' as described and that worked. However putting in
password/code everytime is a pain so I put faststartup back in and it still
works.
I've boomarked that page just in case.
--
Jim S

Jim S wrote:
On Mon, 12 Nov 2018 16:23:51 +0000, Andy Burns wrote:

Jim S wrote:

SilverSlimer wrote:

What happens when you press the spacebar rather than move the mouse?
The same
Is it a wired keyboard? If so do the caps/num/scroll lock keys toggle
the appropriate LEDs after the wake-up? If so it might just be a
failure of the monitor to come out of sleep mode ...

Thanks guys. I found this
https://www.drivereasy.com/knowledge...windows-10/#F3
I unticked 'faststartup' as described and that worked. However putting in
password/code everytime is a pain so I put faststartup back in and it still
works.
I've boomarked that page just in case.

Good catch. I didn't think of that.

I never run with Fast Startup here, because sooner
or later, the hibernated kernel is going to get
corrupted.

Microsoft is supposed to do a regular boot every
once in a while, to "refresh" the hibernated kernel
image. But I don't know how many weeks pass, between
those refreshes (full boot cycle).

Now that this has happened to you, you might want
to run a memory test for a couple hours. I like to run
one of those, roughly once a year, to see if my
memory DIMMs are still good. That's based on my
average time for cheap memory to fail :-) The last memory
I replaced, was four Kingston sticks in this machine
(I couldn't fault isolate to the bad stick so had to
replace all of them).

Paul

On 2018-11-12 9:09 a.m., Jim S wrote:
On Mon, 12 Nov 2018 08:45:10 -0500, SilverSlimer wrote:

On 2018-11-12 7:00 a.m., Jim S wrote:
If I put my desktop to 'sleep' mode (or if it does it on timer) I cannot
get it to wake up.
If I move the mouse I normally hear the drive motor start then the screen,
but now I hear the motor start, but whatever I do the screen remains black.
The only solution is to turn off, wait 30 secs and start from scratch.

Ideas please.

What happens when you press the spacebar rather than move the mouse?

The same

Well, the very fact that it goes to sleep when you close the lid
indicates that it's probably not a hardware. Sleeping problems can occur
if - in a laptop most particularly - the little device which detects the
position of the screen in relation to the palmrest is out of place.
However, your machine goes to sleep so clearly, that piece of hardware
is not at fault.

My suggestion is that your computer is not sleeping when you close the
lid but rather, it's set up to _hibernate_. With hibernation, the
computer would actually be more or less off and restore its state when
you press the power button rather than move the mouse.


--
SilverSlimer
Minds: @silverslimer

On 2018-11-12 11:33 a.m., Jim S wrote:
On Mon, 12 Nov 2018 16:23:51 +0000, Andy Burns wrote:

Jim S wrote:

SilverSlimer wrote:

What happens when you press the spacebar rather than move the mouse?

The same

Is it a wired keyboard? If so do the caps/num/scroll lock keys toggle
the appropriate LEDs after the wake-up? If so it might just be a
failure of the monitor to come out of sleep mode ...

Thanks guys. I found this
https://www.drivereasy.com/knowledge...windows-10/#F3
I unticked 'faststartup' as described and that worked. However putting in
password/code everytime is a pain so I put faststartup back in and it still
works.
I've boomarked that page just in case.

Good to know you've solved the problem!


--
SilverSlimer
Minds: @silverslimer

On Mon, 12 Nov 2018 12:46:47 -0500, SilverSlimer wrote:

On 2018-11-12 9:09 a.m., Jim S wrote:
On Mon, 12 Nov 2018 08:45:10 -0500, SilverSlimer wrote:

On 2018-11-12 7:00 a.m., Jim S wrote:
If I put my desktop to 'sleep' mode (or if it does it on timer) I cannot
get it to wake up.
If I move the mouse I normally hear the drive motor start then the screen,
but now I hear the motor start, but whatever I do the screen remains black.
The only solution is to turn off, wait 30 secs and start from scratch.

Ideas please.

What happens when you press the spacebar rather than move the mouse?

The same

Well, the very fact that it goes to sleep when you close the lid
indicates that it's probably not a hardware. Sleeping problems can occur
if - in a laptop most particularly - the little device which detects the
position of the screen in relation to the palmrest is out of place.
However, your machine goes to sleep so clearly, that piece of hardware
is not at fault.

My suggestion is that your computer is not sleeping when you close the
lid but rather, it's set up to _hibernate_. With hibernation, the
computer would actually be more or less off and restore its state when
you press the power button rather than move the mouse.

Sorted as explained earlier, but you missed the fact that it is my desktop.

--
Jim S

Jim S wrote:

If I put my desktop to 'sleep' mode (or if it does it on timer) I cannot
get it to wake up.
If I move the mouse I normally hear the drive motor start then the screen,
but now I hear the motor start, but whatever I do the screen remains black.
The only solution is to turn off, wait 30 secs and start from scratch.

Same happen when you boot into Windows' safe mode and then sleep and try
to awake? If still a problem, disconnect all attached peripherals,
especially USB devices, except mouse and keyboard, reboot, and retest.

Some hardware or drivers won't resume from sleep. I had that happen
with a magicJack USB dongle that took a long time before they fixed
their driver.

When you awake but the monitor is still black, have you tried power
cycling the monitor?

UPDATE:
I see you disable the fast startup option. That was added in Windows 8
and carried into Windows 10. Normally when powering up a computer, a
reset signal is sent to all hardware to start it in a known state. You
can see the reset when the keyboard's LEDs flash. However, fast startup
saves the kernel state and that's where are the drivers, too. Without
the reset, resuming a driver with hardware in an unknown state may not
work. Depends on how the driver is coded. Unlike hibernation mode
where the system memory is copied into a file (hiberfil.sys), fast start
has you logoff and then the memory is copied which would be just the
kernel for the OS (and why hiberfile.sys is smaller).

Fast start is a hibernate mode; however, instead of saving your Windows
session, your session is logged out and then the hibernate file is
created. Hibernate takes you back into your Windows session. Fast
start is a truncated hibernate that gets you up to logging into a new
session. Fast start results in the computer doing a cold boot that
sends a reset signal to the all of the hardware but then the state of
their drivers is restored by fast start's hibernate state. They may not
match.

Users have reported that they disabled fast start but a subsequent
Windows update reenabled that option. You may have to disable it again
after another update. Microsoft is oh so impolite. My guess is it is a
registry setting, so once you find it then you could export it to a .reg
file. Then add a startup shortcut that runs "regedit.exe /s regfile"
to force the setting you want, not what Microsoft wants. You might want
to add it as a scheduled event triggered by login in Task Scheduler to
run with elevated privileges to avoid any UAC prompt about running
regedit.exe.

Another problem reported with fast start is wake-on-LAN events won't
fire with fast start enabled. Another is the disk space consumed by the
hibernate file (hiberfil.sys). Although smaller than a full hibernate
state for a Windows session because the hibernate file is written after
logging out of your Windows session, it still can suck up a lot of
space. Users of SSDs may not have the financial wherewithall to buy
huge-sized SSDs, so they don't want to waste any space on the small SSD
they do have. Some users report the Power button on their keyboard
ceases to function when using fast start and resuming later (probably
has to do with resuming the kernal in a state whose driver for the
keyboard differs from the reset state during the cold boot).

Since the computer you are asking about is a desktop, do you really need
to save the little bit of money to power it off versus just leaving it
powered up all the time? Sure, if you use your computer just once a
week. I use mine all the time at various times of the day and want it
immediately available when I want to use it, plus I have scheduled
events running when I'm least likely to be using the computer. Having
to power up from any state would be more nuisance than just having the
computer already and immediately ready for me to use. When I go on a
weeklong, or longer, vacation then I power down my computer; else, it's
always ready for me to use. Last I did a power calculation, it cost me
$12 per year to leave my computer always running. That's pretty cheap
convenience. I do have the monitor power down after 1 hour of idle and
the HDDs spin down after 4 hours of idle but that's it, for me,
regarding power saving. Replacing the incandescents and fluourescents
with LEDs saved a lot more (but with the incumbent longer ROI due to
their higher initial cost).

https://www.howtogeek.com/243901/the...-startup-mode/
"Fast Startup combines elements of a cold shutdown and the hibernate
feature. When you shut down your computer with Fast Startup enabled,
Windows closes all applications and logs off all users, just as in a
normal cold shutdown. At this point, Windows is in a state very similar
to when it¢s freshly booted up: No users have logged in and started
programs, but the Windows kernel is loaded and the system session is
running. Windows then alerts device drivers that support it to prepare
for hibernation, saves the current system state to the hibernation file,
and turns off the computer."

What if the driver weren't coded to handle fast start (hibernate
resume)? Did you migrate from a prior version of Windows to move to
Windows 10? Did you check if the maker of each piece of hardware
publishes a Windows 10 compliant driver (well, at least Windows 8
compliant to work with fast start)?

On Mon, 12 Nov 2018 12:46:47 -0500, SilverSlimer
wrote:

On 2018-11-12 9:09 a.m., Jim S wrote:
On Mon, 12 Nov 2018 08:45:10 -0500, SilverSlimer wrote:

On 2018-11-12 7:00 a.m., Jim S wrote:
If I put my desktop to 'sleep' mode (or if it does it on timer) I cannot
get it to wake up.
If I move the mouse I normally hear the drive motor start then the screen,
but now I hear the motor start, but whatever I do the screen remains black.
The only solution is to turn off, wait 30 secs and start from scratch.

Ideas please.

What happens when you press the spacebar rather than move the mouse?

The same

Well, the very fact that it goes to sleep when you close the lid
indicates that it's probably not a hardware.

How does one close the lid of a desktop computer?

Sleeping problems can occur
if - in a laptop most particularly - the little device which detects the
position of the screen in relation to the palmrest is out of place.
However, your machine goes to sleep so clearly, that piece of hardware
is not at fault.

My suggestion is that your computer is not sleeping when you close the
lid but rather, it's set up to _hibernate_. With hibernation, the
computer would actually be more or less off and restore its state when
you press the power button rather than move the mouse.

Come back when you are sober.

On Mon, 12 Nov 2018 14:01:19 -0600, VanguardLH wrote:

Jim S wrote:

If I put my desktop to 'sleep' mode (or if it does it on timer) I cannot
get it to wake up.
If I move the mouse I normally hear the drive motor start then the screen,
but now I hear the motor start, but whatever I do the screen remains black.
The only solution is to turn off, wait 30 secs and start from scratch.

Same happen when you boot into Windows' safe mode and then sleep and try
to awake? If still a problem, disconnect all attached peripherals,
especially USB devices, except mouse and keyboard, reboot, and retest.

Some hardware or drivers won't resume from sleep. I had that happen
with a magicJack USB dongle that took a long time before they fixed
their driver.

When you awake but the monitor is still black, have you tried power
cycling the monitor?

UPDATE:
I see you disable the fast startup option. That was added in Windows 8
and carried into Windows 10. Normally when powering up a computer, a
reset signal is sent to all hardware to start it in a known state. You
can see the reset when the keyboard's LEDs flash. However, fast startup
saves the kernel state and that's where are the drivers, too. Without
the reset, resuming a driver with hardware in an unknown state may not
work. Depends on how the driver is coded. Unlike hibernation mode
where the system memory is copied into a file (hiberfil.sys), fast start
has you logoff and then the memory is copied which would be just the
kernel for the OS (and why hiberfile.sys is smaller).

Fast start is a hibernate mode; however, instead of saving your Windows
session, your session is logged out and then the hibernate file is
created. Hibernate takes you back into your Windows session. Fast
start is a truncated hibernate that gets you up to logging into a new
session. Fast start results in the computer doing a cold boot that
sends a reset signal to the all of the hardware but then the state of
their drivers is restored by fast start's hibernate state. They may not
match.

Users have reported that they disabled fast start but a subsequent
Windows update reenabled that option. You may have to disable it again
after another update. Microsoft is oh so impolite. My guess is it is a
registry setting, so once you find it then you could export it to a .reg
file. Then add a startup shortcut that runs "regedit.exe /s regfile"
to force the setting you want, not what Microsoft wants. You might want
to add it as a scheduled event triggered by login in Task Scheduler to
run with elevated privileges to avoid any UAC prompt about running
regedit.exe.

Another problem reported with fast start is wake-on-LAN events won't
fire with fast start enabled. Another is the disk space consumed by the
hibernate file (hiberfil.sys). Although smaller than a full hibernate
state for a Windows session because the hibernate file is written after
logging out of your Windows session, it still can suck up a lot of
space. Users of SSDs may not have the financial wherewithall to buy
huge-sized SSDs, so they don't want to waste any space on the small SSD
they do have. Some users report the Power button on their keyboard
ceases to function when using fast start and resuming later (probably
has to do with resuming the kernal in a state whose driver for the
keyboard differs from the reset state during the cold boot).

Since the computer you are asking about is a desktop, do you really need
to save the little bit of money to power it off versus just leaving it
powered up all the time? Sure, if you use your computer just once a
week. I use mine all the time at various times of the day and want it
immediately available when I want to use it, plus I have scheduled
events running when I'm least likely to be using the computer. Having
to power up from any state would be more nuisance than just having the
computer already and immediately ready for me to use. When I go on a
weeklong, or longer, vacation then I power down my computer; else, it's
always ready for me to use. Last I did a power calculation, it cost me
$12 per year to leave my computer always running. That's pretty cheap
convenience. I do have the monitor power down after 1 hour of idle and
the HDDs spin down after 4 hours of idle but that's it, for me,
regarding power saving. Replacing the incandescents and fluourescents
with LEDs saved a lot more (but with the incumbent longer ROI due to
their higher initial cost).

https://www.howtogeek.com/243901/the...-startup-mode/
"Fast Startup combines elements of a cold shutdown and the hibernate
feature. When you shut down your computer with Fast Startup enabled,
Windows closes all applications and logs off all users, just as in a
normal cold shutdown. At this point, Windows is in a state very similar
to when it¢s freshly booted up: No users have logged in and started
programs, but the Windows kernel is loaded and the system session is
running. Windows then alerts device drivers that support it to prepare
for hibernation, saves the current system state to the hibernation file,
and turns off the computer."

What if the driver weren't coded to handle fast start (hibernate
resume)? Did you migrate from a prior version of Windows to move to
Windows 10? Did you check if the maker of each piece of hardware
publishes a Windows 10 compliant driver (well, at least Windows 8
compliant to work with fast start)?

Aw man Vanguard, your stuff is obviously full of useful info, but my head
just exploded :-)
My sojourn so far seemed to work, but tonight I left it for two hours and
it would not start.
Just TELL ME what to do!!
When I go to bed shortly I will shut down.
No sleeping tonight for you Mr Computer.
--
Jim S

On Mon, 12 Nov 2018 14:01:19 -0600, VanguardLH wrote:

Jim S wrote:

If I put my desktop to 'sleep' mode (or if it does it on timer) I cannot
get it to wake up.
If I move the mouse I normally hear the drive motor start then the screen,
but now I hear the motor start, but whatever I do the screen remains black.
The only solution is to turn off, wait 30 secs and start from scratch.

Same happen when you boot into Windows' safe mode and then sleep and try
to awake? If still a problem, disconnect all attached peripherals,
especially USB devices, except mouse and keyboard, reboot, and retest.

Some hardware or drivers won't resume from sleep. I had that happen
with a magicJack USB dongle that took a long time before they fixed
their driver.

When you awake but the monitor is still black, have you tried power
cycling the monitor?

UPDATE:
I see you disable the fast startup option. That was added in Windows 8
and carried into Windows 10. Normally when powering up a computer, a
reset signal is sent to all hardware to start it in a known state. You
can see the reset when the keyboard's LEDs flash. However, fast startup
saves the kernel state and that's where are the drivers, too. Without
the reset, resuming a driver with hardware in an unknown state may not
work. Depends on how the driver is coded. Unlike hibernation mode
where the system memory is copied into a file (hiberfil.sys), fast start
has you logoff and then the memory is copied which would be just the
kernel for the OS (and why hiberfile.sys is smaller).

Fast start is a hibernate mode; however, instead of saving your Windows
session, your session is logged out and then the hibernate file is
created. Hibernate takes you back into your Windows session. Fast
start is a truncated hibernate that gets you up to logging into a new
session. Fast start results in the computer doing a cold boot that
sends a reset signal to the all of the hardware but then the state of
their drivers is restored by fast start's hibernate state. They may not
match.

Users have reported that they disabled fast start but a subsequent
Windows update reenabled that option. You may have to disable it again
after another update. Microsoft is oh so impolite. My guess is it is a
registry setting, so once you find it then you could export it to a .reg
file. Then add a startup shortcut that runs "regedit.exe /s regfile"
to force the setting you want, not what Microsoft wants. You might want
to add it as a scheduled event triggered by login in Task Scheduler to
run with elevated privileges to avoid any UAC prompt about running
regedit.exe.

Another problem reported with fast start is wake-on-LAN events won't
fire with fast start enabled. Another is the disk space consumed by the
hibernate file (hiberfil.sys). Although smaller than a full hibernate
state for a Windows session because the hibernate file is written after
logging out of your Windows session, it still can suck up a lot of
space. Users of SSDs may not have the financial wherewithall to buy
huge-sized SSDs, so they don't want to waste any space on the small SSD
they do have. Some users report the Power button on their keyboard
ceases to function when using fast start and resuming later (probably
has to do with resuming the kernal in a state whose driver for the
keyboard differs from the reset state during the cold boot).

Since the computer you are asking about is a desktop, do you really need
to save the little bit of money to power it off versus just leaving it
powered up all the time? Sure, if you use your computer just once a
week. I use mine all the time at various times of the day and want it
immediately available when I want to use it, plus I have scheduled
events running when I'm least likely to be using the computer. Having
to power up from any state would be more nuisance than just having the
computer already and immediately ready for me to use. When I go on a
weeklong, or longer, vacation then I power down my computer; else, it's
always ready for me to use. Last I did a power calculation, it cost me
$12 per year to leave my computer always running. That's pretty cheap
convenience. I do have the monitor power down after 1 hour of idle and
the HDDs spin down after 4 hours of idle but that's it, for me,
regarding power saving. Replacing the incandescents and fluourescents
with LEDs saved a lot more (but with the incumbent longer ROI due to
their higher initial cost).

https://www.howtogeek.com/243901/the...-startup-mode/
"Fast Startup combines elements of a cold shutdown and the hibernate
feature. When you shut down your computer with Fast Startup enabled,
Windows closes all applications and logs off all users, just as in a
normal cold shutdown. At this point, Windows is in a state very similar
to when it¢s freshly booted up: No users have logged in and started
programs, but the Windows kernel is loaded and the system session is
running. Windows then alerts device drivers that support it to prepare
for hibernation, saves the current system state to the hibernation file,
and turns off the computer."

What if the driver weren't coded to handle fast start (hibernate
resume)? Did you migrate from a prior version of Windows to move to
Windows 10? Did you check if the maker of each piece of hardware
publishes a Windows 10 compliant driver (well, at least Windows 8
compliant to work with fast start)?


--
Jim S

Jim S wrote:

My sojourn so far seemed to work, but tonight I left it for two hours and
it would not start.

If the fast startup option was still disabled after a reboot, test with
ALL sleeping disabled. My guess is the 2 hour idle was longer than
whatever sleep time you configured in whichever plan (scheme) you used
in Power Options. Go into the power options and configure to leave the
computer on ALL THE TIME. Then test.

Maybe the problem was not with fast startup mode (a type of hibernate
mode) but with the low-power saving mode (sleep or standby). As
mentioned, some drivers or hardware won't deal well with getting slept.
Test with no sleeping enabled.