Random BSOD, infrequent but regular, 0xc0000005

s3rg3 · 02 Nov 2012

So it's a brand new rig running Windows 7 64-bit, I've had it for about 10 days now.
Started experiencing BSODs from day one. It happens when playing games mostly, but sometimes it crashes w/o any applications running.

I've tried reinstalling Windows a few times, running memory tests (everything seems to be ok) and switching the system SSD (OCZ Vertex 3) to another controller. Nothing helps so far, it still crashes 2-3 times a day.

My ability to research the reason for this behavior is quite limited, so maybe a more competent person than me could look into logs and suggest what to blame? Thanks in advance.

I'm attaching SF Diagnostic Tool data.

s3rg3 · 02 Nov 2012

Here's the Windbg log from the latest minidump (that's right after a fresh Windows installation):

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\110212-9547-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`0305c000 PsLoadedModuleList = 0xfffff800`032a0670
Debug session time: Fri Nov 2 04:50:14.949 2012 (UTC + 4:00)
System Uptime: 0 days 5:05:36.196
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880035235c8, fffff88003522e20, fffff800030eb759}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+169 )

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

4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880035235c8
Arg3: fffff88003522e20
Arg4: fffff800030eb759

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

EXCEPTION_RECORD: fffff880035235c8 -- (.exr 0xfffff880035235c8)
ExceptionAddress: fffff800030eb759 (nt!MiUnlinkPageFromLockedList+0x0000000000000169)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff88003522e20 -- (.cxr 0xfffff88003522e20)
rax=120000000018ffcf rbx=fffffa8005b74ea0 rcx=000000000016458d
rdx=0000000000000000 rsi=0000000000000005 rdi=fffff8000330dd48
rip=fffff800030eb759 rsp=fffff88003523800 rbp=0000000000000000
r8=fffff88003523830 r9=5ffffa8004aff6d0 r10=fffffa80087f7e30
r11=0000000000000000 r12=0000000000000000 r13=0000058000000000
r14=0000000000000001 r15=2aaaaaaaaaaaaaab
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!MiUnlinkPageFromLockedList+0x169:
fffff800`030eb759 410fb6511b movzx edx,byte ptr [r9+1Bh] ds:002b:5ffffa80`04aff6eb=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330a100
GetUlongFromAddress: unable to read from fffff8000330a1c0
ffffffffffffffff

FOLLOWUP_IP:
nt!MiUnlinkPageFromLockedList+169
fffff800`030eb759 410fb6511b movzx edx,byte ptr [r9+1Bh]

FAULTING_IP:
nt!MiUnlinkPageFromLockedList+169
fffff800`030eb759 410fb6511b movzx edx,byte ptr [r9+1Bh]

BUGCHECK_STR: 0x24

LAST_CONTROL_TRANSFER: from fffff800030f06b5 to fffff800030eb759

STACK_TEXT:
fffff880`03523800 fffff800`030f06b5 : fffff6fc`c006d2e8 00000000`00000000 fffffa80`05b74ea0 fffffa80`0a035360 : nt!MiUnlinkPageFromLockedList+0x169
fffff880`03523880 fffff800`03097cce : fffff980`0da5d000 00000000`00000022 00000000`00000005 fffffa80`00040000 : nt!MmCheckCachedPageStates+0x295
fffff880`03523a30 fffff800`033c9c5d : fffffa80`0d667a20 fffffa80`146d6270 00000000`0000000e fffff8a0`0009dab0 : nt!CcMapDataForOverwrite+0x10a
fffff880`03523ac0 fffff880`0131167f : fffffa80`0d667a20 fffff8a0`00040000 fffffa80`0fc5f180 00000005`00000000 : nt!CcPreparePinWrite+0x69
fffff880`03523b80 fffff880`01303e67 : 00000000`00000098 fffff8a0`00302d10 00000000`000000c8 fffff8a0`00302c70 : Ntfs!LfsAllocateLbcb+0x12f
fffff880`03523bf0 fffff880`012fdfff : 00000000`00000000 fffff880`03523ec0 00000000`00000098 00000000`00000000 : Ntfs!LfsPrepareLfcbForLogRecord+0x97
fffff880`03523c20 fffff880`01304955 : fffff8a0`00000000 fffff8a0`00249b00 fffff880`03524600 fffff800`032061de : Ntfs!LfsWriteLogRecordIntoLogPage+0x43f
fffff880`03523cc0 fffff880`01300706 : fffff8a0`009f1078 fffffa80`00000003 00000000`3416ffd4 fffff880`03523f10 : Ntfs!LfsWrite+0x145
fffff880`03523d80 fffff880`0130cd57 : fffff980`02b42000 fffff8a0`009f2bc0 00000000`00002000 fffff880`035246a0 : Ntfs!NtfsWriteLog+0x466
fffff880`03523fd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsUpdateFileNameInIndex+0x357

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiUnlinkPageFromLockedList+169

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be

STACK_COMMAND: .cxr 0xfffff88003522e20 ; kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x24_nt!MiUnlinkPageFromLockedList+169

BUCKET_ID: X64_0x24_nt!MiUnlinkPageFromLockedList+169

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

koolkat77 · 02 Nov 2012

Loads of NTFS errors.

Code:

fffff880`035226b8  fffff880`012650c8 Ntfs!_C_specific_handler
fffff880`035226c0  fffff880`012b3fb8 Ntfs!__PchSym_ <PERF> (Ntfs+0x68fb8)
fffff880`035226c8  fffff880`012cf6d0 Ntfs!NtfsFsdFlushBuffers+0x104
fffff880`035226d0  00000000`00000000
fffff880`035226d8  fffff800`03105aed nt!RtlpExecuteHandlerForException+0xd
fffff880`035226e0  fffff880`01299f6c Ntfs!NtfsRepairEventCounterMutex+0x3c
fffff880`035226e8  fffff880`035245f0
fffff880`035226f0  00000000`00000000
fffff880`035226f8  fffff880`0124b000 Ntfs!NtfsGetNextChildLcb <PERF> (Ntfs+0x0)
fffff880`03522700  fffff880`035227a0
fffff880`03522708  fffff800`031048c5 nt!RtlDispatchException+0x415
fffff880`03522710  fffff880`01299f6c Ntfs!NtfsRepairEventCounterMutex+0x3c
fffff880`03522718  fffff880`03522758
fffff880`03522720  fffff880`035235c8
fffff880`03522728  fffff880`0124b000 Ntfs!NtfsGetNextChildLcb <PERF> (Ntfs+0x0)
fffff880`03522730  00000000`00000000
fffff880`03522738  00000000`00000000
fffff880`03522740  00000000`00000000
fffff880`03522748  00000000`00000000
fffff880`03522750  fffff880`035245f0
fffff880`03522758  fffff880`0124b000 Ntfs!NtfsGetNextChildLcb <PERF> (Ntfs+0x0)
fffff880`03522760  fffff880`01299f6c Ntfs!NtfsRepairEventCounterMutex+0x3c
fffff880`03522768  fffff880`03522cc0
fffff880`03522770  00000000`00000000
fffff880`03522778  fffff880`012b3fb8 Ntfs!__PchSym_ <PERF> (Ntfs+0x68fb8)
fffff880`03522780  fffff880`03525000
fffff880`03522788  fffff880`0351f000
fffff880`03522790  00000000`00000000
fffff880`03522798  00000000`00000000
fffff880`035227a0  fffff880`012cf6d0 Ntfs!NtfsFsdFlushBuffers+0x104
fffff880`035227a8  fffff880`0124b000 Ntfs!NtfsGetNextChildLcb <PERF> (Ntfs+0x0)
fffff880`035227b0  fffff880`012b3fb8 Ntfs!__PchSym_ <PERF> (Ntfs+0x68fb8)
fffff880`035227b8  fffff880`035245f0
fffff880`035227c0  00000000`00000000
fffff880`035227c8  fffff880`035227f0
fffff880`035227d0  fffff880`012650c8 Ntfs!_C_specific_handler
fffff880`035227d8  fffff880`01299f6c Ntfs!NtfsRepairEventCounterMutex+0x3c
fffff880`03522cc8  fffff800`03097bc4 nt!CcMapDataForOverwrite
fffff880`03522cd0  fffff880`013118dc Ntfs!TxfFlushTxfLsnForNtfsLsn
fffff880`03522cd8  fffff800`0305c000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`03522ce0  fffff800`032e1a4c nt!BBTBuffer <PERF> (nt+0x285a4c)
fffff880`03522ce8  fffff800`0305c000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`03522cf0  fffff800`032e20ac nt!BBTBuffer <PERF> (nt+0x2860ac)
fffff880`03522cf8  fffff800`0305c000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`03522d00  fffff800`032dcbec nt!BBTBuffer <PERF> (nt+0x280bec)
fffff880`03522d08  fffff800`0305c000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`03522d10  fffff800`032f5624 nt!BBTBuffer <PERF> (nt+0x299624)
fffff880`03522d18  fffff880`0124b000 Ntfs!NtfsGetNextChildLcb <PERF> (Ntfs+0x0)
fffff880`03522d20  fffff880`012b5008 Ntfs!__PchSym_ <PERF> (Ntfs+0x6a008)
fffff880`03522d28  fffff880`0124b000 Ntfs!NtfsGetNextChildLcb <PERF> (Ntfs+0x0)
fffff880`03522d30  fffff880`012b4c9c Ntfs!__PchSym_ <PERF> (Ntfs+0x69c9c)
fffff880`03522d38  fffff880`0124b000 Ntfs!NtfsGetNextChildLcb <PERF> (Ntfs+0x0)
fffff880`03522d40  fffff880`012b4ba0 Ntfs!__PchSym_ <PERF> (Ntfs+0x69ba0)
fffff880`03522d48  fffff880`0124b000 Ntfs!NtfsGetNextChildLcb <PERF> (Ntfs+0x0)
fffff880`03522d50  fffff880`012b4d14 Ntfs!__PchSym_ <PERF> (Ntfs+0x69d14)
fffff880`03522d58  fffff880`0124b000 Ntfs!NtfsGetNextChildLcb <PERF> (Ntfs+0x0)
fffff880`03522d60  fffff880`012b4c24 Ntfs!__PchSym_ <PERF> (Ntfs+0x69c24)
fffff880`03522d68  fffff880`0124b000 Ntfs!NtfsGetNextChildLcb <PERF> (Ntfs+0x0)
fffff880`03522d70  fffff880`012b4f0c Ntfs!__PchSym_ <PERF> (Ntfs+0x69f0c)
fffff880`03522d78  fffff880`0124b000 Ntfs!NtfsGetNextChildLcb <PERF> (Ntfs+0x0)
fffff880`03522d80  fffff880`012b4ec4 Ntfs!__PchSym_ <PERF> (Ntfs+0x69ec4)
fffff880`03522d88  fffff880`0124b000 Ntfs!NtfsGetNextChildLcb <PERF> (Ntfs+0x0)
fffff880`03522d90  fffff880`012b4d2c Ntfs!__PchSym_ <PERF> (Ntfs+0x69d2c)

Did you update to the latest firmware for your SSD?

s3rg3 · 02 Nov 2012

koolkat77 said:

Did you update to the latest firmware for your SSD?

Working on it right now, it came with a factory installed v. 2.2.
It's a royal pain to update FW on a system drive.

koolkat77 · 02 Nov 2012

OkeDokey :)

s3rg3 · 02 Nov 2012

Updated the SSD firmware. Same BSOD 15 minutes later. Did a quick S.M.A.R.T. check, everything seems to be fine with the SSD itself.

koolkat77 · 02 Nov 2012

What antivirus are you using?

s3rg3 · 02 Nov 2012

I'm not using any antivirus.
I only have Intel chipset, audio and Nvidia drivers installed.

koolkat77 · 02 Nov 2012

Update to the latest drivers for Marvell Marvell - Support

Vir Gnarus · 05 Nov 2012

OCZ SSD drives have a propensity to have higher-than-average failure rates straight out of the factory compared to other SSD brands. I would not doubt it that the drive itself is the cause of your problem, regardless what SMART wishes to say. Understand that SMART only reports block-related issues; it will not tell you on problems dealing with the SSD's internal controller or some other internal problem that does not exactly manifest in the SMART log. You've done all the necessary steps to try and determine any other outlying factors, to no avail. It's best to just replace the fella.

Though the only other recommendation I may have is update the motherboard BIOS and chipset drivers. Make sure you do so with another drive installed in the system that's stable and the SSD removed (save for the chipset drivers of course). If those fail to remedy, replace the drive.