Quest to find the cause of file corruption on a "healthy" SSD


jbcarreon123

jbcarreon123

Well-known member
Power User
VIP
Local time
10:15 AM
Posts
1,185
Location
Quezon City, Philippines
Visit site
OS
Windows 11 Home
Hello there!

I'm figuring out what is the cause of file corruption on a Kingston SV500 240GB SSD. If you want to find out one four occurances of the SSD corrupting files, see the thread below:

PC won't boot - Windows files corrupted (possibly found the culprit?)

Hello! This is not my PC that I put 11 on it even it is incompatible, the PC I'm referring here is my recent modern (but not new) PC that runs 11 without issues. When I put files on it, sometimes other files just corrupted. I experienced 4 of the same issue, PC won't boot. 1st issue: Apps does...
www.elevenforum.com www.elevenforum.com

What software(s) I can use to figure out what the cause of file corruption on this SSD?
I also note that it isn't storage space problems, because I formatted the SSD, installed Visual Studio 2022 on it, and a few days ago, Visual Studio does not run. When I did a full reinstall on a other SSD, installation fails and says "The file is corrupted or unreadable.", and had to format the SSD again to reinstall VS on another drive.
Also note that Kingston's SSD manager didn't recognize the SSD.
 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo
    CPU
    Core i5-12450HX
    Memory
    20GB DDR5-4800
    Graphics Card(s)
    iGPU + RTX 3050 Mobile (6GB)
    Sound Card
    Realtek
    Monitor(s) Displays
    the built-in laptop screen, and a generic monitor
    Screen Resolution
    1080p * 2
    Hard Drives
    GIGABYTE NVMe SSD 256GB (GP-GSM2NE3256GNTD)
    Micron NVMe SSD 512GB (MTFDKCD512QFM-1BDIAABLA)
    Browser
    Firefox
    Antivirus
    WD
  • Operating System
    Windows 10 Pro
    Computer type
    PC/Desktop
    Manufacturer/Model
    Dell
    CPU
    Core i3-2100
    Memory
    4GB DDR3-2133
    Graphics card(s)
    iGPU
    Screen Resolution
    1080p
    Antivirus
    WD
Have you checked the NTFS file system corruption with Chkdsk C: /f command?
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP Pavilion
    CPU
    AMD Ryzen 7 5700G
    Motherboard
    Erica6
    Memory
    Micron Technology DDR4-3200 16GB
    Graphics Card(s)
    NVIDIA GeForce RTX 3060
    Sound Card
    Realtek ALC671
    Monitor(s) Displays
    Samsung SyncMaster U28E590
    Screen Resolution
    3840 x 2160
    Hard Drives
    SAMSUNG MZVLQ1T0HALB-000H1
FreeBooter said:
Have you checked the NTFS file system corruption with Chkdsk C: /f command?
Click to expand...
Code: 
E:\>chkdsk E: /f
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process.  Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
Volume dismounted.  All opened handles to this volume are now invalid.

Stage 1: Examining basic file system structure ...
  29440 file records processed.
File verification completed.
 Phase duration (File record verification): 250.52 milliseconds.
Deleting orphan file record segment 8A.
Deleting orphan file record segment 8D.
Deleting orphan file record segment 8E.
Deleting orphan file record segment 92.
Deleting orphan file record segment 97.
Deleting orphan file record segment 108.
Deleting orphan file record segment 109.
Deleting orphan file record segment 10A.
Deleting orphan file record segment 10B.
Deleting orphan file record segment 110.
Deleting orphan file record segment 114.
Deleting orphan file record segment 2D9.
Deleting orphan file record segment 2DA.
Deleting orphan file record segment 2DD.
Deleting orphan file record segment 2E0.
Deleting orphan file record segment 2E1.
Deleting orphan file record segment 2E2.
Deleting orphan file record segment 2E3.
Deleting orphan file record segment 2E4.
Deleting orphan file record segment 2E6.
Deleting orphan file record segment 2E7.
Deleting orphan file record segment 358.
Deleting orphan file record segment 359.
Deleting orphan file record segment 35A.
Deleting orphan file record segment 35B.
Deleting orphan file record segment 35D.
Deleting orphan file record segment 35E.
Deleting orphan file record segment 35F.
Deleting orphan file record segment 360.
Deleting orphan file record segment 361.
Deleting orphan file record segment 363.
Deleting orphan file record segment 364.
Deleting orphan file record segment 367.
Deleting orphan file record segment 3D9.
Deleting orphan file record segment 3DA.
Deleting orphan file record segment 3DC.
Deleting orphan file record segment 3E5.
  40 large file records processed.
 Phase duration (Orphan file record recovery): 66.75 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 2.29 milliseconds.

Stage 2: Examining file name linkage ...
  1 reparse records processed.
Deleting index entry Azure.Storage.Emulator,version=17.6.326.62524,productarch=neutral in index $I30 of file 31.
Deleting index entry Microsoft.ClickOnce.SignTool.Msi,version=17.6.33605.316 in index $I30 of file 31.
Deleting index entry Microsoft.DiagnosticsHub.DotNetAsync.Targeted,version=17.6.33605.2,productarch=neutral,machinearch=x64 in index $I30 of file 31.
Deleting index entry Microsoft.DiagnosticsHub.DotNetCountersTool.Targeted,version=17.6.33605.2,productarch=neutral,machinearch=x64 in index $I30 of file 31.
Deleting index entry Microsoft.DiagnosticsHub.EventsViewerTool,version=17.6.33605.2,productarch=neutral in index $I30 of file 31.
Deleting index entry Microsoft.Icecap.Analysis.Targeted,version=17.6.33711.286,chip=x64,productarch=x64 in index $I30 of file 31.
Deleting index entry Microsoft.IntelliTrace.CollectorCab,version=17.6.33606.225,productarch=neutral in index $I30 of file 31.
Deleting index entry Microsoft.IntelliTrace.Core.Concord,version=17.6.33620.129,productarch=neutral in index $I30 of file 31.
Deleting index entry Microsoft.Net.4.7.2.TargetingPack,version=4.7.3062.2 in index $I30 of file 31.
Deleting index entry Microsoft.Net.4.7.2.TargetingPack.Resources,version=4.7.3062.2,language=en-US in index $I30 of file 31.
Deleting index entry Microsoft.Net.4.8.SDK,version=4.8.3928.2 in index $I30 of file 31.
Deleting index entry Microsoft.Net.Component.4.7.2.TargetingPack,version=17.6.33605.316 in index $I30 of file 31.
Deleting index entry Microsoft.Net.Component.4.8.SDK,version=17.6.33605.316 in index $I30 of file 31.
Deleting index entry Microsoft.Net.Cumulative.TargetingPack.Resources,version=4.8.9037.0,language=en-US in index $I30 of file 31.
Deleting index entry Microsoft.PackageGroup.Icecap.Core,version=17.6.33605.316 in index $I30 of file 31.
Deleting index entry Microsoft.VisualCpp.Redist.14,version=14.36.32532,chip=x64 in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.Blend.Auto,version=17.6.33513.286 in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.Community.CSharp.Neutral,version=17.6.33705.100,productarch=neutral in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.Community.ProductArch.Targeted,version=17.6.33712.159,productarch=x64 in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.Community.ProductArch.TargetedExtra,version=17.6.33605.316,productarch=x64 in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.Component.DiagnosticTools,version=17.6.33605.316 in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.Component.ManagedDesktop.Prerequisites,version=17.6.33605.316 in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.Debugger.AzureAttach,version=17.6.33605.316 in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.Debugger.BrokeredServices,version=17.6.0.2315901 in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.Debugger.Managed,version=17.6.33606.225,productarch=x64 in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.Debugger.Parallel,version=17.6.33706.43,productarch=x64 in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.Debugger.Script.Remote.Resources,version=17.6.33620.129,chip=x86,language=en-US,productarch=neutral in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.GraphModel,version=17.6.33606.225,productarch=neutral in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.PackageGroup.Debugger.Core,version=17.6.33605.316 in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.Templates.VB.Wpf,version=17.6.33605.316,productarch=neutral in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.Templates.VB.Wpf.Resources,version=17.6.33605.316,language=en-US,productarch=neutral in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.Web.Azure.Common,version=17.6.326.62524,productarch=neutral in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.Workload.CoreEditor,version=17.6.33605.316 in index $I30 of file 31.
Deleting index entry Microsoft.VisualStudio.XamlDesigner.Executables,version=17.6.33712.159,productarch=neutral in index $I30 of file 31.
Deleting index entry Microsoft.WebTools.DotNet.Core.ItemTemplates,version=17.6.4.18916,productarch=neutral in index $I30 of file 31.
Deleting index entry Microsoft.WebTools.Shared,version=17.6.326.62524,productarch=neutral in index $I30 of file 31.
Deleting index entry _package.json in index $I30 of file 42.
Deleting index entry devenv.isolation.ini in index $I30 of file 4A.
Deleting index entry _package.json in index $I30 of file 4A.
Deleting index entry _package.json in index $I30 of file 4B.
Deleting index entry _package.json in index $I30 of file 4C.
Deleting index entry _package.json in index $I30 of file 50.
Deleting index entry _package.json in index $I30 of file E5.
Deleting index entry _package.json in index $I30 of file EC.
Deleting index entry _package.json in index $I30 of file ED.
Deleting index entry _package.json in index $I30 of file F2.
Deleting index entry _package.json in index $I30 of file 100.
Deleting index entry _package.json in index $I30 of file 104.
Deleting index entry _package.json in index $I30 of file 106.
Deleting index entry _package.json in index $I30 of file 107.
Deleting index entry _package.json in index $I30 of file 118.
Deleting index entry _package.json in index $I30 of file 11A.
Deleting index entry _package.json in index $I30 of file 195.
Deleting index entry _package.json in index $I30 of file 196.
Deleting index entry _package.json in index $I30 of file 1D0.
Deleting index entry _package.json in index $I30 of file 1D3.
Deleting index entry _package.json in index $I30 of file 1D6.
Deleting index entry _package.json in index $I30 of file 1DB.
Deleting index entry _package.json in index $I30 of file 1DF.
Deleting index entry _package.json in index $I30 of file 1E0.
Deleting index entry _package.json in index $I30 of file 270.
Deleting index entry _package.json in index $I30 of file 2BB.
Deleting index entry _package.json in index $I30 of file 355.
  42362 index entries processed.
Index verification completed.
 Phase duration (Index verification): 745.37 milliseconds.
CHKDSK is scanning unindexed files for reconnect to their original directory.
  21 unindexed files scanned.
  0 unindexed files recovered to original directory.
 Phase duration (Orphan reconnection): 146.67 milliseconds.
CHKDSK is recovering remaining unindexed files.
  21 unindexed files recovered to lost and found.
    Lost and found is located at \found.000

 Phase duration (Orphan recovery to lost and found): 28.45 milliseconds.
  1 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 1.58 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 2.41 milliseconds.
  6462 data files processed.
 Phase duration (Data attribute verification): 0.61 milliseconds.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.

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

 234428415 KB total disk space.
    599940 KB in 22570 files.
      5440 KB in 6464 indexes.
         0 KB in bad sectors.
    102547 KB in use by the system.
     65536 KB occupied by the log file.
 233720488 KB available on disk.

      4096 bytes in each allocation unit.
  58607103 total allocation units on disk.
  58430122 allocation units available on disk.
Total duration: 1.25 seconds (1258 ms).
 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo
    CPU
    Core i5-12450HX
    Memory
    20GB DDR5-4800
    Graphics Card(s)
    iGPU + RTX 3050 Mobile (6GB)
    Sound Card
    Realtek
    Monitor(s) Displays
    the built-in laptop screen, and a generic monitor
    Screen Resolution
    1080p * 2
    Hard Drives
    GIGABYTE NVMe SSD 256GB (GP-GSM2NE3256GNTD)
    Micron NVMe SSD 512GB (MTFDKCD512QFM-1BDIAABLA)
    Browser
    Firefox
    Antivirus
    WD
  • Operating System
    Windows 10 Pro
    Computer type
    PC/Desktop
    Manufacturer/Model
    Dell
    CPU
    Core i3-2100
    Memory
    4GB DDR3-2133
    Graphics card(s)
    iGPU
    Screen Resolution
    1080p
    Antivirus
    WD
Windows has made corrections to the file system.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP Pavilion
    CPU
    AMD Ryzen 7 5700G
    Motherboard
    Erica6
    Memory
    Micron Technology DDR4-3200 16GB
    Graphics Card(s)
    NVIDIA GeForce RTX 3060
    Sound Card
    Realtek ALC671
    Monitor(s) Displays
    Samsung SyncMaster U28E590
    Screen Resolution
    3840 x 2160
    Hard Drives
    SAMSUNG MZVLQ1T0HALB-000H1
It usually happens after reboot.
 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo
    CPU
    Core i5-12450HX
    Memory
    20GB DDR5-4800
    Graphics Card(s)
    iGPU + RTX 3050 Mobile (6GB)
    Sound Card
    Realtek
    Monitor(s) Displays
    the built-in laptop screen, and a generic monitor
    Screen Resolution
    1080p * 2
    Hard Drives
    GIGABYTE NVMe SSD 256GB (GP-GSM2NE3256GNTD)
    Micron NVMe SSD 512GB (MTFDKCD512QFM-1BDIAABLA)
    Browser
    Firefox
    Antivirus
    WD
  • Operating System
    Windows 10 Pro
    Computer type
    PC/Desktop
    Manufacturer/Model
    Dell
    CPU
    Core i3-2100
    Memory
    4GB DDR3-2133
    Graphics card(s)
    iGPU
    Screen Resolution
    1080p
    Antivirus
    WD
jbcarreon123 said:
I'm figuring out what is the cause of file corruption on a Kingston SV500 240GB SSD.... What software(s) I can use to figure out what the cause of file corruption on this SSD?
.... Also note that Kingston's SSD manager didn't recognize the SSD.
Click to expand...
Hello JB.

Corruption could have been created by the OS, so may have nothing to do with the health of the SSD. Or it may be the SSD itself that's failing.

What makes you describe the disk as "healthy" if the Kingston SSD manager can't see it? Can CrystalDisk Info read its SMART data? If so, how many terabytes have been written to it?

I don't recognise the SSD either, nor can I find it on Kingston's website. There is a Kingston SUV500 240GB SSD however, that has a TBW of 100TB.

If you can read the SMART data a healthy SSD should have a raw values of zero for both the Reallocated Sector Count and the Pending Sector Count, does yours?

jbcarreon123 said:
It usually happens after reboot.
Click to expand...

That is leaning towards the corruption being a software error rather than a hardware fault....
 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, and 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. In-place upgrade to 24H2 using hybrid 23H2/24H2 install media. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
Bree said:
What makes you describe the disk as "healthy" if the Kingston SSD manager can't see it? Can CrystalDisk Info read its SMART data? If so, how many terabytes have been written to it?
Click to expand...
1685026308845.png

Bree said:
If you can read the SMART data a healthy SSD should have a raw values of zero for both the Reallocated Sector Count and the Pending Sector Count, does yours?
Click to expand...
1685026479286.png
1685026468624.png

Bree said:
I don't recognise the SSD either, nor can I find it on Kingston's website. There is a Kingston SUV500 240GB SSD however, that has a TBW of 100TB.
https://www.kingston.com/datasheets/SUV500_en.pdf
Click to expand...
It is actually a SUV500. I forgot the naming scheme again.

Bree said:
That is leaning towards the corruption being a software error rather than a hardware fault....
Click to expand...
It didn't happen again when I changed the boot device to the SSD of my old PC.
 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo
    CPU
    Core i5-12450HX
    Memory
    20GB DDR5-4800
    Graphics Card(s)
    iGPU + RTX 3050 Mobile (6GB)
    Sound Card
    Realtek
    Monitor(s) Displays
    the built-in laptop screen, and a generic monitor
    Screen Resolution
    1080p * 2
    Hard Drives
    GIGABYTE NVMe SSD 256GB (GP-GSM2NE3256GNTD)
    Micron NVMe SSD 512GB (MTFDKCD512QFM-1BDIAABLA)
    Browser
    Firefox
    Antivirus
    WD
  • Operating System
    Windows 10 Pro
    Computer type
    PC/Desktop
    Manufacturer/Model
    Dell
    CPU
    Core i3-2100
    Memory
    4GB DDR3-2133
    Graphics card(s)
    iGPU
    Screen Resolution
    1080p
    Antivirus
    WD
You must log in or register to reply here.

Similar threads

Solved File corruption and unstable system. Cant find problem for the life of me
Replies
12
Views
4K
FreeBooter
FreeBooter

Latest Support Threads

Latest Tutorials

Back
Top Bottom