Windows 10: PC would not restart after sleep until . . .

My PC refused to wake up after a period of sleep. I turned off the power and then on again and it still wouldn't wake. In desperation I replugged the power, whereupon it booted normally. As soon as I could I ran Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:\Sources\Install.esd:1 and SFC /scannow. Errors were found and repaired.

Does anyone know what might have caused this event and how it can be avoided?

HP HP Pavilion Desktop PC 570-pOXX.
Windows 10 Home (X64) Version 1709 (build 16299.192)

:)

 

Computer sleeps, then restarts

This is a continuing problem. It started about 3 weeks ago when it would not stay in sleep mode (it would restart) and it would restart after shutdown. I unchecked "turn on fast start" which solved the restart after shutdown problem. After further searching
I changed windows update to "Notify to schedule restart". That solved the restart after sleep problem until three days ago. The problem is now back. After further searching I ran the Windows System File Checker and it found no problems. I have tried several
suggestions of turning off various sleep related options in device manager but none solved the problem. I restarted the computer in safe mode and it did sleep without restarting. No new programs were added.

I have changed the settings to turn off the screen in 5 minutes but sleep in 30. After 30 minutes the computer sleeps and restarts. The screen comes on for five minutes and the cycle repeats itself.

Any other ideas?????

 

Text cursor disappears while typing and comes back intermittently after windows 10 install. Cannot type while disappeared.

As per an update, this only happens after hibernate or sleep mode. If I restart, the problem disappears until I come back from a hibernate or sleep. It is still doing this and it is very annoying. I would like not to have to restart every time I want to
leave the computer.

 

Run this version of the log collector and post a zip into this thread:
log collector v2-beta08.zip

Please update the spes in the "My Computer" section:
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Site Use Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums


Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)

 

'Preciate your reply. Updated My Computer. Cannot access log collector v2-beta .zip as a url. Where is it?

Found MS update in Event Viewer at about the right time, so maybe system was updating when I tried to wake it.

 

Open administrative command prompt and type or copy and paste:
1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) ckdsk /scan
4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

5) After the above steps run this version of the log collector and post a zip into this thread:
log collector v2-beta08.zip

6) If the above version fails please provide as much information as possible as to what happened. If you can click prt sc etc.

 

The URL for log collector v2-beta08.zip unpacks to Code: Windows 10 Help Forums bsod-crashes-debugging/ 172784d1516099457-bsod-posting- instructions-log-collector-v2-beta08.zip (stitch items together into a single line)[/quote] on my PC. Perhaps you can access that explicit URL directly? It works for me... and asks me if I want to open or save the .zip file. It should do likewise for you, if you paste the items shown above together into a single URL (omitting the parenthetical phrase at the end, please).
HTH,
--Ed--

 

on my PC. Perhaps you can access that explicit URL directly? It works for me... and asks me if I want to open or save the .zip file. It should do likewise for you, if you paste the items shown above together into a single URL (omitting the parenthetical phrase at the end, please).
HTH,
--Ed--[/quote] Ed, All I was seeing in Firefox was a blank screen. Just now I tried the expanded url in IE and got a prompt to download. In the course of selecting a download location (C:\all\down) I saw that I had 12 copies of the file. There was no indication in Firefox that downloads were taking place. So I'll chalk it up to a learning experience.

 

zbook, I'm about to do as you directed. I'll get back later . . .

Code: Microsoft Windows [Version 10.0.16299.192] (c) 2017 Microsoft Corporation. All rights reserved. C:\Users\tcebo>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. C:\Users\tcebo>dism /online /cleanup-image /restorehealth Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.192 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. C:\Users\tcebo>ckdsk /scan 'ckdsk' is not recognized as an internal or external command, operable program or batch file. C:\Users\tcebo>chkdsk /scan The type of the file system is NTFS. Volume label is Windows. Stage 1: Examining basic file system structure ... 414208 file records processed. File verification completed. 11252 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 27978 reparse records processed. 497576 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 27978 reparse records processed. Stage 3: Examining security descriptors ... Security descriptor verification completed. 41685 data files processed. CHKDSK is verifying Usn Journal... 38528056 USN bytes processed. Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 962901083 KB total disk space. 94827704 KB in 215397 files. 144640 KB in 41686 indexes. 0 KB in bad sectors. 560875 KB in use by the system. 65536 KB occupied by the log file. 867367864 KB available on disk. 4096 bytes in each allocation unit. 240725270 total allocation units on disk. 216841966 allocation units available on disk.[/quote] . . . Working on Log collector . . . done.
C:\Users\tcebo>

 

Glad you got the download working, tcebob. Google does that to me sometimes, too. It's always disconcerting to find out stuff is going on in the background without any obvious or noticeable foreground notification. I feel your pain!
--Ed--

 

The logs had 2 unexpected shutdown/restarts, one on 2/3 and one on 2/10.
Otherwise the logs were unremarkable.
There was a problem device:

1) Open device manager > click view > show hidden devices > expand all rows > look for rows that display yellow triangular icons with a black exclamation mark > post images into the thread
2) This was displayed as a problem device:
Unknown USB Device (Device Descriptor Request Failed) USB\VID_0000&PID_0002\6&236F3B91&0&6 43
Look for an unknown device in device manager > post an image into the thread
3) Download and install the latest version of the HP UEFI hardware diagnostics: HP PC Hardware Diagnostics | HP® Official Site
4) Power on repetitively clicking the F2 key for an overnight test > Run the HP UEFI hardware diagnostics in loop until failure overnight > the firmware is designed to abort if there are any problems > if there are no problems the next day click the keyboard escape key to abort the testing > confirm the pass in the BIOS UEFI logs.



Code: Event[2547]: Log Name: System Source: storahci Date: 2018-02-11T13:45:23.942 Event ID: 129 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-VQC5R6M Description: Reset to device, \Device\RaidPort1, was issued.[/quote] Code: Event[2507]: Log Name: System Source: Volsnap Date: 2018-02-10T21:05:52.590 Event ID: 33 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-VQC5R6M Description: The oldest shadow copy of volume C: was deleted to keep disk space usage for shadow copies of volume C: below the user defined limit.[/quote] Code: Event[2455]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2018-02-10T19:58:03.277 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-VQC5R6M Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.[/quote]

 

Here's a shot of Device Manager. I can't find any detail in the unknown USB. Ran repair but no change.





Ran HP UEFI diagnostics.




Can't find the logs but I'm pretty sure the system is OK.

Many thanks for your assistance!

 

For the unknown device: right click on it > left click properties > click details tab > in the properties bar choose hardware IDs > make an image to post into the thread and copy and paste the results in the value area into the thread. Then search the internet using the information in this link for the information about the driver:

How to easily find drivers for Unknown Devices in Windows | PCWorld
How to Find Drivers for Unknown Devices in the Device Manager

Open the HP website > enter the computer's product or serial number > view available drivers > update the HP UEFI hardware diagnostics from version 6.4 to either 6.5 or 6.6. If the up to date version is not listed in the available driver use this HP link:
HP PC Hardware Diagnostics | HP® Official Site

 

Here is a shot of HP Diagnostics 6.5. Seems OK.





And Device Manager. Note that the unknown driver is listed but the yellow flag is not there. There is no reference to the driver.

 

I've seen this kind of thing before, and it usually occurs when a USB driver issue somewhere between the end device (usually a drive, a USB stick, or something similar) and the root hub gets flaky. If you run Uwe Sieber's USB Device Tree Viewer, you'll see something like this:



This will help you zero right in on what's in port#6hub#2 that's "gone missing."
HTH,
--Ed--