Windows 10: Weird CHKDSK issue

Edition: Windows 10 Pro Version: 21H1 OS build: 19043.1081 Hey, all. I decided to do a CHKDSK on my 1TB external HDD after using it on Kubuntu 21.04 with Dislocker. The drive was BitLocker encrypted & I used Dislocker to decrypt it under a Kubuntu 21.04 live CD. The drive was successfully decrypted & I was able to read & write to it. Today, I decided to do a CHKDSK on it to see if there were any issues. I used the "Error checking" option in Windows Explorer. It initially said the drive had no errors, but I decided to scan anyway. Almost immediately, it came up with a message box saying the drive needed to be repaired. I was confused, as it didn't seem to do any actual scanning of the drive (no progress bar, no ETA). I ran "chkdsk F:" from an admin CMD & it finished successfully saying that the drive had no errors. I also ran "chkdsk /f F:" & that too found no issues. What gives? Here are screenshots & logs: Chkdsk was executed in read-only mode. A volume snapshot was not used. Extra errors and warnings may be reported as the volume may have changed during the chkdsk run. Checking file system on F: The type of the file system is NTFS. Insufficient storage available to create either the shadow copy storage file or other shadow copy data. Volume label is SATURN. WARNING! /F parameter not specified. Running CHKDSK in read-only mode. Stage 1: Examining basic file system structure ... 247552 file records processed. File verification completed. Phase duration (File record verification): 8.11 seconds. 144 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.24 milliseconds. Stage 2: Examining file name linkage ... 29 reparse records processed. 314144 index entries processed. Index verification completed. Phase duration (Index verification): 1.53 minutes. 0 unindexed files scanned. Phase duration (Orphan reconnection): 120.77 milliseconds. 0 unindexed files recovered to lost and found. Phase duration (Orphan recovery to lost and found): 0.40 milliseconds. 29 reparse records processed. Phase duration (Reparse point and Object ID verification): 4.13 milliseconds. Stage 3: Examining security descriptors ... Security descriptor verification completed. Phase duration (Security descriptor verification): 116.64 milliseconds. 33297 data files processed. Phase duration (Data attribute verification): 0.63 milliseconds. CHKDSK is verifying Usn Journal... 35727208 USN bytes processed. Usn Journal verification completed. Phase duration (USN journal verification): 666.23 milliseconds. Windows has scanned the file system and found no problems. No further action is required. 976759807 KB total disk space. 976194400 KB in 213871 files. 58144 KB in 33298 indexes. 0 KB in bad sectors. 378671 KB in use by the system. 65536 KB occupied by the log file. 128592 KB available on disk. 4096 bytes in each allocation unit. 244189951 total allocation units on disk. 32148 allocation units available on disk. Total duration: 1.68 minutes (101170 ms). ======================================================== Chkdsk was executed in read/write mode. Checking file system on F: The type of the file system is NTFS. Volume label is SATURN. Stage 1: Examining basic file system structure ... 247552 file records processed. File verification completed. Phase duration (File record verification): 7.30 seconds. 144 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.38 milliseconds. Stage 2: Examining file name linkage ... 29 reparse records processed. 314144 index entries processed. Index verification completed. Phase duration (Index verification): 1.53 minutes. 0 unindexed files scanned. Phase duration (Orphan reconnection): 122.65 milliseconds. 0 unindexed files recovered to lost and found. Phase duration (Orphan recovery to lost and found): 0.66 milliseconds. 29 reparse records processed. Phase duration (Reparse point and Object ID verification): 2.12 milliseconds. Stage 3: Examining security descriptors ... Cleaning up 187 unused index entries from index $SII of file 0x9. Cleaning up 187 unused index entries from index $SDH of file 0x9. Cleaning up 187 unused security descriptors. Security descriptor verification completed. Phase duration (Security descriptor verification): 98.66 milliseconds. 33297 data files processed. Phase duration (Data attribute verification): 0.42 milliseconds. CHKDSK is verifying Usn Journal... 35727840 USN bytes processed. Usn Journal verification completed. Phase duration (USN journal verification): 653.82 milliseconds. Windows has scanned the file system and found no problems. No further action is required. 976759807 KB total disk space. 976194400 KB in 213871 files. 58144 KB in 33298 indexes. 0 KB in bad sectors. 378667 KB in use by the system. 65536 KB occupied by the log file. 128596 KB available on disk. 4096 bytes in each allocation unit. 244189951 total allocation units on disk. 32149 allocation units available on disk. Total duration: 1.67 minutes (100495 ms).

:)

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.

 

chkdsk c: /F

It might be an error on the drive. We suggests that you follow the troubleshooting steps below:

• Run Disk Cleanup utility to clear your junk files.
• Open an elevated CMD type sfc /scannow and hit Enter to run the System File Checker.
  
• Once the scan is completed, restart your computer. Remember to exit ChkDsk
  during boot.
• Next, again open CMD as admin type
  Dism /Online /Cleanup-Image /RestoreHealth and hit Enter to repair the Windows image.
• Now see if ChkDsk able to complete the scan.

Note: Before doing the steps, make sure you save a back up of your files.

Let us know how it goes.

 

Windows 10 weird font issue

Hi Jason,

Thank you for using Windows 10.

Let us know:

• If the issue is specific to any web-browser?
• Does the issue also occur with documents saved in your computer?

Meanwhile, I suggest you to try in “in-Private” mode and check if it helps. Here is the steps:

• 
  Open Internet Explorer.
  
• 
  Press Ctrl+Shift+P.
  

If the issue still persists, then try login in “Compatibility Mode” and check. See the steps:

• 
  Open Internet Explorer.
  
• 
  Click on Tools icon and select
  Compatibility view settings.
  

Share the results and let us know if you need further assistance and we’ll be glad to assist.