Windows doesn't shut down

Hey there,
since I resolved my bluescreen error (Continues BSOD - Different Errorcodes), I have the problem, that I can only shutdown my pc using cmd (shutdown /s) or using the power button? Do you have any idea, what could be the problem?
Thanks for all,
Lars

Build: 1909 (18363.778)

Compumind said:

Hi.

Did you do a CHKDSK, SFC and DISM on the boot drive?

Yep, I did - no errors or warnings anywhere?

The V2 results were not available in the opening post link.

Please make sure the default language is English so that the logs can be scanned:
https://www.tenforums.com/tutorials/...dows-10-a.html
Change Display Language in Windows 10

Upload a new V2 directly into this thread:
BSOD - Posting Instructions

After posting V2, turn off Windows fast startup:

Turn On or Off Fast Startup in Windows 10

LARSKUSCH-PC-(2020-04-21_08-28-21).zip
Turned off the fast boot seetings, will see if it changes something.

The logs displayed multiple recent BSOD.

For all steps / tests post images into the thread:

Take Screenshot in Windows 10
https://support.microsoft.com/en-gb/...re-screenshots
How to Upload and Post Screenshots and Files at Ten Forums

What is the warranty status for the computer?


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) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

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

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

14) Sometimes there are problems in the bios that produce BSOD

15) To ensure that there are no improper bios settings please reset the bios.

15) Sometimes there can be failure to boot after resetting the bios.

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computer’s CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow
3 Easy Ways to Clear CMOS (Reset BIOS)
How to Clear CMOS (AKA Reset BIOS Settings)


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


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

MemTest86 - Official Site of the x86 Memory Testing Tool

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.


18) Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan


19) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows |
Seagate
How to use SeaTools for Windows | Seagate Support US


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

21) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot


22) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10


23) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

Code:

4/16/2020 9:25 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Nicht verfügbar
Cab Id: 0

Problem signature:
P1: 139
P2: 0
P3: 0
P4: 0
P5: fffff502f528e9f0
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\041620-21703-01.dmp
\\?\C:\WINDOWS\TEMP\WER-30875-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER928B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER929C.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER92CA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER92EA.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_8e40d82ddbd56b566d6f7b7e661c8a34c4dc9fa_00000000_cab_cc66dcf3-f6e5-46f2-b9b4-3975739cc172

Analysis symbol: 
Rechecking for solution: 0
Report Id: d2a3c87a-8863-4985-ad80-5885a8632a0d
Report Status: 4
Hashed bucket: 
Cab Guid: 0
4/16/2020 6:04 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Nicht verfügbar
Cab Id: 0

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff80058c906dc
P4: 0
P5: ffffffffffffffff
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\041620-24250-01.dmp
\\?\C:\WINDOWS\TEMP\WER-24734-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7128.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7139.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7157.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7197.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_c9c8b0419560fe235a101a6c7abf49392ca9ee64_00000000_cab_3666eece-3cc1-4696-a7b4-fbaae8145f9b

Analysis symbol: 
Rechecking for solution: 0
Report Id: 1ee731ef-3fb8-4658-98b2-b39d3ce919fc
Report Status: 4
Hashed bucket: 
Cab Guid: 0
4/15/2020 3:15 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Nicht verfügbar
Cab Id: 0

Problem signature:
P1: ef
P2: ffffbf0bc36a9400
P3: 0
P4: 0
P5: 0
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\041520-27984-01.dmp
\\?\C:\WINDOWS\TEMP\WER-28250-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7CC1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7CC2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7CE0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7D10.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ef_4fea81e2d19c775df5568f0bb437a79b62c32f_00000000_cab_3e644b8f-a74f-44ff-b289-92dbf3a8b15a

Analysis symbol: 
Rechecking for solution: 0
Report Id: fc6697d1-fc7c-4e18-9b5d-7bd8c269e0f0
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Code:

4/16/2020 9:25 AM	Windows Error Reporting	Fault bucket 0x139_0_LEGACY_GS_VIOLATION_nt!_guard_icall_handler, type 0
Event Name: BlueScreen
Response: Nicht verfügbar
Cab Id: c18c05ce-ff03-4a88-afbe-3350c4e23051

Problem signature:
P1: 139
P2: 0
P3: 0
P4: 0
P5: fffff502f528e9f0
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\041620-21703-01.dmp
\\?\C:\WINDOWS\TEMP\WER-30875-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER928B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER929C.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER92CA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER92EA.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_8e40d82ddbd56b566d6f7b7e661c8a34c4dc9fa_00000000_cab_cc66dcf3-f6e5-46f2-b9b4-3975739cc172

Analysis symbol: 
Rechecking for solution: 0
Report Id: d2a3c87a-8863-4985-ad80-5885a8632a0d
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
4/16/2020 6:04 AM	Windows Error Reporting	Fault bucket 0x1E_c0000005_R_nt!KiGeneralProtectionFault, type 0
Event Name: BlueScreen
Response: Nicht verfügbar
Cab Id: b6f81532-490b-475f-a1c9-32933d4b2e88

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff80058c906dc
P4: 0
P5: ffffffffffffffff
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\041620-24250-01.dmp
\\?\C:\WINDOWS\TEMP\WER-24734-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7128.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7139.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7157.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7197.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_c9c8b0419560fe235a101a6c7abf49392ca9ee64_00000000_cab_3666eece-3cc1-4696-a7b4-fbaae8145f9b

Analysis symbol: 
Rechecking for solution: 0
Report Id: 1ee731ef-3fb8-4658-98b2-b39d3ce919fc
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
4/15/2020 3:16 PM	Windows Error Reporting	Fault bucket 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c0000005_nt!PspCatchCriticalBreak, type 0
Event Name: BlueScreen
Response: Nicht verfügbar
Cab Id: 789e06a8-b4ac-46e3-959a-24ee0ccdcbe1

Problem signature:
P1: ef
P2: ffffbf0bc36a9400
P3: 0
P4: 0
P5: 0
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\041520-27984-01.dmp
\\?\C:\WINDOWS\TEMP\WER-28250-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7CC1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7CC2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7CE0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7D10.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_4fea81e2d19c775df5568f0bb437a79b62c32f_00000000_cab_3e644b8f-a74f-44ff-b289-92dbf3a8b15a

Analysis symbol: 
Rechecking for solution: 0
Report Id: fc6697d1-fc7c-4e18-9b5d-7bd8c269e0f0
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0

Code:

Event[2787]:
  Log Name: System
  Source: Ntfs
  Date: 2020-04-18T09:31:05.443
  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: LarsKusch-PC
  Description: 
A corruption was discovered in the file system structure on volume C:.

Die genaue Art der Beschõdigung ist unbekannt. Die Dateisystemstrukturen m³ssen offline ³berpr³ft und repariert werden.

Code:

Event[155]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2020-04-15T11:20:32.422
  Event ID: 17
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT-AUTORIT─T\Lokaler Dienst
  Computer: LarsKusch-PC
  Description: 
A corrected hardware error has occurred.

Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)

Primary Bus:Device:Function: 0x0:0x1C:0x0
Secondary Bus:Device:Function: 0x0:0x0:0x0
Primary Device Name:PCI\VEN_8086&DEV_A110&SUBSYS_86941043&REV_F1
Secondary Device Name: