Resolved Win 10 - Wake Up Hassle

After the latest Windows 10 pro upgrade to 1511 | OS Build 10586.318 (automatic update) my computer has some waking up from sleep problems. It refuses to wake up on moving the mouse or a pressing a button. It literally needs to be restarted or refreshed. I have double checked the power and sleep settings where nothing is extraordinary.

Any suggestions - wizards ?

Regards,

Rista
Ps: If I didn't already say, overall nice and comfortable design..

 

Hi Evan,

Many thanks for the advice. The power setting was "Balanced" is now on "High Performance ", the USB as well as the Hybrid Sleep were otherwise, but are now as per your instructions. I also went for a "Clean Reboot ", but the problem still remains impudent as ever.

However, I observed, when the computer is in "Sleep" the pilot light blinks and when it wakes up comes on there is a small surge of the fan, the pilot light becomes constant again and the screen comes back; at least that is just how it used to be. This time it did all that - surge of fan and constant pilot light, but the screen remains black and unchanged. This could mean the power settings may be working, but there may be sand in the screen settings..!? The screen is a 27" Samsung SyncMaster S27B550 if that means anything at the moment.

I will look deeper in the event viewer tomorrow and let you know if I find something there.

Thanks and best regards for the moment,

Rista

 

All the Root Hub entries were already not set to be turned off as illustrated in the link you sent.

 

Morning Evan,

Yes, the USB Hubs and all others in Device Manager seem to be OK. I also updated the ATI Radeon 2600 Pro Driver and it successfully installed it once again, but the Driver Date still shows 13-Jan-15, version 8.970.100.9001 which it also showed previously.

Since the computer is attached to an additional screen which is the same make , only a little smaller and I tried to use that as the main display, but the behavior did not change. I have a dual boot system and there is a Windows 8.1 on the second partition. I just used the sleep function on that and it worked and then I tried a second time leaving in sleep for about 10 min and this time it did not work. It went into short surges of activity several times to get itself on the screen, but it couldn't. So it gave up and went on with a black screen as usual. I tried again, but it did not work. So there is something, most probably, not working properly on the Hardware side.If there is how can one be sure? That is baffling since the machine works quite efficiently, except for this anomaly. One can also live with that... until it gives up completely.

Regards,

Rista

 

I have just checked what's in the BIOS Power Settings:

ACPI Support : Yes
ACPI Suspend Type: S3
Soft Off by PWR-BTTN: Delay 4 sec
PWRON After PWR-Fail: Former-Sts

Resume by
RING: Disabled
PCI/PCI-E/LAN PME: Enabled
USB (S1/S3): Enabled
PS2 KB (S1/S3): Disabled
PS2 MS (S1/S3): Disabled
RTC Alarm: Disabled

Apart from that:
Main Board ID: EG31M
SM BIOS Version: 2.5.0
System BIOS Version: R01-A3
BIOS Release Date: 08/28/07
American Megatrends, Inc.

There are no other "Sleep" related settings.

I have been rather busy with something else today, thus the delayed answer.

Regards,

 

Hi Evan,

Yes, I am using a wireless Logitech Mouse and Keyboard set.

I "ve changed the BIOS settings all three are now enabled and it showed one new option for the Key Board which it set to any key.

On testing it failed. This time the system tried man times with short surges of activity to reinstate, but it failed to make it - the screen remained black.

Something is either preventing it to come back on or something is not getting triggered in the system (it may even be Hardware). I also took an Event Viewer screen shot (see attachment) and the most prominent one is KERNEL POWER.

The explanation for this Event ID 41 | Task Category 63 "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. "

Regards,

 

Hi Evan,

Sorry for the sluggish responses from me. In the meanwhile I'm quite certain that the problem lies with the power appliance or the power transmission or something thereabouts. This morning it did the same thing on start as by trying to wake up from sleep. It may also just be dust which is bogging down the works. I don't have any compressed air to let you know straight away, but I will definitely let you know after cleaning it and if I install a new part or whatever fixes it..

Thank you so much for your help in the matter,

Regards,

 

Hi Evan,
I cleaned the system, though it was hardly dust covered, but no betterment. I also rechecked all the connections as a wobbly connection is often the hidden problem, but in this case nothing new. Finally I got someone to check if the power supply was gone south, but his inference was that it was in good condition and functioned exactly expected.

On further carping, the START is also showing problems too - takes too long shows the bios entrance page twice (originally only once) before it gave the options for windows 8 and Windows 10. It seems to start a couple of times before showing the options. Perhaps removing Windows 8 might fix it.. Perhaps you can give me some tips to how best to remove and store it somewhere else. It is on a different partition of the same 750 GB disk.
This afternoon I bumped into this very interesting article while researching Git Bash commands:

Investigate Windows sleep states with the PowerCfg command - TechRepublic

I went ahead to generate the report and came up with the following (I will get further reports with the other specified states and parameters):

PS C:\Scripts> powercfg /devicequery /?
POWERCFG /DEVICEQUERY <QUERYFLAG>
Description:
Returns a list of devices that meet the specified criteria.
Parameter List:
<QUERYFLAG> Specifies one of the following criteria:

wake_from_S1_supported Return all devices that support waking the system from a light sleep state.
wake_from_S2_supported Return all devices that support waking the system from a deeper sleep state.
wake_from_S3_supported Return all devices that support waking the system from the deepest sleep state.
wake_from_any Return all devices that support waking the system from any sleep state.
S1_supported List devices supporting light sleep.
S2_supported List devices supporting deeper sleep.
S3_supported List devices supporting deepest sleep.
S4_supported List devices supporting hibernation.
wake_programmable List devices that are user-configurable to wake the system from a sleep state.
wake_armed List devices that are currently configured to wake the system from any sleep state.
all_devices Return all devices present in the system.

PS C:\Scripts> powercfg /devicequery wake_programmable
Logitech HID-compliant Cordless Mouse
HID Keyboard Device
HID-compliant vendor-defined device
HID-compliant consumer control device
HID-compliant system controller
HID-compliant consumer control device (001)
Logitech HID Keyboard Consumer Controls
Logitech HID-Compliant Keyboard (001)
Logitech HID Keyboard Power Key (001)
HID-compliant vendor-defined device (003)
Realtek PCIe GBE Family Controller
HID-compliant vendor-defined device (004)

PS C:\Scripts> powercfg /devicequery wake_from_S1_supported
Logitech Driver Interface (001)
Logitech HID-compliant Cordless Mouse
Logitech Driver Interface (002)
Logitech Driver Interface (003)
Logitech Driver Interface (004)
HID Keyboard Device
HID-compliant vendor-defined device
HID-compliant consumer control device
HID-compliant system controller
Logitech Driver Interface (005)
HID-compliant consumer control device (001)
Logitech HID Keyboard Consumer Controls
Logitech HID-Compliant Keyboard (001)
USB Composite Device
Realtek USB 2.0 Card Reader
Logitech HID Keyboard Power Key (001)
USB Input Device (001)
HID-compliant vendor-defined device (003)
Microsoft Hosted Network Virtual Adapter
USB Input Device (004)
HID-compliant vendor-defined device (004)
USB Input Device (005)

Please let me know what you think as time allows.

Regards,

 

Hi Evan,

Good day to you. I have cleaned up the system, reorganized, removed and stored away Windows 8.1. Unfortunately, the problem still remains, but what the heck I can live with it. It would have been nice to finally know what's wrong, but who knows some update down the line will mysteriously fix it just as mysteriously it appeared. I have many other computers powerful, gamers with many gimmicks, bells and whistles but I will continue to work with this one. This one however, is so quiet that you can have complete pin drop silence in the room no matter how high the load. And there is no extra sound insulation as I have with a couple of gamers. You did your best and we went down in the dungeons and I learnt and read a lot on the subject. Perhaps Arie can stow it away in one of those dungeons as one of those X-files..

Thanks a lot for your help and support.

Best regards,

 

I tried it this morning and I cannot boot anymore!!! I must have goofed it terribly..

On trying to boot it gives a message:

Recover
PC/Device needs to be repaired.
Application/Operating System couldn't be loaded because a required file is missing or corrupted
File :\windows\system 32\winload.exe Error code: 0xc0000225
You'll need to use recovery tools. If you don't have any installation media (like a disc or USB device) contact your PC Admin or PC/Device manufacturer.
Press ENTER to try again
Press F8 for Startup settings

On using any of these options nothing happens it does not take you anywhere, it remains as it is no matter which option you press.

So I now thought that I did make a Recovery CD with Acronis True Image 2016 and made Backups for Windows 8 as well as for Windows 10. So I tried that and Acronis goes in there fine and can find installations as well as all the Backups, but won't or can't recover C:\ which is listed now as "D:\" . I tried to find winload.exe under system 32, but it isn't in there and it is nowhere else. How to place it there even if I could find one. I did not try it for windows 8 as I don't want that.
Now, I downloaded and made another Installation/Recover DVD with Windows 10 iso and tried to repair with that. Using the repair option on that notifies that, "Repair could not be done . Try Advance Options or Shut Down ". Tried Advance Options, nothing works there either. I tried going in through command prompt, but it has an " X:<Sources>" which doesn't let you change to any of the Drives. I was hoping that one might be able to somehow copy and place the missing winload.exe in system 32 if that is the only problem..

I am feeling quite frustrated at the moment and am using a laptop writing to you. Perhaps you know of someway to get it going? If nothing works I may have to make a new installation and then copy all the files as they seem to be available, but that is such a drag redoing everything from scratch..

Regards,

 

Today I am no longer frustrated. Last night before hitting the sack I wondered why the backup wasn't materializing and I realized that I wasn't offering it a "new location ". Acronis needs to be taken to this location and it even then gives options for fixing unallocated space before and after the partition as it confirmed this morning. So as I tried with the new settings it worked and restored the Local Disc. It took about 40 min. and finished successfully.

Now I readjusted the BIOS start order for booting and did a fresh boot. To my dismay it did not boot and showed a similar screen as yesterday. That got my gizzard so I wanted now to re-install the whole thing afresh. So I stuck in the ISO Repair disc to start a new installation, but here I said let me try the repair version once more This time it tried to repair and kept on churning at "Attempting to Repair" for about a half an hour before I interrupted the futile attempt. Somewhere it also lingered in my mind, I had read somewhere last year, that Windows 10 was done away with winload.exe - it was no longer part of the boot process. So I checked for it on the net and found this post:
Windows 10 will not boot

And that did the trick it had all along been asking for winload.exe and since this is not a part of Windows 10 it could not produce it and neither repair the process. So you see the boot process, in my case dual booting with Windows 8.1, is entangled with the booting process of Windows 10 and the new Start in Win 10 does not overtake the previous Start as was the case in previous versions Vista/Windows 7/ Windows 8 etc. And all that makes me feel good again about the mishap. Increased experience and knowledge one more notch!

Now that we know that my backups are working and we also know about the boot process/mbr, I would like to know how to decouple the winload.exe from windows 10 and let it start as it independently would do.

All the best for now,