BSOD randomly (mostly) when idle dxgkrnl.sys

I should have the dump files now. Please let me know if something is missing.

Thanks.

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\ckonze\Windows_NT6_BSOD_jcgriff2\041712-7612-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 Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02a02000 PsLoadedModuleList = 0xfffff800`02c46650
Debug session time: Mon Apr 16 20:52:00.248 2012 (UTC - 6:00)
System Uptime: 5 days 19:33:51.075
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffea8011f3e3b2, 0, fffff80002a5fb59, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiValidateImagePages+329 )

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

1: 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: ffffea8011f3e3b2, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002a5fb59, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb0100
 ffffea8011f3e3b2 

FAULTING_IP: 
nt!MiValidateImagePages+329
fffff800`02a5fb59 41f644242a02    test    byte ptr [r12+2Ah],2

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x50

PROCESS_NAME:  GoogleUpdate.e

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800a6d5530 -- (.trap 0xfffff8800a6d5530)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007df0a00 rbx=0000000000000000 rcx=fffff880009eb180
rdx=0000058000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a5fb59 rsp=fffff8800a6d56c0 rbp=fffff8a0073d9790
 r8=fffffa8000000008  r9=fffffa8004aae640 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiValidateImagePages+0x329:
fffff800`02a5fb59 41f644242a02    test    byte ptr [r12+2Ah],2 ds:3d48:00000000`0000002a=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a29ba7 to fffff80002a7ec80

STACK_TEXT:  
fffff880`0a6d53c8 fffff800`02a29ba7 : 00000000`00000050 ffffea80`11f3e3b2 00000000`00000000 fffff880`0a6d5530 : nt!KeBugCheckEx
fffff880`0a6d53d0 fffff800`02a7cdae : 00000000`00000000 ffffea80`11f3e3b2 fffff880`09f35100 00000000`0029fae0 : nt! ?? ::FNODOBFM::`string'+0x43cc1
fffff880`0a6d5530 fffff800`02a5fb59 : fffff8a0`073d9790 fffffa80`07df0a00 00000000`00000000 fffff8a0`073d9780 : nt!KiPageFault+0x16e
fffff880`0a6d56c0 fffff800`02d59a81 : fffffa80`11f3e2d0 fffff6fc`40047e28 fffff8a0`00000002 00000000`00000000 : nt!MiValidateImagePages+0x329
fffff880`0a6d5770 fffff800`02d59bc0 : ffffffff`ffffffff 00000000`00000001 fffff8a0`073eb000 00000000`00000024 : nt!MiSwitchBaseAddress+0x61
fffff880`0a6d57a0 fffff800`02d7a79f : 00000000`00000004 00000000`00000080 00000000`01000000 00000000`01000000 : nt!MiRelocateImageAgain+0x100
fffff880`0a6d57f0 fffff800`02d59306 : fffff880`0a6d5a40 fffff880`0a6d5b60 00000000`00000000 fffff880`0a6d5a38 : nt!MmCreateSection+0x2df
fffff880`0a6d59f0 fffff800`02a7df13 : fffffa80`1385bb60 00000000`0008e2d8 fffff880`0a6d5a88 00000000`00000000 : nt!NtCreateSection+0x171
fffff880`0a6d5a70 00000000`77c317ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c317ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiValidateImagePages+329
fffff800`02a5fb59 41f644242a02    test    byte ptr [r12+2Ah],2

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiValidateImagePages+329

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_VRF_nt!MiValidateImagePages+329

BUCKET_ID:  X64_0x50_VRF_nt!MiValidateImagePages+329

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

Appears to be due to memory problems.

• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Ok, I've run the Memtest86 and have errors. It is still running and it showing a lot of things in red. Does this mean I have to change the RAM?

This is my second round of ram, so I'm wondering if maybe something else would be causing an error like this?

I would recommend running with 8GB and seeing how the system responds in Windows through your normal routine. Run for as long, or better twice as long, as you normally need to for crashes to occur and do the things that normally cause crashes. See if you can isolate a good set of 8 GB of RAM. If both sets of 8 GB work, it may be that the RAM settings are not configured properly.

writhziden said:

I would recommend running with 8GB and seeing how the system responds in Windows through your normal routine. Run for as long, or better twice as long, as you normally need to for crashes to occur and do the things that normally cause crashes. See if you can isolate a good set of 8 GB of RAM. If both sets of 8 GB work, it may be that the RAM settings are not configured properly.

Thanks. At this point, I'm not sure what causes the crashes. It will be fine for sometimes as long as 2 weeks and then during a point of being completely idle -- BSOD.

Our first round of RAM was Corsair 8gb and we had crashes on/off for months. We installed the current Corsair 16gb maybe a month ago and still the same frequency of crashes.

Forgive my ignorance, but how would I adjust the RAM settings if that is the issue?

Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

Also, go into your BIOS and post all Voltages (CPU, RAM, NB, IMC, etc.) and all RAM settings (timings, frequency, etc.)

Thanks to Dave76 for help learning RAM Stability

Here are the screenshots. I will report back shortly with the requested BIOS info.

Hopefully I have all the correct info. I felt very lost in the BIOS. :)

Voltage
CPU Core 1.192v
CPU Load Line level 5
DRAM 1.500v
PCH 1.059v
CPU PLL 1.823v
VTT 1.057v
VCCSA 0.925V

RAM Settings
9-9-9-24 1.50v DDR3-1600
Frequency DDR3-1333
Latency 9
Active Time 24
CR 2N
tWR 10
tRFC 107
tRRD 5
tFAW 25

Timings look good. The RAM was tested at 1.5 V, so DRAM voltage should remain there for now. Bump your VTT voltage to 1.157V and see if the system is more stable. Be careful doing this and double check that the number is indeed 1.157V because too high a voltage can damage components.