Assistance - Calling all Samsung EVO owners

Interesting, would this explain why my bf4 maps taking longer to load? I thought it was just me but am sure they used to load much faster.

Bf4 has been on my ssd since release so that's well over the one month, for the read bug.
 
Just seen a comment on anand which links to a german site claiming samsung are to release a firmware update on the 14th October.

http://www.anandtech.com/comments/8...read-performance-bug-fix-is-on-the-way/423251

In the mean time you can restore perf by re imaging as we have found out here and it's also possible by defragging. Using a defregger that will shift all data even if it's not fragmented is best.

I used MyDefrag and the Data Disk Monthly option, with 19GB used space it generated about 40GB of writes according to magician but perf is mostly back. Boot times and app load times are faster, still remarkable how well it was managing to perform despite low reads on most of my files. Access time really is king.

Before defrag
Y6Axrzi4.png


after
nzuwaszb.png


A marked improvement but not 100% back to normal, a secure erase would be more thorough no doubt but this was much easyer and will do untill a firmware update is released. Hopefully just a few weeks to wait now.
 
You ran defrag on your ssd?......

Its not ideal but some defragging tools will re-write all data on the drive and the problem is postulated to be due to the locations where older data is losing their charge causing an overload of the ECC hardware while reading data off a higher frequency of those locations than it was designed for, defragging is one albeit less ideal way of refreshing the data.
 
Yeah don't get me wrong, ordinarily you shouldn't run defrag on your SSDs. In this case it's just an easyer means to rewrite the data in order to work around the bug vs imaging the drive. And it only used twice the amount of writes imaging would have used which is nothing especially as a one off.
 
Last edited:
You shouldn't Defrag your SSD, it dont store data like a Hard-Drive and I have heard Defrag can damage the SSD.

A lot of defraging will damage an SSD. A small amount of defraging won't damage it.

However, it depends on your definition of "damage". Every time you write data to an SSD your are "damaging" it, as SSDs have a limit on the number of times data can be written.

For the EVO SSDs, this is something like 70TB to 700TB of writes, depending on how you use it.

http://ssdendurancetest.com/ssd-endurance-test-report/Samsung-840-EVO-120

http://uk.hardware.info/reviews/417...-with-final-conclusion-final-update-20-6-2013

A single, or even several defrags will not reduce the life of the SSD significantly.
 
Do you mean 830 or maybe 840 Pro, there wasn't an 830 Pro. In any case Pro versions are not effected, only drives that use TLC NAND are effected, so Samsung 840 and Samsung 840 EVO.
 
Just heard about this issue today. Hearing a lot of people talking about an application called DiskFresh that will read and write the data restoring the drives performance temporarily. Is this harmful in any way if it's just ran as a one off?
 
I have been chasing Samsung for a solution on this and know the update is coming soon but I don't have a date on it yet. I will keep chasing them to find out when it will be released.
 
Just heard about this issue today. Hearing a lot of people talking about an application called DiskFresh that will read and write the data restoring the drives performance temporarily. Is this harmful in any way if it's just ran as a one off?
Basically with that tool you are unnecessarily wearing out your SSD. Given a firmware update is coming soon, I'd just wait.
 
Well having 2 of the samsung 840's i have been following this closely (and also suffer like everyone else :( ) and were i do think they can help the problem this "fix" is probaly gonna be more of a band aid which slows the degradation down so people dont notice it/figure it out.

Reason is a few people have done tests of putting data on to it and turning it off and putting it away for a few weeks and they are degrading also here is a video of were they had it off for 9 months and the read speed went down to 50 to 100mb/s... :( https://www.youtube.com/watch?v=GSrfOkr5hCc

Atm i am very very disappointed in my ssd's as they have slowed down a lot and it is defintly noticeable in load times now :( i really hope samsung can fix it but i have a feeling that is gonna turn out to be a hardware issue and non fixable.
 
it can also be the controller not fully maintaining/trimming the drive and performance drops off

that's why your seeing performance being restored after a secure erase,might not be the actual nand degrading as that should still last for 10 years + even if its tlc
 
hang on guys...the problem lies in the TLC . how is a firmware update going to fix it? it is a logic gate level fault no software can correct that. you may be able to correlate the degradation over time for compensation, but it will get to a point where ECC cannot fix the problem and therefore you will be left with a completely useless drive...unless the controller programming is changed to periodically move the files...but then you are effectively reducing the life span of the drive...as well as needing the drive to be plugged in and powered up all the time for that to happen. so what if i am using it as a backup or storage...then i am still going to be screwed.

if it is controller level error i.e. garbage control or whatever the term is...then i guess there is a fix. but that shouldn't affect the dramatic speed drop off seen on wider community especially there are tests done to the drives which effectively rewrites the entire drives over and over to test longevity, and it is proven that the speed do not drop off that quickly. or rather nominal drop offs.

this symptom seems to be related to age of file and therefore can only be attributed to a design flaw in the nand gates...

I would be very curious as to what the update will do. personally i was looking forward to getting one of these as the price is very attractive, but I certainly won't bother now.
 
Last edited:
Back
Top Bottom