Has anyone worn their SSD down to 0%

iv noticed watching youtube videos causes writes to occur. seems the entire video is buffered from disk and not ram. 4k video has a lot of writes. and sometimes i have music videos running in one tab and that adds up to the writes.
browsers should really change the way youtube content is streamed and just use ram buffer for it and not disk.
 
my 970 EVO before I pulled it out was at 11% life.

It seems two things affect this counter.

Spare sectors and erase cycles, not just erase cycles.

The short story below.

After getting a RTX 3080, I was forced to ditch my win 8 install for win 10 as the drivers for the card only support win 10 so I got to work on the migration.

Part of this work was doing a backup of my D: drive which is my gaming partition on the boot ssd (in this case the 970 evo which by the way is only 13 months old).

Macrium reflect failed with a unable to read CRC error.
I kept retrying.
I then noticed on every attempt not only was the data integrity error in smart increasing but also available spares were slowly going down.
I then read on macrium support pages to try and stop the error so the backup can be completed it was advised to run chkdsk /r to reallocate sectors, so I did this.
At this point on each run of chkdsk /r the spare went down crazy fast and I was eventually able to read the data when it was down to 11.

I dont have much hope for a successful RMA as samsung are known for been super stingy and amazingly samsung magician claims there is no issue with the drive with over 3000 data errors and down to 11% available spare sectors, diskinfo reports a fail threshold as 10, but it stopped going down at 11.

For what it is worth I think this is nothing to do with nand expiry, I think I had a dud from the start, I remember posting on here some months back that the drive registered its first data integrity errors after only a few months of use, which in my experience will lead to eventual failure if ignored. That is why I have an opinion that manufacturer diagnosis tools should report failure imminent the moment a single warning counter increases as in healthy hardware they stay at 0. But obviously they want to keep RMA numbers down whilst advertising lengthy warranties so they dont do this.
 
iv noticed watching youtube videos causes writes to occur. seems the entire video is buffered from disk and not ram. 4k video has a lot of writes. and sometimes i have music videos running in one tab and that adds up to the writes.
browsers should really change the way youtube content is streamed and just use ram buffer for it and not disk.

In chrome based browsers you can change this behaviour (not sure why it isnt default).

goto the expiremental flags page and look for this, its labeled as a battery life saver, but I think it has much bigger benefits.
Set it to enabled and restart the browser.

Code:
Turn off caching of streaming media to disk.
Reduces disk activity during media playback, which can result in power savings. – Mac, Windows, Linux, Chrome OS, Android

#turn-off-streaming-media-caching-always

But be warned these flags can just be removed without warning or even reset to default on a browser update. So check it every now and again to make sure sticks, I expect firefox can do the same in its flags somewhere.
 
In chrome based browsers you can change this behaviour (not sure why it isnt default).

goto the expiremental flags page and look for this, its labeled as a battery life saver, but I think it has much bigger benefits.
Set it to enabled and restart the browser.

Code:
Turn off caching of streaming media to disk.
Reduces disk activity during media playback, which can result in power savings. – Mac, Windows, Linux, Chrome OS, Android

#turn-off-streaming-media-caching-always

But be warned these flags can just be removed without warning or even reset to default on a browser update. So check it every now and again to make sure sticks, I expect firefox can do the same in its flags somewhere.


confirmed this method works. no more full on disk writes when watching youtube vids. there is still some random kb's being written but no more sustained megabytes that i normally used to see. someone should sticky this cant believe that i would not have come across this solution if i had not asked.
i did google "youtube ssd wear" but no solution like yours came up. excellent.
 
This is on by default in Edge Chromium. The option only exists thanks to MS - they saw it was a problem and fixed it in Edge, google then applied the fix upstream to chromium but for whatever reason didnt disable caching by default.
 
On the 970 evo it is out the system now, will test in ryzen rig to see if symptoms are same, if yes will go for RMA.

I was reminded why I hate m.2 slots though, very fiddly the tiny screws, took me nearly an hour to put screw back in empty slot.

This is on by default in Edge Chromium. The option only exists thanks to MS - they saw it was a problem and fixed it in Edge, google then applied the fix upstream to chromium but for whatever reason didnt disable caching by default.

Yeah microsoft have contributed some good things to chromium.

There is a thread somewhere on their (google) dev page, where me and a few others reported some stuff which causes massive writes. The obvious one is cache, which is easy to deal with by moving to another drive (I put on ram disk), but in recent years they have been adding more and more scratch data written all to the c: drive non configurable, there is even a virtual filesystem now where sites like meganz will write there for no obvious reason before copying to your destination folder, I observed yesterday I had 7 gig in that folder with files a year old never cleaned out by any kind of maintenance. Then there is all the databases, many of which are duplicates, and when you debug and watch what chrome is doing its quite an eye opener. On my system it is likely easily accountable for 90% of my writes.
 
This is on by default in Edge Chromium. The option only exists thanks to MS - they saw it was a problem and fixed it in Edge, google then applied the fix upstream to chromium but for whatever reason didnt disable caching by default.

just read up about this and from the looks of this the change was made for battery saving reasons. nothing mentioned about ssd wear. odd.
 
Back
Top Bottom