Here is the output of tuneup.bat:
Code:
###########################################################
# The following commands will be run in sequence. #
# The first 5 will take quite a while to run, be patient. #
###########################################################
sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow
chkdsk /scan
wmic recoveros get autoreboot
wmic recoveros set autoreboot = false
wmic recoveros get autoreboot
wmic recoveros get DebugInfoType
wmic recoveros set DebugInfoType = 7
wmic recoveros get DebugInfoType
wmic pagefile list /format:list
wmic Computersystem where name="VIDAR" get AutomaticManagedPagefile
wmic Computersystem where name="VIDAR" set AutomaticManagedPagefile=True
wmic Computersystem where name="VIDAR" get AutomaticManagedPagefile
bcdedit /enum {badmemory}
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 /scanhealth
Deployment Image Servicing and Management tool
Version: 10.0.19041.572
Image Version: 10.0.19041.572
[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
C:\Windows\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.19041.572
Image Version: 10.0.19041.572
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
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>chkdsk /scan
The type of the file system is NTFS.
Volume label is OS NTFS.
Stage 1: Examining basic file system structure ...
523776 file records processed.
File verification completed.
Phase duration (File record verification): 8.57 seconds.
9650 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.82 milliseconds.
Stage 2: Examining file name linkage ...
254 reparse records processed.
Found an unneeded link ($FILE_NAME: "SYSTEM~1") in index "$I30" of directory "\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft <0x2,0x14000>"
... repaired online.
Found an unneeded link ($FILE_NAME: "c728efb32d94b737_0") in index "$I30" of directory "\Users\agent\AppData\Roaming\discord\Code Cache\js <0xa,0x220a1>"
... repaired online.
Found an unneeded link ($FILE_NAME: "C728EF~1") in index "$I30" of directory "\Users\agent\AppData\Roaming\discord\Code Cache\js <0xa,0x220a1>"
... repaired online.
687744 index entries processed.
Index verification completed.
Phase duration (Index verification): 27.40 seconds.
4 unindexed files scanned.
Phase duration (Orphan reconnection): 0.00 milliseconds.
4 unindexed files recovered to lost and found.
Found 4 lost files (...\Certificates <0x1,0x14b80>, ...\CRLs <0x1,0x14b81>, ...); requesting reconnection to index "$I30" of directory "\??\C:\found.000"
... repaired online.
Phase duration (Orphan recovery to lost and found): 0.00 milliseconds.
254 reparse records processed.
Phase duration (Reparse point and Object ID verification): 4.60 milliseconds.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 77.01 milliseconds.
81985 data files processed.
Phase duration (Data attribute verification): 0.44 milliseconds.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Windows has found problems and some were fixed online;
the remaining problems must be fixed offline.
Please run "chkdsk /f" to fix the issues.
499468346 KB total disk space.
96144196 KB in 299747 files.
274132 KB in 81988 indexes.
0 KB in bad sectors.
608710 KB in use by the system.
65536 KB occupied by the log file.
402441308 KB available on disk.
4096 bytes in each allocation unit.
124867086 total allocation units on disk.
100610327 allocation units available on disk.
Total duration: 38.80 seconds (38801 ms).
C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE
C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\VIDAR\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk1\\Partition3"'
Property(s) update successful.
C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE
C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7
C:\Windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\VIDAR\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk1\\Partition3"'
Property(s) update successful.
C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7
C:\Windows\system32>wmic pagefile list /format:list
AllocatedBaseSize=2048
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20200920035244.872423+600
Name=C:\pagefile.sys
PeakUsage=0
Status=
TempPageFile=FALSE
C:\Windows\system32>wmic Computersystem where name="VIDAR" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE
C:\Windows\system32>wmic Computersystem where name="VIDAR" set AutomaticManagedPagefile=True
Updating property(s) of '\\VIDAR\ROOT\CIMV2:Win32_ComputerSystem.Name="VIDAR"'
Property(s) update successful.
C:\Windows\system32>wmic Computersystem where name="VIDAR" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE
C:\Windows\system32>bcdedit /enum {badmemory}
RAM Defects
-----------
identifier {badmemory}
badmemorylist 0x537f8
0x537f9
0x537fa
0x537fb
0x537fc
0x537fd
0x537fe
0x537ff
Press any key to continue . . .
I note the badmemorylist however this RAM is brand new and was in fact an RMA for some RAM that failed memtest86+.
After seeing this badmemorylist I booted into memtest and ran a few passes which reported no errors, however I am skeptical. Is their anything that could be killing RAM?
In addition I updated the AMD chipset drivers and will run the machine under load later today to see if we can trigger a BSOD and I can then provide a memory dump assuming it will complete.
Thanks