Solved BSOD randomly (mostly) when idle dxgkrnl.sys

[ckonze]

I'm hoping you can help us out. I'm stepping up to the plate because my poor husband has been trying to correct these issues for a month now and has pretty much had it.

New computer, home build, specs below. We've had it for a bit over 30 days. It frequently gets the BSOD, usually when idle. They are also completely random in their frequency. We've gone as short as a day and as long as two weeks between BSOD's. Attempts at correcting this thus far have included replacing all hardware EXCEPT for the motherboard, PSU and CPU. Unfortunately I have passed the return period on all three, although maybe I can sweet talk a new mb and psu out of Amazon if I really need to. He's been monitoring temps and all seems well. He also ran a stress test on the GPU/RAM, but that was a few Window's installs prior to this one (if that matters/makes sense).

We used BlueScreenViewer and it spat back the dxgkrnl.sys error at us yesterday. The error on the BSOD is "Attempt to reset the display driver and recover from timeout failed." He reinstalled windows, updated all drivers and directX and it crashed again today. On a previous install he downloaded an ISO of Windows and used that in case there was in issue with our retail install discs. I'm pretty sure that's about it.

He has also re-installed windows/started from scratch more times than I can count.

I tried following the wiki, but please let me know if I've missed anything!

Thanks.

System Specs (via the "System Spec" tab): http://www.sevenforums.com/member.php?u=203155

Attached the necessary files.

Things that have been replaced:
SSD
GPU
RAM

 

[zigzag3143]

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps

http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

 

[ckonze]

Thanks but as I mentioned in my initial post, temperatures have been monitored (via GPU-Z and CPU-Z) and are well within the limits. Overheating is simply not the problem. Especially when you consider that the vast majority of these BSOD's occur when the computer is idle. Dust build-up is also not the problem as the system was hand build about a month ago and has been reopened several times over the last thirty days in order to swap components as means of troubleshooting this very issue. The fans as well as every other component are clean as a whistle. Nevertheless, the BSOD's continue to occur. Any other ideas?

 

[zigzag3143]

Thanks but as I mentioned in my initial post, temperatures have been monitored (via GPU-Z and CPU-Z) and are well within the limits. Overheating is simply not the problem. Especially when you consider that the vast majority of these BSOD's occur when the computer is idle. Dust build-up is also not the problem as the system was hand build about a month ago and has been reopened several times over the last thirty days in order to swap components as means of troubleshooting this very issue. The fans as well as every other component are clean as a whistle. Nevertheless, the BSOD's continue to occur. Any other ideas?

If you are still having BSOD'S upload the DMPs as they may narrow the focus. BCC116 are almost always heat, or power related.

 

[ckonze]

I thought I uploaded the dmp file. Did I do something incorrectly? The BSODs are random and can happen every day or every week, seems to vary. I tried the recommendations (as stated above, for reference) and BSODs have been recurrent for the past 4 weeks. I do not have other dmp files though because I have swapped drives and reinstalled Windows a few times.

 

[zigzag3143]

I thought I uploaded the dmp file. Did I do something incorrectly? The BSODs are random and can happen every day or every week, seems to vary. I tried the recommendations (as stated above, for reference) and BSODs have been recurrent for the past 4 weeks. I do not have other dmp files though because I have swapped drives and reinstalled Windows a few times.

Have to wait for more then

 

[ckonze]

Happened again on 4/17 while the computer was left on overnight. Any thoughts? It is getting remarkably frustrating and husband wants to now sell it for parts rather than troubleshoot further. Would prefer a working computer.

 

[ckonze]

Bump. Anyone have any ideas? This error code is different than the last one.

 

[writhziden]

No .dmp files were included.

Re-install or install the latest drivers for your display card. Your current drivers may be corrupt and/or outdated. Use the following method to re-install the drivers.

1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Click Control Panel
4. Click Uninstall a program
5. For AMD:
   • Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
   • If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
     1. Click Start Menu
     2. Right Click My Computer/Computer
     3. Click Manage
     4. Click Device Manager from the list on the left
     5. Expand Display adapters
     6. Do the following for each adapter (in case you have multiple display cards)
        • Right click the adapter
        • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
        • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
     7. Restart your computer after uninstalling drivers for all display cards
     8. Install the latest driver for the display cards once Windows starts
     
     Alternatively:
     1. Login as an adminstrative user
     2. Click Start Menu
     3. Click Control Panel
     4. Click Hardware and Sound
     5. Click Device Manager (the last link under Devices and Printers)
     6. Expand Display adapters
     7. Do the following for each adapter (in case you have multiple display cards)
        • Right click the adapter
        • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
        • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
6. Restart your computer after uninstalling drivers for all display cards
7. Install the latest driver for the display cards once Windows starts

 

[ckonze]

Hmm, sorry about the missing file. I will update that tonight. I don't recall the error code anymore, but the second BSOD was not giving the same dxgkrnl.sys.

I did the above listed steps before the most recent BSOD.

 

[ckonze]

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

Thanks.

 

[writhziden]

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.

 

[ckonze]

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?

 

[writhziden]

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.

 

[ckonze]

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?

 

[writhziden]

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

 

[ckonze]

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

 

[ckonze]

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

 

[writhziden]

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.

 

[ckonze]

I mistyped the VTT voltage. It was actually 1.151V, not 1.157V. No doubt this changes the value that I should change it to.

I also do not have full manual control over the VTT voltage value. It does not allow me to simply type in the value I want. I can only change it to one of several predetermined values. The VTT voltage levels that I can change it to that are close to the value you are looking for are 1.142V, 1.155V, and 1.168V. Which of those should I change it to?

Also, after changing the VTT voltage value, in order to test system stability, should I run Memtest86 again or should I just stand by for another BSOD?