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 Event Name: APPCRASH
Application Name: Intel SSD Toolbox.exe
Application Version: 188.8.131.520
Application Timestamp: 53c8395c
Fault Module Name: Intel SSD Toolbox.exe
Fault Module Version: 184.108.40.2060
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.
Additional research, followed by additional commentary:
Related posts include:
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.
Note that for a HP ENVY 15t-3000 CTO Notebook PC, this really was a premium-priced upcharge at dollars per GByte. Even now:
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:
If you had actually read the post, or looked at the first screen shot, you'd see that I did:
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.
Can you please attach here your System32 report? Have you tried connecting it to a different SATA ports and using different cables.
Is this happening when the SSD is connected to another computer?