Crucial MX100 512GB - unlucky?

JamesLit

New member
Hi all,

I've been having some mysterious and pretty major system issues recently. The longest running problem is that Windows will randomly bluescreen, with no trend in any possible causes etc. It will restart literally immediately and upon trying to boot will tell me it cannot access the boot device - my Crucial MX100 512GB SSD, which is only 9 months old.

It will keep giving me this error until I (safely) swap the SATA cable to a different slot in the motherboard. After I do this it will work fine until the crash happens again. All I can think of is that the data flow between the SSD and the system seems to be just... well, stopping. I've troubleshooted every other conceivable part and driver, got everything updated and checked etc, done all kinds of validations, memory checks, you name it. All I can think of is that.

What I'd like to know is if you guys agree or if something else might be at fault. I've tried every different SATA slot and every different SATA cable I have. The only constant variable has been the SSD itself.

If it IS the SSD that's causing the problem, does this sound like something that can be fixed (not holding my breath, here) or am I going to have to get a new one?

Which also then brings me onto Crucial themselves - as this is a fairly weird problem in my experience, what support, if any, RMA wise are they likely to be able to provide? I can't just send it to them, I need to back up my data which will take up more room than I've got right now, and obviously that means I'll also be without a PC - which is crucial to my work as well as your typical gaming stuff. What are you guys' experiences with Crucial's support?

All the best and TIA.
 
Get your drive RMA'd with Crucial, they have a great customer care service and are genuinely courteous. They will test the drive and either repair it and extent the warranty or replace it completely.
 
Get your drive RMA'd with Crucial, they have a great customer care service and are genuinely courteous. They will test the drive and either repair it and extent the warranty or replace it completely.

Well that's pleasing to hear, I've had some bad experiences with other companies in the past. Only problem with that is, as described, I can't really be without access to my PC. I suppose I'll have to liaise with them as to the best course of action - but at least I can have faith in their process. :)
 
Well that's pleasing to hear, I've had some bad experiences with other companies in the past. Only problem with that is, as described, I can't really be without access to my PC. I suppose I'll have to liaise with them as to the best course of action - but at least I can have faith in their process. :)
You can always be a touch cheeky and communicate with them through Facebook as well while the RMA is being carried out. ;)
 
Are you sure it's not motherboard's fault?

A bad OC could create issues if you touch the wrong values...
 
You can always be a touch cheeky and communicate with them through Facebook as well while the RMA is being carried out. ;)

That's a good idea. :D

Are you sure it's not motherboard's fault?

A bad OC could create issues if you touch the wrong values...

Hmm, well I had previously gotten my CPU up to 4.8Ghz (this is a 4790k with closed loop water cooling in the form of a Corsair H105 in a nice and roomy case) but it was unstable under heavy load at that clock so I put it down to 4.6GHz and haven't had any issues that have been attributed to anything like that since.

I could try 4.4GHz I suppose but then that means another performance hit, and more importantly, it could take ages before I find out - if I do - whether that does the trick. I guess I might try it anyway to see if it solves any other issues but I'm pretty skeptical as to it possibly causing these BSOD and boot issues. I can't really see why a clock would do that, in all honesty - even if voltages were dodgy, how would they magically become fixed upon changing the SATA port being used? I've overclocked it using ASUS' own utilities (I have an ASUS mobo) and it's only over the past month or two (bearing in mind I built this system last year) that I've had these problems - despite everything being the same the whole time.
 
I could try 4.4GHz I suppose but then that means another performance hit, and more importantly, it could take ages before I find out - if I do - whether that does the trick. I guess I might try it anyway to see if it solves any other issues but I'm pretty skeptical as to it possibly causing these BSOD and boot issues. I can't really see why a clock would do that, in all honesty - even if voltages were dodgy, how would they magically become fixed upon changing the SATA port being used? I've overclocked it using ASUS' own utilities (I have an ASUS mobo) and it's only over the past month or two (bearing in mind I built this system last year) that I've had these problems - despite everything being the same the whole time.


Try using BIOS fail safe defaults, then optimized defaults ( if AHCI is not in the default configurations, put it back on )

Don't use software utilities for overclocking, especially for daily OCs.
 
Back
Top