BSOD SSD related?

fiddlefaddle · 26 May 2013

Hello everyone,

Recently built this computer.
Had a BSOD within 24hrs of running but otherwise was fine in the first few days, even finished Crysis 3 without any problems.
Had a bunch of BSODs yesterday, so I started poking around. Updated MOBO and SSD firmware. Realized the timings on my RAM was on Auto so I set it to the correct timing according to the RAM manufacturer.
System ran fine after that but I just had a BSOD again so I thought I should post and see if anyone can help and in the worst case I need to RMA something.
I think it is SSD related, BugCheck F4, but I don't really know anything about reading these .dmp logs.

Best Regards

Arc · 26 May 2013

Do two things .....
Check that the Samsung 840 Series SSD is running with the latest firmware.
Asmedia 106x SATA Host Controller Driver is up to date. ASMedia Technology Inc. ????

Let us know the results.
__________________________________________________________________________________
BSOD ANALYSIS:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa801a628b30, fffffa801a628e10, fffff80002f7d350}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

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

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa801a628b30, Terminating object
Arg3: fffffa801a628e10, Process image file name
Arg4: fffff80002f7d350, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----

PROCESS_OBJECT: fffffa801a628b30

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.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:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`12f98e38 fffff800`03004d22 : 00000000`000000f4 00000000`00000003 fffffa80`1a628b30 fffffa80`1a628e10 : nt!KeBugCheckEx
fffff880`12f98e40 fffff800`02fb108b : ffffffff`ffffffff fffffa80`1ee59060 fffffa80`1a628b30 fffffa80`1a628b30 : nt!PspCatchCriticalBreak+0x92
fffff880`12f98e80 fffff800`02f31144 : ffffffff`ffffffff 00000000`00000001 fffffa80`1a628b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`12f98ed0 fffff800`02c75e93 : fffffa80`1a628b30 fffff800`c0000006 fffffa80`1ee59060 00000000`02b90c40 : nt!NtTerminateProcess+0xf4
fffff880`12f98f50 fffff800`02c72450 : fffff800`02cc181f fffff880`12f99a38 fffff880`12f99790 fffff880`12f99ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`12f990e8 fffff800`02cc181f : fffff880`12f99a38 fffff880`12f99790 fffff880`12f99ae0 00000000`ff39b4d8 : nt!KiServiceLinkage
fffff880`12f990f0 fffff800`02c76282 : fffff880`12f99a38 00000000`02c10000 fffff880`12f99ae0 00000000`ff39fb88 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`12f99900 fffff800`02c74dfa : 00000000`00000000 00000000`ff393900 00000000`777ce701 00000000`02c10000 : nt!KiExceptionDispatch+0xc2
fffff880`12f99ae0 00000000`776c8f55 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`02b91360 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776c8f55


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe

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

fiddlefaddle · 28 May 2013

Drivers were already up to date, it turns out it was hardware-related but not with the SSD alone.
Always forget that the answer to most questions are simple

Took it out of the case's "X-Dock" and put it in the HD rack.
Up and running for about 2 days, no BSODs so far.
Maybe I could get that part replaced if I figure out how to take it out.

Thanks for your help.

Arc · 29 May 2013

fiddlefaddle said:

Drivers were already up to date, it turns out it was hardware-related but not with the SSD alone.
Always forget that the answer to most questions are simple

Took it out of the case's "X-Dock" and put it in the HD rack.

That's a good move, and the perfect practice.

For any further issue, let us know.