BSOD randomly on idle and usually when playing Civilization 5

rfw213 · 07 Jan 2012

Hi,

I would really appreciate some expert advice. I have done what I can to repair the problem and am now admitting defeat. I've been having random blue screen stops since the day I added itunes match to my itunes account, though I have no idea if there is any relation. For some reason, the Windows system restore only had one prior restore point, and that did not seem to fix the problem. I use the computer mostly for media storage and photo and video work, but occassionally play Civilization on it.

I built this computer nearly 5 years ago and have, over the years, had a few periods where I got BSODs. It turns out that when I originally built it, the heatsink was not seated properly. About a year ago, I added the H50 to my system and things were stable until recently.

To problem solve my current issue, I have run memtest 86 for three passes (about 6 hours) without error. (I also played with RAM timing settings and system voltage settings based on forum posts at the g.skill forum.) I ran prime95 overnight without error. I then figured the problem must be with my graphics card, so yesterday I went out and bought a new graphics card, but that did not fix the problem either.

WhoCrashed suggests the problem is a driver, not hardware, but doesn't say which driver. I've tried turning verifier on, but the system gets unusably slow and (perversely) fails to crash with verifier on. Perhaps I should just wait longer.

Thanks for any and all help and suggestions.

Rob

OS

Windows 7 Professional x64
CPU

Q6600 @2.40 Ghz
Motherboard

Gigabyte GA-P35-ds3l
Memory

4x2gb 1066 modules: g.skill f2-8500cl5d
Graphics Card(s)

Nividia 9600 gt
Sound Card

N/A (on motherboard)
Monitor(s) Displays

N/A (LG 1600x1050 & HP 1920x1080)
Hard Drives

3 disks: WDC7500AAKS, WD20EARX, WD10EACS
PSU

PC Power and Cooling S61EPS 610W Continuous @ 40°C EPS12V SL
Cooling

Corsair H50

writhziden · 07 Jan 2012

Code:


Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\rfw213\Windows_NT6_BSOD_jcgriff2\010312-44226-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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`02c17000 PsLoadedModuleList = 0xfffff800`02e5c670
Debug session time: Tue Jan  3 10:03:45.432 2012 (GMT-7)
System Uptime: 0 days 2:30:13.172
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88007241048, fffff880072408a0, fffff80002caba00}

Unable to load image \SystemRoot\system32\DRIVERS\mozy.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mozy.sys
*** ERROR: Module load completed but symbols could not be loaded for mozy.sys
Probably caused by : Ntfs.sys ( Ntfs!NtfsCachedRead+180 )

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

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: fffff88007241048
Arg3: fffff880072408a0
Arg4: fffff80002caba00

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


EXCEPTION_RECORD:  fffff88007241048 -- (.exr 0xfffff88007241048)
ExceptionAddress: fffff80002caba00 (nt!MmMapViewInSystemCache+0x0000000000000280)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880072408a0 -- (.cxr 0xfffff880072408a0)
rax=ffb5fa8007b448f8 rbx=fffff6fcc025b000 rcx=0000000000000000
rdx=fffffa8009916080 rsi=fffff8a004405000 rdi=fffff8a004404000
rip=fffff80002caba00 rsp=fffff88007241280 rbp=fffff6fcc025b200
 r8=fffffa8000000020  r9=fffff880072412f0 r10=0000000000000000
r11=0000000000000000 r12=fffffa8009916010 r13=fffffa800b994ec0
r14=fffffa800b89eb60 r15=fffffa8008ff5840
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!MmMapViewInSystemCache+0x280:
fffff800`02caba00 4c896808        mov     qword ptr [rax+8],r13 ds:002b:ffb5fa80`07b44900=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

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 fffff80002ec6100
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsCachedRead+180
fffff880`0124a730 84c0            test    al,al

FAULTING_IP: 
nt!MmMapViewInSystemCache+280
fffff800`02caba00 4c896808        mov     qword ptr [rax+8],r13

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff80002caab87 to fffff80002caba00

STACK_TEXT:  
fffff880`07241280 fffff800`02caab87 : fffff8a0`190f9c60 fffff800`02e0a530 fffff880`07241428 fffffa80`07e1c810 : nt!MmMapViewInSystemCache+0x280
fffff880`072413f0 fffff800`02ca9aef : 00000000`00000000 00000000`08f00000 01ccca39`a7383e92 fffff780`00000000 : nt!CcGetVacbMiss+0x177
fffff880`072414b0 fffff800`02f7ddc2 : fffffa80`00000000 00000000`08f00000 fffff880`07241580 fffff880`07241610 : nt!CcGetVirtualAddress+0x2e0
fffff880`07241540 fffff880`0124a730 : fffff8a0`00000000 00000000`00000003 fffff8a0`03185c70 fffff800`02caa701 : nt!CcCopyRead+0x132
fffff880`07241600 fffff880`0124ada3 : fffff8a0`03185c70 fffff8a0`03185c70 fffff880`07241830 fffff880`07241728 : Ntfs!NtfsCachedRead+0x180
fffff880`07241660 fffff880`0124ca68 : fffffa80`06f585b0 fffffa80`06fc8010 fffff880`07241801 fffffa80`07984000 : Ntfs!NtfsCommonRead+0x583
fffff880`07241800 fffff880`0114ebcf : fffffa80`06fc83f8 fffffa80`06fc8010 fffffa80`079840d0 00000000`00000001 : Ntfs!NtfsFsdRead+0x1b8
fffff880`072418b0 fffff880`0114d6df : fffffa80`07628860 00000000`00000000 fffffa80`07628800 fffffa80`06fc8010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`07241940 fffff880`017e07a9 : fffffa80`06fc8000 fffffa80`07984198 fffff880`07241b40 fffff880`0116e541 : fltmgr!FltpDispatch+0xcf
fffff880`072419a0 fffffa80`06fc8000 : fffffa80`07984198 fffff880`07241b40 fffff880`0116e541 00000000`00000000 : mozy+0x47a9
fffff880`072419a8 fffffa80`07984198 : fffff880`07241b40 fffff880`0116e541 00000000`00000000 00000000`00008000 : 0xfffffa80`06fc8000
fffff880`072419b0 fffff880`07241b40 : fffff880`0116e541 00000000`00000000 00000000`00008000 fffff880`07241b10 : 0xfffffa80`07984198
fffff880`072419b8 fffff880`0116e541 : 00000000`00000000 00000000`00008000 fffff880`07241b10 fffffa80`097d5560 : 0xfffff880`07241b40
fffff880`072419c0 fffffa80`097d5560 : 00000000`00000001 fffffa80`06fc8010 00000000`00000004 00000000`00000000 : fltmgr!FltpFastIoRead+0xe1
fffff880`07241a60 00000000`00000001 : fffffa80`06fc8010 00000000`00000004 00000000`00000000 00000000`0000000c : 0xfffffa80`097d5560
fffff880`07241a68 fffffa80`06fc8010 : 00000000`00000004 00000000`00000000 00000000`0000000c 00000000`06cbd5d0 : 0x1
fffff880`07241a70 00000000`00000004 : 00000000`00000000 00000000`0000000c 00000000`06cbd5d0 fffff880`017ebc01 : 0xfffffa80`06fc8010
fffff880`07241a78 00000000`00000000 : 00000000`0000000c 00000000`06cbd5d0 fffff880`017ebc01 fffffa80`06fc8010 : 0x4


SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  Ntfs!NtfsCachedRead+180

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b

STACK_COMMAND:  .cxr 0xfffff880072408a0 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCachedRead+180

BUCKET_ID:  X64_0x24_Ntfs!NtfsCachedRead+180

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\rfw213\Windows_NT6_BSOD_jcgriff2\010512-17955-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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`02c5c000 PsLoadedModuleList = 0xfffff800`02ea1670
Debug session time: Thu Jan  5 20:10:35.351 2012 (GMT-7)
System Uptime: 0 days 13:44:37.787
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa7fffffff20, 2, 1, fffff80002cfd5ae}

Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+13e )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa7fffffff20, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002cfd5ae, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0b100
 fffffa7fffffff20 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiRemoveAnyPage+13e
fffff800`02cfd5ae f0410fba6c241000 lock bts dword ptr [r12+10h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88003193660 -- (.trap 0xfffff88003193660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cfd5ae rsp=fffff880031937f0 rbp=fffff88003193840
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiRemoveAnyPage+0x13e:
fffff800`02cfd5ae f0410fba6c241000 lock bts dword ptr [r12+10h],0 ds:4180:00000000`00000010=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cd81e9 to fffff80002cd8c40

STACK_TEXT:  
fffff880`03193518 fffff800`02cd81e9 : 00000000`0000000a fffffa7f`ffffff20 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03193520 fffff800`02cd6e60 : 00000000`849d0000 fffff8a0`01f922f0 00000000`00000000 00000000`0000000e : nt!KiBugCheckDispatch+0x69
fffff880`03193660 fffff800`02cfd5ae : 00000000`00000001 fffff800`02c6db25 fffffa80`00d17120 00000000`00000000 : nt!KiPageFault+0x260
fffff880`031937f0 fffff800`02c9d240 : fa80094d`f95004c0 00000000`00000000 00000000`0000001c 00000000`00000000 : nt!MiRemoveAnyPage+0x13e
fffff880`03193910 fffff800`02f754ea : fffffa80`09f5da90 fffffa80`00000001 fffffa80`09f5da90 00000000`00000005 : nt!MiPfPutPagesInTransition+0x7c7
fffff880`03193a80 fffff800`02c84d37 : fffffa80`09f5da90 00000000`849af000 00000000`849af000 fffff800`02e79260 : nt!MmPrefetchForCacheManager+0x8e
fffff880`03193ad0 fffff800`02d1e98e : fffffa80`085b6990 fffffa80`06729100 fffff880`6b576343 fffff880`03f6a734 : nt!CcPerformReadAhead+0x2f3
fffff880`03193c00 fffff800`02ce3001 : fffffa80`06765660 fffff800`02fcf901 fffff800`02eda8d0 fffffa80`00000002 : nt!CcWorkerThread+0x21e
fffff880`03193cb0 fffff800`02f73fee : 00000000`00000000 fffffa80`067291a0 00000000`00000080 fffffa80`066e12b0 : nt!ExpWorkerThread+0x111
fffff880`03193d40 fffff800`02cca5e6 : fffff880`02f64180 fffffa80`067291a0 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03193d80 00000000`00000000 : fffff880`03194000 fffff880`0318e000 fffff880`031939e0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRemoveAnyPage+13e
fffff800`02cfd5ae f0410fba6c241000 lock bts dword ptr [r12+10h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiRemoveAnyPage+13e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiRemoveAnyPage+13e

BUCKET_ID:  X64_0xA_nt!MiRemoveAnyPage+13e

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\rfw213\Windows_NT6_BSOD_jcgriff2\010612-16317-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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`02c00000 PsLoadedModuleList = 0xfffff800`02e45670
Debug session time: Fri Jan  6 12:04:21.127 2012 (GMT-7)
System Uptime: 0 days 2:52:35.938
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88004580cf7, fffff88003fe26a8, fffff88003fe1f00}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004580cf7, The address that the exception occurred at
Arg3: fffff88003fe26a8, Exception Record Address
Arg4: fffff88003fe1f00, Context Record Address

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


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

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
fffff880`04580cf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh

EXCEPTION_RECORD:  fffff88003fe26a8 -- (.exr 0xfffff88003fe26a8)
ExceptionAddress: fffff88004580cf7 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x000000000000002b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003fe1f00 -- (.cxr 0xfffff88003fe1f00)
rax=fffff8a019ea6980 rbx=ff73f8a019ea0000 rcx=fffffa8008db9000
rdx=fffffa800b5aec40 rsi=fffffa8008db9000 rdi=fffffa8008db9000
rip=fffff88004580cf7 rsp=fffff88003fe28e0 rbp=fffffa800b813a58
 r8=fffffa800b740c01  r9=0000000000000000 r10=0000000000000000
r11=0000000000000144 r12=fffffa800b5aec40 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b:
fffff880`04580cf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh ds:002b:ff73f8a0`19ea0054=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_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 fffff80002eaf100
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
fffff880`04580cf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8800457ded3 to fffff88004580cf7

STACK_TEXT:  
fffff880`03fe28e0 fffff880`0457ded3 : 00000000`00000000 fffffa80`0b811370 00000000`000000d6 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b
fffff880`03fe2910 fffff880`0459865d : 00000000`00000000 fffff8a0`16e765b0 fffffa80`00000000 fffffa80`0b740c70 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`03fe2ae0 fffff880`04598398 : fffff800`00b96080 fffff880`04597d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`03fe2cd0 fffff880`04597e96 : 00000000`00000000 fffffa80`079b1010 00000000`00000080 fffffa80`08d72280 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`03fe2d00 fffff800`02f17fee : 00000000`fffffc32 fffffa80`08db8620 fffffa80`06705040 fffffa80`08db8620 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`03fe2d40 fffff800`02c6e5e6 : fffff800`02df2e80 fffffa80`08db8620 fffff800`02e00cc0 fffff880`01257cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`03fe2d80 00000000`00000000 : fffff880`03fe3000 fffff880`03fdd000 fffff880`03fe2680 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff88003fe1f00 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\rfw213\Windows_NT6_BSOD_jcgriff2\010612-16536-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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`02c1e000 PsLoadedModuleList = 0xfffff800`02e63670
Debug session time: Fri Jan  6 13:06:18.442 2012 (GMT-7)
System Uptime: 0 days 0:35:01.237
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {4, 2, 1, fffff80002ccc3a2}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGCONTEXT::ResizeUserModeBuffers+5a3 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000004, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ccc3a2, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ecd100
 0000000000000004 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KxWaitForLockOwnerShip+12
fffff800`02ccc3a2 48890a          mov     qword ptr [rdx],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  CivilizationV.

TRAP_FRAME:  fffff880075b8fd0 -- (.trap 0xfffff880075b8fd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880075b9220
rdx=0000000000000004 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ccc3a2 rsp=fffff880075b9160 rbp=fffff880075b9200
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8006601240
r11=fffff80002ed0a80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KxWaitForLockOwnerShip+0x12:
fffff800`02ccc3a2 48890a          mov     qword ptr [rdx],rcx ds:00000000`00000004=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c9a1e9 to fffff80002c9ac40

STACK_TEXT:  
fffff880`075b8e88 fffff800`02c9a1e9 : 00000000`0000000a 00000000`00000004 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`075b8e90 fffff800`02c98e60 : fffff880`08d00000 fffff880`08d03000 00000500`0000002d fffffa80`023cfdc0 : nt!KiBugCheckDispatch+0x69
fffff880`075b8fd0 fffff800`02ccc3a2 : 00000000`00000000 00000000`00000001 fffffa80`06705c68 00000000`00000001 : nt!KiPageFault+0x260
fffff880`075b9160 fffff800`02cab26d : fffffa80`023cfdc0 00000000`00000000 fffff880`075b9200 fffffa80`06705b60 : nt!KxWaitForLockOwnerShip+0x12
fffff880`075b9190 fffff800`02ccd967 : 00000000`00000000 fffff680`00054e80 00000000`00000000 fffffa80`08a70010 : nt!MiInsertPageInFreeOrZeroedList+0x55d
fffff880`075b92a0 fffff800`02cccbb7 : fffff880`02f64100 fffff680`00054e80 fffffa80`090159e0 fffff880`075b9518 : nt!MiDeletePteRun+0x4ed
fffff880`075b9450 fffff800`02c880ff : fffffa80`00000000 00000000`0a9d7fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`075b9610 fffff800`02c99ed3 : ffffffff`ffffffff fffff8a0`114f3950 fffff8a0`114f3948 6d646156`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`075b9710 fffff800`02c96470 : fffff880`0426fb63 fffff880`075b9ca0 00000000`00000003 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`075b98a8 fffff880`0426fb63 : fffff880`075b9ca0 00000000`00000003 00000000`00000000 00000000`00000500 : nt!KiServiceLinkage
fffff880`075b98b0 fffff880`0429588e : fffff8a0`114f38f0 fffffa80`095bd100 00000000`00003000 00000000`00000400 : dxgkrnl!DXGCONTEXT::ResizeUserModeBuffers+0x5a3
fffff880`075b9980 fffff960`001ef80e : 00000000`0f00e6b0 00000000`fdf8f000 00000000`0f2bc3c0 00000000`00003000 : dxgkrnl!DxgkRender+0x502
fffff880`075b9bf0 fffff800`02c99ed3 : 00000000`00000001 00000000`0a9d0000 00000000`00000001 00000000`0f2bc3d0 : win32k!NtGdiDdDDIRender+0x12
fffff880`075b9c20 00000000`7222164a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0f00e688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7222164a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DXGCONTEXT::ResizeUserModeBuffers+5a3
fffff880`0426fb63 4d897e68        mov     qword ptr [r14+68h],r15

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  dxgkrnl!DXGCONTEXT::ResizeUserModeBuffers+5a3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799fa

FAILURE_BUCKET_ID:  X64_0xA_dxgkrnl!DXGCONTEXT::ResizeUserModeBuffers+5a3

BUCKET_ID:  X64_0xA_dxgkrnl!DXGCONTEXT::ResizeUserModeBuffers+5a3

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\rfw213\Windows_NT6_BSOD_jcgriff2\010612-16879-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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`0301b000 PsLoadedModuleList = 0xfffff800`03260670
Debug session time: Fri Jan  6 20:58:10.117 2012 (GMT-7)
System Uptime: 0 days 5:27:11.943
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffff89580847, 1, fffff8800fceec21, 5}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Could not read faulting driver name
Probably caused by : hardware ( nvlddmkm+c37c21 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffff89580847, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8800fceec21, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032ca100
 ffffffff89580847 

FAULTING_IP: 
nvlddmkm+c37c21
fffff880`0fceec21 4eff8b47084c89  dec     qword ptr [rbx-76B3F7B9h]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002b9b5b0 -- (.trap 0xfffff88002b9b5b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000002b9b7c8
rdx=000001dff61802d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800fceec21 rsp=fffff88002b9b740 rbp=000000000a452c80
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffff8a010d321c4 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nvlddmkm+0xc37c21:
fffff880`0fceec21 4eff8b47084c89  dec     qword ptr [rbx-76B3F7B9h] ds:0234:ffffffff`894c0847=????????????????
Resetting default scope

MISALIGNED_IP: 
nvlddmkm+c37c21
fffff880`0fceec21 4eff8b47084c89  dec     qword ptr [rbx-76B3F7B9h]

LAST_CONTROL_TRANSFER:  from fffff800030423bf to fffff80003097c40

STACK_TEXT:  
fffff880`02b9b448 fffff800`030423bf : 00000000`00000050 ffffffff`89580847 00000000`00000001 fffff880`02b9b5b0 : nt!KeBugCheckEx
fffff880`02b9b450 fffff800`03095d6e : 00000000`00000001 ffffffff`89580847 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44791
fffff880`02b9b5b0 fffff880`0fceec21 : fffffa80`06fdc000 fffff880`02b9b950 00000000`00000000 fffffa80`08fc95d0 : nt!KiPageFault+0x16e
fffff880`02b9b740 fffffa80`06fdc000 : fffff880`02b9b950 00000000`00000000 fffffa80`08fc95d0 fffffa80`00000001 : nvlddmkm+0xc37c21
fffff880`02b9b748 fffff880`02b9b950 : 00000000`00000000 fffffa80`08fc95d0 fffffa80`00000001 fffff880`0f15a149 : 0xfffffa80`06fdc000
fffff880`02b9b750 00000000`00000000 : fffffa80`08fc95d0 fffffa80`00000001 fffff880`0f15a149 fffff880`0fceea3c : 0xfffff880`02b9b950


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+c37c21
fffff880`0fceec21 4eff8b47084c89  dec     qword ptr [rbx-76B3F7B9h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+c37c21

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_nvlddmkm.sys

BUCKET_ID:  X64_IP_MISALIGNED_nvlddmkm.sys

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\rfw213\Windows_NT6_BSOD_jcgriff2\010712-16536-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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`0321a000 PsLoadedModuleList = 0xfffff800`0345f670
Debug session time: Sat Jan  7 08:40:30.793 2012 (GMT-7)
System Uptime: 0 days 0:32:12.619
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff800032999a9, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXRstor+c7 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800032999a9, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


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

FAULTING_IP: 
nt!SwapContext_PatchXRstor+c7
fffff800`032999a9 c3              ret

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034c9100
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800032e2588 to fffff80003296c40

STACK_TEXT:  
fffff880`09523d08 fffff800`032e2588 : 00000000`0000001e ffffffff`c0000005 fffff800`032999a9 00000000`00000000 : nt!KeBugCheckEx
fffff880`09523d10 fffff800`032962c2 : fffff880`095244e8 fffff800`0340ce80 fffff880`09524590 fffffa80`07c92b60 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`095243b0 fffff800`03294bca : 00000000`00000000 fffff800`03299552 00000000`00000040 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`09524590 fffff800`032999a9 : ff02f800`032994da ff6efa80`07c92c20 00610000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`09524728 ff02f800`032994da : ff6efa80`07c92c20 00610000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXRstor+0xc7
fffff880`09524730 ff6efa80`07c92c20 : 00610000`00000000 00000000`00000000 00000000`00000000 fffffa80`07c92c68 : 0xff02f800`032994da
fffff880`09524738 00610000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`07c92c68 fffff800`0329bf32 : 0xff6efa80`07c92c20
fffff880`09524740 00000000`00000000 : 00000000`00000000 fffffa80`07c92c68 fffff800`0329bf32 04000800`38006c61 : 0x610000`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!SwapContext_PatchXRstor+c7
fffff800`032999a9 c3              ret

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!SwapContext_PatchXRstor+c7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_nt!SwapContext_PatchXRstor+c7

BUCKET_ID:  X64_0x1E_nt!SwapContext_PatchXRstor+c7

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

Your blue screen errors are all over the place, which usually signifies a hardware problem, system file corruption, or an underlying driver that is incompatible with your system. Proceed with the following steps.

Update the driver
Code:
```
speedfan fffff880`01941000 fffff880`01948000 Sun Sep 24 07:26:48 2006 (45168798) 00005062 speedfan.sys
```
To find information about drivers and their manufacturers, see Driver Reference and Drivers and Downloads respectively.
Run Disk Check with both boxes checked for all drives.
Use SFC /SCANNOW Command - System File Checker to check for system file corruption.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. If Memtest86+ has no errors after seven passes, run the extended version of Memory Diagnostics Tool for at least five passes. You may want to run these overnight as they take a while to complete.
You had a hardware crash, though not in the traditional sense. Still, Stop 0x124 - what it means and what to try may be worth looking into.
Since your hardware crash was related to your display driver, and you had another DirectX related crash in a different crash report, recommend Diagnosing basic problems with DirectX
For display card driver swapping, use the following steps.

a. Download and install Driver Sweeper
b. Download the latest driver for your display card
c. Click Start Menu
d. Right Click My Computer
e. Click Manage
f. Click Device Manager from the list on the left
g. Click the + next to Display adapter
h. Right click your display/graphics card device
i. Click Uninstall (do not hit ok when the dialog box shows up after clicking uninstall)
j. Check the box to Delete driver software for the device
k. Click OK
l. Restart your computer in safe mode
m. Run Driver Sweeper, select display card manufacturer's drivers, analyze, clean
n. Restart your computer
o. Install the latest drivers

rfw213 · 07 Jan 2012

Thank you for your help. I will begin the extended memory tests tonight.

writhziden · 29 Jan 2012

What were the results of the memory tests?

rfw213 · 30 Jan 2012

Thank you for your help with this.

The memory tests showed nothing when I ran them the first night. However, I reran them again the other night and during the first pass a number of errors came up. After the first pass there were no errors. I am not sure whether these are the result of bad memory, bad settings in the bios, or incompatability between the motherboard and the memory. (Although the memory is of a type and speed supported by the motherboard, the manufacturer does not include it in the list of supported memory modules.) In the past I have spent untold hours researching memory settings on the g.skill site and others and trying them for stability. I thought that I had found stable settings, but I suppose I have not.

Things are pressing at work, so I have not spent much time on the matter. But I need a stable system for both work and to keep my family photos safe on Lightroom. I hate to spend the money, but I think the most efficient option at this point is to get a new motherboard and make sure I buy memory on the manufacturer's supported list. Would you agree?

writhziden · 30 Jan 2012

Sometimes setting the BIOS DRAM voltage to that specified for the RAM modules works. Occasionally the Auto feature in the BIOS does not work as well as the manual option. If that does not work, try setting the voltage to 0.1 Volts higher than that specified for your RAM.

As for overall stability, it is always a good idea to get memory that has been tested by the motherboard manufacturer and is listed in their compatibility table. If you feel you need a new motherboard, you are right that buying memory on the supported list for that motherboard is the best option. Make sure when you install the memory modules that you are well grounded. It is possible to have electrostatic discharge into RAM that is not felt and ruin the RAM without realizing it. It takes very little voltage to ruin RAM, ~400 V, and you will not feel the discharge until it reaches ~1400 V-3000 V.

rfw213 · 30 Jan 2012

Thanks again for your help.

I did not realize that static discharge could occur and damage RAM yet remain physically unfelt.

Maybe that is what is wrong with my current RAM.

Regardless, I'll give building a computer another--careful--try this weekend.

Best,

Rob

writhziden · 30 Jan 2012

Yeah, many people do not realize the affects of static discharge. I did not know until a few years ago when I had it explained to me by an electrical engineer. RAM can function fine for a time after being damaged, and then it starts acting strangely and erratically due to the discharge during its installation. Many times, the user is unaware of why the RAM suddenly is failing because it has been slowly failing over time without giving obvious symptoms.

How did the new build go?