new thread for surface pro X shutdown randomly issue

galvin 1 Reputation point
2021-06-11T20:14:44.09+00:00

Let me re-phase my observation again.
https://learn.microsoft.com/en-us/answers/questions/431350/surface-pro-x-shutdown-randomly-after-disable-hibe.html#answer-431370

Initially, the surface pro X tablet will hibernate after turning on for a few seconds, I was wondering if a sensor exists to turn off the device automatically. a previous reply below from Chamblis mentioned something about this sensor.
https://answers.microsoft.com/en-us/surface/forum/all/why-does-surface-randomly-go-onto-sleep-mode-while/2ff79410-e362-485b-8cc0-31dd2505133d

From this youtube link below, you can know what I was experiencing at that moment.

https://youtu.be/ywj7MSe4gBc

By referring to another thread below, I am able to stop the tablet from hibernate immediately (powercfg -h off), but it still randomly shutdown.
https://answers.microsoft.com/en-us/surface/forum/surfacepro-surfver_surfpro5-surftop_battery/surface-pro-latest-edition-turning-off-randomly/12e99f9b-f486-45d2-a121-f8b5eff832be

I use "powercfg /sleepstudy" command to record down what I see.

  1. The shutdown is related with "Battery Count Changed" and "Kernel API", "AC/DC display burst" as the log file shows from sleepstudy.

104885-image.png

104778-image.png

  1. status of Power source change/Battery count change is continuously swapped though the AC power is always on

104922-image.png

  1. Abnormal shutdown is reported after Battery County change.

104850-image.png

104886-image.png

  1. Windows 10 Pro battery panel will sometimes show me that no battery is detected
    104898-image.png

After a few seconds, the battery status will be normal.

104923-image.png

Still, I don't know why this device continuously shutdown by itself in a random base, if someone can help to have a look, it will be really appreciated.

I have the V2 log collector results presented here
https://1drv.ms/u/s!ArbVpeDKYDFtgoV7mb5EEZ13cfjKAQ?e=xBGk2Z

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
38,659 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Anonymous
    2021-06-11T20:35:01.207+00:00

    Surface is not currently supported here on QnA. The product group for Surface hardware actively monitors questions over at
    https://answers.microsoft.com/en-us/surface/forum
    https://techcommunity.microsoft.com/t5/surface-devices/ct-p/SurfaceDevices

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  2. Docs 15,511 Reputation points
    2021-06-11T21:38:34.577+00:00

    Dxdiag displayed:


    System Information

      Time of this report: 6/11/2021, 13:12:03
             Machine name: TABLET-OMUT5T0S
               Machine Id: Unknown
         Operating System: Windows 10 Pro 32-bit (10.0, Build 19042) (19041.vb_release.191206-1406)
                 Language: English (Regional Setting: English)
      System Manufacturer: Microsoft Corporation
             System Model: Surface Pro X
                     BIOS: 7.563.140 (type: UEFI)
                Processor: Microsoft SQ2 @ 3.15 GHz (8 CPUs), ~3.1GHz
                   Memory: 16384MB RAM
      Available OS Memory: 15842MB RAM
                Page File: 10662MB used, 7611MB available
              Windows Dir: C:\WINDOWS
          DirectX Version: DirectX 12
      DX Setup Parameters: Not found
         User DPI Setting: 192 DPI (200 percent)
       System DPI Setting: 192 DPI (200 percent)
          DWM DPI Scaling: UnKnown
                 Miracast: Available, with HDCP
    

    Microsoft Graphics Hybrid: Not Supported
    DirectX Database Version: Unknown
    DxDiag Version: 10.00.19041.0928 32bit Unicode

    Please check whether 64x or 32x:

    https://www.tenforums.com/tutorials/4399-see-if-system-type-32-bit-x86-64-bit-x64-windows-10-a.html

    1) Open administrative command prompt (ACP) 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) wmic recoveros get autoreboot
    10) wmic recoveros get DebugInfoType
    11) wmic Computersystem where name="%computername%" set AutomaticManagedPagefile=True
    12) wmic Computersystem where name="%computername%" get AutomaticManagedPagefile
    11) bcdedit /enum {badmemory}
    12) wmic os get OSArchitecture

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

    The logs displayed many:

    Event[1183]:
    Log Name: System
    Source: disk
    Date: 2021-06-02T01:48:01.1120000Z
    Event ID: 11
    Task: N/A
    Level: Error
    Opcode: N/A
    Keyword: Classic
    User: N/A
    User Name: N/A
    Computer: TABLET-OMUT5T0S
    Description:
    The driver detected a controller error on \Device\Harddisk2\DR2.

    Event[1434]:
    Log Name: System
    Source: disk
    Date: 2021-06-02T09:34:07.4270000Z
    Event ID: 11
    Task: N/A
    Level: Error
    Opcode: N/A
    Keyword: Classic
    User: N/A
    User Name: N/A
    Computer: TABLET-OMUT5T0S
    Description:
    The driver detected a controller error on \Device\Harddisk3\DR3

    Event[2743]:
    Log Name: System
    Source: disk
    Date: 2021-06-03T22:14:15.9870000Z
    Event ID: 11
    Task: N/A
    Level: Error
    Opcode: N/A
    Keyword: Classic
    User: N/A
    User Name: N/A
    Computer: TABLET-OMUT5T0S
    Description:
    The driver detected a controller error on \Device\Harddisk2\DR5.

    Event[3017]:
    Log Name: System
    Source: disk
    Date: 2021-06-03T22:39:33.8510000Z
    Event ID: 11
    Task: N/A
    Level: Error
    Opcode: N/A
    Keyword: Classic
    User: N/A
    User Name: N/A
    Computer: TABLET-OMUT5T0S
    Description:
    The driver detected a controller error on \Device\Harddisk1\DR4.

    Event[3227]:
    Log Name: System
    Source: disk
    Date: 2021-06-04T00:11:18.9090000Z
    Event ID: 11
    Task: N/A
    Level: Error
    Opcode: N/A
    Keyword: Classic
    User: N/A
    User Name: N/A
    Computer: TABLET-OMUT5T0S
    Description:
    The driver detected a controller error on \Device\Harddisk1\DR1.

    Event[13281]:
    Log Name: System
    Source: Microsoft-Windows-USB-USBHUB3
    Date: 2021-06-11T10:12:45.3820000Z
    Event ID: 196
    Task: Surprise Removal
    Level: Warning
    Opcode: Warning
    Keyword: N/A
    User: S-1-5-18
    User Name: NT AUTHORITY\SYSTEM
    Computer: TABLET-OMUT5T0S
    Description:
    USB device draining system power when system is idle.

    USB Device: VID: 0x5E3 PID: 0x749 REV: 0x1535
    Removal action failed: SkippedAsRecentIoObservered

    Event[13282]:
    Log Name: System
    Source: Microsoft-Windows-USB-USBHUB3
    Date: 2021-06-11T10:13:20.3820000Z
    Event ID: 196
    Task: Surprise Removal
    Level: Warning
    Opcode: Warning
    Keyword: N/A
    User: S-1-5-18
    User Name: NT AUTHORITY\SYSTEM
    Computer: TABLET-OMUT5T0S
    Description:
    USB device draining system power when system is idle.

    USB Device: VID: 0x5E3 PID: 0x749 REV: 0x1535
    Removal action failed: SkippedAsPersistentIoObserved

    An end user should not have to troubleshoot:
    controller errors
    unexpected shutdows and restarts
    etc.

    on a new computer.

    Please contact the manufacturer / vendor for a Return Merchandise Authorization (RMA).

    .
    .
    .
    .
    .

    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
    .
    .
    .
    .
    .

    0 comments No comments

  3. galvin 1 Reputation point
    2021-06-11T22:24:19.717+00:00

    Thanks, this is very useful information.

    104780-image.png
    104868-image.png

    Microsoft Windows [Version 10.0.19042.1052]
    (c) Microsoft Corporation. All rights reserved.

    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.19041.746

    Image Version: 10.0.19042.1052

    [==========================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.19041.746

    Image Version: 10.0.19042.1052

    [==========================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 Local Disk.

    Stage 1: Examining basic file system structure ...
    461056 file records processed.
    File verification completed.
    Phase duration (File record verification): 7.39 seconds.
    29085 large file records processed.
    Phase duration (Orphan file record recovery): 0.00 milliseconds.
    0 bad file records processed.
    Phase duration (Bad file record checking): 1.19 milliseconds.

    Stage 2: Examining file name linkage ...
    12837 reparse records processed.
    670504 index entries processed.
    Index verification completed.
    Phase duration (Index verification): 11.55 seconds.
    0 unindexed files scanned.
    Phase duration (Orphan reconnection): 4.17 seconds.
    0 unindexed files recovered to lost and found.
    Phase duration (Orphan recovery to lost and found): 1.41 milliseconds.
    12837 reparse records processed.
    Phase duration (Reparse point and Object ID verification): 41.34 milliseconds.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    Phase duration (Security descriptor verification): 51.69 milliseconds.
    104725 data files processed.
    Phase duration (Data attribute verification): 1.28 milliseconds.
    CHKDSK is verifying Usn Journal...
    35789072 USN bytes processed.
    Usn Journal verification completed.
    Phase duration (USN journal verification): 308.58 milliseconds.

    Windows has scanned the file system and found no problems.
    No further action is required.

    249324543 KB total disk space.
    46745508 KB in 300865 files.
    173740 KB in 104726 indexes.
    0 KB in bad sectors.
    593847 KB in use by the system.
    65536 KB occupied by the log file.
    201811448 KB available on disk.

      4096 bytes in each allocation unit.  
    

    62331135 total allocation units on disk.
    50452862 allocation units available on disk.
    Total duration: 23.55 seconds (23559 ms).

    C:\WINDOWS\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\TABLET-OMUT5T0S\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 '\TABLET-OMUT5T0S\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\WINDOWS|\Device\Harddisk0\Partition3"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE

    C:\WINDOWS\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7

    C:\WINDOWS\system32>wmic Computersystem where name="%computername%" set AutomaticManagedPagefile=True
    Updating property(s) of '\TABLET-OMUT5T0S\ROOT\CIMV2:Win32_ComputerSystem.Name="TABLET-OMUT5T0S"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic Computersystem where name="%computername%" get AutomaticManagedPagefile
    AutomaticManagedPagefile
    TRUE

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

    RAM Defects

    -----------

    identifier {badmemory}
    isolatedcontext Yes

    C:\WINDOWS\system32>wmic os get OSArchitecture
    OSArchitecture
    ARM 64-bit Processor

    C:\WINDOWS\system32>

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.