• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Media and Data Integrity Error

Joined
Mar 6, 2017
Messages
3,385 (1.14/day)
Location
North East Ohio, USA
System Name My Ryzen 7 7700X Super Computer
Processor AMD Ryzen 7 7700X
Motherboard Gigabyte B650 Aorus Elite AX
Cooling DeepCool AK620 with Arctic Silver 5
Memory 2x16GB G.Skill Trident Z5 NEO DDR5 EXPO (CL30)
Video Card(s) XFX AMD Radeon RX 7900 GRE
Storage Samsung 980 EVO 1 TB NVMe SSD (System Drive), Samsung 970 EVO 500 GB NVMe SSD (Game Drive)
Display(s) Acer Nitro XV272U (DisplayPort) and Acer Nitro XV270U (DisplayPort)
Case Lian Li LANCOOL II MESH C
Audio Device(s) On-Board Sound / Sony WH-XB910N Bluetooth Headphones
Power Supply MSI A850GF
Mouse Logitech M705
Keyboard Steelseries
Software Windows 11 Pro 64-bit
Benchmark Scores https://valid.x86.fr/liwjs3
What does this mean? CrystalDiskInfo indicates that one of my SSDs, the Samsung 970 EVO, had one such error in its history. Is this something I should worry about? Should I be contacting Samsung about this and getting a replacement?

Also, the "Number of Error Information Log Entries" is at a staggeringly high 3,427.

1662668239829.png
 
Last edited:
No. With the write levels you have that's a normal and acceptable number.

"Error Information" log always rises as it contains both errors AND standard information. Nothing to worry about yet.
 
If it was something to worry about, my 970 evo should have issues too.

Screenshot 2022-09-27 205010.png
 
Yours is slightly more worrisome, but only if it's actively rising would I worry at all. Still probably fine.

It's not doing much these days, use it for backup storage.

This drive used to be my Windows 10 OS drive.
 
It's not doing much these days, use it for backup storage.

This drive used to be my Windows 10 OS drive.
Yeah I think I recall some 979 evos came with a weird high level of uncorrectables out of the gate. If they survive the initial surge they are generally fine though.
 
36 isnt a lot as I think that also logs the issues encountered when attempting to write to bad cells. when you are doing terabytes of data or high use hours this isnt super uncommon.

Yall should see the ECC logs on servers when it comes to ram. or even ent SSDs. bit flips are super real and would also register this.
 
all of my SSDs have this value at 0.
the only one that a couple was my first MX500 which died a couple months later.
 
all of my SSDs have this value at 0.
the only one that a couple was my first MX500 which died a couple months later.

This is about NVMe SSD's, these values aren't there for SATA SSD's.
 
Contrary to what people said in this thread, I sent it off to Samsung for the warranty and I got a new SSD back and apparently Samsung saw fit to replace the SSD for they sent me a new SSD. And not only that but it appears that they're out of stock of plain 970 EVOs so they sent me a newer 970 EVO Plus; same capacity though.
 
Last edited:
 
this look normal ,..,warnings or red color is problem

if you need
cmd
chkdsk G: /F


disk verification/repair for disk "G" ,.,.change letter and possible scan all others storage

,.,.for correct function >> correct AHCI or RST drivers or NVME driver

for my config "raid0" in oem i get lot errors ,,drivers and ROM not works under win10 correctly "MSI" :D
if exist try also bios update > this contains RST ROM and install correct drivers
"chipset version determine supported version" or RST rom / drivers >1/1 status for correct functions "example 17.1rom > 17series drivers"

and this must works perfect ! "reduce un-safe shutdowns ,..,etc"
also exist FW updates for NVME or HDD > try check manufacture web

edit
my score for OEM config
Unsafe Shutdowns: 7249
after RST repair > +1 after year or still identical
;)
 
I bought my 970 evo on Jan 15 2019, so still have warranty till Jan 15 2024, so if it dies within the warranty period I also get a new one anyway.

See how it goes.

Not sure why the number of error information log entries runs up in value, the ssd isn't actively used anymore either.

My 980 pro has 0 media and data integrity errors and 0 error information log entries.
 
That big percentage isn't lying. SSDs are built to handle some of the flash going bad. We've had these with HDDs before (bad sectors). For HDDs, the file system would just mark the sector as unusable. For SSDs, there's a small amount of unused flash capacity that is used when some of the rest goes bad.
You needn't be concerned, unless the number of errors sees a sudden spike.

In theory, even is a SSD goes belly-up, it will go into read-only mode, so you can still read it. In practice, most modern file systems want to write metadata as soon as you mount the drive, so a read-only mode drive is only readable in a specialized shop. It may be worth the trouble, depending on the value of the data on such a drive.
 

for Samsung
some older is only in AHCI mode + special NVME drivers ,.,.some new no need any special drivers :)
.,or MAGICAN SW for full info and advanced control or FW updates.
 
Contrary to what people said in this thread, I sent it off to Samsung for the warranty and I got a new SSD back and apparently Samsung saw fit to replace the SSD for they sent me a new SSD. And not only that but it appears that they're out of stock of plain 970 EVOs so they sent me a newer 970 EVO Plus; same capacity though.
They'll replace pretty much any drive you RMA so not surprised. I doubt they have time to individually check smart data on claims.
 
  • Like
Reactions: bug

for Samsung
some older is only in AHCI mode + special NVME drivers ,.,.some new no need any special drivers :)
.,or MAGICAN SW for full info and advanced control or FW updates.
Yeah, but that special Samsung driver hasn't been updated in nearly three years which in terms of tech, that might as well be dog years.
 
looks little old "2020" probarly is now better works using windows build-in driver
it just depends on what works for your system.

windows 10 it has gone through so many builds that each can be considered a separate version of the system and last builds > identical like win11
370chipset ? > oem is RST ROM 17/18 ,.,.,.try 18.37.4.1007 drivers version for SATA controller on last windows.
,,for AHCI is probarly all drivers identical "not affected performance" or 17.11-x version contains more ID for 300-series "when not works 18.37-x"

edit
or best is 1/1 ROM vs Drivers
17.5.0.4136 is bios rom > 17series drivers
 
Last edited:
Back
Top