BSODs - 1000007e & 116

ProdigyGamer · 05 Mar 2013

This just popped up on Windows Update while my Galaxy S3 phone was plugged intot he USB port and I think it may have been what started all fo these BSODs:

SAMSUNG Electronics Co., Ltd. - Other hardware - SAMSUNG Mobile USB Composite Device
Download size: 6.5 MB
You may need to restart your computer for this update to take effect.
Update type: Recommended
SAMSUNG Electronics Co., Ltd. Other hardware software update released in January, 2013
More information:
Driver Information
Help and Support:
Product Solution Centers

I have not downloaded it as I do not need it and i do not want it to start me on a vicious cycle of BSOD again!

Saurabh A · 05 Mar 2013

Hi ProdigyGamer,

If you suspect the Samsung phone update as the root cause of the issue, you may ignore it; shouldn't really matter if all functionality is in place.

ProdigyGamer · 07 Mar 2013

Went well for 2 days until I got another 116 BSOD, I have uploaded to SkyDrive: 030713-38220-01

I still have not reinstalled Malwarebytes or TuneUp Utilities yet, as I wanted to follow your advice and test the PC performance for a few days.

I did idownload 4 games from Steam, 2 of which I installed (some updated windows for DirectX and/or Microsoft .NET Frame work.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 116
BCP1: FFFFFA8025A00210
BCP2: FFFFF880073C96C4
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\030713-38220-01.dmp
C:\Users\A5ASIN\AppData\Local\Temp\WER-81073-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Saurabh A · 07 Mar 2013

Hi ProdigyGamer,

The recent crash reflects an issue with 'nvlddmkm.sys driver'

Code:

Loading Dump File [C:\Users\saurabh_aggarwal\Downloads\030713-38220-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`03a60000 PsLoadedModuleList = 0xfffff800`03ca4670
Debug session time: Thu Mar  7 13:54:00.121 2013 (UTC + 5:30)
System Uptime: 0 days 8:51:04.980
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8025a00210, fffff880073c96c4, ffffffffc000009a, 4}

*** 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+9316c4 )

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

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

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

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


FAULTING_IP: 
nvlddmkm+9316c4
fffff880`073c96c4 4055            push    rbp

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`08a47a48 fffff880`04b3e000 : 00000000`00000116 fffffa80`25a00210 fffff880`073c96c4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`08a47a50 fffff880`04b11867 : fffff880`073c96c4 fffffa80`24a85000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`08a47a90 fffff880`04b3de0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`25a00210 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`08a47b40 fffff880`07577ec1 : fffffa80`22064180 00000000`00000080 00000000`00000000 fffffa80`213f0010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`08a47bc0 fffff800`03d7634a : 00000000`07128259 fffffa80`2252ab50 fffffa80`1942cb30 fffffa80`2252ab50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`08a47c00 fffff800`03ac6946 : fffff880`03942180 fffffa80`2252ab50 fffff880`0394d1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`08a47c40 00000000`00000000 : fffff880`08a48000 fffff880`08a42000 fffff880`08a474d0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+9316c4
fffff880`073c96c4 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+9316c4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5116d804

FAILURE_BUCKET_ID:  X64_0x116_VRF_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_VRF_IMAGE_nvlddmkm.sys

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

This driver relates to 'nVidia Video drivers'. Please update the 'nVidia display drivers' and check results.
You may try this link first: Driver Details | Dell US

If you still experience the issue, the current driver may be corrupt; uninstall that driver and install a fresh one from 'nVidia website'. Follow these steps: Open 'Device Manager' > Expand 'Display Adapters' > Uninstall 'nVidia driver' and follow through > Restart the system > Install fresh drivers for 'nVidia GeForce 590 card' from this link:

Do reply with the findings.

ProdigyGamer · 07 Mar 2013

Downloading now, thanks Saurabh.

ProdigyGamer · 07 Mar 2013

Saurabh A said:

Hi ProdigyGamer,

The recent crash reflects an issue with 'nvlddmkm.sys driver'

Code:

Loading Dump File [C:\Users\saurabh_aggarwal\Downloads\030713-38220-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`03a60000 PsLoadedModuleList = 0xfffff800`03ca4670
Debug session time: Thu Mar  7 13:54:00.121 2013 (UTC + 5:30)
System Uptime: 0 days 8:51:04.980
Loading Kernel Symbols
.
 
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
 
..............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 116, {fffffa8025a00210, fffff880073c96c4, ffffffffc000009a, 4}
 
*** 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+9316c4 )
 
Followup: MachineOwner
---------
 
11: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8025a00210, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880073c96c4, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
 
Debugging Details:
------------------
 
 
FAULTING_IP: 
nvlddmkm+9316c4
fffff880`073c96c4 4055            push    rbp
 
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
 
CUSTOMER_CRASH_COUNT:  1
 
BUGCHECK_STR:  0x116
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
STACK_TEXT:  
fffff880`08a47a48 fffff880`04b3e000 : 00000000`00000116 fffffa80`25a00210 fffff880`073c96c4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`08a47a50 fffff880`04b11867 : fffff880`073c96c4 fffffa80`24a85000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`08a47a90 fffff880`04b3de0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`25a00210 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`08a47b40 fffff880`07577ec1 : fffffa80`22064180 00000000`00000080 00000000`00000000 fffffa80`213f0010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`08a47bc0 fffff800`03d7634a : 00000000`07128259 fffffa80`2252ab50 fffffa80`1942cb30 fffffa80`2252ab50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`08a47c00 fffff800`03ac6946 : fffff880`03942180 fffffa80`2252ab50 fffff880`0394d1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`08a47c40 00000000`00000000 : fffff880`08a48000 fffff880`08a42000 fffff880`08a474d0 00000000`00000000 : nt!KxStartSystemThread+0x16
 
 
STACK_COMMAND:  .bugcheck ; kb
 
FOLLOWUP_IP: 
nvlddmkm+9316c4
fffff880`073c96c4 4055            push    rbp
 
SYMBOL_NAME:  nvlddmkm+9316c4
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nvlddmkm
 
IMAGE_NAME:  nvlddmkm.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  5116d804
 
FAILURE_BUCKET_ID:  X64_0x116_VRF_IMAGE_nvlddmkm.sys
 
BUCKET_ID:  X64_0x116_VRF_IMAGE_nvlddmkm.sys
 
Followup: MachineOwner
---------

This driver relates to 'nVidia Video drivers'. Please update the 'nVidia display drivers' and check results.
You may try this link first: Driver Details | Dell US

If you still experience the issue, the current driver may be corrupt; uninstall that driver and install a fresh one from 'nVidia website'. Follow these steps: Open 'Device Manager' > Expand 'Display Adapters' > Uninstall 'nVidia driver' and follow through > Restart the system > Install fresh drivers for 'nVidia GeForce 590 card' from this link:

Do reply with the findings.

I tried the Dell drivers that rolled me back but I continually went into BSOD and couldn't even load Windows without hitting F2 to go into the menu then exit to continue windows loading.

Once I got back into Windows, I Uninstalled/Deleted current drivers, reboot the PC then installed a fresh set of latest WHQL drivers and I have spent around 1 hour testing in a game and so far no 116 BSOD.

I will continue testing but so far so good, thanks again Saurabh :)

Saurabh A · 10 Mar 2013

Hi ProdigyGamer,

Glad that the 'WHQL drivers' exhibited better results.
Please check the system performance and post the findings; glad to assist.

ProdigyGamer · 10 Mar 2013

Just got a 116 BSOD while watching a video, first one since my last post and I have been testing pretty heavily.

Uploaded to SkyDrive: 031113-36894-01

https://skydrive.live.com/#cid=F9598...14D867BA%21115

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 116
BCP1: FFFFFA801A5BE4E0
BCP2: FFFFF8800660D6C4
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\031113-36894-01.dmp
C:\Users\A5ASIN\AppData\Local\Temp\WER-90511-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Saurabh A · 10 Mar 2013

Hi ProdigyGamer,

The 'nvlddmkm.sys' (nVidia Video driver) seems to be causing the crash again.
Error: 'VIDEO_TDR_FAILURE (116): Attempt to reset the display driver and recover from timeout failed'.

Code:

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


Loading Dump File [C:\Errors\031113-36894-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`03a0a000 PsLoadedModuleList = 0xfffff800`03c4e670
Debug session time: Mon Mar 11 05:48:41.368 2013 (UTC + 5:30)
System Uptime: 0 days 0:20:03.228
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa801a5be4e0, fffff8800660d6c4, ffffffffc000009a, 4}

*** 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+9316c4 )

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

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

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

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


FAULTING_IP: 
nvlddmkm+9316c4
fffff880`0660d6c4 4055            push    rbp

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03335a48 fffff880`06aa5000 : 00000000`00000116 fffffa80`1a5be4e0 fffff880`0660d6c4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`03335a50 fffff880`06a78867 : fffff880`0660d6c4 fffffa80`24a03000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03335a90 fffff880`06aa4e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`1a5be4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`03335b40 fffff880`06b73ec1 : fffffa80`1a954010 00000000`00000080 00000000`00000000 fffffa80`248f2410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`03335bc0 fffff800`03d2034a : 00000000`06a96cfb fffffa80`2474db50 fffffa80`1942cb30 fffffa80`2474db50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`03335c00 fffff800`03a70946 : fffff880`03942180 fffffa80`2474db50 fffff880`0394d1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03335c40 00000000`00000000 : fffff880`03336000 fffff880`03330000 fffff880`033354d0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+9316c4
fffff880`0660d6c4 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+9316c4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5116d804

FAILURE_BUCKET_ID:  X64_0x116_VRF_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_VRF_IMAGE_nvlddmkm.sys

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

11: kd> !sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM) i7-3960X CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3300

This behavior can occur for one or more of the following reasons:
- You may need to install the latest updates for your display driver (Already done)
- Visual effects, or too many programs running in the background may be slowing your PC down
- The 'GPU' is taking more time than permitted to display graphics to your monitor

Please refer to the following 'Microsoft Article' to see if that helps (run the fixit): "Display driver stopped responding and has recovered" error in Windows 7 or Windows Vista

Hope this helps. Do reply with the findings.

ProdigyGamer · 10 Mar 2013

This behavior can occur for one or more of the following reasons:
- You may need to install the latest updates for your display driver (Already done)
- Visual effects, or too many programs running in the background may be slowing your PC down (usually only 1 - either 1 game or 1 video on a web page like YouTube etc.)
- The 'GPU' is taking more time than permitted to display graphics to your monitor

I have run the "Fit It" program and done a reboot, I will continue testing now, thank you Saurabh.