PLEASE READ BSOD mostly Graphics and Harddisk errors..at random times

[writhziden]

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


Loading Dump File [D:\Kingston\BSODDmpFiles\misanthropic42\Windows_NT6_BSOD_jcgriff2\030212-21746-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0304f000 PsLoadedModuleList = 0xfffff800`03294670
Debug session time: Fri Mar  2 13:57:16.811 2012 (UTC - 7:00)
System Uptime: 0 days 21:22:54.050
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88009f782b8, fffff88009f77b10, fffff8800126458a}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: 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: fffff88009f782b8
Arg3: fffff88009f77b10
Arg4: fffff8800126458a

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


EXCEPTION_RECORD:  fffff88009f782b8 -- (.exr 0xfffff88009f782b8)
ExceptionAddress: fffff8800126458a (Ntfs!ProcessSavepointListForCurrentLogRec+0x000000000000007a)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff88009f77b10 -- (.cxr 0xfffff88009f77b10)
rax=0000000000000001 rbx=fffff8a0031479a0 rcx=fffff8a0031479a0
rdx=fffff88000cef5e8 rsi=0000000000000000 rdi=fffff8a0031479a0
rip=fffff8800126458a rsp=fffff88009f784f0 rbp=fffff8000326c260
 r8=0000000000000000  r9=fffff8a0031479a0 r10=0000000000000000
r11=fffff88009f78400 r12=fffff8a015a07000 r13=fffff8a015a07001
r14=fffff880012d73b0 r15=0000000000000008
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
Ntfs!ProcessSavepointListForCurrentLogRec+0x7a:
fffff880`0126458a 48              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x24

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

LAST_CONTROL_TRANSFER:  from fffff880013afeca to fffff8800126458a

STACK_TEXT:  
fffff880`09f784f0 fffff880`013afeca : fffff8a0`031479a0 fffff800`0326c260 00000000`00000000 00000000`00000000 : Ntfs!ProcessSavepointListForCurrentLogRec+0x7a
fffff880`09f78520 fffff880`013b3b41 : fffff8a0`15a07000 fffff8a0`031479a0 00000000`00000000 00000000`00000082 : Ntfs!TxfTransMgrAbort+0x3da
fffff880`09f78690 fffff880`0131c499 : fffff8a0`15a07000 fffff880`09f786f0 00000000`00000000 00000000`00000000 : Ntfs!TxfRollforwardUndo+0xdb1
fffff880`09f78920 fffff880`012b581f : fffffa80`0df0f180 fffffa80`0d711501 00000000`00000001 00000000`00000168 : Ntfs!TxfInitializeVolume+0x98d
fffff880`09f78a50 fffff880`0123c985 : 00000000`00000000 fffffa80`0df0f180 fffffa80`11edd110 fffff800`030d3f93 : Ntfs!NtfsCommonFileSystemControl+0x6b
fffff880`09f78a90 fffff800`030d6001 : fffffa80`0cb21600 fffff800`0326c200 fffff800`032cd800 00000000`00000001 : Ntfs!NtfsFspDispatch+0x2ad
fffff880`09f78b70 fffff800`03366fee : fffff880`0a5ea550 fffffa80`11b06450 00000000`00000080 fffffa80`0caf29e0 : nt!ExpWorkerThread+0x111
fffff880`09f78c00 fffff800`030bd5e6 : fffff800`03241e80 fffffa80`11b06450 fffffa80`0caf2500 fffff880`01247cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`09f78c40 00000000`00000000 : fffff880`09f79000 fffff880`09f73000 fffff880`09f779b0 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
    fffff8800126458b - Ntfs!ProcessSavepointListForCurrentLogRec+7b
	[ 83:82 ]
1 error : !Ntfs (fffff8800126458b)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr 0xfffff88009f77b10 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

The most recent crash does point toward memory. You could run with one module at a time and just see if you get any crashes rather than running the memtest86+ software to test. Also, make sure to Avoid Static Damage to Your PC when swapping out components.

 

[misanthropic42]

Thanks for the heads up. I ran memtest on 2 of the sticks, one at a time, each for 7 passes last night. The 2nd stick was stuck on the modulo 20 test, test 8. It didn't come up with any errors but it wouldn't complete the pass. Instead it kept running the same test over and over for a few hours. So currently I have that stick out and the other 3 in. Now just another wait and see.

 

[writhziden]

That is a good troubleshooting step. Let us know how the waiting game goes.

 

[misanthropic42]

Well so far so good. Must've been the one stick that was messed up. It hasn't crashed or blue screened since I took it out. Thanks a bunch for the help.

 

[writhziden]

You're welcome. Please keep us updated over the next few days how things go.