Mystery shut downs on 1903--help me diagnose!


  1. Posts : 35
    Windows 10 Pro for Workstations
       #1

    Mystery shut downs on 1903--help me diagnose!


    Summary:

    My laptop sometimes mysteriously shuts down, and I have no idea why.

    I need advice on trouble shooting this, especially seeing if my Windows event logs hold any clues.

    Details:

    I have a 7 month old Dell Precision 7530 laptop. It is running Windows 10 Pro for Workstations version 1903 patched thru the latest updates. If Dell Command update is to be believed, all my hardware related software (e.g. BIOS, drivers) is also fully patched.

    Several times in the last couple of weeks I have come back to my laptop after being away for several hours only to find it shut down. And I mean, totally shut down, not in sleep or hibernation: after pressing on the power button it boots up and no programs are there, like it was a clean start.

    The last 2 times this happened were sometime early Sunday morning (1 day ago, between ~02:30 and ~10:37) and sometime later on again on Sunday (perhaps ~10:50); more on those times below.

    In the first case, I started a backup process around 02:30 before going to bed. When I came to my laptop at ~10:30, it was shut down. Had to press the power key to get it running once more. Minutes after it booted, I needed to leave the house.

    When I was next able to return to my laptop in the afternoon, around ~14:40, it was again shut down just like in the morning.I started examining my Windows event logs for clues.

    This link led to this link which had some suggestions. One way is to use Event Viewer; good tutorial for this is here. Another way is to execute the program TurnedOnTimesView. However, to get text output for this post, yet another way is to execute this in Powershell:
    Code:
    Get-WinEvent -FilterHashtable @{Logname='System';ID=6006,6008,1074}
    The relevant part of the output for the 2 mystery shut downs on Sunday are these lines:
    Code:
           ProviderName: EventLog
    
        TimeCreated                     Id LevelDisplayName Message
        -----------                     -- ---------------- -------
        2019-06-23 14:42:05           6008 Error            The previous system shutdown at 10:36:59 AM on ?6/?23/?2019 was unexpected. 
        2019-06-23 10:36:59           6008 Error            The previous system shutdown at 6:42:46 AM on ?6/?23/?2019 was unexpected.
        2019-06-23 01:20:37           6006 Information      The Event log service was stopped.
    Those 2 6008 Error lines are surely the 2 mystery shut downs, but other than give me the time, they are not telling me anything! I have no idea what process caused this!

    Because I use BitLocker to fully software encrypt my SSD, I have disabled all Sleep, and only allow Hibernate; see this link.

    This may be unrelated, but I should mention that this evening my Start Menu and search bar stopped working! Clicking on them did nothing I have never experienced this before. Found a web link that suggested ctrl-alt-delete and then sign out. That cured it, altho it forcefully killed some processes that I would have preferred to manually gracefully terminate.

    I do not see either shut downs or loss of Start Menu in Brink's list of open 1903 issues.

    My symptoms are distinct from the shut down issues reported in this post.

    This post suggested to execute in an elevated cmd shell
    Code:
    powercfg /SYSTEMPOWERREPORT
    I examined the report, but it did not tell me anything new.

    - - - Updated - - -

    As a followup to my original post, I opened Event Viewer -> Windows Logs --> System and started looking for suspects. Below are some of the things that I found. Nothing stands out as a cause to me, but maybe it will to someone more experienced.

    Critical logs:

    I see one Event ID 41 at 10:36:49 with the message
    Code:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Error logs:

    I see bursts of Event ID 2505; i think that all have the message
    Code:
    The server could not bind to the transport \Device\NetBT_Tcpip_{5F182740-E841-4CF8-A439-D3F5954BA1C2} because another computer on the network has the same name.  The server could not start.
    I see a few Event ID 4207; I think that all have the message
    Code:
    The IPv6 TCP/IP interface with index 17 failed to bind to its provider.
    I see a few Event ID 5010; I think that all have the message
    Code:
    Intel(R) Wireless-AC 9260 160MHz : The network adapter has returned an invalid value to the driver.
    I see one Event ID 7000 with the message
    Code:
    The DellWAL service failed to start due to the following error: The system cannot find the file specified.
    There may be more; I am doing this manually...

    Warning logs:

    I see a few Event ID 219; they have different messages, for example
    Code:
    The driver \Driver\WudfRd failed to load for the device ACPI\INT3400\2&daba3ff&0.
    or
    Code:
    The driver \Driver\WudfRd failed to load for the device USB\VID_0A5C&PID_5832&MI_01\6&528937a&0&0001.

    I see a few Event ID 10016; they have different messages, for example
    Code:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
    {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
     and APPID
    {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
     to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
    or
    Code:
    The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
    Windows.SecurityCenter.SecurityAppBroker
     and APPID
    Unavailable
     to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
      My Computer


  2. Posts : 42,989
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2

    Hi, does it shut down if you leave it in Safe Mode for 'long enough'?

    If it doesn't shut down in Safe Mode, what happens if you do a clean boot?

    Does the onset of these shutdowns correlate with any update or change you've made?

    Your specs say Desktop, Win 7 Pro - could you please complete your specs? 2 systems are allowed- see mine for comparison.

    Have you added any RAM recently? Have you run a memory check?

    If you get the chance try
    Enable and Disable Driver Verifier in Windows 10
    @zbook will probably recommend you run the tool used in the BSOD section of the forum to capture data about your system. Please have a look there, run the tool there and upload the zip file. Thanks.
    Last edited by dalchina; 25 Jun 2019 at 06:47.
      My Computers


  3. Posts : 41,474
    windows 10 professional version 1607 build 14393.969 64 bit
       #3

    1) There are log collectors used in another forum.
    Please run both V2 and DM log collectors and upload results into this thread:
    BSOD - Posting Instructions

    2) update the specs in the my computer section:

    System Specs - Fill in at Ten Forums
    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.)


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

    4) If the computer has Ccleaner (do not install the software if it is not already installed) > click windows tab > scroll down to system and advanced > post an image into the thread

    5) Open administrative command prompt and type or copy and paste:
    6) sfc /scannow
    7) dism /online /cleanup-image /restorehealth
    8) chkdsk /scan
    9) wmic recoveros set autoreboot = false
    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) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
    Speccy - Free Download - Piriform: Speccy - System Information - Free
    Download Speccy | Find your computer specs, free!
    Download Speccy | Find your computer specs, free!
    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
    HWMONITOR | Softwares | CPUID
    SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
    SpeedFan - Access temperature sensor in your computer
      My Computer


  4. Posts : 18
    Windows 10 Pro 64-bit
       #4

    Qucikest method is to re-install...
      My Computer


  5. Posts : 42,989
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #5

    Need to discriminate between possible hardware problems, and the software configuration.

    If it shuts down in Safe Mode, then my bet would be a hardware problem. Likewise if it shut down when booted from a live boot disk, such as Kyhi's, which supports utilities some of which could be useful here.
      My Computers


  6. Posts : 35
    Windows 10 Pro for Workstations
    Thread Starter
       #6

    dalchina said:
    Hi, does it shut down if you leave it in Safe Mode for 'long enough'?

    If it doesn't shut down in Safe Mode, what happens if you do a clean boot?
    Good idea. I should try restarting my computer each day before I go to work and leave it running and see if it has shut down when I get home.

    If that does not trigger a shutdown within a few days, I should try the same but restart into a Clean Boot.


    dalchina said:
    Does the onset of these shutdowns correlate with any update or change you've made?
    I do not think so. Before the last 2 unexpected shut downs last Sunday, I did run Dell Command Update and it installed 2 things. But, I had seen a few unexpected shutdowns before that, and I have had no unexpected shut downs since Sunday; my computer has not changed much since Sunday.

    Erratic issues like this are the worst to debug.


    dalchina said:
    Your specs say Desktop, Win 7 Pro - could you please complete your specs? 2 systems are allowed- see mine for comparison.
    You are right that I should update my profile. But my original post was very specific: "I have a 7 month old Dell Precision 7530 laptop. It is running Windows 10 Pro for Workstations version 1903".


    dalchina said:
    Have you added any RAM recently? Have you run a memory check?
    I added 32 GB of ECC DRAM soon after I got it ~7 months ago, and have not touched the DRAM since. I may add another 32 GB in the future, should I need it.

    Any particular memory check that you advocate? I have used memtest86 in the past.


    dalchina said:
    I am going to try that next, stay tuned!

    dalchina said:
    I @zbook will probably recommend you run the tool used in the BSOD section of the forum to capture data about your system. Please have a look there, run the tool there and upload the zip file. Thanks.
    zbook: your response is amazing. I do not have time to work thru it tonight, but hopefully can start on it tomorrow. Many thanks.

    - - - Updated - - -

    dalchina said:
    I let my computer run for ~24 hours (last night till now) with Driver Verifier running the whole time.

    No issues: my computer never shutdown unexpectedly.
    Last edited by up2trix; 26 Jun 2019 at 22:37.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:40.
Find Us




Windows 10 Forums