Assistance - Calling all Samsung EVO owners

Before!

Clipboard02.jpg


After!

Clipboard02_B.jpg
 
So I've done mine, took about an hour I think? Didn't really time it. But, I do notice a difference, boot up is faster, genmerally a little more snappier. I now realise that it had slowed down.

Before

ddYtKzw.png



After

IT44qwa.png




Does that still seem a little slow? Its the 500Gb version if it makes any difference

Redid mine with 8MB setting...

Qe85Mc5.png




Much better. :)
 
I must admit to be sceptical about this when I first read this thread but everyone who owns a Samsung EVO drive must run this. Here are my results:=

Before

before_zpsd0f28aff.png


After!

after_zps091257ac.png
 
The maximum read speed is sensitive to the CPU clock speed. For 8MB block, I get maximum read 515MB/s at idle CPU speed 0.8GHz, and 530MB/s at speed 4.4GHz.

For 64KB, maximum read 400MB/s at idle CPU and 450MB/s at 4.4GHz.

Rapid Mode makes no difference to the HD tune benchmark and boot time. I guess I should just disable it.
 
Last edited:
2 spins, before this fix it was about 3-4, so I have noticed a slightly quicker bootup.

edit- Sorry I was looking at my windows 7 bootup, which doesn't even have a cog spin so I don't know why I responded ha. Tired I guess... but yea 7 bootup does seem a bit faster.
 
Has anyone else experienced an error during the restoration process, around 85% ?

I`ve seen this on the 3 updates I`ve done so far. All that seems to be needed is to click on "start" and the retoration continues from 80% and completes succesfully.

Make that 4 updates, it's just happened again.
 
Last edited:
Has anyone else experienced an error during the restoration process, around 85% ?

I`ve seen this on the 3 updates I`ve done so far. All that seems to be needed is to click on "start" and the retoration continues from 80% and completes succesfully.

Make that 4 updates, it's just happened again.
Only happened once for me.
 
Only happened once for me.

Have you done an update when it worked without the error ?

I`ve just got off the phone from another customer who said that he had to click "start" to get the restoration to complete. I`ve got a fair few more to do, and I'm expecting this to happen every time.
 
It's odd.

It happened with my own machine, an i3 based laptop, an older (SATA 2) Intel dual core laptop and a Haswell based desktop that I built about 2 months ago. All different machines, and all downloaded the update from the Samsung website.

The only thing I can think of so far is that I installed Avast Free on all of them. Maybe that interferes with the resoration process for some reason.

I`ve got a customer updating his overclocked i5 Haswell as I type. I`ve warned him that it might stop around 85%, and to just start it again. I'll find out later if it did happen.
 
Have you done an update when it worked without the error ?

I`ve just got off the phone from another customer who said that he had to click "start" to get the restoration to complete. I`ve got a fair few more to do, and I'm expecting this to happen every time.
Worked fine first time for me.
 
Have you done an update when it worked without the error ?

I`ve just got off the phone from another customer who said that he had to click "start" to get the restoration to complete. I`ve got a fair few more to do, and I'm expecting this to happen every time.
My own drive update stopped at 84% and I had to click start again, but 2 others I did for friends went without any error. Weird.
 
The customer who I left with the update earlier has reported that his updated without the error.

Just got off the phone to another customer who had the error (HP AIO PC).

Oh, and the customer before that (Lenovo i3 laptop) also had to hit "start" to get it to finish.

It's not a big problem, but something's not quite right.
 
Last edited:
It's odd.

It happened with my own machine, an i3 based laptop, an older (SATA 2) Intel dual core laptop and a Haswell based desktop that I built about 2 months ago. All different machines, and all downloaded the update from the Samsung website.

The only thing I can think of so far is that I installed Avast Free on all of them. Maybe that interferes with the resoration process for some reason.

I`ve got a customer updating his overclocked i5 Haswell as I type. I`ve warned him that it might stop around 85%, and to just start it again. I'll find out later if it did happen.

I don't have avast on my machine so still a possibility. I guess if one AV causes issues there may be others that do too. If we can find a common theme for who has issues then maybe we can help others avoid it...

Success for me was on an old i5 750 on p7p55d le mobo (sata 2) with most of the drive empty (~70%) all set up as a single partition and a secondary HDD for storage. OS: Win 7 x64, AV: MSE (I know, really should replace it as it's no longer competitive but most AV are just too annoying)
 
The firmware update and restore worked without any issues on my 1tb Evo 840 (PC in sig), I use Avast antivirus.

On my grandfathers laptop with a 250gb Evo 840, the firmware update went ok, but the restore failed at 82%, clicked start again and it went through just fine.

My grandfather uses the same Windows 8.1 Pro x64 and Avast antivirus.
 
Thanks for the info.

There doesn't seem to be any common denominator so far. At least the process completes, and doesn't seem to cause any further problem.
 
Back
Top Bottom