06-10-2015 09:35 AM - edited 06-10-2015 09:36 AM
I believe I'm not alone when I say that I've been experiencing the 'Internal Error' issue with Crucial Storage Executive version 3.20.
I have tried a few things to resolve the problem, which include:
So far none of this has helped in the slightest, the program will load and give the Internal Error message. Nothing more.
I didn't have this issue with the previous version of CSE, interestingly enough I also installed CSE on my PC and ironically, it does work; even though I don't even have a Crucial SSD installed in my PC. To clarify, this problem is happening on my server, the SSD is a MX200 250 GB
I have uploaded the CSE log to pastebin for the techs to look at, here is the link: http://pastebin.com/xQd1Rgig
Thanks in advance.
06-19-2015 10:33 AM
I have tried all the exact same things without success. Oddly technical support seems to think this is a most unusual problem. Also the old version of the program simply disappeared off my desktop one morning and so I downloaded the new version which does not work. Please let me know if a solution becomes available.
06-20-2015 07:26 AM
Oddly technical support seems to think this is a most unusual problem.
This does seem to be the case, judging by the current lack of response by any Crucial rep. I've yet to find any solution myself, I guess only time will tell.
07-17-2015 09:18 PM
07-22-2015 07:59 AM
I have this error on a Windows 7 32 laptop. I have also got it to run on a Windows 8 x64 - but only because the drive itself failed, corrupting the boot sector and somebody suggested a firmware issue. Frankly I wouldn't have bothered except I really wanted the data back as the CSE software corrupts everything and it took some work including mounting the SSD MX100 in an external harness to recover it. Now I have done all this I would like the software to work.
08-17-2015 11:52 AM
I have the same problem :-
Brand new MX200 1TB drive.
Windows7 64 bit
Running in AHCI mode - no RAID.
Press the Update Firmware button and I get an Internal Error.