Computer restart although a click on shutdown

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 4,187
    Windows 11 Pro, 22H2
       #11

    One more idea. Let's see if you have Fast Startup enabled. If so, let's disable it as a test to see if it is involved here.

    select Start > Settings > System > Power & sleep > Additional power settings > Choose what the power buttons do > Change settings that are currently unavailable

    If "Turn on fast startup" is enabled, disable it.

    Let's see if that makes any difference.
      My Computers


  2. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #12

    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /restorehealth
    4) chkdsk /scan
    5) wmic recoveros set autoreboot = false
    6) 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

    7) Run V2 and DM log collectors > upload results into this thread
    BSOD - Posting Instructions
      My Computer


  3. Posts : 23
    Windows 10
    Thread Starter
       #13

    hsehestedt said:
    One more idea. Let's see if you have Fast Startup enabled. If so, let's disable it as a test to see if it is involved here.

    select Start > Settings > System > Power & sleep > Additional power settings > Choose what the power buttons do > Change settings that are currently unavailable

    If "Turn on fast startup" is enabled, disable it.

    Let's see if that makes any difference.
    After disabling the "Turn on fast startup" I could not start Windows. After trying a couple of times it worked. Never-the-less I enable again this option.

    - - - Updated - - -

    zbook said:
    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /restorehealth
    4) chkdsk /scan
    5) wmic recoveros set autoreboot = false
    6) 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

    7) Run V2 and DM log collectors > upload results into this thread
    BSOD - Posting Instructions

    I follow the steps 1 to 7. Please find attached the outputs (unfortunately they are in German as I have bough a German Windows 10 OS)

    DESKTOP-T8OPRMK-(2019-06-23_15-07-11).zip
    DESKTOP-T8OPRMK-23_06_2019_151113,59.zip
    Step1to5output.zip
      My Computer


  4. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #14

    The logs were in a foreign language.
    Please change the default language to English so that the logs can be scanned and read:
    https://www.tenforums.com/tutorials/...dows-10-a.html
      My Computer


  5. Posts : 23
    Windows 10
    Thread Starter
       #15

    zbook said:
    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /restorehealth
    4) chkdsk /scan
    5) wmic recoveros set autoreboot = false
    6) 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

    7) Run V2 and DM log collectors > upload results into this thread
    BSOD - Posting Instructions
    I follow the steps 1 to 7. Please find attached the outputs

    DMlogCollector-14_07_2019_194811_74.zip
    V2Collector-(2019-07-14_19-45-59).zip
    Step1to5.zip
    Last edited by puertas12; 14 Jul 2019 at 12:57. Reason: Correct format
      My Computer


  6. Posts : 6,306
    Windows 11 Pro - Windows 7 HP - Lubuntu
       #16

    Fast startup is a hybrid hibernation and fresh start. I think it's more part of a problem than a solution. I would turn it off.

    Try this.
    Right click on the desktop and select NEW - Shortcut
    On the Location Copy the following cmd to it
    C:\Windows\System32\shutdown.exe /p
    Next - rename as Shutdown

    This command instructs to shut down (no delay)
      My Computers


  7. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #17

    The logs started on 5/30/2019.

    There were multiple problems seen in the logs including:
    a) use of Windows 1709 (failure to upgrade to 1803, 1809 , or 1903)
    b) use of 32 bit architecture with 24 GB RAM
    c) failure of Windows fast startup
    d) BSOD
    e) insufficient free drive space on the Windows drive:
    Code:
    Free Space: 7.0 GB
    f) insufficient drive size to upgrade to Windows 1903: 30 GB

    Code:
          Drive: C:
     Free Space: 7.0 GB
    Total Space: 30.5 GB
    File System: NTFS
          Model: TOSHIBA-TR200

    g) possible drive file system corruption


    Consider the following steps:

    1) Determine whether the CPU can or cannot support 64x architecture
    2) The computer has 24 GB RAM and can only use 4 GB RAM with its 32x architecture
    3) Windows 1903 requires a larger capacity drive size than earlier Windows builds
    4) Replace drive 0 with a larger size drive: consider drive size > 100 GB so that
    a) the page file is on the Windows drive
    b) there is 15 - 20% free space
    c) there is sufficient reserved storage for future Windows upgrades
    5) Replacing the windows drive with a windows clean install (replace drivers and applications) may fix the BSOD
    Last edited by zbook; 14 Jul 2019 at 17:25. Reason: spelling
      My Computer


  8. Posts : 6,306
    Windows 11 Pro - Windows 7 HP - Lubuntu
       #18

    Puertas12, please edit your profile with ALL your hardware specs. It will help us to help you.
    System Specs - Fill in at Ten Forums
    I seems that you have the wrong Windows (32Bits) installed, don't have enough disk space etc.

    To guide you, we need to know your hardware.
    Last edited by Megahertz; 14 Jul 2019 at 18:42.
      My Computers


  9. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #19

    The drive size using dxdiag was 30 GB and appears to be partition size instead of physical size.
    The drive size may be 250 GB and the partition allocated for Windows is only 30 GB.

    If this is the case then partition resizing may be another option.

    If you had upgraded from windows 7 or 8 to 10 then the license information should be on a Microsoft server.
    To change 32x to 64x plan a clean install.


    Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
    Disk Management - How to Post a Screenshot of



    These were some of the problems seen in the logs:

    Code:
    The logs started on 5/30/2019
    
    The operating system is:   
    Code:
    Version        : 10.0.16299
    The operating system architecture is:
    Code:
    32-bit
    The computer has: 24 GB MB RAM The operating system is on: C:
    Code:
          Drive: C:
     Free Space: 7.0 GB
    Total Space: 30.5 GB
    File System: NTFS
          Model: TOSHIBA-TR200
    First recorded BSOD 5/31. Latest recorded BSOD 7/4.
    Code:
    Event[6186]:
      Log Name: System
      Source: volmgr
      Date: 2019-07-04T10:40:34.696
      Event ID: 46
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-T8OPRMK
      Description: 
    Crash dump initialization failed!
    Code:
    Event[3755]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Boot
      Date: 2019-06-16T22:07:02.674
      Event ID: 29
      Task: N/A
      Level: Error
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      Description: 
    Windows failed fast startup with error status 0xC00000D4.
    Code:
    Display Tab 1: Your PC is using the Microsoft Basic Display Adapter. For the best experience, get the latest drivers from Windows Update or from your hardware manufacturer's website. For more information search for 'Microsoft Basic Display Adapter'
    Code:
    Name	Microsoft Basic Display Adapter
    PNP Device ID	PCI\VEN_8086&DEV_5912&SUBSYS_872F1043&REV_04\3&11583659&0&10
    Adapter Type	Intel(R) SKL/KBL Mobile/Desktop, (Standard display types) compatible
    Adapter Description	Microsoft Basic Display Adapter
    Adapter RAM	0 bytes
    Installed Drivers	Not Available
    Driver Version	10.0.16299.15
    INF File	display.inf (MSBDA section)
    Colour Planes	Not Available
    Colour Table Entries	4294967296
    Resolution	1920 x 1080 x 1 hertz
    Bits/Pixel	32
    Memory Address	0xDE000000-0xDEFFFFFF
    Memory Address	0xB0000000-0xBFFFFFFF
    I/O Port	0x0000F000-0x0000F03F
    I/O Port	0x000003B0-0x000003BB
    I/O Port	0x000003C0-0x000003DF
    Memory Address	0xA0000-0xBFFFF
    Driver	c:\windows\system32\drivers\basicdisplay.sys (10.0.16299.15, 45.50 KB (46,592 bytes), 29/09/2017 13:49)
    	
    Name	AMD Radeon R7 200 Series
    PNP Device ID	PCI\VEN_1002&DEV_6819&SUBSYS_3000148C&REV_00\4&35D4F288&0&0008
    Adapter Type	AMD Radeon Graphics Processor (0x6819), Advanced Micro Devices, Inc. compatible
    Adapter Description	AMD Radeon R7 200 Series
    Adapter RAM	(2,147,483,648) bytes
    Installed Drivers	C:\Windows\System32\DriverStore\FileRepository\ct313676.inf_x86_4caaee15f1d03005\aticfx32.dll,C:\Windows\System32\DriverStore\FileRepository\ct313676.inf_x86_4caaee15f1d03005\aticfx32.dll,C:\Windows\System32\DriverStore\FileRepository\ct313676.inf_x86_4caaee15f1d03005\aticfx32.dll,C:\Windows\System32\DriverStore\FileRepository\ct313676.inf_x86_4caaee15f1d03005\amdxc32.dll
    Driver Version	22.19.162.4
    INF File	oem18.inf (ati2mtag_R575BDS section)
    Colour Planes	Not Available
    Colour Table Entries	Not Available
    Resolution	Not Available
    Bits/Pixel	Not Available
    Memory Address	0xC0000000-0xCFFFFFFF
    Memory Address	0xDF2C0000-0xDF2FFFFF
    I/O Port	0x0000EF00-0x0000EFFF
    IRQ Channel	IRQ 4294967281
    Driver	c:\windows\system32\driverstore\filerepository\ct313676.inf_x86_4caaee15f1d03005\atikmpag.sys (22.19.162.4, 405.38 KB (415,104 bytes), 16/05/2017 17:58)
    Code:
    ------------------------
    Disk & DVD/CD-ROM Drives
    ------------------------
          Drive: C:
     Free Space: 7.0 GB
    Total Space: 30.5 GB
    File System: NTFS
          Model: TOSHIBA-TR200
    
          Drive: D:
     Free Space: 320.7 GB
    Total Space: 715.4 GB
    File System: NTFS
          Model: SAMSUNG HD753LJ
    
          Drive: E:
     Free Space: 106.8 GB
    Total Space: 114.5 GB
    File System: NTFS
          Model: KINGSTON SA400S37120G
    
          Drive: F:
     Free Space: 7624.4 GB
    Total Space: 7630.9 GB
    File System: NTFS
          Model: ST8000DM004-2CX188
    
          Drive: H:
     Free Space: 0.2 GB
    Total Space: 0.5 GB
    File System: NTFS
          Model: TOSHIBA-TR200
    
          Drive: I:
     Free Space: 1727.9 GB
    Total Space: 4769.2 GB
    File System: NTFS
          Model: Seagate Expansion Desk SCSI Disk Device
    
          Drive: G:
          Model: HL-DT-ST DVD-RAM GH22NS30
         Driver: c:\windows\system32\drivers\cdrom.sys, 10.00.16299.0579 (English), 7/18/2018 04:11:27, 116736 bytes
    Code:
    Event[3469]:
      Log Name: System
      Source: Microsoft-Windows-Ntfs
      Date: 2019-06-14T20:37:31.523
      Event ID: 140
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      Description: 
    The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume15.
    (A device which does not exist was specified.)
    Code:
    Event[7076]:
      Log Name: System
      Source: User32
      Date: 2019-07-14T16:43:09.857
      Event ID: 1073
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: S-1-5-21-1826033184-2796454349-1185601217-1001
      User Name: DESKTOP-T8OPRMK\vicpu
      Computer: DESKTOP-T8OPRMK
      Description: 
    The attempt by user DESKTOP-T8OPRMK\vicpu to restart/shutdown computer DESKTOP-T8OPRMK failed
    Code:
    Event[3539]:
      Log Name: System
      Source: Disk
      Date: 2019-06-15T10:35:56.773
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-T8OPRMK
      Description: 
    An error was detected on device \Device\Harddisk4\DR5 during a paging operation.
    
    Event[3540]:
      Log Name: System
      Source: Disk
      Date: 2019-06-15T10:35:56.773
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-T8OPRMK
      Description: 
    An error was detected on device \Device\Harddisk4\DR5 during a paging operation.
    Code:
    Event[1217]:
      Log Name: System
      Source: Microsoft-Windows-Ntfs
      Date: 2019-05-31T11:31:09.561
      Event ID: 98
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      Description: 
    Volume C: (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
    Code:
    Event[1104]:
      Log Name: System
      Source: Ntfs
      Date: 2019-05-31T09:31:00.890
      Event ID: 130
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      Description: 
    The file system structure on volume H: has now been repaired.
    
    Event[1105]:
      Log Name: System
      Source: Ntfs
      Date: 2019-05-31T09:32:03.734
      Event ID: 130
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      Description: 
    The file system structure on volume H: has now been repaired.
    
    Event[1106]:
      Log Name: System
      Source: Ntfs
      Date: 2019-05-31T09:32:03.748
      Event ID: 130
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      Description: 
    The file system structure on volume H: has now been repaired.
    
    Event[1107]:
      Log Name: System
      Source: Ntfs
      Date: 2019-05-31T09:32:03.748
      Event ID: 130
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      Description: 
    The file system structure on volume H: has now been repaired.
    
    Event[1108]:
      Log Name: System
      Source: Ntfs
      Date: 2019-05-31T09:32:03.749
      Event ID: 130
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      Description: 
    The file system structure on volume H: has now been repaired.
    
    Event[1109]:
      Log Name: System
      Source: Ntfs
      Date: 2019-05-31T09:32:47.765
      Event ID: 130
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      Description: 
    The file system structure on volume H: has now been repaired.
    Code:
    Event[1079]:
      Log Name: System
      Source: Microsoft-Windows-Ntfs
      Date: 2019-05-30T21:56:17.904
      Event ID: 98
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      Description: 
    Volume H: (\Device\HarddiskVolume14) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
    Code:
    Event[1083]:
      Log Name: System
      Source: Ntfs
      Date: 2019-05-30T21:56:47.243
      Event ID: 55
      Task: N/A
      Level: Error
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      Description: 
    A corruption was discovered in the file system structure on volume H:.
    
    Die Masterdateitabelle (MFT) beinhaltet einen beschädigten Dateidatensatz. Die Dateireferenznummer ist 0x1000000000027. Der Name der Datei ist "\$RECYCLE.BIN\S-1-5-21-3795879806-1195599964-868843373-1000".
    Code:
    Event[6853]:
      Log Name: System
      Source: Tcpip
      Date: 2019-07-14T11:06:40.616
      Event ID: 4229
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-T8OPRMK
      Description: 
    TCP/IP has detected high memory utilization and has terminated some existing connections to  maintain system stability.
    Code:
    Event[1100]:
      Log Name: System
      Source: Tcpip
      Date: 2019-05-31T09:30:36.406
      Event ID: 4229
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-T8OPRMK
      Description: 
    TCP/IP has detected high memory utilization and has terminated some existing connections to  maintain system stability.
    Code:
    Event[6744]:
      Log Name: System
      Source: EventLog
      Date: 2019-07-14T10:49:04.545
      Event ID: 6008
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-T8OPRMK
      Description: 
    The previous system shutdown at 10:45:56 on ?14.?07.?2019 was unexpected.
    Code:
    Event[6757]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2019-07-14T10:48:54.854
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      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.
    Code:
    Event[6684]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2019-07-07T19:59:43.644
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      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.
    Code:
    Event[6672]:
      Log Name: System
      Source: EventLog
      Date: 2019-07-07T19:59:52.814
      Event ID: 6008
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-T8OPRMK
      Description: 
    The previous system shutdown at 11:58:24 on ?06.?07.?2019 was unexpected.
    Code:
    Event[6191]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2019-07-04T10:40:34.952
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      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.
    Code:
    Event[6186]:
      Log Name: System
      Source: volmgr
      Date: 2019-07-04T10:40:34.696
      Event ID: 46
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-T8OPRMK
      Description: 
    Crash dump initialization failed!
    Code:
    Event[5913]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2019-07-04T08:07:38.705
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      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.
    Code:
    Event[5893]:
      Log Name: System
      Source: EventLog
      Date: 2019-07-04T08:07:47.726
      Event ID: 6008
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-T8OPRMK
      Description: 
    The previous system shutdown at 09:47:48 on ?04.?07.?2019 was unexpected.
    Code:
    Event[5867]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2019-07-04T09:47:37.722
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      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.
    Code:
    Event[5854]:
      Log Name: System
      Source: EventLog
      Date: 2019-07-04T09:47:48.930
      Event ID: 6008
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-T8OPRMK
      Description: 
    The previous system shutdown at 09:30:19 on ?04.?07.?2019 was unexpected.
    Code:
    Event[5815]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2019-07-04T09:30:10.465
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      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.
    Code:
    Event[5802]:
      Log Name: System
      Source: EventLog
      Date: 2019-07-04T09:30:19.456
      Event ID: 6008
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-T8OPRMK
      Description: 
    The previous system shutdown at 09:09:54 on ?04.?07.?2019 was unexpected.
    Code:
    Event[5762]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2019-07-03T22:29:45.125
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      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.
    Code:
    Event[5749]:
      Log Name: System
      Source: EventLog
      Date: 2019-07-03T22:29:54.430
      Event ID: 6008
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-T8OPRMK
      Description: 
    The previous system shutdown at 19:58:12 on ?03.?07.?2019 was unexpected.
    Code:
    Event[5667]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2019-07-03T19:58:00.800
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT-AUTORITÄT\SYSTEM
      Computer: DESKTOP-T8OPRMK
      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.
    Code:
    Event[5647]:
      Log Name: System
      Source: EventLog
      Date: 2019-07-03T19:58:12.073
      Event ID: 6008
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-T8OPRMK
      Description: 
    The previous system shutdown at 19:53:45 on ?03.?07.?2019 was unexpected.
      My Computer


  10. Posts : 671
    Win 10 21H1 (OS Build 19043.1151)
       #20

    Have you checked your Power Options.
    Computer restart although a click on shutdown-screenshot-38-.png

    Choose what the power button does.
    Computer restart although a click on shutdown-screenshot-39-.png

    Check if it is properly set to Shut down.
    Computer restart although a click on shutdown-screenshot-40-.png
      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 18:47.
Find Us




Windows 10 Forums