BCCode: 116 when starting games with enabled sli using x79(bluescreen)

leksandarn · 15 Dec 2012

I don´t know if it have something to do with my drivers or anything, i attached the file i got from the SF Diagnostic Tool. Hope this is enough info for you guys :)

With one card activated everything works just fine but when i enable sli and start a game i get bluescreen and get this message:

Problemsignatur:
Problemhändelsens namn: BlueScreen
OS-version: 6.1.7600.2.0.0.256.1
Språkvariant-ID: 1053

Ytterligare information om problemet:
BCCode: 116
BCP1: FFFFFA80118FF010
BCP2: FFFFF88007BFAB10
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

My rig is i7 3820, gigabyte ud3, gtx 580 sli

bagavan · 15 Dec 2012

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80118ff010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007bfab10, 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:
------------------


OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap

FAULTING_IP: 
nvlddmkm+993b10
fffff880`07bfab10 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02313b48 fffff880`06d14cbc : 00000000`00000116 fffffa80`118ff010 fffff880`07bfab10 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`02313b50 fffff880`06ce8867 : fffff880`07bfab10 fffffa80`0eba9000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02313b90 fffff880`06d14acb : fffffa80`ffffd87b ffffffff`fffe7960 fffffa80`118ff010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`02313c40 fffff880`06de3ec1 : fffffa80`0d9a5010 00000000`00000080 00000000`00000000 fffffa80`0cdc02e0 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`02313cc0 fffff800`03769166 : 00000000`00000000 fffffa80`0f164b60 fffffa80`0cd77040 00000000`00000000 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`02313d00 fffff800`034a4486 : fffff800`0363ee80 fffffa80`0f164b60 fffff800`0364cc40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02313d40 00000000`00000000 : fffff880`02314000 fffff880`0230e000 fffff880`023135d0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+993b10
fffff880`07bfab10 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+993b10

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50b97852

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

Please update your nvidia drivers to the latest version.

http://www.nvidia.com/Download/index.aspx

leksandarn · 16 Dec 2012

bagavan said:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80118ff010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007bfab10, 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:
------------------


OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap

FAULTING_IP: 
nvlddmkm+993b10
fffff880`07bfab10 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02313b48 fffff880`06d14cbc : 00000000`00000116 fffffa80`118ff010 fffff880`07bfab10 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`02313b50 fffff880`06ce8867 : fffff880`07bfab10 fffffa80`0eba9000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02313b90 fffff880`06d14acb : fffffa80`ffffd87b ffffffff`fffe7960 fffffa80`118ff010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`02313c40 fffff880`06de3ec1 : fffffa80`0d9a5010 00000000`00000080 00000000`00000000 fffffa80`0cdc02e0 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`02313cc0 fffff800`03769166 : 00000000`00000000 fffffa80`0f164b60 fffffa80`0cd77040 00000000`00000000 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`02313d00 fffff800`034a4486 : fffff800`0363ee80 fffffa80`0f164b60 fffff800`0364cc40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02313d40 00000000`00000000 : fffff880`02314000 fffff880`0230e000 fffff880`023135d0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+993b10
fffff880`07bfab10 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+993b10

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50b97852

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

Please update your nvidia drivers to the latest version.

Drivers - Download NVIDIA Drivers

That is what i also thought, so i tried installing the latest beta driver but i did get the same error. Then i tried an old driver that have worked for me with this rig. Exactly the same error. Can it be some settings or anything with the drivers?
I have tried 306.97 also.

bagavan · 16 Dec 2012

Have you over clocked your GPU?

If you experience new crashes post the dumps

leksandarn · 16 Dec 2012

bagavan said:

Have you over clocked your GPU?

If you experience new crashes post the dumps

Not atm, but i have before. I have not overclocked since my fresh windows install.
I´m not home atm, but i can start a game and i will get bluescreen after 1sec, it happens everytime. Do you just want windows error message or should i use SF Diagnostic Tool?

bagavan · 16 Dec 2012

I believe your GPU setting are in their default values.

Use SF diag tool

leksandarn · 16 Dec 2012

bagavan said:

I believe your GPU setting are in their default values.

Use SF diag tool

I have now updated the drivers to the latest beta drivers (310.70). Did get the same error so i´ll attach the new file here.

bagavan · 16 Dec 2012

Don`t update to beta drivers as they might be unstable.

Install the latest stable version

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8010e46010, fffff88007bebb10, ffffffffc000009a, 4}

Unable to load image 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+993b10 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8010e46010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007bebb10, 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+993b10
fffff880`07bebb10 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0e862b48 fffff880`06c5dcbc : 00000000`00000116 fffffa80`10e46010 fffff880`07bebb10 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0e862b50 fffff880`06c31867 : fffff880`07bebb10 fffffa80`0d388000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0e862b90 fffff880`06c5dacb : fffffa80`ffffd87b ffffffff`fffe7960 fffffa80`10e46010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0e862c40 fffff880`06d2cec1 : fffffa80`0f1c0d50 00000000`00000080 00000000`00000000 fffffa80`0cf582c0 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0e862cc0 fffff800`03760166 : 00000000`00000000 fffffa80`0e982470 fffffa80`0cd77040 00000000`00000000 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0e862d00 fffff800`0349b486 : fffff800`03635e80 fffffa80`0e982470 fffff800`03643c40 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`0e862d40 00000000`00000000 : fffff880`0e863000 fffff880`0e85d000 fffff880`0e8625d0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+993b10
fffff880`07bebb10 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+993b10

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50b97852

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

Still blames nvidia drivers

leksandarn · 17 Dec 2012

bagavan said:

Don`t update to beta drivers as they might be unstable.

Install the latest stable version

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8010e46010, fffff88007bebb10, ffffffffc000009a, 4}

Unable to load image 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+993b10 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8010e46010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007bebb10, 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+993b10
fffff880`07bebb10 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0e862b48 fffff880`06c5dcbc : 00000000`00000116 fffffa80`10e46010 fffff880`07bebb10 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0e862b50 fffff880`06c31867 : fffff880`07bebb10 fffffa80`0d388000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0e862b90 fffff880`06c5dacb : fffffa80`ffffd87b ffffffff`fffe7960 fffffa80`10e46010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0e862c40 fffff880`06d2cec1 : fffffa80`0f1c0d50 00000000`00000080 00000000`00000000 fffffa80`0cf582c0 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0e862cc0 fffff800`03760166 : 00000000`00000000 fffffa80`0e982470 fffffa80`0cd77040 00000000`00000000 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0e862d00 fffff800`0349b486 : fffff800`03635e80 fffffa80`0e982470 fffff800`03643c40 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`0e862d40 00000000`00000000 : fffff880`0e863000 fffff880`0e85d000 fffff880`0e8625d0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+993b10
fffff880`07bebb10 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+993b10

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50b97852

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

Still blames nvidia drivers

Nvidia set the 310.70 as stable today. So i downloaded their stable one and after installing and activating sli, the same error again. What in the drivers can be wrong? What can i do when no drivers are working? Hardware problems?

bagavan · 17 Dec 2012

run this

Driver Verifier - Enable and Disable

post back the dumps