Personal computing discussed
Moderators: renee, morphine, Steel
just brew it! wrote:Not sure what page you're looking at, their main SSD firmware download page (http://www.samsung.com/global/business/ ... loads.html) includes the April 15 EXT0DB6Q firmware release for the 840 EVO.
cobalt wrote:And here's my "after" result. I gotta say, it's the slow access times that worry me possibly even more than the slow reads. At some point I suspect it will have degraded so far it won't be able to read that data at all. I'm happy that the access times are fixed as well.
As per Chrispy's advice, set DiskFresh to launch once a month.
(And thanks, all, for the moral support and advice!)
Welch wrote:He act of writing an image to the drive itself would refresh the cells. However to answer your question, the firmware is responsible for periodically refresh the cells to avoid the read performance degradation. The software however has a faster refresh function that does the entire drive in case you don't want to wait for a specific affected area to be refreshed. If you arsn't feeling large hits in performance or you aren't in some rush then simply let the firmware do its job. Using the software to perform the "fix" actually wears down the drive faster and eats up some of your drives lifetime write cycles before it reaches end of life.
morphine wrote:Arguably, just installing the firmware and letting the drive take care of it is easier
localhostrulez wrote:Yep, I've washed my hands clean of Samsung garbage. Same with Crucial - talk about firmware bugs. Seems like Sandisk is my SSD vendor at the moment - an M500 resulted in constant crashes when I tried to run Windows Updates on a Windows 7-equipped 6530b (really, a drive that's only half stable, and passed QC?). Although I do have another 6530b with a different M500 that works all right. But meanwhile, a Sandisk Ultra II did the job just fine where the M500 barfed, and the machine feels a bit faster too. (Somehow M500's make Windows feel a tad slow for an SSD. Turns out that the issue isn't the Core 2 in that machine, it's that M500's are just sluggish.)
morphine wrote:Arguably, just installing the firmware and letting the drive take care of it is easier
I couldn't flash my drive because I think there's an issue with using Magician to flash the firmware when the drive is hooked up to an AMD chipset
Deanjo wrote:localhostrulez wrote:Yep, I've washed my hands clean of Samsung garbage. Same with Crucial - talk about firmware bugs. Seems like Sandisk is my SSD vendor at the moment - an M500 resulted in constant crashes when I tried to run Windows Updates on a Windows 7-equipped 6530b (really, a drive that's only half stable, and passed QC?). Although I do have another 6530b with a different M500 that works all right. But meanwhile, a Sandisk Ultra II did the job just fine where the M500 barfed, and the machine feels a bit faster too. (Somehow M500's make Windows feel a tad slow for an SSD. Turns out that the issue isn't the Core 2 in that machine, it's that M500's are just sluggish.)
Odd, I haven't had a single issue with the M500's I have (500, 250 and 120 varieties).
Chrispy_ wrote:I couldn't flash my drive because I think there's an issue with using Magician to flash the firmware when the drive is hooked up to an AMD chipset
Could potentially be the AMD chipset I suppose
-------------------------------------------------
| Chipset | Driver | Supported |
-------------------------------------------------
| Intel | Microsoft | Yes |
| | Intel | Yes |
-------------------------------------------------
| AMD | Microsoft | Yes |
| | AMD | Yes(With Latest Driver) |
| | NVIDIA | Yes |
-------------------------------------------------
Samsung Magician v.4.5 Introduction and Installation Guide wrote:
General Limitations
18) Firmware Update may fail on Samsung brand SSDs connected to AMD Controller.
Please retry using default sata ahci controller(Microsoft drivers)
DOS Utility Limitations
1) The DOS Utility is not compatible with pure SCSI or SATA NVIDIA/LSI/AMD chipset
drivers
RAPIDmode Limitations
10) Sometimes on AMD PC with AMD and ASMedia storage controllers it was found
that the IOs takes a longer time to complete. In such cases if Rapid was
enabled, it may get automatically disabled due to such IO errors. It may
display "Rapid is in inactive state". User has to reboot the PC to enable the
Rapid back.
11) If multiple iterations of Read and Write are performed, RAPIDmode may
become inactive due to system internal errors on some of the AMD /
AsMedia Controller or Driver.
Chrispy_ wrote:If you read back through the thread you'll see that the built-in benchmark is worthless, people posting the Samsung results giving the all-clear, whilst actual full-drive scans from HDTune or HDTach showing horrific, slower-than-5400rpm-drives transfer rates with huge access times.
just brew it! wrote:Hance, which Samsung do you have (840 or 840 EVO), and what firmware version are you running on it?
ronch wrote:Hey guys, just curious.. Since I got my 250GB 840 EVO back in Dec. 2013, Samsung Magician gives me these benchmark scores. Are these in line with what you guys are getting? Other pertinent hardware: FX-8350, Gigabyte 990FXA-UD3 rev. 4 (this is my second AM3+ mobo; my first board, an MSI 990FXA-GD65, gave me the same bench scores as well), 2 x G.skill 4GB DDR3-1866, Hitachi 1TB HDD, an LG DVD-RW drive. Been using different versions of their chipset drives, and right now I'm using their latest. Windows 7 64-bit Ultimate. BIOS set to AHCI, not IDE or RAID. Firmware is EXT0CB6Q. Latest is EXT0DB6Q but I'm not sure I wanna flash it since it just rewrites data on the SSD automatically and may potentially reduce the SSD's life. I use DiskFresh instead. Obviously, when I got this SSD the firmware in it was older so I obviously got the same numbers using those older firmware versions.