Persistent BSODs for several months

Hey guys, I've already posted for help with this on Tom's Hardware forum, but one of the main admins there has been having GPU issues and was no longer able to help. He said to try coming here. I'm new to this forum so I'll just include as much useful info as I can, and a link to the original post.

Original post: Question - Persistent BSODs for several months | Tom's Hardware Forum
Google drive folder with minidumps and V2 Log collector output: dumps - Google Drive

System Info:
CPU: i7-6700, no overclock
RAM: 16 GB (2x8GB) 2133MHz clock, no xmp, DDR4, corsair, SKU CMK16GX4M2Z2400C16
SSD: Kingston SA400S37480G
HDD: ST2000DM008-2FR102, ST2000DM001-1ER164, WDC WD7501AAES-60Z2A0
GPU: EVGA GeForce GTX 1660 XC, RMA'd once
Mobo: Gigabyte GA-H110-D3A, latest BIOS
PSU: Seasonic 620 Watts
Windows build number: 19041.450, version 2004

Tests/troubleshooting done:
Temperatures checked with OCCT, all good
memtest86, 12 passes, and windows memory diagnostic, no issues found
Checked drive health with CrystalDiskInfo, removed one drive possibly close to failure
Refreshed all Windows system files, and ran SFC
Prime95 cpu testing for 3 hours, max temps of 80c, no issues
Updated Lan drivers and BIOS
RepairImage showed a healthy image

Thank you for any and all help.

Hi knotimpressed,


I've not yet viewed your other thread nor debugged any dump files.

1) The logs displayed drive problems including bad blocks.

This needs to be evaluated.

2) Make sure images are posted for all steps / tests:

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


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


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


5) 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 /b /v C: or chkdsk /b /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /b /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


6) 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 a one drive, drop box, or google drive 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

Code:

Event[1697]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:10:38.4890000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1698]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:10:41.1410000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1699]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:10:43.7920000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1700]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:10:46.4400000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1701]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:10:49.0900000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1702]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:10:51.7410000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1703]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:10:54.3920000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1704]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:10:57.0410000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1705]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:10:59.6920000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1706]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:11:02.3450000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1707]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:11:04.9940000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1708]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:11:07.6460000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1709]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:11:10.2950000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1710]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:11:12.9440000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1711]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:11:15.5930000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1712]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:11:18.2430000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1713]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:11:20.8930000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1714]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:11:23.5410000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1715]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:11:26.1890000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR10, has a bad block.

Event[1716]:
  Log Name: System
  Source: disk
  Date: 2020-08-08T15:11:49.0080000Z
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP
  Description: 
The device, \Device\Harddisk4\DR11, has a bad block.

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 97.9 GB
Total Space: 457.2 GB
File System: NTFS
      Model: KINGSTON SA400S37480G

      Drive: D:
 Free Space: 146.0 GB
Total Space: 1893.1 GB
File System: NTFS
      Model: ST2000DM001-1ER164

      Drive: G:
 Free Space: 1511.1 GB
Total Space: 1907.7 GB
File System: NTFS
      Model: ST2000DM008-2FR102

Thanks for the Quick response! I'll start doing those, However I have run chkdsk twice before and neither time did event viewer show the logs. I'll see how it goes this time, that tutorial is much more thorough than the one I found before.

There are multiple Chkdsk switches.
The b switch is the most thorough.
Please run it overnight and the next day on all drives.
The larger size drives can take substantial time with this switch.
This switch is for known bad blocks.

Thank you for your help so far.

I have removed the D drive from my computer as I am able to do so in the short term, and the crashes have persisted. HD tune was also crashing on the D drive, the error scan never completed. I am continuing to try with the seagate utility, but the same thing is happenning, freezing after under an hour. I will attach the completed scan images (except for d, thats just the farthest it got).Attachment 295007Attachment 295008Attachment 295009Attachment 295010Attachment 295011Attachment 295012Attachment 295013Attachment 295014Attachment 295015

- - - Updated - - -

As a side note, there was a drive in my system previously with many bad blocks that I used as non-trustable, short-term storage. Not sure if that's whats actually coming up in the log files.

I'll run chkdsk tonight, if I get the chance.

In terms of debugging, other than issues with drivers, could I swap my boot drive into another machine and see if the crashes persist?

Could I install windows on a new drive/partition in my current setup, remove all other drives, and see if the crashes persist?

- - - Updated - - -

Seatools passed. Anyone still there?Attachment 295066

See if the HD Tune full error scan can be run while in safe mode: (shift + restart)
Boot into Safe Mode on Windows 10

If there are problems with HD tune in safe mode then see if it will run Macrorit surface scan:
http://www.softpedia.com/get/PORTABL...Portable.shtml

For Sea Tools create a flash drive for testing the drives:
SeaTools | Seagate Support US

The drive can be moved to an empty bay of another computer or HD enclosure for testing purposes.

To rule in / rule out misbehaving software versus malfunctioning hardware safe mode is a useful tool.
The longer the testing period (for example 4 - 7 days or more) the better the testing conditions.
Stability in safe mode is usually a misbehaving software problem.
Instability in safe mode is usually malfunctioning hardware.

I don't understand why you're asking me to run it in safe mode. HD tune crashed on the D drive, I removed the D drive, crashes have persisted, ergo no issue with the D drive. Seagate also has passed, why do I need to test it again?

And with the end of that, are you saying to run the tests back to back for a week, in safe mode?

What about just booting a fresh windows install from a known good drive and seeing if it crashes?

The earlier post that you made was updated while my post was typed.
So the comments for Sea Tools were made when you reported that you were having problems.
It was ran and displayed pass.
So Sea Tools was successfully run.


The HD Tune full error scan was incomplete.

Windows had reported bad blocks.

The testing is to locate them.

If drive problems are ruled in / out then other testing can be done to workup the cause of the BSOD.


You can make free backup images.
Then clean install Windows for testing purposes.
When testing has completed you can restore the image.

Generally before going to clean install testing other tests are performed.

Ah I see, my bad for the first part then.

I understand that the test was incomplete, however I said that I had removed that drive and that the issue persisted. I can sort out the bad blocks and what to do with that drive after, but I wish to fix the BSODs and only those for now. If the drive is not connected to my system, I do not think it is likely it is causing the issues, no?

Also I would not go to a clean install this soon in most other cases, but a clean install and waiting for a crash takes way less time than 4-7 days of drive scanning.

Windows has a tool that stress tests drivers.
If there is a problematic driver the operating system crashes.
If dump files are created they can be debugged.
If a misbehaving driver is identified it can be updated, uninstalled and reinstalled, or uninstalled.
The tool is restarted to find the next misbehaving driver.
This tool is ran for 48 hours to fix drivers and then for an additional 36 hours of typical computer use.

If this testing is of interest it can be started once you learn how to customize the tool and recover from BSOD that occur while using the tool.