I have NET Framework 4.5.2 installed with all patches/updates as of this post. Event logs of the app crash implicate the fault is tied to NET Framework (unhandled exception) 4.0.x. I could send it by pm EDIT: i cant find anything about pm. I dont know if it is possible post link here. At least users of this forum can have something more. probably is the same with the other.but for free. 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). But anyway i want to give you the link of this EZ Gig IV.just for your information. Not through the SATA controller ports on the mobo. If it matters, when this happened, the SSD was plugged through a USB 3.0 enclosure or drive dock. Note that when the bad sectors be fixed (if it could be), all data on that sector would lose. You may need to run CHKDSK to check hard drive for errors.
![ez gig iv external erased ez gig iv external erased](https://i0.wp.com/blog.seagate.com/wp-content/uploads/2017/03/PS4-with-Seagate-Backup-Plus.jpg)
Specify a drive letter that has not been used for the current drive, such as E, F, G, etc., and click OK to save the change. When EZ Gig IV copies bad sectors, it may stick or just stop the cloning progress, which results in cloning failure directly.
#EZ GIG IV EXTERNAL ERASED DRIVERS#
Latest (or very recent) drivers available In the Disk Management, right-click the external hard drive (it shall be displayed as 'unallocated' state), and select 'Change Drive Letter and Paths' from in the menu. Windows 7 Professional 64-bit SP1 with all updates I assume this is due to the Secure Erase procedure crashing and leaving the SSD in an invalid or ‘locked’ (i.e. Tried the bootable USB tool, it can’t write to the drive, either. 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. 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 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). I hve two Ultra II 480GB drives recently purchased.