BSOD after several days of SSD boot drive; not with standard HDD

I am running Windows 7 x64 on an AMD 970. The boot drive is a Corsair CSSD-F120GB3 (Users, ProgramData reside on a separate, standard HDD; this was done correctly at installation).

After several hours to 7 days the PC would BlackScreen to a blinking cursor. This happened for months. Eventually, after replacing every other piece of hardware and updating all drivers, swapped out the SSD (copied the image to an older WD 250GB drive).

I have run 17 days without a crash.

I have run every health check I can on the SSD, but no errors.

Any ideas how to deal with this? I am not sure I can get a replacement, as I cannot test for a fault in the drive. I am also not sure it's not a software problem.

Here's a link to my last thread, where I figured this out, which has the minidumps. But this is the specific error:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80079a69e0, Terminating object
Arg3: fffffa80079a6cc0, Process image file name
Arg4: fffff800035e38b0, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: fffffa80079a69e0

IMAGE_NAME: csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR: 0xF4_IOERR

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`021b80e8 fffff800`0366a5e2 : 00000000`000000f4 00000000`00000003 fffffa80`079a69e0 fffffa80`079a6cc0 : nt!KeBugCheckEx
fffff880`021b80f0 fffff800`0361799b : ffffffff`ffffffff fffffa80`07c84060 fffffa80`079a69e0 fffffa80`079a69e0 : nt!PspCatchCriticalBreak+0x92
fffff880`021b8130 fffff800`03597448 : ffffffff`ffffffff 00000000`00000001 fffffa80`079a69e0 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`021b8180 fffff800`032deed3 : fffffa80`079a69e0 fffff800`c0000006 fffffa80`07c84060 00000000`01f80ea0 : nt!NtTerminateProcess+0xf4
fffff880`021b8200 fffff800`032db470 : fffff800`0332b67f fffff880`021b8b78 fffff880`021b88d0 fffff880`021b8c20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`021b8398 fffff800`0332b67f : fffff880`021b8b78 fffff880`021b88d0 fffff880`021b8c20 00000000`01f81a40 : nt!KiServiceLinkage
fffff880`021b83a0 fffff800`032df2c2 : fffff880`021b8b78 00000000`00013510 fffff880`021b8c20 00000000`01f81518 : nt! ?? ::FNODOBFM::`string'+0x49874
fffff880`021b8a40 fffff800`032dde3a : 00000000`00000000 000007fe`fdd3d8b4 00000000`01f91501 00000000`00013510 : nt!KiExceptionDispatch+0xc2
fffff880`021b8c20 00000000`778c9c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`01f81460 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778c9c12


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe

Followup: MachineOwner
---------

Um so why did you start a new thread for the same BSOD problem?


We need the newer BSOD's to see what is happening now.

There are no new crashes. The bug report was for the last crash I had with the SSD. I swapped the SSD for a standard HDD, so I am running fine (albeit slower).

However, I can't tell if the problem is a Hardware problem or a software problem. So I posted here in Hardware hoping to find someone who has seen this problem with SSDs before. The drive does not fail any error checks, so I am not sure I can request an RMA for it. Plus, I am not convinced that this will fix it.

ultralame said:

There are no new crashes. The bug report was for the last crash I had with the SSD. I swapped the SSD for a standard HDD, so I am running fine (albeit slower).

However, I can't tell if the problem is a Hardware problem or a software problem. So I posted here in Hardware hoping to find someone who has seen this problem with SSDs before. The drive does not fail any error checks, so I am not sure I can request an RMA for it. Plus, I am not convinced that this will fix it.

Ok, so if the below DMP is from before why did you include it now?


Have you looked in event viewer to see what is logged there? [B]


To check for freezing/crashing you need to check several things.

Event viewer.

Type eventvwr in search and go to the windows log>application tab.
Look for errors. Errors have red in the left hand column.

Look for errors that say app hang, or app crash, or anything related to the problem.
When you find them either take a screenshot of them and upload them to us, or note the event ID and source codes and look them up in google. If you cant find them in google tell us what they are.

There was a recall on that SSD. If yours was not one of the problem ones what firmware is it. All force3 need the latest to run correctly. 1.3.3.

Plug it back in & check the firmware. One way to do it is with over here. Grab the right one.

zigzag3143,

Thanks for the info...
1) I included the old crash because that's what I am trying to analyze. I would like to make this drive work/
2) I have checked through everything that was mentioned in the Crashes forum (events, debugs, etc) and essentially the error was a generic hardware error. I have only semi-verified it by swapping out the offending hardware.
3) I reposted to the hardware forum hoping there would be a little better help here, since it appears to be the SSD.

Thank you!

ultralame said:

zigzag3143,

Thanks for the info...
1) I included the old crash because that's what I am trying to analyze. I would like to make this drive work/
2) I have checked through everything that was mentioned in the Crashes forum (events, debugs, etc) and essentially the error was a generic hardware error. I have only semi-verified it by swapping out the offending hardware.
3) I reposted to the hardware forum hoping there would be a little better help here, since it appears to be the SSD.

Thank you!

It is not a hardware error

It is a software error as described here


CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.

That process could be terminated by a device but it is highly unlikely.

But is it not possible that this thread died due to a hardware error?

Hipster Doofus mentioned that this drive may have bad firmware (something I didn't think to check).

ultralame said:

But is it not possible that this thread died due to a hardware error?

Hipster Doofus mentioned that this drive may have bad firmware (something I didn't think to check).

Anything is possible but there is absolutely no mention in the logs you have given us to make me think it is hardware. It may still be, but I doubt it.

Quick update; My SSD did have old firmware on it. So I updated that and I am in the process of imaging the drive back to it. Hopefully that will take care of the issue.

I will keep it updated.