Jump to content
Corsair Community

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


Recommended Posts

  • Replies 623
  • Created
  • Last Reply

Well i don't mind letting you konw what's on the disk, if it will help solve the problem.

Do you want us to post it here, or send it to you directly.

 

Just 1 question. Why does this problem not exist on my physical drive, with the exact same programs on both drives.

Link to comment
Share on other sites

  • Corsair Employees

Did I send you a PM Heintz.G to contact me?

 

If not I will send you my contact info tomorrow other wise you can call our Tech support and ask for me I will be happy to help you directly.

8:30 AM to 5:30 PM Pacific Time Monday Through Friday.

Link to comment
Share on other sites

Same problem here. system data is in my profile.

 

BSOD 0xF4 when idle

csrss.exe crashed

kernel memory dump is available (if you need it, i can send it ;). Eventlog says: Kernel Power Event 41, after resetting the system the F60-SSD is not recognized. Power off and on and everything works again.

 

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

DEBUG_FLR_IMAGE_TIMESTAMP:  0

PROCESS_OBJECT: fffffa80094e8910

IMAGE_NAME:  csrss.exe

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xF4

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`06ab80f8 fffff800`03013c72 : 00000000`000000f4 00000000`00000003 fffffa80`094e8910 fffffa80`094e8bf0 : nt!KeBugCheckEx
fffff880`06ab8100 fffff800`02fc10a3 : ffffffff`ffffffff fffffa80`095c6060 fffffa80`094e8910 fffffa80`094e8910 : nt!PsSetCurrentThreadPrefetching+0x6e2
fffff880`06ab8140 fffff800`02f4569c : ffffffff`ffffffff 00000000`00000001 fffffa80`094e8910 fffff6fb`00000008 : nt!RtlGUIDFromString+0x11277
fffff880`06ab8190 fffff800`02c86853 : fffffa80`094e8910 fffff800`c0000005 ffffe679`3b0d81f8 fffffa80`095c6060 : nt!MmUnmapViewOfSection+0x228
fffff880`06ab8210 fffff800`02c82df0 : fffff800`02cc1cac fffff880`06ab8b78 fffff880`06ab88e0 fffff880`06ab8c20 : nt!KeSynchronizeExecution+0x3a43
fffff880`06ab83a8 fffff800`02cc1cac : fffff880`06ab8b78 fffff880`06ab88e0 fffff880`06ab8c20 00000000`009e1c30 : nt!ZwUnlockFile+0x130
fffff880`06ab83b0 fffff800`02c86c42 : fffff880`06ab8b78 00000000`00011e34 fffff880`06ab8c20 00000000`009e1708 : nt!FsRtlInitializeBaseMcbEx+0x46d8
fffff880`06ab8a40 fffff800`02c857ba : 00000000`00000001 00000000`00011e34 00000000`00000001 00000000`771090e4 : nt!KeSynchronizeExecution+0x3e32
fffff880`06ab8c20 00000000`76ff592d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x29aa
00000000`009e09b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ff592d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner

 

BSOD 0x1A MEMORY_MANAGEMENT when idle/active

Kernel Power Event 41. Seems to be SSD related, because it happened three times since the ssd is built-in, no BSODs with HDD. I got a live BSOD of this while surfing on a website. System froze for a few seconds with HDD LED permanently on, then crash to BSOD.

 

some configuration thingies:

 

win 7 x64 clean install with MSAHCI

balanced energy saving mode (no idle standby / hibernation)

pagefile.sys moved to hdd

hiberfil.sys on ssd, but not in use

TEMP files on hdd

 

following diagnostics where done:

 

memtest86+: 48h without errors (to exclude cpu/ram issues)

prime95 + furmark: 12h without errors (to exclude power supply issues)

prime95: 18h without errors (to exclude cpu/ram issues)

h2testw on ssd: 25GB data written to ssd, 6h permanently rereading and checking this data for consistency: no error

 

http://www.media-nocte.de/user/cwe/ssd-info.jpg

Link to comment
Share on other sites

  • Corsair Employees

It would help to know who is getting what error, please let me know if you are getting an error and what that error is and you system info should be updated and please let me know what O.S. you are using.

I have sent a few of you a PM to get your drives replaced so we can test your drive for the BSOD error.

Link to comment
Share on other sites

Earlier someone posted a program to trigger TRIM, did you try it? It's in this thread. There's another post on another thread, and that fella took a photo of the BSOD. That's one of the two BSOD's but believe me, the problem here is NOT the bsod, but rather TRIM causing the harddisk to "dismount"/shutdown/vanish/become unrecognized in the BIOS if that's the correct word. As a result, with system drive dismounted, it will eventually result in a BSOD. If you really care about testing, just try and take my word for it.

 

What about, you share with us a sample gigabyte configuration that was used in testing, we who suffer the problems might be able to see something. Better if you take the RMA unit from USA as I'm the opposite side of the world. Might be able to work quicker.

Link to comment
Share on other sites

  • Corsair Employees

I will get a configuration for you ASAP.

But I can tell you they have been tested on most popular Intel Core I7 and I5 chipsets with Windows 7 Ultimate using the latest BIOS and updates from the respective manufacturer.

Link to comment
Share on other sites

Just so you know, since TRIM was disabled, I haven't had any issues. Have you tried triggering TRIM on your test systems and see that it actually works?

 

we gave the issue on a silver spoon and unable to reproduce?

what are you guys doing to reproduce it? what hardware are you using? use any branded socket 1156 board with i5/i7, enable trim and let the system run for at least 12 hours in idle.

i found a way in less then 2 days to reproduce the error within seconds on my system. see specs.

the drive works with trim disabled. for me that's not acceptable.

 

i got the drive back from my friend whom i gave it too to test cause he has the same issue. an asus intel board with i7 cpu.

so i'm stuck with it.. a non trimmable 300 bucks brick. an other branded sandforce drive works fine with trim as i stated before.

 

just trying to help here. i do not think that all those drives are defective and rma it will not solve the problem at all.

if you cannot reproduce the error at all why even bother to collect drives on rma.

i count at least a dozen people with same problem. even a guy with 8 drives and all fail. no offence but rma? really?

if you use drives with same firmware as current retail drive you can reproduce it, if i can do it you guys need to be able to do it too..

gonna test it in other intel system today. see if i can reproduce it there too.

 

pm if you need some help ram guy.

if you guys do not want any help and waste more time on it fine by me. i'll take my loss and get out of here.

 

to force trim either wait long enough till windows kicks in, use tool i posted or Delphi executable with this attached batch file:

all force drives always get 0x000000F4 bsod and no other.

and 90% of the time it happens when system is in idle mode when trim kicks in.

i got it one time during using the computer while i was coping 20gb data from ssd to other drive, other times i can send trim command with the tool or batch file and make the drive go cripple within seconds.

 

do you guys need more info? just let the techies check the trim functionality in the firmware if there is no typo in the commands.

i know reproducing errors is abitch so why not try to rebuild my system, get a msi P55-GD65 motherboard with any intel cpu and test that.

 

also i did some sniffin around the forum on who has the issue and all people run windows 7 X64 bit version.

trim.zip

Link to comment
Share on other sites

I highly doubt it's an isolated incident. The same drive can't possibly be defective the same way for this many people. Most people turn off their computer before trim gets in. Others, they don't know about this forum. They thought something else is causing the issue. But most of us got the problem resolved by disabling trim. If you can't come up with a new firmware, fine. Just provide a manual trimming tool. If you don't even have that no wonder why you can't reproduce the problem. If you spend your work day playing with the drive you are not going to see this bsod. You have to let the computer sit idle till trim kicks in.
Link to comment
Share on other sites

I'd wager they're recommending RMAs so they can look at your SPECIFIC drive. Could just be a batch issue, but without someone RMAing a drive, they can't eliminate that as a possibility. Having said that, a clarification on Corsair's testing methodology would be nice, as well as if they've tried the aforementioned "triggers".
Link to comment
Share on other sites

I'd wager they're recommending RMAs so they can look at your SPECIFIC drive. Could just be a batch issue, but without someone RMAing a drive, they can't eliminate that as a possibility. Having said that, a clarification on Corsair's testing methodology would be nice, as well as if they've tried the aforementioned "triggers".

 

true on the batch failure but i still think it's a firmware issue.

only time will tell:sunglasse

yes i would really like to know how there testing this issue. i spend enough time on it and replicating the issue, hope they would even try to do the same.

able to replicate the issue makes it easier to solve it.

Link to comment
Share on other sites

It's always possible it's a batch issue, I did get mine only shortly after it was released after all. Now there's the newer F100 series I wonder how those are doing.

 

I may be the unusual one out here, I have an EVGA x58 SLI LGA1366 board, most people have Gigabyte or Asus and I'm still getting the same issue as you guys with TRIM enabled.

 

The one other issue while I was actually at the computer and on Google Earth when the entire desktop froze up and the HDD light stayed on scares me too, that only happened once so far and when TRIM was enabled. But it's the only time I had an issue when the system was NOT idle. I'll post here if it happens again with TRIM disabled, but so far so good.

 

I am happy to report that since I disabled TRIM last week, not a single problem.

Link to comment
Share on other sites

so how can we compare batches? what info is needed?

 

xennox, there was a thread here of someone having 80 of these drives running linux on various kinds of boards and he experienced drives disappearing after kernel panics if im not wrong.

Link to comment
Share on other sites

so how can we compare batches? what info is needed?

 

xennox, there was a thread here of someone having 80 of these drives running linux on various kinds of boards and he experienced drives disappearing after kernel panics if im not wrong.

 

dunno missed that thread. i just hope tech do not wast there time and look at the trim right away.

Link to comment
Share on other sites

 

http://www.media-nocte.de/user/cwe/ssd-info.jpg

 

 

umm.. question... i just purchased a new CSSD-F120GB2 like 4 days ago, and my CrystalDiskInfo says my drive is 90% good. Should I be worried??

 

http://imgur.com/3kvvA.jpg

Link to comment
Share on other sites

Hmmm,

 

sorry, i can't answer that. Mine was at 97% on delivery. Maybe thats an erraneous reading or a misinterpretation by the software - it's the only smart-tool which delivers usable readings.

Thats a question for the guys @corsair ;)

Link to comment
Share on other sites

  • Corsair Employees
Hmmm,

 

sorry, i can't answer that. Mine was at 97% on delivery. Maybe thats an erraneous reading or a misinterpretation by the software - it's the only smart-tool which delivers usable readings.

Thats a question for the guys @corsair ;)

 

That's exactly correct that is a third party application and officially its not supported even though its one we have suggested to get other information.

At this time there its not been proven to be accurate information and should not be trusted.

Link to comment
Share on other sites

That's exactly correct that is a third party application and officially its not supported even though its one we have suggested to get other information.

At this time there its not been proven to be accurate information and should not be trusted.

 

Good to know Thanks

Link to comment
Share on other sites

I ran trim.bat, and it didn't delay at all. it was incredibly quick. no bsod either.

 

BUT i moved my CSSD-F120GB2 to my Marvell Controller instead of the Intel one so that may be why

 

either you did not have the delphi executable within the same folder as the batch file. or marvel does not support trim

Link to comment
Share on other sites

I'm realy sad to Report that in my case disabling TRIM did not solve the problem of the BSOD.

 

C:\Users\sherlock>fsutil behavior query disabledeletenotify

DisableDeleteNotify = 1

 

I reported that disablig trim does not fix the problem, but I got exactly one BSOD after I disabled trim, and that could be that i did not reboot the PC after entering the command. I'm now running 4 days 24/7 and it looks that disabling trim indeed patches the problem. It is still not the fix but, at least the PC is stable.

 

Now I just need a new drive with the proper Firmware.

Link to comment
Share on other sites

Archived

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


×
×
  • Create New...