Unpredictable BSODs with different stop codes

Okay, will do.

Do you think that part of the issue with the initial chkdsk could be because in order to run cmd.exe as an administrator, I had to use the Run function from Task Manager, select "Create this task with administrative privileges," and the UAC screen never popped up? The chkdsk ran fine upon restart, but could there have been an issue with the results because the UAC screen never showed up when running cmd? When I attempted to choose "Run As Administrator" from the Windows Start menu or by right clicking on it in the search and choosing "Run As Administrator," the UAC screen didn't pop up and cmd wouldn't open, so I had to use the Task Manager Run workaround.

- - - Updated - - -

Here are the Application logs from Event Viewer: Application Logs 9-8.evtx - Google Drive
Here are the System logs from Event Viewer: System Logs 9-8.evtx - Google Drive

I reran chkdsk overnight on the D: drive (the one with bad sectors). Upon waking, once again my computer was at the login screen. Is this normal to happen after chkdsk? Or is there a chance that my cat stepped on the keyboard in the middle of the night and either canceled it, closed it early, or bypassed the end screen for the check?

Find a flash drive that you can format (> or = 8 GB).

Create a bootable Windows 10 Media Creation Tool (MCT) (Windows 10 iso)

Download Windows 10 ISO File

https://www.microsoft.com/en-us/soft...load/windows10

Code:

Checking file system on D:
The type of the file system is NTFS.
Volume label is 3TB.

A disk check has been scheduled.
Windows will now check the disk.                         

Stage 1: Examining basic file system structure ...
The total allocated size 0x15dd50000 of attribute of type 0x80 and instance
tag 0x1 in file 0x204c8 is incorrect.  The expected value is 19f200000.
Correcting total allocated size in attribute record (80, "")
of file 40000000204C8.
  254208 file records processed.                                                         
File verification completed.
 Phase duration (File record verification): 4.19 seconds.
  10380 large file records processed.                                    
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.                                      
 Phase duration (Bad file record checking): 0.66 milliseconds.

Stage 2: Examining file name linkage ...
  7604 reparse records processed.                                       
  287628 index entries processed.                                                        
Index verification completed.
 Phase duration (Index verification): 9.91 seconds.
  0 unindexed files scanned.                                         
 Phase duration (Orphan reconnection): 66.62 milliseconds.
  0 unindexed files recovered to lost and found.                     
 Phase duration (Orphan recovery to lost and found): 1.56 milliseconds.
  7604 reparse records processed.                                       
 Phase duration (Reparse point and Object ID verification): 15.43 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 25.15 milliseconds.
  16711 data files processed.                                            
 Phase duration (Data attribute verification): 0.67 milliseconds.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
  254192 files processed.                                                                
File data verification completed.
 Phase duration (User file recovery): 4.23 hours.

Stage 5: Looking for bad, free clusters ...
  116046004 free clusters processed.                                                        
Free space verification is complete.
 Phase duration (Free space recovery): 0.00 milliseconds.
Adding 3 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

   2861458 MB total disk space.
   2407701 MB in 194505 files.
     53316 KB in 16712 indexes.
        12 KB in bad sectors.
    410319 KB in use by the system.
     65536 KB occupied by the log file.
 464184008 KB available on disk.

      4096 bytes in each allocation unit.
 732533503 total allocation units on disk.
 116046002 allocation units available on disk.
Total duration: 4.23 hours (15250003 ms).

Internal Info:
00 e1 03 00 1c 39 03 00 18 39 03 00 00 00 00 00  .....9...9......
b4 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

I actually already have a Windows 10 bootable installation media because I recently built my girlfriend a Windows 10 PC. Are you suggesting a fresh Windows install?

Drive letters may change when booting into Windows Recovery Environment (RE).

Boot to the Windows 10 MCT > command prompt > type:

C:
dir

D:
dir

E:
dir


Run the chkdsk switches overnight while in Windows RE:


chkdsk /b /v W: (change the drive letter W: to the applicable drive letter)


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 as needed.

Okay - would you like me to prioritize this over any of the prior requested tests such as other HD Tune error scans?

There is flexibility > complete them in any order.

Here is another HD Tune error scan for one of my drives - I chose to do this before the Windows RE chkdsks because I want to run those during the daytime in the next couple of days so I can ensure they complete correctly.



- - - Updated - - -

I had a couple hours away from the PC today so was able to run another HD Tune error scan during the daytime:

I ordered a USB LAN Adapter that should arrive in a few days and will get you chkdsk results over the next few days as well!

Ok.

mcaulfield said:

I ordered a USB LAN Adapter that should arrive in a few days and will get you chkdsk results over the next few days as well!

I think that's wise since in post #2 I showed you that the BSOD dump files pointed clearly at the Intel Gigabit LAN adapter. If you recall you couldn't obtain a more recent driver than the June 22nd 2021 version you have installed. In post #5 I then noted that the problem could well be the LAN adapter itself - that's why I sugested you try using WiFi (which I understand isn't that easy at your site).

Trying a USB LAN adapter will be an excellent test then to prove whether the BSOD of which you first complained was caused by the LAN card.