Windows 7: BSOD The bugcheck was: 0x00000116

cyla · 11 Feb 2010

Hi guys I have a new windows 7 computer and I had my first bsod with the following bugcheck.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xfffffa800679b4e0, 0xfffff880048ec220, 0x0000000000000000, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 012210-38859-01.

I have attached the memory.dmp Since then I have had two more BSOD with the following info, but they have not been recorded in the memory.dmp.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x0000000000000018, 0x0000000000000000, 0xfffff88003115180, 0x0000000000000006). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

I have changed the settings to a small memory dump instead of the kernel one, in the hope that it will save a dump the next time, but if anyone can help me out with this I would be grateful!

thanks C

zigzag3143 · 11 Feb 2010

Quote: Originally Posted by cyla

Hi guys I have a new windows 7 computer and I had my first bsod with the following bugcheck.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xfffffa800679b4e0, 0xfffff880048ec220, 0x0000000000000000, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 012210-38859-01.

I have attached the memory.dmp Since then I have had two more BSOD with the following info, but they have not been recorded in the memory.dmp.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x0000000000000018, 0x0000000000000000, 0xfffff88003115180, 0x0000000000000006). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

I have changed the settings to a small memory dump instead of the kernel one, in the hope that it will save a dump the next time, but if anyone can help me out with this I would be grateful!

thanks C

HI C

this crash was caused by your video driver.

you should
downlaod afresh copy and install it
run a system sile check
type cmd in search>right click and run as admin>sfc /scannow

Ken

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\012210-38859-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 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e56e50
Debug session time: Fri Jan 22 03:11:29.842 2010 (GMT-5)
System Uptime: 0 days 23:11:48.889
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800679b4e0, fffff880048ec220, 0, 2}

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
Probably caused by : nvlddmkm.sys ( nvlddmkm+e7220 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800679b4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880048ec220, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+e7220
fffff880`048ec220 803d31c0960000  cmp     byte ptr [nvlddmkm+0xa53258 (fffff880`05258258)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`065159c8 fffff880`05327ef8 : 00000000`00000116 fffffa80`0679b4e0 fffff880`048ec220 00000000`00000000 : nt!KeBugCheckEx
fffff880`065159d0 00000000`00000116 : fffffa80`0679b4e0 fffff880`048ec220 00000000`00000000 00000000`00000002 : dxgkrnl+0x5cef8
fffff880`065159d8 fffffa80`0679b4e0 : fffff880`048ec220 00000000`00000000 00000000`00000002 00000000`00000000 : 0x116
fffff880`065159e0 fffff880`048ec220 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`0679b4e0
fffff880`065159e8 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`05327c02 : nvlddmkm+0xe7220


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+e7220
fffff880`048ec220 803d31c0960000  cmp     byte ptr [nvlddmkm+0xa53258 (fffff880`05258258)],0

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+e7220

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4abfff56

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

cyla · 12 Feb 2010

Thanks Ken

I did update my nvidia drivers after it happened, and then I got the two BSOD that didn't create a dump file. I have run a system file check and it couldn't find anything.

I guess I will have to wait and see whether it happens again.

thanks!
C

usasma · 12 Feb 2010

Info on the STOP 0x116: BSOD Index
More info on this particular error: AMD Game Forums - ATIKMDAG.sys problems and TDR FAQ

Best advice that I've seen about this error (from here: http://www.sevenforums.com/crashes-d...tml#post280172 )

Quote:

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." - H2SO4

If all that doesn't work, then I'd have to suggest trying a new video card.

Windows 7: BSOD The bugcheck was: 0x00000116

BSOD The bugcheck was: 0x00000116 problems?