F120 SSD Random Kernel-Power 41 BSOD; Not Detected on Boot

[biatche]

Mine stays at 1 without restarting. Strange.

[Mummy]

So puting 2 of F60 in Raid0, was good choice? ..as Trim dont work, for Raid array

Edit; Dont know why, but on firsth w7 install 8.9 drivers, didnt work on sleep mod. Now at secend clean install, they seems to work.

[biatche]

perhaps my experience with raid and black screen of death was coincidentally caused by something else.

[Mummy]

@dikai_yang; If its that trim, where that 10hours + get to do with this?

Edit: You worked so hard that it didnt get idel even for coffee breack?

[dikai_yang]

I'm actually at work now. I Every so often vnc connect to my computer remotely to see if it's still running. It's always a good thing to know it has Not restarted on its own.

About 8.9.0.1023 not having sleep/wake issue, I can't guarentee that one. I justed tested it a few times and it worked. Because with rst 9.6, it doesn't work not even once. If I do find 8.9.0.1023 bsod on me on wake I'll just set disabledeletenotify to 1 on ms ahci. But that's a secondary issue at this time. I'm still trying to make sure the random restart problem is fixed.

If you're using raid on rst 9.6 trim does get sent through. So in theory your comp should bsod eventually. But on 8.9 or ms ahci with trim disabled, it would probably work. But don't take my words for it. We're working on a single ssd set up in this thread.

[biatche]

trim doesnt work with raid, but other ssd drives running single will have trim pass through support.

[Mummy]

Yep,
Trim Dont work in SSD's that are in Raid mode. Not even 9.6.

[dikai_yang]

Yup. Biatche is right. If bios is set to raid (vs IDE/ahci), trim still works on single ssd not in an raid array. (Rst 9.6 only). See how hard I'm working I'm getting forgetful now

[dikai_yang]

Alright. I will declare that the problem is solved. Corsair tech support should add disabling trim to their solution list for people who have random restart/bsod/drive not detected by bios after reboot. fsutil behavior set disabledeletenotify 1 solved the problem

[Xenn0X]

my system is running 14 hours straigt and no failures more. even made it through th night.. only disabled trim with fsutil behavior set disabledeletenotify 1..

just like we thought dikai_yang.
drive needs a firmware update asap to fix trim..

[biatche]

So good so far across 2 pcs. After so many posts, and trying all kinds of funny stuff, I find it pretty amazing the users actually found the culprit, more so than the makers themselves -- sandforce actually.

[Xenn0X]

Originally Posted by biatche

So good so far across 2 pcs. After so many posts, and trying all kinds of funny stuff, I find it pretty amazing the users actually found the culprit, more so than the makers themselves -- sandforce actually.

like i said before, if a different brand with the exact same sandforce chip works fine on trim then this is a firmware issue.
my system still runs fine now. but trim is still essential for ssd to keep up the speed.
so hopefully someone from corsair wil use this information and fix this with an new firmware.

and mods need to make a sticky that the corsair sandforce ssd need trim disabled for now to prevent bricks or data loss.

Edit:
=====================================================================
done some more research cause i cannot stand this..
i can reproduce the error now using a custom command string to trigger the trim on windows 7.
triggers the trim on drive and a few seconds later i get 0x000000f4 and the drive dissapeared.

so i force windows to send trim command to the drive and boom, it's done, system bsod, reboots and then goes to black screen with boot error after restart.
and the drive completely gone. need to power down and remove powercable, then hold pwr button to release the juice thats still left in the system.
power back on and the drive is there again.

so here you go, it's definitely a firmware issue with trim..
no thanks, now just fix it please..

[Balder88]

How did you trigger the trim on Win7? I need to be able to make sure that the store were I bought the SSD can reproduce the error (I'm experiencing the same errors as everyone else in this thread) so that I can get a functional SSD in return (Other brand perhaps)

[Xenn0X]

Originally Posted by Balder88

How did you trigger the trim on Win7? I need to be able to make sure that the store were I bought the SSD can reproduce the error (I'm experiencing the same errors as everyone else in this thread) so that I can get a functional SSD in return (Other brand perhaps)

using Delphi to send the command.
also after some googling i found a custom tool on that does the same, works only on sandfore ssd's
if you use it run in with with administrator permission.
i do not know if this app uses the windows 7 commands to trim so this might work or not. not my work.

they way i tested i get it to fail.

but i do not think you get get this drive swapped out for an other cause it's no defective but needs a proper firmware.

[biatche]

Those sandforce techs or whoever's responsible should be ashamed of themselves. Letting the users go through so much difficulty to find the culprit while we're paying for it.