SSD Dashboard bricked drive due to app crash

I hve two Ultra II 480GB drives recently purchased. After performing some benchmarking and testing of one drive, I decided to Secure Erase it using SSD Dashboard v1.4.1 (latest as of this post). In the middle of the Secure Erase procedure (right after the confirmation prompt), SSD Dashboard application crashed (Windows displayed notification of the app crash). After restarting the PC and SSD Dashboard, the SSD is no longer accessible or cannot be written to; SSD Dashboard reports there is a Secure ATA password set on the drive. Tried the bootable USB tool, it can’t write to the drive, either. I assume this is due to the Secure Erase procedure crashing and leaving the SSD in an invalid or ‘locked’ (i.e. bricked) state.

My system is very stable and as follows:

Intel Pentium G3220 (no overclocking)

Intel H97 chipset (Asrock mobo)

8GB DDR3 RAM (no overclocking)

Windows 7 Professional 64-bit SP1 with all updates

Latest (or very recent) drivers available

If it matters, when this happened, the SSD was plugged through a USB 3.0 enclosure or drive dock. Not through the SATA controller ports on the mobo. I tried plugging the SSD into the SATA ports on the mobo but it won’t boot at all beyond the POST screen (I assume because the drive is ATA Secure Locked). Event logs of the app crash implicate the fault is tied to NET Framework (unhandled exception) 4.0.x. I have NET Framework 4.5.2 installed with all patches/updates as of this post.

1
17 replies