Community
cancel
Showing results for 
Search instead for 
Did you mean: 
AAmbr
New Contributor I
2,587 Views

SSD Toolbox crashes after launch

Jump to solution

Since the purchase of my Intel SSD drive (Intel SSD 335) I am unable to run the SSD Toolbox software. I have tried with the then-current version (3.1.0) and three consequent versions (3.2.0, 3.2.1 and lastly 3.2.3).

The issue is always the same - I install the software without problems, but after launching the application it crashes with the typical Windows' "application has stopped working" modal.

I have contacted support a few times already with this issue, but it's gone nowhere; today I performed two tests with the software:

I installed the SSD Toolbox on another computer, where it had no problem with running (note: there are only HDDs installed on said computer), while on my laptop (where my SSD is installed and used as the only/primary disc) the toolbox kept crashing (always referencing a faulty msvcr90.dll - multiple versions, removals, reinstalls or updates did not help at all.).

So, using Microsoft's Dependency Walker I ran the software on both PCs, with 'Profiling' option on and after reviewing the logs I found one difference - some libraries aren't being run/loaded on the 'faulty' machine. The diff of both logs is available at this link - http://www.diffchecker.com/j4p4joi4 http://www.diffchecker.com/j4p4joi4 - on the left is the log of the 'running' machine, on the right the faulty one.

They are pretty much the same (only the addresses change) until the line 1812, where the 'OK' machine runs a few wintrust.dll & setupapi.dll functions, while the other one doesn't at all. After few more lines, at 1850, an exception occurs on the 'faulty' one, which then propagates to the end of the log and the program termination.

I'm using (on both machines) Windows 7 64-bit. I'll be happy to supply more debug data if requested.

Tags (1)

Accepted Solutions
AAmbr
New Contributor I
293 Views

bump?

//EDIT: Okay, it seems I figured it out

What I did was I opened the Intel Turbo Memory Console, unchecked both Windows ReadyBoost and Windows ReadyDrive functions (restarted the pc when prompted both times), opened Disk Management, right-clicked the IMD-0 drive and set it to offline, uninstalled the Turbo Memory driver, restarted, and voilà.

Device Manager is now showing an unknown device, there is no extra drive in Disk Management, and Intel SSD Toolbox 3.2.3.400 runs perfectly fine.

So I guess my year-long issue is solved

(now another question arises - is there any way I could get the Turbo Memory thing working as a paging partition and still use the Toolbox? Hm hm... But let's leave that for another thread )

 

//EDIT2: okay, so I fiddled with it some more and reinstalled the Turbo Memory driver. After the compulsory restart I opened Turbo Memory Console, disabled ReadyBoost (& rebooted), disabled ReadyDrive (& rebooted again), formatted the 1.3GB partition with NTFS and assigned a letter to it, and now I can use both disks while being able to run SSD Toolbox the new partition isn't showing up in the Toolbox, but I guess that's not a problem.

 

View solution in original post

19 Replies
Jose_H_Intel1
Employee
293 Views

Hi eidam655, thank you for posting in Intel Support Communities.

I suggest you repairing your Microsoft* .NET framework installation; this is very easy to accomplish by opening Programs and Features, highlighting this software component and clicking Uninstall/Change and then you can click Repair. I am very positive this will help because the log appears to be pointing at it.

I also found after a quick online search that msvcr90.dll is related to the http://www.microsoft.com/en-us/download/details.aspx?id=26368 Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package. Uninstalling and reinstalling this package may help too.

AAmbr
New Contributor I
293 Views

hi Joe,

i tried repairing the .NET 4.5.1 package installed and also tried to uninstall and reinstall all the Visual C++ 2008 redistributables, but nothing helped; the application still crashes after launch.

Jose_H_Intel1
Employee
293 Views

Please share more information about your system, such as: processor, chipset, SATA controller model and SATA mode (AHCI, IDE, RAID). You may also attach the msinfo32 report with the Advanced Editor (press Windows* key + R key, type "msinfo32", press OK and then File, Export).

AAmbr
New Contributor I
293 Views

i'm on a laptop (lenovo x200 tablet, 7449-fxg) with an intel SL9400 1.86GHz CPU, SATA is in AHCI mode, the SSD is the only drive in the system.

i'm attaching the msinfo32 report.

JKing16
Beginner
293 Views

I had exactly the same and went back to 3.1.6. That works fine.

AAmbr
New Contributor I
293 Views

as i wrote in the original post, i have tried it with 3.1.0... but could you perhaps link me to the 3.1.6? it's worth the try, if nothing else.

Jose_H_Intel1
Employee
293 Views

eidam655, I have sent you a PM.

AAmbr
New Contributor I
293 Views

thank you joe. i tried the v3.2.1 that you sent me, but i still get the appcrash.

Jose_H_Intel1
Employee
293 Views

Let's try with 3.1.6, again via PM.

AAmbr
New Contributor I
293 Views

thank you joe; but to no avail.

my biggest problem is that i can'r really tell why the app keeps crashing. it's obviously some kind of a magic combination of my hardware and software packages; i just wish i knew what was happening :/

can the toolbox be run from a command line with some sort of verbose output?

Jose_H_Intel1
Employee
293 Views

eidam655, I am sorry for my delayed response.

Please check the suggestion I posted here: /message/249343# 249343 https://communities.intel.com/message/249343# 249343

Let us know if this works.

AAmbr
New Contributor I
293 Views

hi joe,

i left a response in /message/249343 that thread.

AAmbr
New Contributor I
293 Views

okay guys,

SO something incredible happened

I found out that the application errorcode was c00000005, which means 'access violation exception.' so after a while of googling around i found http://stackoverflow.com/a/21765759/2708401 this answer directing me to try to create a dump file out of the crash. i created the mentioned registry keys, downloaded http://technet.microsoft.com/cs-cz/sysinternals/dd996900.aspx ProcDump 7.0 and tried to get the dump.

after few tries with the command line i got this line working:

"C:\Program Files (x86)\Intel\Intel(R) SSD Toolbox\Intel SSD Toolbox.exe" & procdump.exe -ma -e 1 "Intel SSD Toolbox.exe"

...which ran the program and immediately ran the debug process so it would catch the exception and create a dump out of it.

incredibly, when i ran it the first time this way, the toolbox ran without any crashing, straight into menu, telling me it's never been run before and that there's a firmware update etc.

so i closed the application, tried it again with the command line - and no crashes again.

HOWEVER, since the third time's a charm, i ran the command one more time - but this time the application reverted to its 'default' behavior, ie. crashing with an access ciolation exception.

good news is, i've got the dump out of it and it is available at https://dl.dropboxusercontent.com/u/50406255/Intel%20SSD%20Toolbox.exe_140905_163923.dmp https://dl.dropboxusercontent.com/u/50406255/Intel%20SSD%20Toolbox.exe_140905_163923.dmp (it's 150MB though; but it could be useful to someone with app's source code, i hope )

EDIT: i should also add that i removed the files "Microsoft.VC90.CRT.manifest", "msvcm90.dll", "msvcp90.dll' and "msvcr90.dll" from their default location into a temporary subfolder. I ran the SSD Toolbox v3.2.3.

I tried running the command combo again and the Toolbox successfully launched again. The successful runs seem to be completely random, though, so i'm still a bit scared to run the firmware upgrade.

EDIT 2: you might be onto something with the TurboMemory drive thing. After the toolbox launched, there was a 1GB drive in the Other Drives category, and when i tried clicking on it, the app immediately crashed.

EDIT 3: yes, this behaviour is consistent whether the TurboMemory drive is set to Offline (through Windows' Disk Management tool) or Online, whether it's controlled by TurboMemory, or the partition is deleted, reformatted (FAT32/NTFS), the SSD Toolbox always crashes immediately after I click on this partition in the Toolbox. I'm guessing the Procmon command combo somehow delays the TurboMemory drive initialization, and that's why I'm occasionaly successful in launching the application.

This is progress, gentlemen!

AAmbr
New Contributor I
294 Views

bump?

//EDIT: Okay, it seems I figured it out

What I did was I opened the Intel Turbo Memory Console, unchecked both Windows ReadyBoost and Windows ReadyDrive functions (restarted the pc when prompted both times), opened Disk Management, right-clicked the IMD-0 drive and set it to offline, uninstalled the Turbo Memory driver, restarted, and voilà.

Device Manager is now showing an unknown device, there is no extra drive in Disk Management, and Intel SSD Toolbox 3.2.3.400 runs perfectly fine.

So I guess my year-long issue is solved

(now another question arises - is there any way I could get the Turbo Memory thing working as a paging partition and still use the Toolbox? Hm hm... But let's leave that for another thread )

 

//EDIT2: okay, so I fiddled with it some more and reinstalled the Turbo Memory driver. After the compulsory restart I opened Turbo Memory Console, disabled ReadyBoost (& rebooted), disabled ReadyDrive (& rebooted again), formatted the 1.3GB partition with NTFS and assigned a letter to it, and now I can use both disks while being able to run SSD Toolbox the new partition isn't showing up in the Toolbox, but I guess that's not a problem.

 

View solution in original post

DSher3
Beginner
293 Views

I find it unbelievable that these threads have not been publicly addressed by Intel. Most of us who bought Intel SSD's paid a premium over some of the other 3rd party brands as we wanted Intel reliably and compatibility when using these drives as our most critical component within out machines - our boot drive with the operating system.

For Intel to release a piece of software that renders itself incompatible with the drive (ver 3.2.3) and not offer a solution is outrageous. Since my drive was working just fine till Intel's update and since it is still under warranty - my only option looks like it's going to be to return the drive to Intel and demand a refund.

Unit was working flawlessly in my Intel i7 laptop until the update. Now the Toolbox crashes 9 out of 10 times that it is launched (nothing else has changed on the drive). If it does open, it will NOT allow me to run the Optimizer. It says it can run because Volume Shadow Copy may be doing a backup. If I shut down the VSS service, then I get the message that it has to be running. I have Framework .NET version 4.5.1 on the machine. I've tried removing it and installing version 3.0 but it won't let me do that. If I go into programs remove and try to remove it under windows services, the only version showing is 3.5.1. If I uncheck all of the boxes and try to remove it... it gives error msg and says it can't complete.

Removing and re-installing ToolBox 3.2.3 allows it to open ONCE. It still won't run Optimizer due to the VSS error messages and as soon as I reboot the machine, I'm right back at the constant crashes.

C'mon Intel.... you are better than this. At the very least you could provide a link to the previous working version.

Very dissappointed!

Thx1326

DSher3
Beginner
293 Views

David Sherfy Dec 19, 2014 8:10 AM (/message/247427# 247427 in response to eidam655)

I find it unbelievable that these threads have not been publicly addressed by Intel. Most of us who bought Intel SSD's paid a premium over some of the other 3rd party brands as we wanted Intel reliably and compatibility when using these drives as our most critical component within out machines - our boot drive with the operating system.

For Intel to release a piece of software that renders itself incompatible with the drive (ver 3.2.3) and not offer a solution is outrageous. Since my drive was working just fine till Intel's update and since it is still under warranty - my only option looks like it's going to be to return the drive to Intel and demand a refund.

Unit was working flawlessly in my Intel i7 laptop until the update. Now the Toolbox crashes 9 out of 10 times that it is launched (nothing else has changed on the drive). If it does open, it will NOT allow me to run the Optimizer. It says it can run because Volume Shadow Copy may be doing a backup. If I shut down the VSS service, then I get the message that it has to be running. I have Framework .NET version 4.5.1 on the machine. I've tried removing it and installing version 3.0 but it won't let me do that. If I go into programs remove and try to remove it under windows services, the only version showing is 3.5.1. If I uncheck all of the boxes and try to remove it... it gives error msg and says it can't complete.

Removing and re-installing ToolBox 3.2.3 allows it to open ONCE. It still won't run Optimizer due to the VSS error messages and as soon as I reboot the machine, I'm right back at the constant crashes.

C'mon Intel.... you are better than this. At the very least you could provide a link to the previous working version.

Very dissappointed!

Thx1326

Jose_H_Intel1
Employee
293 Views

Thx1326, we will be glad to assist you.

Usually you will get an option to repair Microsoft* .Net Framework 4.x after clicking Uninstall/Change.

You can also try downloading the following Microsoft* Updates for Windows* 8.1 if this step above does not work for you:

I will share with you the link for an older Intel® SSD Toolbox version.

There may be different causes for this particular issue; therefore we would like to get the following information if your issue persists:

  • Operating system version. Elaborate on whether it is a fresh or upgrade installation.
  • Computer's brand and model.
  • The msinfo32 report (press Windows* key + R key, type "msinfo32", press OK and then File, Export).
DSher3
Beginner
293 Views

I am running Windows 7 64 Bit Pro. So the Windows 8 solutions do me little good. I am still waiting for the links to the previous version on Toolbox. The disappointment still remains that I have to revert back to old software due to Intel's lack of a fix.

Jose_H_Intel1
Employee
293 Views

Please take a look here: /thread/57166 https://communities.intel.com/thread/57166

Would you provide the rest of the information from the last bullets above?