cancel
Showing results for 
Search instead for 
Did you mean: 

Toolbox v3.2.3 SSD Optimizer Crash

NSCL
New Contributor

Intel Solid State Drive Toolbox v3.2.3

Intel SSD 520 Series drive

Every time the SSD Optimizer is ran, it crashes with the error: "Analyzer.exe has stopped working".

This error appears in Windows Event Viewer:

Event ID 1000, Application Error. Faulting application Analyzer.exe, version 0.0.0.0, time stamp 0x535a83f1, faulting module Analyzer.exe, version 0.0.0.0, time stamp 0x535a83f1, exception code 0x40000015, fault offset 0x000097cf, process id 0x17c4, application start time 0x01cfcd19a9a82310.

And it creates 20 files named --=={Intel_Trim_File_(number)}==--.bin that fill up my entire drive.

Windows Event Viewer shows that Intel Toolbox SSD.exe creates an error Event ID 1026 with .NET 4.0, so I removed and reinstalled NET 4.0. The problem still happens. Reinstalling all versions of .NET didn't help either.

Please help ASAP because an SSD without trim is doomed.

15 REPLIES 15

Hi nwt,

Can you please try booting into safe mode and run the Optimizer there?

Kevin M

NSCL
New Contributor

It crashes in safe mode too.

Thank you for the information. I will check more and I will be back with more updates.

NSCL
New Contributor

It is now more than three weeks later and still nothing. Three weeks is unacceptable.

I have been promised that "I will need to research on this", that "we are still working on this", and several times that "I will be back soon with more updates".

But there have been no updates. Zero. Nothing at all.

I have done everything asked, even things that could easily be done by the engineers themselves if they truly were "working on this". By the looks of things here, I have put more effort into solving this than Intel.

I can't use products that aren't supported. Especially hard drives! Hard drives are critical. It is about time to write this off as a lost cause and switch all computers to a different brand.

NSCL
New Contributor

More than a month and STILL nothing.

I have given plenty of opportunity. It is now safe to assume that Intel is brushing off this bug and sweeping it under the table. Time to publish.