Windows 10 shuts down out of the blue while hardware still on

dalchina · 16 Jun 2019

8. All drivers are up to date and I have everything updated in general.

Can you confirm you have not used a 3rd party driver updater?

Manosman · 16 Jun 2019

Megahertz said:

Linux Mint is very good. I use Lubuntu. Lubuntu x64
You don't need to install on a HDD, it will run from a USB flash disk.
Mount the iso and extract all files and folders to a Fat32 USB flash disk (min 2G).
Boot from it and choose: Try before install.

Thanks! I'll see what I can do there.

As for my drivers, the only third party app is GeForce Experience for my NVIDIA graphics.

zbook · 16 Jun 2019

When available please upload results for V2 and DM per post #27.

Manosman · 16 Jun 2019

I'm terribly sorry, I didn't see that post. I'm uploading them right now!

PS: How come I can't write from my PC here? There's no space for text. Is this a bug? I just thought I should mention it.

EDIT: It seems I can't upload them since I can't write at least three characters 😂
Okay, I just edited them in this one!

- - - Updated - - -

And I got a new problem...
Today, I played a lot of Destiny 2. I played for many hours and a while ago an error happened, which also closed the game. I tried again, but 10 minutes later it happened again.

According to Windows, it's a Hardware error (Live Kernel Event) and it has to do with my GPU.

This is the first time that happens. My drivers are all up to date by the way.

I don't think it has to do with my other problem, since it only happened now and it's not like the other problem had to do with graphics, since the OS closed. Also, this problem only affected the game, nothing else (as far as I saw).

Yesterday, I tried to change my PSU with a brand new one (I had one). The thing is that the new one didn't work at all, even though everything was plugged in correctly (I built my desktop pc and I have helped my friend with his, so I know the connections). I then went back to my other PSU, since the new one didn't even work. I don't know if I did something wrong, I'll check again to make sure the GPU is all good.

I'll attach the pictures I took about the new problem.

Like one problem wasn't enough...

zbook · 16 Jun 2019

The logs displayed problems with:

BSOD (multiple)
Drive (bad block etc.)
BIOS is old

Some tests / steps may have already been performed.
For all tests please post images into the thread.
Use share links in case there are any problems posting images (one drive, drop box, google drive)

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) Make sure that there is no over clocking while troubleshooting.

8) Sometimes there are problems in the bios that produce bsod.

The BIOS: Version/Date American Megatrends Inc. P4.90, 7/6/2018

9) Upgade the BIOS: P4.90 > 5.80 2019/4/23

ASRock > AB350M Pro4

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

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

12) Backup the computer files to another drive or to the cloud.

13) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free

14) Create a brand new restore point.
Create System Restore Point in Windows 10

How to Clear Your Computers CMOS to Reset BIOS Settings:
https://www.howtogeek.com/131623/how...bios-settings/
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

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

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

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

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

19) Read these links on Windows driver verifier: (do not use the tool until it is communicated in the thread)

Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Code:

Event[13367]:
  Log Name: System
  Source: Disk
  Date: 2019-06-12T12:55:54.774
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-1I7P34A
  Description: 
The device, \Device\Harddisk0\DR0, has a bad block.

Code:

Event[13543]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2019-06-12T22:36:26.519
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-1I7P34A
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8036f1eb380, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e2c03e86-1155-496e-bc54-e3b7908e1c42.

Code:

4/25/2019 5:10 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff8001c947380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\042519-36906-01.dmp
\\?\C:\WINDOWS\TEMP\WER-358921-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8DEC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8E0D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8E0C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8E2C.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_de58ae26e5111118f18845270355e5bb8cd365_00000000_cab_2a5e95ba

Analysis symbol: 
Rechecking for solution: 0
Report Id: 390bd829-66b1-4c0c-a822-4a09b893b795
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
4/25/2019 5:10 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff8001c947380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\042519-36906-01.dmp
\\?\C:\WINDOWS\TEMP\WER-358921-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8DEC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8E0D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8E0C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8E2C.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_de58ae26e5111118f18845270355e5bb8cd365_00000000_03568e29

Analysis symbol: 
Rechecking for solution: 0
Report Id: 390bd829-66b1-4c0c-a822-4a09b893b795
Report Status: 4
Hashed bucket: 
Cab Guid: 0
4/27/2019 9:57 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff800777e9380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\042719-31078-01.dmp
\\?\C:\WINDOWS\TEMP\WER-386812-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A14.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A44.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B5C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B8C.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_e327aa5d1eb36b6fda8b649864ec463f758f7f_00000000_cab_32127e4a

Analysis symbol: 
Rechecking for solution: 0
Report Id: bdef92fa-04fa-40da-bd95-09d40a3399fb
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
4/27/2019 9:57 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff800777e9380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\042719-31078-01.dmp
\\?\C:\WINDOWS\TEMP\WER-386812-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A14.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A44.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B5C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B8C.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_e327aa5d1eb36b6fda8b649864ec463f758f7f_00000000_034a7b8b

Analysis symbol: 
Rechecking for solution: 0
Report Id: bdef92fa-04fa-40da-bd95-09d40a3399fb
Report Status: 4
Hashed bucket: 
Cab Guid: 0
4/10/2019 8:49 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff8020c550380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\041019-29953-01.dmp
\\?\C:\WINDOWS\TEMP\WER-888718-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5DBE.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E0D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E0C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E3C.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_9160efa9b39f72d358e418254155c635a4e1383_00000000_cab_091a63b7

Analysis symbol: 
Rechecking for solution: 0
Report Id: b290debb-986d-49c2-b2dc-514e4a8e70b9
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
4/10/2019 8:49 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff8020c550380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\041019-29953-01.dmp
\\?\C:\WINDOWS\TEMP\WER-888718-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5DBE.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E0D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E0C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E3C.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_9160efa9b39f72d358e418254155c635a4e1383_00000000_039a5e58

Analysis symbol: 
Rechecking for solution: 0
Report Id: b290debb-986d-49c2-b2dc-514e4a8e70b9
Report Status: 4
Hashed bucket: 
Cab Guid: 0
4/19/2019 9:53 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff80272b51380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\041919-31093-01.dmp
\\?\C:\WINDOWS\TEMP\WER-266453-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER83C3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER84AE.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8605.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8625.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_67d728c6592e191512a3828b5519a8a62d654_00000000_cab_09b08922

Analysis symbol: 
Rechecking for solution: 0
Report Id: cbdfed0b-d57c-491b-b021-494306be2a24
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
4/19/2019 9:52 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff80272b51380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\041919-31093-01.dmp
\\?\C:\WINDOWS\TEMP\WER-266453-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER83C3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER84AE.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8605.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8625.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_67d728c6592e191512a3828b5519a8a62d654_00000000_03588643

Analysis symbol: 
Rechecking for solution: 0
Report Id: cbdfed0b-d57c-491b-b021-494306be2a24
Report Status: 4
Hashed bucket: 
Cab Guid: 0
4/26/2019 9:15 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff8032f343380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\042619-28640-01.dmp
\\?\C:\WINDOWS\TEMP\WER-230437-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREA32.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREA62.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREAFD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREB3D.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_86a41d181b4f8eb1b9576484c01d7464ced4c9_00000000_cab_27e7ed9d

Analysis symbol: 
Rechecking for solution: 0
Report Id: 731843ec-46f4-4d0b-8171-0d87804159e3
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
4/26/2019 9:15 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff8032f343380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\042619-28640-01.dmp
\\?\C:\WINDOWS\TEMP\WER-230437-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREA32.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREA62.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREAFD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREB3D.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_86a41d181b4f8eb1b9576484c01d7464ced4c9_00000000_0353eb3c

Analysis symbol: 
Rechecking for solution: 0
Report Id: 731843ec-46f4-4d0b-8171-0d87804159e3
Report Status: 4
Hashed bucket: 
Cab Guid: 0
6/12/2019 7:36 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff8036f1eb380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\061219-30328-01.dmp
\\?\C:\WINDOWS\TEMP\WER-333234-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72ED.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72EE.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72ED.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER730E.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_2ef5f4f864aad2aa48ac5904cff8257c9b0c636_00000000_cab_06b1770c

Analysis symbol: 
Rechecking for solution: 0
Report Id: e2c03e86-1155-496e-bc54-e3b7908e1c42
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
6/12/2019 7:36 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff8036f1eb380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\061219-30328-01.dmp
\\?\C:\WINDOWS\TEMP\WER-333234-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72ED.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72EE.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72ED.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER730E.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_2ef5f4f864aad2aa48ac5904cff8257c9b0c636_00000000_03497353

Analysis symbol: 
Rechecking for solution: 0
Report Id: e2c03e86-1155-496e-bc54-e3b7908e1c42
Report Status: 4
Hashed bucket: 
Cab Guid: 0
6/4/2019 9:46 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff8040f159380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\060419-30343-01.dmp
\\?\C:\WINDOWS\TEMP\WER-63156-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5918.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5928.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5927.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5938.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_ce50b7269aa19181be89f18e9d4f382a57b231_00000000_cab_18c56b86

Analysis symbol: 
Rechecking for solution: 0
Report Id: 92fa8c21-344a-4423-9d8c-a409c6928506
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
6/4/2019 9:46 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff8040f159380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\060419-30343-01.dmp
\\?\C:\WINDOWS\TEMP\WER-63156-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5918.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5928.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5927.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5938.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_ce50b7269aa19181be89f18e9d4f382a57b231_00000000_033d5927

Analysis symbol: 
Rechecking for solution: 0
Report Id: 92fa8c21-344a-4423-9d8c-a409c6928506
Report Status: 4
Hashed bucket: 
Cab Guid: 0
4/17/2019 3:17 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff8043b5f4380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\041719-35093-01.dmp
\\?\C:\WINDOWS\TEMP\WER-147781-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B4C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B8B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9E49.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9E98.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_9bf4a9ad2091f693feaccf7e6a80f38c11a961fd_00000000_cab_07aea0da

Analysis symbol: 
Rechecking for solution: 0
Report Id: 03630a9e-41d7-4569-b024-54fdf730c72f
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
4/17/2019 3:17 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff8043b5f4380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\041719-35093-01.dmp
\\?\C:\WINDOWS\TEMP\WER-147781-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B4C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B8B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9E49.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9E98.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_9bf4a9ad2091f693feaccf7e6a80f38c11a961fd_00000000_03529ed6

Analysis symbol: 
Rechecking for solution: 0
Report Id: 03630a9e-41d7-4569-b024-54fdf730c72f
Report Status: 4
Hashed bucket: 
Cab Guid: 0
5/11/2019 12:50 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff8051f15e380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\051119-36156-01.dmp
\\?\C:\WINDOWS\TEMP\WER-286375-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58A7.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5915.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59EF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5AAB.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_9bdb36a8364a28272e6b4a85fe5b6dc1ae708c36_00000000_cab_21095d2b

Analysis symbol: 
Rechecking for solution: 0
Report Id: 1b87d4a5-3683-4427-8883-d449bedf5542
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
5/11/2019 12:50 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff8051f15e380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\051119-36156-01.dmp
\\?\C:\WINDOWS\TEMP\WER-286375-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58A7.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5915.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59EF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5AAB.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_9bdb36a8364a28272e6b4a85fe5b6dc1ae708c36_00000000_03455ad9

Analysis symbol: 
Rechecking for solution: 0
Report Id: 1b87d4a5-3683-4427-8883-d449bedf5542
Report Status: 4
Hashed bucket: 
Cab Guid: 0
6/8/2019 10:58 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff80660de3380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\060819-37343-01.dmp
\\?\C:\WINDOWS\TEMP\WER-126906-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4ED6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4ED7.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4ED6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EE6.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_912122d3b12fd4eb51e129e39efda21be9c6f_00000000_cab_03065308

Analysis symbol: 
Rechecking for solution: 0
Report Id: b0b29df9-8ae0-4c2f-8d5e-e131cd7e40ab
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
6/8/2019 10:58 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff80660de3380
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\060819-37343-01.dmp
\\?\C:\WINDOWS\TEMP\WER-126906-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4ED6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4ED7.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4ED6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EE6.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_912122d3b12fd4eb51e129e39efda21be9c6f_00000000_038a4f00

Analysis symbol: 
Rechecking for solution: 0
Report Id: b0b29df9-8ae0-4c2f-8d5e-e131cd7e40ab
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Manosman · 16 Jun 2019

Thanks! I'll start right away by running the test and sharing the results. Plus, I'm not overclocking at all, so that's good.

farrellart · 16 Jun 2019

Personally, I would leave the Bios update unless you absolutely have to update it. Why introduce more issues (potentially) and open up a can of worms?

Look up what the Bios update offers, usually it's compatibility with new hardware ( processors, RAM etc... ). Obviously, it's up to you - wasting time fixing a messed up boot after a Bios update/reset is just a waste of time if you don't have to.

EDIT: You probably already know this. Never update the bios within Windows, always do it within the Bios....sorry if that's obvious.

Manosman · 17 Jun 2019

You did well to say that. I always update it through the BIOS, but you never know 😂
Plus the updates only offer compatibility with some stuff that I don't have and some corrections to things that I don't think would apply to me (because I don't use any 3rd party apps that much about CPU and stuff). So, I'll leave it for now. Plus, when the problem started happening, I updated the BIOS to the latest version hoping to fix it. It didn't work obviously... So, it's not the BIOS, that's for sure!

-----
Now then, time to post the results from the scan:

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 /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.557

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

C:\WINDOWS\system32>chkdsk /scanchkdsk /scaned
Invalid parameter - /scanchkdsk

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
795136 file records processed.
File verification completed.
19775 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
28094 reparse records processed.
947880 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
28094 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
76373 data files processed.
CHKDSK is verifying Usn Journal...
36114688 USN bytes processed.
Usn Journal verification completed.

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

976276768 KB total disk space.
140182092 KB in 293575 files.
204652 KB in 76374 indexes.
0 KB in bad sectors.
943364 KB in use by the system.
65536 KB occupied by the log file.
834946660 KB available on disk.

4096 bytes in each allocation unit.
244069192 total allocation units on disk.
208736665 allocation units available on disk.

C:\WINDOWS\system32>lwmic recoveros set autoreboot = false
'lwmic' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-1I7P34A\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Education|C:\\WINDOWS|\\Device\\Harddisk1\\Partition1"'
Property(s) update successful.

-----

I'll also backup again (I always backup) and I'll create a new restore point, just in case. Also, I don't have Ccleaner (since it was mentioned).

PS: I'll also run the HD Tune and Sea Tools as suggested. Should I do anything else?

EDIT: I made a restore point and a backup. And I read the suggested articles as well.

- - - Updated - - -

So, I'll start by posting the results from the HD Tune software. I'm currently running the Sea Tools for Windows as well!

EDIT: It seems the Sea Tools failed to scan my 2TB HDD twice (it's not the one I have my Windows on).

- - - Updated - - -

I'm also uploading the Sea Tools results. And I think I did everything you told me (other than the Bios thing). Is there anyting else? I also see lots of warnings and stuff...

zbook · 17 Jun 2019

Manosman said:

Hey guys,

You can see my specs in my profile, but I should also note a few things:
1. The pc temp is better than normal, so there's no overheating.
2. The HDDs are 100% healthy.

In our forum we see a significant number of drive failures (long DST or long generic) with normal SMART and error scans.

Had only one drive been tested before the opening post?
If not, what test(s) had been performed on the second drive?

1) Plan to replace: WDC WD20EZRZ-00Z5HB0

2) Make sure all important files are backed up to another drive or to the cloud.

Some end users replace drives as soon as there is a questionable test result and others may wait until the drive no longer functions.

Once you have files on this drive backed up comment into the thread.

Manosman · 17 Jun 2019

Well, I already have a small foldier on the cloud with a file or two about that drive. I'll have to re-download the rest anyway.

Before this thread I had only tested the first drive and it was fine (as it is now). As for the second drive, since it doesn't has the Windows or the drivers, I didn't think that it would cause this problem. Plus it functions just fine (as far as I can tell), even the load times are good (for an HDD).