none
Win 10 Pro going to sleep in spite of settings RRS feed

  • Question

  • Just purchased a new Dell Inspiron with Win 10 Home, upgraded to Pro.  I have modified one power setting - 'put computer to sleep - when plugged in - never'.  And yet after some time we find it has gone to sleep.  Actually, looks like it completely shut down, as hitting the power button it starts with the dell logo from the bios.

    I have not yet determined at what point it sleeps/shuts down, but I know it is less than three hours.

    Ideas?

    Thursday, November 14, 2019 3:02 AM

All replies

  • Hi,

    It may cause from "System unattended sleep timeout".
    If so, please try this (use PowerConfig):

    1) open command prompt: [windows]+[R] > type cmd and [Enter]
    2) type (copy this and paste in command prompt)
       powercfg -attributes SUB_SLEEP 7bc4a2f9-d8fc-4469-b07b-33eb785aaca0 -ATTRIB_HIDE
       and [Enter]
       

    3) (you will be able to see [Sleep] in Power Options)
       
       Please change them as you like.

    Regards,

    Ashidacchi -- http://hokusosha.com


    • Edited by Ashidacchi Thursday, November 14, 2019 3:55 AM
    Thursday, November 14, 2019 3:46 AM
  • Just purchased a new Dell Inspiron with Win 10 Home, upgraded to Pro.  I have modified one power setting - 'put computer to sleep - when plugged in - never'.  And yet after some time we find it has gone to sleep.  Actually, looks like it completely shut down, as hitting the power button it starts with the dell logo from the bios.

    I have not yet determined at what point it sleeps/shuts down, but I know it is less than three hours.

    Ideas?

    Hello,

    Please run Power troubleshooter from Settings app > Update & Security > Troubleshoot. 

    Also, see if suggestions provided here helps you:

    https://www.kapilarya.com/fix-windows-10-shuts-down-instead-of-sleep-hibernate

    Let us know if this helps!

    Note: Included link in this reply refers to blog post by a trusted Microsoft MVP.


    Microsoft MVP (Windows and Devices for IT)

    Windows Insider MVP

    Windows Help & Support [www.kapilarya.com]

    Thursday, November 14, 2019 9:23 AM
  • Lest anyone think I'm a WORN participant (WORN = Write Once Read Never), I'm still here - just juggling several chainsaws at once.  I'll go through all of the suggestions, but actual testing can take quite some time, waiting for the 'timeout' to occur.  And it appears it may still be user error/misunderstanding on exactly how this particular hardware/OS combination responds.  It doesn't help that this particular computer has no LEDs indicating its current power status - on, hibernate, sleep, etc.  So one can only guess based on behavior of touching the power button vs. touching the mouse, etc.
    Friday, November 15, 2019 3:47 PM
  • @Ashidacchi - I'm sure you can understand a bit of reluctance on executing an arcane, invasive command just on the recommendation of a stranger on the internet.  :-)   So I reserched 'powercfg' first, and find no reference to a '-attributes' option. 
    Friday, November 15, 2019 4:29 PM
  • Would you mind letting me know the update of the problem? If you need further assistance, feel free to let me know. 

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, December 9, 2019 8:56 AM
    Moderator
  • The only update I have on this is that I've at least found a pattern to getting it restarted.  As said earlier, the machine appears to go to sleep at random intervals. When in this state it doesn't respond to any keyboard, mouse, or touchpad activity.  It also doesn't respond to a simple press of the power button.  But if I hold the power button for a few seconds, then release and wait a few seconds, then press again, the machine appears to go through a complete power up sequence. I know that holding the power button several seconds initiates a forced power-off.  But still no clues as to why it is getting itself into this state in the first place.
    Monday, December 9, 2019 3:19 PM
  • @edstevensdba,

    I could execute the above powercfg command with Windows 10 Pro successfully.
    I also could not find -attribute option in powercfg. But it worked and new option could be seen in Power Options.
    Did you try to execute that powercfg command?

    Regards,

    Ashidacchi -- http://hokusosha.com

    Tuesday, December 10, 2019 2:25 AM
  • Well, this is very strange.  When I link to this thread from the latest email notification, I see later replies, like a second request from @Ashidacchi to execute the undocumented powercfg command.  But when I click to reply, I get prompted to log on with my MS account, and after that the thread comes back without the message I wanted to reply to ....

    And now, when I type in more reply, and paste a couple of screen shots, then hit 'submit', I get a message that my reply must be between 4 and (some very large number - in the 10s of thousands) characters.  So I'm trying again without the screen shots to see what happens.

    Nevertheless, again, first please accept my apologies for not responding quickly.  I'm still in the mode of juggling several chain saws.  Also, again I hope you will understand my reluctance to issue an undocumented command offered by (to me) a stranger on the internet.  That said, I'm on the verge of issueing that command and am at this point just looking for some clarification/assurance.  I ran 'powercfg /q', redirecting the output to a text file for examination.  Searched it for 'UnattendTimeout' and for '7bc4a2f9-d8fc-4469-b07b-33eb785aaca0'.  Did not get a hit on either, but don't know if that is expected at this point.  Also compared my Power Options Advanced Settings, and they look to be as we want, even though mine is breaking out options for 'on battery' and 'plugged in'.  Values for 'plugged in' are as follows:

    sleep after - never

    Allow mybrid sleep - off

    hibernate after - never

    Allow wake timers - Important wake timers only

    Which seems to square with above.

    Friday, December 13, 2019 5:33 PM
  • @Ashidacchi - out of desparation I executed the powercfg command.  Since the problem is erratic, we'll have to wait a few (several?) days to evaluate.  Thanks for your assistance, patience, and understanding.
    Tuesday, December 17, 2019 11:18 PM
  • After running the previously suggested powercfg command, the problem persists.
    Friday, December 20, 2019 3:44 PM
  • You say the PC goes to sleep unexpectedly and refuses to wake.  However, your description of using the power button suggests it has crashed, needing a forced shutdown.

    It seems to me you may be seeking a solution to the wrong problem.  As it was recently purchased perhaps consult Dell support for a warranty fix.

    • Proposed as answer by Ashidacchi Friday, December 20, 2019 8:27 PM
    Friday, December 20, 2019 5:45 PM
  • Hello,

    Open an elevated CMD prompt and run powercfg /systempowerreport.

    Post the results back to the thread.

    Also open the System Event log and look for Kernel Power events Event 506.

    Post the information from the Details tab.


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Friday, December 20, 2019 7:32 PM
  • The powercfg /systempowerreport produced an html file.  I'm not sure of the best way of posting it, but I can say that examining it, I didn't see anything suspicious. It did report "abnormal shutdown" at 8:40 this morning, which is the most recent time I had to do the hard shutdown described above. 

    I found no 506 events in the system event log, but here are the even surrounding the hard shutdown I performed at 08:40.  That was the first time I touched the machine today, so whatever it was doing the last 12 or more hours prior was its own internal operations.

    evel    Date and Time    Source    Event ID    Task Category
    Information    12/21/2019 8:40:02 AM    Microsoft-Windows-Kernel-Power    521    (220)    Active battery count change.
    Information    12/21/2019 8:40:02 AM    Microsoft-Windows-Kernel-Processor-Power    55    (47)    "Processor 7 in group 0 exposes the following power management capabilities:
     
    Idle state type: ACPI Idle (C) States (3 state(s))
     
    Performance state type: ACPI Collaborative Processor Performance Control
    Nominal Frequency (MHz): 1800
    Maximum performance percentage: 216
    Minimum performance percentage: 55
    Minimum throttle percentage: 5"
    Information    12/21/2019 8:40:02 AM    Microsoft-Windows-Kernel-Processor-Power    55    (47)    "Processor 5 in group 0 exposes the following power management capabilities:
     
    Idle state type: ACPI Idle (C) States (3 state(s))
     
    Performance state type: ACPI Collaborative Processor Performance Control
    Nominal Frequency (MHz): 1800
    Maximum performance percentage: 216
    Minimum performance percentage: 55
    Minimum throttle percentage: 5"
    Information    12/21/2019 8:40:02 AM    Microsoft-Windows-Kernel-Processor-Power    55    (47)    "Processor 3 in group 0 exposes the following power management capabilities:
     
    Idle state type: ACPI Idle (C) States (3 state(s))
     
    Performance state type: ACPI Collaborative Processor Performance Control
    Nominal Frequency (MHz): 1800
    Maximum performance percentage: 216
    Minimum performance percentage: 55
    Minimum throttle percentage: 5"
    Information    12/21/2019 8:40:02 AM    Microsoft-Windows-Kernel-Processor-Power    55    (47)    "Processor 1 in group 0 exposes the following power management capabilities:
     
    Idle state type: ACPI Idle (C) States (3 state(s))
     
    Performance state type: ACPI Collaborative Processor Performance Control
    Nominal Frequency (MHz): 1800
    Maximum performance percentage: 216
    Minimum performance percentage: 50
    Minimum throttle percentage: 5"
    Information    12/21/2019 8:40:02 AM    Microsoft-Windows-Kernel-Processor-Power    55    (47)    "Processor 6 in group 0 exposes the following power management capabilities:
     
    Idle state type: ACPI Idle (C) States (3 state(s))
     
    Performance state type: ACPI Collaborative Processor Performance Control
    Nominal Frequency (MHz): 1800
    Maximum performance percentage: 216
    Minimum performance percentage: 50
    Minimum throttle percentage: 5"
    Information    12/21/2019 8:40:02 AM    Microsoft-Windows-Kernel-Processor-Power    55    (47)    "Processor 4 in group 0 exposes the following power management capabilities:
     
    Idle state type: ACPI Idle (C) States (3 state(s))
     
    Performance state type: ACPI Collaborative Processor Performance Control
    Nominal Frequency (MHz): 1800
    Maximum performance percentage: 216
    Minimum performance percentage: 50
    Minimum throttle percentage: 5"
    Warning    12/21/2019 8:40:02 AM    rt640x64    1    None    Realtek PCIe FE Family Controller is disconnected from network.
    Information    12/21/2019 8:40:02 AM    Microsoft-Windows-Kernel-Processor-Power    55    (47)    "Processor 2 in group 0 exposes the following power management capabilities:
     
    Idle state type: ACPI Idle (C) States (3 state(s))
     
    Performance state type: ACPI Collaborative Processor Performance Control
    Nominal Frequency (MHz): 1800
    Maximum performance percentage: 216
    Minimum performance percentage: 61
    Minimum throttle percentage: 5"
    Information    12/21/2019 8:40:02 AM    Microsoft-Windows-Kernel-Processor-Power    55    (47)    "Processor 0 in group 0 exposes the following power management capabilities:
     
    Idle state type: ACPI Idle (C) States (3 state(s))
     
    Performance state type: ACPI Collaborative Processor Performance Control
    Nominal Frequency (MHz): 1800
    Maximum performance percentage: 216
    Minimum performance percentage: 22
    Minimum throttle percentage: 5"
    Information    12/21/2019 8:40:01 AM    Microsoft-Windows-Ntfs    98    None    Volume \\?\Volume{679a3d44-59b2-4b81-a235-d8a37c1f8e4b} (\Device\HarddiskVolume4) is healthy.  No action is needed.
    Warning    12/21/2019 8:40:01 AM    Microsoft-Windows-Kernel-PnP    219    (212)    The driver \Driver\WudfRd failed to load for the device PCI\VEN_8086&DEV_1903&SUBSYS_08CA1028&REV_0C\3&11583659&0&20.
    Information    12/21/2019 8:40:01 AM    Microsoft-Windows-DriverFrameworks-UserMode    10118    Startup of the UMDF reflector    UMDF reflector is unable to connect to service control manager (SCM). This is expected during boot, when SCM has not started yet. Will retry when it starts.
    Information    12/21/2019 8:40:01 AM    Microsoft-Windows-Kernel-Power    172    (203)    Connectivity state in standby: Disconnected, Reason: NIC compliance
    Critical    12/21/2019 8:40:01 AM    Microsoft-Windows-Kernel-Power    41    (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.
    Information    12/21/2019 8:40:01 AM    Microsoft-Windows-FilterManager    6    None    File System Filter 'npsvctrig' (10.0, ‎1977‎-‎09‎-‎12T09:19:34.000000000Z) has successfully loaded and registered with Filter Manager.
    Information    12/21/2019 8:40:01 AM    Microsoft-Windows-FilterManager    6    None    File System Filter 'FileCrypt' (10.0, ‎2011‎-‎10‎-‎30T09:56:49.000000000Z) has successfully loaded and registered with Filter Manager.
    Information    12/21/2019 8:40:01 AM    Microsoft-Windows-Ntfs    98    None    Volume C: (\Device\HarddiskVolume3) is healthy.  No action is needed.
    Information    12/21/2019 8:40:01 AM    Microsoft-Windows-FilterManager    6    None    File System Filter 'mfehidk' (0.0, ‎2019‎-‎08‎-‎16T07:36:39.000000000Z) has successfully loaded and registered with Filter Manager.
    Information    12/21/2019 8:40:01 AM    Microsoft-Windows-FilterManager    6    None    File System Filter 'Wof' (10.0, ‎2096‎-‎10‎-‎27T07:24:16.000000000Z) has successfully loaded and registered with Filter Manager.
    Information    12/21/2019 8:40:01 AM    Microsoft-Windows-FilterManager    6    None    File System Filter 'FileInfo' (10.0, ‎1989‎-‎07‎-‎12T19:15:12.000000000Z) has successfully loaded and registered with Filter Manager.
    Information    12/21/2019 8:40:00 AM    Microsoft-Windows-Kernel-General    20    (6)    "The leap second configuration has been updated.
    Reason: Leap second data initialized from registry during boot
    Leap seconds enabled: true
    New leap second count: 0
    Old leap second count: 0"
    Information    12/21/2019 8:40:00 AM    Microsoft-Windows-Kernel-Boot    30    (21)    The firmware reported boot metrics.
    Information    12/21/2019 8:40:00 AM    Microsoft-Windows-Kernel-Boot    32    (58)    The bootmgr spent 0 ms waiting for user input.
    Information    12/21/2019 8:40:00 AM    Microsoft-Windows-Kernel-Boot    18    (57)    There are 0x1 boot options on this system.
    Information    12/21/2019 8:40:00 AM    Microsoft-Windows-Kernel-Boot    27    (33)    The boot type was 0x0.
    Information    12/21/2019 8:40:00 AM    Microsoft-Windows-Kernel-Boot    25    (32)    The boot menu policy was 0x1.
    Information    12/21/2019 8:40:00 AM    Microsoft-Windows-Kernel-Boot    20    (31)    The last shutdown's success status was false. The last boot's success status was true.
    Information    12/21/2019 8:40:00 AM    Microsoft-Windows-Kernel-Boot    153    (62)    Virtualization-based security (policies: 0) is disabled.
    Information    12/21/2019 8:40:00 AM    Microsoft-Windows-Kernel-General    12    (1)    The operating system started at system time ‎2019‎-‎12‎-‎21T14:39:59.500000000Z.
    Information    12/20/2019 9:13:18 PM    Service Control Manager    7040    None    The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.
    Information    12/20/2019 8:47:21 PM    Service Control Manager    7040    None    The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start.
    Information    12/20/2019 8:43:16 PM    Service Control Manager    7040    None    The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.
    Information    12/20/2019 8:40:57 PM    Microsoft-Windows-Kernel-General    1    (5)    "The system time has changed to ‎2019‎-‎12‎-‎21T02:40:57.251645000Z from ‎2019‎-‎12‎-‎21T02:40:57.251062700Z.
     
    Change Reason: An application or system component changed the time.
    Process: '\Device\HarddiskVolume3\Windows\System32\svchost.exe' (PID 18908)."
    Information    12/20/2019 8:40:57 PM    Microsoft-Windows-Time-Service    35    None    The time service is now synchronizing the system time with the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->40.119.6.228:123) with reference id 3825628968. Current local stratum number is 4.
    Information    12/20/2019 8:40:44 PM    Microsoft-Windows-Kernel-General    16    None    The access history in hive \??\C:\Users\edste\AppData\Local\Packages\microsoft.windows.secureassessmentbrowser_cw5n1h2txyewy\Settings\settings.dat was cleared updating 2 keys and creating 1 modified pages.
    Information    12/20/2019 8:40:44 PM    Microsoft-Windows-Kernel-General    16    None    The access history in hive \??\C:\Users\edste\AppData\Local\Packages\microsoft.windows.assignedaccesslockapp_cw5n1h2txyewy\Settings\settings.dat was cleared updating 2 keys and creating 1 modified pages.
    Information    12/20/2019 8:40:42 PM    Microsoft-Windows-Time-Service    37    None    The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->40.119.6.228:123).
    Information    12/20/2019 8:40:41 PM    Microsoft-Windows-Time-Service    158    None    The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well.
    Information    12/20/2019 8:17:22 PM    Service Control Manager    7040    None    The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start.
    Information    12/20/2019 8:13:18 PM    Service Control Manager    7040    None    The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.
    Information    12/20/2019 7:47:21 PM    Service Control Manager    7040    None    The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start.
    Information    12/20/2019 7:43:16 PM    Service Control Manager    7040    None    The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.
    Information    12/20/2019 7:17:22 PM    Service Control Manager    7040    None    The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start.
    Information    12/20/2019 7:13:18 PM    Service Control Manager    7040    None    The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.
    Information    12/20/2019 6:47:21 PM    Service Control Manager    7040    None    The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start.

    Saturday, December 21, 2019 3:57 PM
  • FWIW, I just got off a lengthy session with dell.  They ran a lot of diagnostics, found no hardware errors, but did update the BIOS.  We'll see . . .
    Saturday, December 21, 2019 5:56 PM
  • To evaluate the computer environment please post logs for troubleshooting.

    Using administrative command prompt copy and paste this whole command.

    Make sure the default language is English so that the logs can be scanned and read.

    https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html

    The command will automatically collect the computer files and place them on the desktop.

    Then use 7zip to organize the files and one drive, drop box, or google drive to place share links into the thread for troubleshooting.

    https://support.office.com/en-us/article/Share-OneDrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

    This command will automatically collect these files:  msinfo32, mini dumps, drivers, hosts, install, uninstall, services, startup, event viewer files, etc.

    Open administrative command prompt and copy and paste the whole command:

    copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

    There is one file for you to find manually: dxdiag:  

    In the left lower corner search type:  dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread
    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is: 

    Propose as answer = answered the question

    On the left side of each post:  Vote = a helpful post
    .
    .
    .
    .
    .
    Saturday, December 21, 2019 9:16 PM
  • I hope I understood and followed the instructions correctly.  The One Drive link is https://1drv.ms/u/s!AhqFQ1aMIMs9ggqx5OEDqy1Xn9Ck?e=G5Jj0A
    Saturday, December 21, 2019 9:57 PM

  • The findings in the logs were a significant number of event 6008 and 41.

    Unexpected shutdowns are seen when there are manual power offs, temperature problems, BSOD, malfunctioning hardware, etc.

    There is a faulting application related to 64bitproxy.exe that needs to be identified then uninstalled and reinstalled.

    The longer that you can leave it uninstalled the better the testing environment.

    Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
    Speccy - Free Download - Piriform: Speccy - System Information - Free 
    https://www.piriform.com/speccy
    https://www.ccleaner.com/speccy
    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
    http://www.cpuid.com/softwares/hwmonitor.html
    SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
    http://www.almico.com/speedfan.php

    Windows Error Reporting:
    +++ WER0 +++:
    Fault bucket 2176479382194672881, type 4
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: 64bitProxy.exe
    P2: 3.6.11682.2
    P3: 5aa98589
    P4: ntoskrnl.exe
    P5: 10.0.18362.535
    P6: 12dcb470
    P7: c0000005
    P8: 000000000036f047
    P9: 
    P10: 


    +++ WER1 +++:
    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: 64bitProxy.exe
    P2: 3.6.11682.2
    P3: 5aa98589
    P4: ntoskrnl.exe
    P5: 10.0.18362.535
    P6: 12dcb470
    P7: c0000005
    P8: 000000000036f047
    P9: 
    P10: 


    +++ WER2 +++:
    Fault bucket 2176479382194672881, type 4
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: 64bitProxy.exe
    P2: 3.6.11682.2
    P3: 5aa98589
    P4: ntoskrnl.exe
    P5: 10.0.18362.535
    P6: 12dcb470
    P7: c0000005
    P8: 000000000036f047
    P9: 
    P10: 


    +++ WER3 +++:
    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: 64bitProxy.exe
    P2: 3.6.11682.2
    P3: 5aa98589
    P4: ntoskrnl.exe
    P5: 10.0.18362.535
    P6: 12dcb470
    P7: c0000005
    P8: 000000000036f047
    P9: 
    P10: 

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is: 

    Propose as answer = answered the question

    On the left side of each post:  Vote = a helpful post
    .
    .
    .
    .
    .


    Saturday, December 21, 2019 10:56 PM
  • @questionsformicrosoftproducts - when I first saw this, I thought 'finally, we might be making some headway".  However, on closer inspection --

    Event 41 - The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly

    Event 6008 - The previous system shutdown at ... was unexpected

    These two are simply telling us that we are restarting after a system crash. We already knew that.  They say nothing about the cause of the crash/freeze.

    64bitproxy.exe is associated with ClearPass vpn service. While the failures are in themselves a bit worrisome, the times that they occur seem to have no correlation to the times of the system crashes.  However, I will, in the interest of testing, disable all of the ClearPass services for the time being, and see what happens.

    <style type="text/css">p { margin-bottom: 0.1in; line-height: 115%; background: transparent none repeat scroll 0% 0%; }</style>

    <style type="text/css">p { margin-bottom: 0.1in; line-height: 115%; background: transparent none repeat scroll 0% 0%; }</style>

    Sunday, December 22, 2019 7:49 PM
  • For events 41 and 6008

    a) Monitor temps

    b) For startup and recovery system failure make sure automatically restart is unchecked so that you do not miss BSOD (if they occur)

    c) These are recorded for any power off after hangs / freezes so record the dates and times

    d) Reduce the confounding factors (uninstall any application that is a common faulting application as seen in Windows error reporting) 

    etc.

    Sunday, December 22, 2019 9:56 PM
  • a) monitor temps - ok, I've installed Speccy and see it giving real-time temp reporting,b ut do not see a way to capture/log it for analysis after a crash.

    b) how do I disable auto restart for this purpose?  Googling the subject presented a variety of widely differing methods.

    c) Have created a spreadsheet to record/sort/analyze key events - 41 and 6008 events from the event log, as well as any manual forced restarts.

    d) Have disabled 3 services associated with ClearPass (64bitproxy.exe was found only in the ClearPass installation folder).

    Sunday, December 22, 2019 11:01 PM
  • Hello,

    Post the information on the Details Tab of the Event log for the Kernel Power Event 41.

    See this link for documentation  on the information in the details tab

    https://support.microsoft.com/en-us/help/2028504/windows-kernel-event-id-41-error-the-system-has-rebooted-without-clean


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Sunday, December 22, 2019 11:54 PM
  • Just had another one, as I went to gather the reqested event 41 detail.  Here it is:

    - System

      - Provider

       [ Name]  Microsoft-Windows-Kernel-Power
       [ Guid]  {331c3b3a-2005-44c2-ac5e-77220c37d6b4}
     
       EventID 41
     
       Version 6
     
       Level 1
     
       Task 63
     
       Opcode 0
     
       Keywords 0x8000400000000002
     
      - TimeCreated

       [ SystemTime]  2019-12-23T02:43:19.541566200Z
     
       EventRecordID 11956
     
       Correlation
     
      - Execution

       [ ProcessID]  4
       [ ThreadID]  8
     
       Channel System
     
       Computer STEVENS-NB5
     
      - Security


       [ UserID]  S-1-5-18
     

    - EventData

      BugcheckCode 0
      BugcheckParameter1 0x0
      BugcheckParameter2 0x0
      BugcheckParameter3 0x0
      BugcheckParameter4 0x0
      SleepInProgress 0
      PowerButtonTimestamp 0
      BootAppStatus 0
      Checkpoint 0
      ConnectedStandbyInProgress false
      SystemSleepTransitionsToOn 0
      CsEntryScenarioInstanceId 0
      BugcheckInfoFromEFI false
      CheckpointStatus 0

    Monday, December 23, 2019 2:49 AM
  • 1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan
    7) wmic recoveros set autoreboot = false
    8) wmic recoveros set DebugInfoType = 7
    9) bcdedit /enum {badmemory}

    10) 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

    11) Make sure that there is no over clocking while troubleshooting 

    12) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings 

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

    13) Run Memtest86 version 8.3 (or newer version if available) for four passes.
    Repeat the test so that eight passes are performed.

    https://www.memtest86.com/

    Use a camera or smart phone camera to take pictures and post images into the thread.
    In case there are any problems uploading images use share links (one drive, drop box, or google drive)

    Memtest86 has a feature to produce a text report.  
    Please post this in addition to the images.



    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is: 

    Propose as answer = answered the question

    On the left side of each post:  Vote = a helpful post
    .
    .
    .
    .
    .


    Monday, December 23, 2019 3:33 AM
  • 1) through 10), cmd line diagnostics:

    C:\Windows\system32>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:\Windows\system32>dism /online /cleanup-image /scanhealth

    Deployment Image Servicing and Management tool

    Version: 10.0.18362.1

    Image Version: 10.0.18362.535

    [==========================100.0%==========================] No component store corruption detected.

    The operation completed successfully.

    C:\Windows\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool

    Version: 10.0.18362.1

    Image Version: 10.0.18362.535

    [==========================100.0%==========================] The restore operation completed successfully.

    The operation completed successfully.

    C:\Windows\system32>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:\Windows\system32>chkdsk /scan

    The type of the file system is NTFS.

    Volume label is OS.

    Stage 1: Examining basic file system structure ...

    331776 file records processed.

    File verification completed.

    8307 large file records processed.

    0 bad file records processed.

    Stage 2: Examining file name linkage ...

    194 reparse records processed.

    446338 index entries processed.

    Index verification completed.

    0 unindexed files scanned.

    0 unindexed files recovered to lost and found.

    194 reparse records processed.

    Stage 3: Examining security descriptors ...

    Security descriptor verification completed.

    57282 data files processed.

    CHKDSK is verifying Usn Journal...

    40529792 USN bytes processed.

    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.

    No further action is required.

    248229887 KB total disk space.

    41775400 KB in 216411 files.

    151912 KB in 57283 indexes.

    0 KB in bad sectors.

    449675 KB in use by the system.

    65536 KB occupied by the log file.

    205852900 KB available on disk.

    4096 bytes in each allocation unit.

    62057471 total allocation units on disk.

    51463225 allocation units available on disk.

    C:\Windows\system32>wmic recoveros set autoreboot = false

    Updating property(s) of '\\STEVENS-NB5\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition3"'

    Property(s) update successful.

    C:\Windows\system32>wmic recoveros set DebugInfoType = 7

    Updating property(s) of '\\STEVENS-NB5\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition3"'

    Property(s) update successful.

    C:\Windows\system32>bcdedit /enum {badmemory}

    RAM Defects

    -----------

    identifier {badmemory}

    isolatedcontext Yes

    C:\Windows\system32>

    11) overclocking – how to check?


    12a) startup and recovery:

    12b> virtual memory

    See link at https://support.office.com/en-us/article/Share-OneDrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07


    13) memory test. Already been thorugh that with Dell. Memory past a very deep test.
    Monday, December 23, 2019 8:11 PM
  • 1) The link opened:

    https://support.office.com/en-us/article/Share-OneDrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

    2) Check links before posting them

    3) False negatives ( test pass with malfunctioning RAM is common with memory testing)

    Eight or more passes are needed.

    Testing can be performed overnight.

    See step #13 in the prior post:  Run two tests of 4 passes each using Memtest86 version 8.3

    4) Post a share link for this folder:  C:\Windows\LiveKernelReports

    5) Post images or share links for startup and recovery and virtual memory windows


    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is: 

    Propose as answer = answered the question

    On the left side of each post:  Vote = a helpful post
    .
    .
    .
    .
    .

    Monday, December 23, 2019 9:46 PM
  • Sorry 'bout that! :-)  This link should get all requested diagnostics:

    https://1drv.ms/u/s!AhqFQ1aMIMs9ghmWQAhsNbGQ5aOq?e=kiasaM

    From that you should be able to see that I made two runs of the memory test, and there were no failures.  I've also been tracking cpu temps, but since the utility has no logging capability, it is just random observations.  But With that, temps have been in the 30 to 37 deg. F range, with one observation at 47 deg.

    One other observation that may be meaningful.  Thinking that perhaps when the system crashed there should be a BSOD, but with the screen set to turn off after some time, it (the BSOD) was not being seen. So I changed that setting to 'never turn off the screen if on AC power'.  It has been that way for several days now, in that configuration there has never been a crash.

    Sunday, December 29, 2019 8:52 PM