BSOD when unplugging ethernet

Problem Devices:

Code:

LGE Android Phone    USB\VID_1004&PID_618E\033C118940A06157    The drivers for this device are not installed.

Possible outdated drivers:

Code:

rixdpx64    fffff880`040de000    fffff880`04135000    Fri Jul 27 04:45:50 2007 (46a9ccde)    0000fbda        rixdpx64.sys
rimspx64    fffff880`040c7000    fffff880`040de000    Mon Mar 03 02:19:03 2008 (47cbc287)    000122a5        rimspx64.sys
rimmpx64    fffff880`040b1000    fffff880`040c7000    Fri Oct 03 00:39:15 2008 (48e5be13)    0001567d        rimmpx64.sys
GEARAspiWDM    fffff880`0418a000    fffff880`04197000    Mon May 18 06:17:04 2009 (4a1151c0)    000159b4        GEARAspiWDM.sys
bcmwl664    fffff880`04a08000    fffff880`04cb0000    Tue Jul 07 18:45:04 2009 (4a53ec10)    002a9bad        bcmwl664.sys

rixdpx64.sys
rimspx64.sys
rimmpx64.sys
GEARAspiWDM.sys
bcmwl664.sys

Code:

 
Loading Dump File [D:\Kingston\BSODDmpFiles\Amearai\Windows_NT6_BSOD_jcgriff2\012812-26364-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c59000 PsLoadedModuleList = 0xfffff800`02e9e670
Debug session time: Sat Jan 28 16:36:18.294 2012 (UTC - 7:00)
System Uptime: 0 days 1:41:40.792
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 116, {fffffa80071b24e0, fffff8800f385cd8, 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+170cd8 )
 
Followup: MachineOwner
---------
 
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80071b24e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f385cd8, 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+170cd8
fffff880`0f385cd8 4883ec28        sub     rsp,28h
 
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
 
CUSTOMER_CRASH_COUNT:  1
 
BUGCHECK_STR:  0x116
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
STACK_TEXT:  
fffff880`033ff988 fffff880`0fed8000 : 00000000`00000116 fffffa80`071b24e0 fffff880`0f385cd8 00000000`00000000 : nt!KeBugCheckEx
fffff880`033ff990 fffff880`0fed7d0a : fffff880`0f385cd8 fffffa80`071b24e0 fffffa80`064a9d50 fffffa80`064a4010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`033ff9d0 fffff880`0ff7ef07 : fffffa80`071b24e0 00000000`00000000 fffffa80`064a9d50 fffffa80`064a4010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`033ffa00 fffff880`0ffa8b75 : 00000000`ffffffff 00000000`0005f709 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`033ffae0 fffff880`0ffa72bb : 00000000`00000102 00000000`00000000 00000000`0005f709 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`033ffb10 fffff880`0ff7a2c6 : ffffffff`ff676980 fffffa80`064a4010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`033ffbb0 fffff880`0ffa6e7a : 00000000`00000000 fffffa80`03dd1850 00000000`00000080 fffffa80`064a4010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`033ffcc0 fffff800`02f70fee : 00000000`fffffc32 fffffa80`064a58c0 fffffa80`03cceb30 fffffa80`064a58c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`033ffd00 fffff800`02cc75e6 : fffff880`009e9180 fffffa80`064a58c0 fffff880`009f3f40 fffff880`0121a384 : nt!PspSystemThreadStartup+0x5a
fffff880`033ffd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
 
 
STACK_COMMAND:  .bugcheck ; kb
 
FOLLOWUP_IP: 
nvlddmkm+170cd8
fffff880`0f385cd8 4883ec28        sub     rsp,28h
 
SYMBOL_NAME:  nvlddmkm+170cd8
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nvlddmkm
 
IMAGE_NAME:  nvlddmkm.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4e391010
 
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
 
BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
 
Followup: MachineOwner
---------

H2SO4 said:

These are all stop 0x116 VIDEO_TDR_FAILURE conditions.

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.

The above quote was taken from https://www.sevenforums.com/crashes-d...tml#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining STOP 0x116: VIDEO_TDR_ERROR troubleshooting and proceed through each step. Let us know if you need further help.


Have you done the steps for the VIDEO_TDR_ERROR? Let us know if you need any help.