ssd toolbox 3.2.3 appcrash with Intel SSD 320, Windows 7 Pro 64-bit, Microsoft .Net 4.5.1

[RW4]

The Intel SSD firmware was verified to already be up-to-date by burning an ISO (since SSD Toolbox bombs), so out-of-date firmware is not the issue:

The application brings up the GUI when run on an HP laptop with a non-Intel internal SSD.

When an Intel SSD is connected via a SATA (not USB) cable, that SSD being the problem-child internal SSD of a second laptop, the application starts to bring up the GUI, but immediately is overridden by the failure dialog.

Problem signature:

Problem Event Name: APPCRASH

Application Name: Intel SSD Toolbox.exe

Application Version: 3.2.3.400

Application Timestamp: 53c8395c

Fault Module Name: Intel SSD Toolbox.exe

Fault Module Version: 3.2.3.400

Fault Module Timestamp: 53c8395c

Exception Code: c0000005

Exception Offset: 000de447

OS Version: 6.1.7601.2.1.0.256.48

Locale ID: 1033

Additional Information 1: 0a9e

Additional Information 2: 0a9e372d3b4ad19135b953a78882e789

Additional Information 3: 0a9e

Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

The Intel app has been removed and re-installed, so that is not the fix.

The laptop has been rebooted (e.g between removal and install, and after installs), so that is not the fix.

[RW4]

Additional research, followed by additional commentary:

Related posts include:

• SSD can fail even with latest firmware

• SSD issue known since 2011.

So, both Intel (SSD manufacturer) and HP (laptop systems integrator) share in the blame for making and selecting this device, and failing to warn consumers.

The laptop is 2 years and 1 month old, from mid-2012. The intent was to get SSD performance (no rotational delays) and SSD reliability (no mechanical head crashes). On two laptops, the SSDs have actually been less reliable than some bottom-of-the-line disk.

• warranty replacement is a weak response, reactive and occurring after the fact. It doesn't proactively lead to behaviors or choices that avoid data loss.

Note that for a HP ENVY 15t-3000 CTO Notebook PC, this really was a premium-priced upcharge at dollars per GByte. Even now:

• part 668846-001 is In stock as a 300GB - Solid State Drive SATA for $ 642.68

http://h20141.www2.hp.com/Hpparts/Search_Results.aspx?mscssid=3CBC8DBE65A24CAEB0CC9E631A655FD1&Searc... http://h20141.www2.hp.com/Hpparts/Search_Results.aspx?mscssid=3CBC8DBE65A24CAEB0CC9E631A655FD1&Searc...

http://h20141.www2.hp.com/Hpparts/part_where_used.aspx?mscssid=3CBC8DBE65A24CAEB0CC9E631A655FD1&Sear... http://h20141.www2.hp.com/Hpparts/part_where_used.aspx?mscssid=3CBC8DBE65A24CAEB0CC9E631A655FD1&Sear...

[RW4]

for completeness, cross-referencing use of Linux to erase the disk (but not recover the data)

/message/145676 https://communities.intel.com/message/145676

[Kevin_M_Intel]

I am sorry you are having this problem.

I know this issue has been reported many times but I would like you to try this:

1. Update the SSD firmware to latest. Here you can get it:

https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=18363&lang=eng&ProdId=3761 https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=18363&lang=eng&ProdId=3761

1. If issue persists, try power cycling the computer. If you have laptop, disconnect the batter and press and hold the power button for about 30-40 seconds. If you have a desktop, disconnect the batter and power supply and other devices from the motherboard for about 20-30 minutes and then reconnect all components.

Kevin M

[RW4]

If you had actually read the post, or looked at the first screen shot, you'd see that I did:

1. attempt to update the firmware using that latest Intel software. However, since the firmware was up-to-date, the Intel utility provided no option to (redundantly) replace the current firmware with a duplicate instance of current firmware . Intel's software gave me no choice to do so;
2. power-cycle AND isolate the disk from power -- it was taken out of one laptop and attached by SATA cable to another.

There's plenty I don't know, and I can overlook something, but try and give me credit for the basics. I've built HeathKit, done ASIC design, written OS and driver software, delivered product from a large company, and led developments in startups. I have used hardware test gear in labs and written low-level diagnostics as part of achieving that.

And I still think that a proactive consumer recall was called for, given what is indicated on the web. Between retail price declines and tiers of margins, the hardware cost of (newer) substitutions would have been covered by the original defective product sales and by the general allowances for warranty that are applied as part of pricing strategies by corporations. It would have preserved good will (colloquial and balance-sheet) and corporate reputation.