Write error during benchmark - killed the drive??

[TyantA]

Today, with my FM-25S2S-64GBF1 (Falcon 64GB), I upgraded the FW from 1916 to 2030. Ran CrystalDisk before/after and noticed some change. Performance still was lower than I'd like (185/85) so I followed the thread mentioning using Parted Magic and wrote zeroes to the drive. No problem.

Then, I tried once more to benchmark the drive and half way though it generated a write error and the drive no longer showed up in Windows or under Computer Management.

I rebooted the computer and the BIOS wouldn't detect it. I tried in another system and it was detected but hung while posting.

Is there any way to fix this?

[G.SKILL]

Hi TyantA

You need this Firmware 1916 Updated (w/ Clean Function).
Please follow this document try re-write the firmware(1916) to fix your SSD.
This step has been included "secure erase".
So you don't need erase this SSD again.

If you follow the document is can't fix your SSD, Then you need send this SSD back to G.Skill RMA it.

[TyantA]

Thanks GSKILL,

Is this procedure supported in Windows 7 64bit? This is all I have on all my machines. And should I have it in IDE mode or AHCI for this process?

Edit: This process worked! Thanks. Looks like I'm back up and running.

[GSKILL TECH]

Great! Glad to hear.

Thank you
GSKILL TECH