BSOD:: BCCode: 116; BCCode: f4 (mostly f4)

[Looni3]

Hard drive failed in late October, replaced with SSD.

Started getting BSOD whenever doing anything graphical (flash in a web browser, or a game) in November. Tried Driver Fusion (|MG| Driver Fusion (Driver Sweeper) 1.4.0 Download) and installiing older NVIDIA drivers, this reduced the freqquency of BSODs to the point where they'd only happen roughly once a night and I could mostly ignore it.

Any help diagnosing would be greatly appreciated. My thoughts are replacing motherboard and RAM, I suspect driver controller might be to blame.

 

[Vir Gnarus]

Did you make sure to update the firmware for your SSD and update your drive controller & chipset drivers as well as the BIOS? All of those elements are involved with drive operations compatibility patches are often added to them to ensure your SSD is compatible with your system.

Yes, these all seem to be involved with your SSD drive. There are crashes occurring because during disk I/O operations the storage device being accessed ended up missing, typically due to failure to respond to the OS. I cannot ascertain from these tiny minidumps what storage device it's trying to access, nor can I discern if it's even attempting to access a legitimate device and isn't just scrambling the device object number. However I can say it fits the bill with common SSD issues that stem from incompatibility or just plain bad SSD drives. Again, make sure all the aforementioned items are up-to-date.

What SSD do you have? Certain brand names like Samsung (considered best so far) and Crucial are often reliable, and some - like OCZ and Rosewill - are about as much a gamble as winning the lottery. Brand name makes a big difference when it comes to reliability, so it would be best to pick your options wisely. Even so, even the most reliable brands can still churn out a dirty drive or two, that's to be expected.

Analysts:

Consistent pattern in the crashdumps are c000000e NTSTATUS errors residing in the crashing thread's callstack. The error means the device attempted to access does not exist. Again, as stated before, minidumps don't hold info on the specified device.

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: fffffa8007013b30, Terminating object
Arg3: fffffa8007013e10, Process image file name
Arg4: fffff80003392460, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

PROCESS_OBJECT: fffffa8007013b30

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) [COLOR=Red]0xc0000005 [/COLOR]- The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0xF4_fffff800c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`066d7e38 fffff800`0341a822 : 00000000`000000f4 00000000`00000003 fffffa80`07013b30 fffffa80`07013e10 : nt!KeBugCheckEx
fffff880`066d7e40 fffff800`033c6e0b : ffffffff`ffffffff fffffa80`06b24640 fffffa80`07013b30 fffffa80`07013b30 : nt!PspCatchCriticalBreak+0x92
fffff880`066d7e80 fffff800`03345f04 : ffffffff`ffffffff 00000000`00000001 fffffa80`07013b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176e6
fffff880`066d7ed0 fffff800`03092253 : fffffa80`07013b30 fffff800`c0000005 fffffa80`06b24640 00000000`01cc0700 : nt!NtTerminateProcess+0xf4
fffff880`066d7f50 fffff800`0308e810 : fffff800`030ddb7f fffff880`066d8a38 fffff880`066d8790 fffff880`066d8ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`066d80e8 fffff800`030ddb7f : fffff880`066d8a38 fffff880`066d8790 fffff880`066d8ae0 00000000`01cc2210 : nt!KiServiceLinkage
fffff880`066d80f0 fffff800`03092642 : fffff880`066d8a38 00000000`000713b8 fffff880`066d8ae0 00000000`01cc1ce8 : nt! ?? ::FNODOBFM::`string'+0x488a4
fffff880`066d8900 fffff800`030911ba : 00000000`00000001 00000000`01cc0e18 00000000`77488d01 00000000`000713b8 : nt!KiExceptionDispatch+0xc2
fffff880`066d8ae0 00000000`77378e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`01cc0e20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77378e3d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_fffff800c0000005_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_fffff800c0000005_IMAGE_csrss.exe

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

0: kd> [COLOR=Blue]!niemiro.rawstack[/COLOR] [COLOR=Green]//Windbg extension made by Niemiro from Sysnative Forums. Dumps rawstack of thread.[/COLOR]
dps fffff880066d7000 fffff880066d8c68
fffff880`066d7000  fffff800`031d6ff4 nt!_imp_NtOpenSymbolicLinkObject+0x5aec
fffff880`066d7008  fffff800`0360c2ec hal!HalpTscStallExecutionProcessor+0xe8
fffff880`066d7010  fffff880`066d7eb8
fffff880`066d7018  fffff800`03014000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`066d7020  fffff880`0141c000 Ntfs!NtfsGetNextChildLcb <PERF> (Ntfs+0x0)
fffff880`066d7028  fffff880`066d7150
fffff880`066d7030  fffff880`014357f0 Ntfs!_GSHandlerCheck_SEH
fffff880`066d7038  00000000`00000004

...

fffff880`066d83f8  00000000`00000002
fffff880`066d8400  00000000`00000001
fffff880`066d8408  00000000`[COLOR=Red]c000000e[/COLOR]
fffff880`066d8410  00000000`00000000
fffff880`066d8418  fffff8a0`07000c70

...

0: kd> !error c000000e
Error code: (NTSTATUS) [COLOR=Red]0xc000000e [/COLOR](3221225486) - A device which does not exist was specified.

 

[Looni3]

I did flash the BIOS when I rolled back the graphic card's driver. The SSD is an OCZ Agility3, I'll see if updating the firmware has any effect.

Thanks very much for your help.

 

[Vir Gnarus]

I understand. OCZ is one of the least reliable brand names in the SSD industry. If you're lucky and get a stable one, they're crazy fast, but you may have to run through several replacements before you find one. I hope the firmware update works for you, but if not, it may be in your best interest to look for another brand SSD. Samsung, Crucial and Intel seem to be the top dogs in reliability, with Samsung currently sitting in the throne.