BSOD once a day for the past week

For at least a week now, my computer has had a BSOD once a day, but after that it's fine for the rest of the day until the next day when I boot my PC up again. Today, however, it crashed twice in one day. I've had help from my friend to try and solve this but he can't come up with anything, it's out of my reach as well since my knowledge is very limited. I have attached a zip of the V2 Log collector scan from my PC. Help would be appreciated immensely.

No memory dumps in the uploaded reports.
No significant (tot the BSOD's) Error Reports in that folder either
No bugchecks in the System log of event viewer
Only 1 critical event (Event ID 41) in the system log of event viewer
Very few WER events in the MSINFO32 report

It seems as if you may have used an app such as CCleaner to clean out all the reports.
If not, then the system isn't generating/collecting reports - and that's a whole different problem!

Have you used an app/utility to clean out the reports? If so, please let the system BSOD a time or two.
Then check in C:\Windows\Mindump to ensure a few minidumps were collected (their filenames will include the date of the crash). Once you have minidumps - please run the V2 log collector and upload the report with your next post.

If it doesn't collect memory dumps, or if there are different problems, please post back for further suggestions.

The only serious problem I saw was with Twitch - so please uninstall it and leave it uninstalled while troubleshooting this problem.

I haven't used an app/utility to clean up the reports, but I did use the program when it didn't bluescreen so that would be a problem, my mistake. I'll also do what you said and wait for a BSOD to happen then run the program again. Also I took your advice and uninstalled the Twitch app just in case.

- - - Updated - - -

Just remembered I sent my friend a zip of the mindump i had from one of the BSODs, I have attached it to this post.Attachment 246474

So all 4 of the dump files reported an error relating to disk I/O, namely:

Code:

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

Given that you are using the in-box Windows NVMe driver, it's unlikely that your storage driver is the culprit.

I think we should start by looking at your 970 EVO SSD:

Install Samsung's Magician SSD management tool from Samsung's website.

• Check to see if the Magician tool shows an problems or errors related to the disk.
  Please also post the output of the following command from an elevated PowerShell prompt:
  Get-PhysicalDisk | ForEach-Object { $_ | Get-StorageReliabilityCounter | Select * } > "$home\desktop\disk-info.txt"
  The command will retrieve disk health statistics, and output them to a file on your desktop called "disk-info.txt".
• Upgrade your drive's firmware, you are currently on firmware version 1B2QEXE7 but the latest release is 2B2QEXE7.
  You can use the Samsung Magician Software or a bootable .iso to update the drive's firmware.
• Run HDTune's Error Scan on both your SSD and HDD, and post the results if it finds anything.

Alright so I updated my firmware, there also doesn't seem to be any problems or errors from what I can see with the Magician tool. Currently I am scanning my HDD with HDTune scan, however, when I first did the scan with my SSD, it BSOD about half way through, dunno if that has anything to do with having other programs open while running it. I ran the scan again after booting my PC back up after that. I attached the scan info with this post as well. I am currently waiting on the HDD scan to complete.

- - - Updated - - -
Attachment 246567Attachment 246568

Could you please show us the health section of HDTune as well?

I'm wondering if your NVMe drive is potentially overheating due to the test.

Spectrum said:

Could you please show us the health section of HDTune as well?

I'm wondering if your NVMe drive is potentially overheating due to the test.

Yeah I'll post the SSD health section after the HDD is done scanning.

- - - Updated - - -

Here is the HDD scan and the Health tab screenshots. For some reason, the health tab for the SSD doesn't show up after a scan with it.

Did that blue screen during the SSD error scan generate a crash dump by chance? If so, could you run the V2 Log Collector again?

I'm interested in seeing if there are any errors logged by the NVMe driver. You can export its event log by running the following command:
wevtutil.exe export-log "Microsoft-Windows-Storage-Storport/Operational" "$home\desktop\storport-log.evtx"

This will place "storport-log.evtx" on your desktop, zip that up and upload it to google drive/dropbox/onedrive/etc.

Also, monitor your Samsung 970's temperature, I'm not sure if you can monitor that from the Samsung Magician software, but something like CrystalDiskInfo (Standard) should be able to.

Here's the two zipped log, the BSOD happened last night, no idea if the log will catch it now.

Looking at the StorPort event log, there are quite a few events that indicate something is going wrong with your storage.

35 NVMe Controller Errors - Event ID 534: Controller Fatal Status

Code:

Miniport logs an error for device(Port = 2, Path = 255, Target = 255, Lun = 255).                    
Id: 7                    
Error description: Controller Fatal Status is set                    
Corresponding Class Disk Device Guid: {00000000-0000-0000-0000-000000000000}                    
Adapter Guid: {df732f7b-d0fb-11e9-8443-806e6f6e6963}                    
Miniport driver name: stornvme                    
VendorId:                     
ProductId:                     
DataLength: 4                    
Data: 0x03000000

This would appear to indicate that there is a problem with your Samsung 970 EVO's controller.