Jump to content
Corsair LogoCorsair Logo
Corsair Community
CORSAIR COMMUNITY Survey, we want to hear your feedback!

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

dikai_yang

Recommended Posts

saikoh

saikoh

Posted
Posted
Well, I've loaded Win 7 - 32-bit on a Gigabyte EP45-UD3P test system. With a fresh load of windows and the ForceTrim program, I cannot re-create your error. No other drivers / programs loaded. Just load Win 7 and test.

 

Mind you, I've had my own issues with this drive: http://forum.corsair.com/v3/showthread.php?t=88741

 

I've let it idle for 12 hours and no crash....I'll test Win 7 x64 and see if this is a key element to the problem......

 

I have a similar motherboard, Win 7 x64. The ForceTrim program does not trigger the problem either for me. The system still BSODs and 'loses' the drive on average once a day tho. But the time varies - on occasion it can go on working up to 72 hours (so 12 hours might not be enough for a reliable test) while another time itll crash twice within one day.

Link to comment
Share on other sites
  • Replies 623
  • Created
  • Last Reply
dikai_yang

dikai_yang

Posted
  • Author
Posted

This is the greatest post yet from Corsair.

 

The components that can possibily be involved in the compatibility issue: motherboard, chipset, windows version, and driver version.

 

Now, this does NOT work (very general)

i7 motherboard with ICH10R (very common for all of us)

Windows 7 64-bit (I think everyone having the issue on this thread uses 64bit. Did someone say 32bit works?)

Driver: only works on Intel 8.9 and before. No luck with Intel 9.6 or msahci.

Link to comment
Share on other sites
andrewc513

andrewc513

Posted
Posted

Add one more to the list with this issue. I have a Corsair Force 60GB under Windows 7 x64, and it is the boot drive in my Precision 390 workstation. Every morning when I come into work, the system is sitting there saying "Drive 0 not detected", meaning it had crashed and rebooted overnight, and doesn't see it upon restarting. Turning the system off and then on again makes it pop right back up. If I remote into the machine overnight before this happens, I can reboot it so that the drive crashes during the day so I can actually see it. It's a non-descript BSOD with no stop code, and it leaves no memory dump.

 

This is very disappointing given the fact that this is the main backup system I use in my repair shop. I cannot run scans or anything overnight anymore because of this issue.

 

I appreciate the kind words previously given by the Corsair mod, but words don't exactly counteract lost productivity. I'm patiently waiting any sort of fix, whether that be a firmware update or SSD replacement, but in the mean time I still stand behind you guys, Corsair.

 

Thanks!

Link to comment
Share on other sites
  • Corsair Employees
RAM GUY

RAM GUY

Posted
  • Corsair Employees
Posted

andrewc513

The issue is slightly different that I have seen I would suggest checking with the maker of the system for the latest BIOS for the issue you have seems to maybe related to BIOS issue. ( Notice Maybe )

If you can test the drive on another system that is a little newer that may help as well.

 

I would be happy to have you send the drive and test it for you to see if that may be a problem with the drive if you like. Just let me know and we can set up a RMA for you.

Link to comment
Share on other sites
andrewc513

andrewc513

Posted
Posted

This system has its latest BIOS. I stopped auto reboot on failures last night, and I actually have a stop code now, 0x07B. Other than the different BSOD stop code, my symptoms are spot on with that of the OP. I've also tried several different controllers, including a SiL 3132 and SiL 3512, with same results.

 

I'll toss my old 250GB WDC Blue boot drive in the system and try the Force on something else and get back to you. I reckon I'll try it on my box, here's the specs:

 

Gigabyte GA-P55M-UD2 rev1.1

Core i5-750

4GB ******** RipJaws 1333

Corsair 750W PSU

 

Thanks!

Link to comment
Share on other sites
andrewc513

andrewc513

Posted
Posted

Yep, 48 hours on my personal system (above) and it works like a charm (GSATA controller, not Intel controller; Win7 x64) . Obviously the drive isn't at fault, so I guess I'm stuck until a fix of some sort comes out.

 

Off topic, but I'm still all giddy about the speed of these Sandforce drives. 286/268MB sequential read/write in ATTO and 10 seconds boots? :D::D::D:

Link to comment
Share on other sites
Yellowbeard

Yellowbeard

Posted
Posted
so we clients are suppose to wait indefinitely for a solution... is this fair? a lot of trouble, no solution, no compensation. failed product, no recall.

 

No one has stated a time frame nor have we stated indefinitely. We will make the appropriate decisions as this situation pans out. Please be patient. We have already stated that we will update the forum as new information comes along. As of now, there is no new information.

Link to comment
Share on other sites
andrewc513

andrewc513

Posted
Posted

I've noticed this issue spread across multiple threads. When a solution is reached, will there be a new sticky? I don't imagine posting in every single thread being a good method. Perhaps PMs?

 

Just wondering, in no rush. I understand it takes time to figure out issues for literally thousands of possible hardware configs. Those who are getting impatient need to chill and realize this is Corsair we're talking about. They're on the ball, not giving us some runaround or BS.

Link to comment
Share on other sites
Yellowbeard

Yellowbeard

Posted
Posted
I've noticed this issue spread across multiple threads. When a solution is reached, will there be a new sticky? I don't imagine posting in every single thread being a good method. Perhaps PMs?

 

Just wondering, in no rush. I understand it takes time to figure out issues for literally thousands of possible hardware configs. Those who are getting impatient need to chill and realize this is Corsair we're talking about. They're on the ball, not giving us some runaround or BS.

 

Most likely, there will be an entirely new post. So many of the existing threads are off topic and diluted and we will make a clear and concise announcement. However, this is not etched in stone and will most likely be decided by RAM GUY.

Link to comment
Share on other sites
sstanojevic

sstanojevic

Posted
Posted

You can add me to the list of people having occasional BSODs with the SSD F120, which is annoying considering I like to keep the computer on 24h/day. That and the fact that last time it crashed, I had a hard time getting Windows to work again...

Most of the times, the crash occurs when the computer is idle, but I've had it happen to me while I was playing Starcraft 2 :(

 

I believe I have the latest updates on everything (Windows, AMD chipset, Motherboard BIOS firmware, etc..)

I'm using AHCI.

TRIM is enabled in Windows.

And I have disabled all the sleep/hibernate options..

May be worth mentioning that the SSD is connected to a SATA 3 port, which is what now comes with my motherboard.

 

And when the BSOD happens, like others mentioned, I need to cold boot my computer for the SSD to get recognized again.

 

What do you recommend I do? You guys are giving the impression that there may be a fix on the way at some point... Do you recommend I wait and see, RMA, other?

 

Thanks

sam

Link to comment
Share on other sites
andrewc513

andrewc513

Posted
Posted

RMA's probably won't do much for us, if it's an issue between the drive's controller/firmware and certain hardware. Another SSD of the same type should give similar issues...

 

Mine is collecting dust right now. Still patiently awaiting a fix.

 

Also, I wonder if other Sandforce-based SSDs are having this issue. Like the G.Skill Phoenix Pro, Patriot Inferno, or the OCZ Agility 2.

 

If the issue was centered around the Sandforce controller and not these particular Corsair Force drives, i'd probably feel much better.... :roll:

Link to comment
Share on other sites
Bergkamp

Bergkamp

Posted
Posted

Hi everyone,

Just registered to said that I have been using the F60 SSD for about a month (following this thread too), using Win7 32bit without a single BSOD or drive not being recognized in bios problem.

 

I have a P5K-E wifiAP mobo, ICH9R controller using AHCI and the latest Intel Rapid Storage driver.

 

Hope this help a little.

Link to comment
Share on other sites
Yellowbeard

Yellowbeard

Posted
Posted
You can add me to the list of people having occasional BSODs with the SSD F120, which is annoying considering I like to keep the computer on 24h/day. That and the fact that last time it crashed, I had a hard time getting Windows to work again...

Most of the times, the crash occurs when the computer is idle, but I've had it happen to me while I was playing Starcraft 2 :(

 

I believe I have the latest updates on everything (Windows, AMD chipset, Motherboard BIOS firmware, etc..)

I'm using AHCI.

TRIM is enabled in Windows.

And I have disabled all the sleep/hibernate options..

May be worth mentioning that the SSD is connected to a SATA 3 port, which is what now comes with my motherboard.

 

And when the BSOD happens, like others mentioned, I need to cold boot my computer for the SSD to get recognized again.

 

What do you recommend I do? You guys are giving the impression that there may be a fix on the way at some point... Do you recommend I wait and see, RMA, other?

 

Thanks

sam

 

Some issues have been attributed to the Gigabyte BIOS. Do you have the most recent BIOS? Please list the BIOS version and if you have it, the date on the BIOS.

Link to comment
Share on other sites
dikai_yang

dikai_yang

Posted
  • Author
Posted

I started this thread a while back. I think there's something we should try and i haven't gotten a bsod for one night (I know, not very comforting but try this with me).

 

in power option, Do not set "turn off monitor after x minutes". Not just no sleep. Set this in the power options.

Disable disk write caching for the force ssd from device manager

enable trim, fsutil behavior set disabledeletenotify 0

download and install intel rst 9.6.4.1002 (google it)

restart

 

trim might work without bsod

sleep and wake no longer causes bsod

 

edit: make sure it's the 9.6.4.1002 driver and NOT the currently-available 9.6.1

 

please try and let us know your experience. Note, not turning off the monitor might not be necessary for you, it's more for me. If windows turns off the monitor while I try to remote connect via ultravnc the computer would be unresponsive for a minute or so. But if you use the mouse to gain direct control, there seems to be no problem.

Link to comment
Share on other sites
djbigbear

djbigbear

Posted
Posted

i think mine work the other way around.

when i set to turn off monitor, it stays on till morning

when i set not to turn off monitor, it left me with fail raid array in the morning.

currently i'm setting it 30 mins to turn off monitor, and haven't turn off write caching, if i got another bsod i might try turning off write caching and see if that might cure it for a while.

Link to comment
Share on other sites
sstanojevic

sstanojevic

Posted
Posted
Some issues have been attributed to the Gigabyte BIOS. Do you have the most recent BIOS? Please list the BIOS version and if you have it, the date on the BIOS.

as indicated in my specs, I have the v2.0 of the motherboard, and the FD revision of the BIOS, which is the latest, and dated the 2010/07/23 on their site.

 

From what you know with other people's issues with the Gigabyte BIOS, do you think I should open a case with them, or can I expect that you guys will be the ones to fix something on your end?

 

your help is appreciated. And as long as there is light at the end of the tunnel, I am more than willing to be patient. I know all too well how hard it can be to deal with bugs/issues that are very hard to reproduce, or when multiple factors are at play.

Link to comment
Share on other sites
Yellowbeard

Yellowbeard

Posted
Posted
as indicated in my specs, I have the v2.0 of the motherboard, and the FD revision of the BIOS, which is the latest, and dated the 2010/07/23 on their site.

 

From what you know with other people's issues with the Gigabyte BIOS, do you think I should open a case with them, or can I expect that you guys will be the ones to fix something on your end?

 

your help is appreciated. And as long as there is light at the end of the tunnel, I am more than willing to be patient. I know all too well how hard it can be to deal with bugs/issues that are very hard to reproduce, or when multiple factors are at play.

 

Gigabyte is already aware of the issue. Watch their site or check with them directly to see if there is a newer BIOS.

Link to comment
Share on other sites
djbigbear

djbigbear

Posted
Posted

as for my motherboard, the latest bios i can find is the beta bios F7W dated august 2nd 2010

so i don't think this is the bios mentioned. i'll keep my eyes opened.

 

@yellowbeard

i'm still expecting your email btw ;)

*update*

thank you, email received ;)

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

Go to topic listing
×
×
  • Create New...