BSD's are pretty constant over the past few weeks...

Here are the other two internal drives, the SSD and the Seagate's Benchmark results. 1 Pass for each like the Hitachi drive

Attachment 172883Attachment 172884

Today is January 16, 2018 and the logs displayed that a startup repair was done yesterday indicating corruption.

Code:

Event[9134]:  Log Name: System  Source: Microsoft-Windows-StartupRepair  Date: 2018-01-15T11:49:07.145  Event ID: 1104  Task: N/A  Level: Information  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Richards-PC-Pro10  Description: The system volume was corrupt.

Code:

Event[9059]:  Log Name: System  Source: Ntfs  Date: 2018-01-15T11:41:47.387  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Richards-PC-Pro10  Description: A corruption was discovered in the file system structure on volume C:.A corruption was found in a file system index structure.  The file reference number is 0x9000000000009.  The name of the file is "<unable to determine file name>".  The corrupted index attribute is ":$SDH:$INDEX_ALLOCATION".

Code:

Event[9041]:  Log Name: System  Source: Ntfs  Date: 2018-01-15T11:22:20.985  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Richards-PC-Pro10  Description: A corruption was discovered in the file system structure on volume C:.A corruption was found in a file system index structure.  The file reference number is 0x9000000000009.  The name of the file is "<unable to determine file name>".  The corrupted index attribute is ":$SDH:$INDEX_ALLOCATION".Event[9042]:  Log Name: System  Source: Ntfs  Date: 2018-01-15T11:23:24.013  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Richards-PC-Pro10  Description: A corruption was discovered in the file system structure on volume C:.A corruption was found in a file system index structure.  The file reference number is 0x9000000000009.  The name of the file is "<unable to determine file name>".  The corrupted index attribute is ":$SDH:$INDEX_ALLOCATION".

This evening open administrative command prompt and type: chkdsk /x /f /r C:
This may take many hours.
Let this run overnight.
Tomorrow look for the chkdsk report in the event viewer. Use copy and paste > notepad > save to desktop > post a one drive or drop box share link into the thread
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

OK, so far no BSoD but I kinda figured this would happen. The boot manager is screwed up. I have to hit F12 every time I boot in now. I went into the BIOS and looked for my SSD drive, it's not there but it is there because I'm using it as my C drive for Windows. I've tried Googling the needed fix but the posts are ages old. There was one that suggested that I use the Command Prompt and Bootrec.exe tool. Not found so now what do I do to get this machine of mine auto booting to my SSD drive again? It's always something! lol

OK, updated the BIOS, one more thing done but I really need a fix for the MBR or what ever it's called these days!

BIOS Version/Date American Megatrends Inc. F6, 6/9/2017

Tonight fix the drive file system with chkdsk /x /f /r C:
Tomorrow perform an in place upgrade repair:
Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials

To fix the boot > open the windows advanced troubleshooting menu by rebooting and holding down the shift key.
Open command prompt > Admnistrator: X:\windows\system32\cmd.exe > X:\Sources>
1) type: bootrec /fixmbr
Click enter to see (The operation completed successfully)

2) type: bootrec /fixboot
Click enter to see (The operation completed successfully)

3) type: bootrec /scanos
Click enter to see (Scanning all disks for Windows installations; Please wait, since this may take a while.........Successfully scanned Windows installations. Total identified Windows installations: 0; The operation completed successfully) (This may display 0 or 1)

4) type: bootrec /rebuildbcd
Click enter to see (Scanning all disks for Windows installations; Please wait, since this may take a while.........Successfully scanned Windows installations. Total identified Windows installations: 0; The operation completed successfully) (This may display 0 or 1)

The above are the 4 common boot repair commands however with the video TDR it may be best to start with a clean install and fix any underlying problems with the operating system and registry so that there are no confounding factors.
For this you could make a backup image with Macrium and have the option to restore if for whatever reason it is needed.
Macrium Software | Macrium Reflect Free

With a clean install the grahics driver in addition to the OS and registry will be new. Then the GPU could be stressed to see its performance.
Clean Install Windows 10 Installation Upgrade Tutorials

Thank you, I'll give this a try.

I know, it's entered my mind a few times since this has begun to simply do a clean install but I'm on my last day of vacation and tomorrow I start back in the grind so not much time and I HATE installing all my programs, being a graphics artist on the side you can imagine, I have allot of programs to first deauthorize a whole mess of programs like ZBrush, Photoshop, iTunes and then start the process, boot in, set up my desktop again and get all my bits back in place, run all the updates to make sure Win 10 is solid and THEN reinstall all my programs. It's a day I'll never get back. So if I CAN I'd like to make this work for a while longer if possible. I'm off next in May!

Okay.
Perform these steps:
1) repair the drive files system overnight
2) repair the boot with the above commands
3) perform an in place upgrade repair with a windows 10 iso:
Download Windows 10
Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials

When available please post the full error scans for each drive.

For all HD (skip SSD) run:
Run Sea tools for windows on your drive using SMART, and long generic tests:


How to use SeaTools for Windows
http://www.seagate.com/support/downl...ls-win-master/
How to use SeaTools for Windows
http://www.seagate.com/support/downloads/seatools/

Finally had the time to do some of these tests. ALL of the tests for my two other drives passed using the SeaTools but I'm still waiting on the Long Generic test.

I removed all the external drives and for a while I thought "maybe that was the culprit" but today I had another one but it's been about a week so at least it's not multiple times a day.