KERNEL_DATA_INPAGE_ERROR (csc.sys) & UNEXPECTED_STORE_EXCEPTION

[FordGT90Concept]

About a month ago my Crucial MX100 died (lost half of the root folders in it), I returned it, and Crucial sent me back a refurb MX100. Now, maybe two or three weeks later, I'm running into exceptions again but this time, luckily, minimal/no data loss.

Just before KERNEL... BSOD, I was playing FortressCraft and an error popped up saying it couldn't save to some file in:
C:\Users\fordg\AppData\LocalLow\ProjectorGames\FortressCraft\Worlds\NOOB

That's the Crucial MX100. I'm clueless as to what is going on. Sure I have bad luck, but that bad?

Both crashes actually occurred with FortressCraft running. I should mention that FortressCraft makes my D: drive (7200 RPM Barracuda) noticeably thrash as it is writing to a log file.


I already tried disabling Fast Boot (still does it) and I'm going to update the BIOS from 1.6 to 1.7 soon (minor update, doubt it will fix anything).

 

[OneMoar]

could be a issue with the drive controller
test the drive in another machine
need the full bugcheck code that will tell you if its disk or memory
leaning toward controller/cable/ if the drive checks out in another machine
if you restored from a disk-image you might have a driver thats misbehaving

 

[FordGT90Concept]

That's all it showed on the BSOD. Looking through eventvwr, a few interesting ones come up:
-The previous system shutdown at 8:53:05 AM on ‎11/‎2/‎2015 was unexpected.
-The EventSystem sub system is suppressing duplicate event log entries for a duration of 86400 seconds. The suppression timeout can be controlled by a REG_DWORD value named SuppressDuplicateDuration under the following registry key: HKLM\Software\Microsoft\EventSystem\EventLog.
No event logs just before that.

The controller is whatever Z170 has.

%SystemRoot%\MEMORY.DMP does not exist.

 

[Parn]

I used to also have a Crucial MX100 before the current Samsung 850 Pro in my work PC.

It caused BSODs with similar types of errors you've got. The only difference was the system would BSOD/Froze while I was only browsing the web. And the system would not be able to detect the drive after the restart until it was powered off and then back on with the power button. Searching on the Internet it seemed these errors were caused by a firmware bug which would kick in during SATA Link Power state transitions. Updating the firmware to the latest version MU02 made no difference. I RMA'ed the drive and got a replacement which now sits on my desk as a spare.

Yours might be suffering from the same problem. I'd switch to another model/maker, then RMA the drive.

 

[FordGT90Concept]

The only difference was the system would BSOD/Froze while I was only browsing the web.

That is exactly what I was doing when it originally crashed and I RMA'd it. I didn't catch the BSOD that time because it was set to automatically reboot.

The one I sent back was on MU01 and the one they sent me shipped with MU02.

 

[Parn]

That is exactly what I was doing when it originally crashed and I RMA'd it. I didn't catch the BSOD that time because it was set to automatically reboot.

The one I sent back was on MU01 and the one they sent me shipped with MU02.

Firmware MU02 won't make any difference. I updated mine but it kept on crashing. The replacement I got was also factory updated to MU02. I've only used it once while I was diagnosing my new Z170 build. It hasn't been used much so I can't find out if it still suffers from the same problem.

Either Crucial has not fixed the bug in MU02 or there is a manufacture defect in some batches of MX100.

 

[FordGT90Concept]

If it does it again, I guess the logical thing to do is send it back. I mean, the OS is on it. D: only has games. If D: completely stopped responding, it shouldn't cause a BSOD because there's nothing critical on it. Both BSODs are attributed to SSD/HDD and the MX100 is really the only one that could be responsible.

 

[95Viper]

Looking around the internet... it seems from what I read, they have a problem with their MX100 line doing exactly what you all are describing and more.

There is a long forum thread, here, about some of it: MX100 will not boot sometimes

If you google it, a lot of hits for the problems. Googled Crucial MX100 bsod crashes

And, MU02 seems to be the last firmware update.

A few people attribute it to power schemes/settings/sleep states.

Try disabling link management in RST, if used; and, in the power settings of windows, if you have the options.

Try selling it and getting a different brand.

Good luck

 

[FordGT90Concept]

When it BSOD'd before I RMA'd, it was under low load. Both BSODs in the thread title, however, were under moderate/high load.

Pretty sure HDD sleeping was disabled before and after RMA. I think it was set to High Performance profile in both cases.

I disabled link management in RST just now.

I wouldn't want to dump this POS on someone else. I originally bought it from Amazon. If I RMA it and the next drive does the same thing, I'll take it up with Amazon. If Amazon's hands are tied, BBB. I think it has a three year warranty so it's all on Crucial to own up to it.

 

[95Viper]

I wouldn't want to dump this POS on someone else

You are a good soul.

 

[FordGT90Concept]

I finally figured out what was causing this: Crucial MX100 is incompatible with my Z170A Gaming M7 motherboard. I upgraded to a Crucial MX300 and no problems so far.

The Crucial MX100 has 2% of its health used and is otherwise healthy.

TL;DR: Be wary of installing old SSDs in new motherboards.



Edit: It did CRITICAL_PROCESS_DIED occasionally too.

 

[eidairaman1]

I finally figured out what was causing this: Crucial MX100 is incompatible with my Z170A Gaming M7 motherboard. I upgraded to a Crucial MX300 and no problems so far.

The Crucial MX100 has 2% of its health used and is otherwise healthy.

TL;DR: Be wary of installing old SSDs in new motherboards.



Edit: It did CRITICAL_PROCESS_DIED occasionally too.

Id take a hammer to that drive.

 

[Toothless]

Id take a hammer to that drive.

See now it's a good drive for say, a Z77 chipset and older but not anything newer. Had the same issue with my OCZ Petrol drive which works perfectly in my HP 1368dx laptop.

 

[FordGT90Concept]

Yeah, the original MX100 and refurb MX100 did the exact same thing in my system. Both were healthy.

 

[Parn]

MX100 always had flaky firmware causing all sort of issues. Ditched them for 850pro.