Blue screen while playing F1 2012, BCCode 116

Pullrod · 12 Jul 2013

Hey,

Today blue screen appeared while playing F1 2012 for about 40 minutes. I played the game ever since it came out and had so far no problems. I even played it on Monday for about 2 hours-still no problem. I haven´t installed any new software, the only thing that is changed from Monday are couple of Windows updates (NET framework, Silverlight) and QuickTime+iTunes update. Video card is not overheating since it is was running at 55°C at the time of playing. Then I updated video card drivers, ran the game again, and again blue screen appeared after 40 min. What is going on?

I would be glad if you could help me. Thanks!

Arc · 13 Jul 2013

Post it following the Blue Screen of Death (BSOD) Posting Instructions and upload your MSINFO32.nfo file.

Click on the start button
Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
Give the time for processing, it will save a .nfo file on your desktop.
Zip it, and upload it following the instruction.

We need to see some more stuff to infer about the situation.

Pullrod · 13 Jul 2013

Thanks for reply! Unfortunately I am on holidays at the moment. I will follow your instructions as soon as I come home next Saturday. I would post that file in this thread. Please reply then as well. Cheers, mate!

Pullrod · 20 Jul 2013

Hey,

Here I am again! When I turned the computer on, it asked me to download some video card software updates. I chose to download and install them. I then tried to play F1 2012 again, and this time blue screen appeared after 8 min of playing. I uploaded new diagonistic file and msinfo file as well (both created today). Hope you will be able to help me.

Arc · 20 Jul 2013

One thing caught my attention at the first point. The BIOS date.

Code:

BiosVersion = F7
BiosReleaseDate = 08/18/2008

Which indicates that the computer is old. An old computer is supposed to be a victim of dust allocation and dried up thermal paste. The heat factor will not allow to do any stressful operation for long.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.
Better do it twice... once after one hour of usage and the other after two hours of usage.

Also let us know the wattage of your PSU.

The dump shoes that it is a display caused stop 0x116, whereas the display driver is of the latest version.

Code:

.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8003d8e4e0, fffff880051a2700, 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+8ed700 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8003d8e4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880051a2700, 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+8ed700
fffff880`051a2700 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`064aeb48 fffff880`03f60054 : 00000000`00000116 fffffa80`03d8e4e0 fffff880`051a2700 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`064aeb50 fffff880`03f33867 : fffff880`051a2700 fffffa80`05e92000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`064aeb90 fffff880`03f5fe63 : fffffa80`ffffd84d 00000000`00000000 fffffa80`03d8e4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`064aec40 fffff880`053d203d : fffffa80`0641ac90 00000000`00000080 00000000`00000000 fffffa80`05ba2410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`064aecc0 fffff800`02d6cede : 00000000`050f7b7c fffffa80`0547e060 fffffa80`039a9380 fffffa80`0547e060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`064aed00 fffff800`02abf906 : fffff800`02c49e80 fffffa80`0547e060 fffff800`02c57cc0 00000000`00000021 : nt!PspSystemThreadStartup+0x5a
fffff880`064aed40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+8ed700
fffff880`051a2700 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+8ed700

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51c41788

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

1: kd> lmvm nvlddmkm
start             end                 module name
fffff880`048b5000 fffff880`0539a000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Jun 21 14:36:16 2013 (51C41788)
    CheckSum:         00AB87FF
    ImageSize:        00AE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Pullrod · 23 Jul 2013

Hey,

I uploaded three screenshots. Two were taken after 1 and 2 hours, whereas the third one one was taken immediately after comuter rebooted after blue screen. I checked the PSU case but havent found any numbers on it. What is strange is that yesterday I played the game for 2 hours without any problems. Video card temperature seems to be the same. I was experiencing blue screen with one game before (last year), but it always seemed to appear after FPS have dropped significantly and video card reached really high temperature (around 70-80°C). Is there any connection between blue screen, FPS and video card temperature? Thanks for help!

Arc · 23 Jul 2013

Yes, there is a connection. It happens to a GPU that is starting to fail to take load. It needs to work extra for the FPS, and so it becomes hot. As it goes hot, it crashes to BSOD.

I would to suggest you to change the GPU.

Pullrod · 24 Jul 2013

The reason I am asking you is that in this particular game, blue screen appears when GPU temperature is not really hot (around 65°C or even lower). I used to play games with the same computer and temperatures often reached 70°C and beyond without crashing. It usually crashed when it reached 80°C. I think thats weird. Is it possible that some software updates are causing this problems?

Arc · 24 Jul 2013

In that case, the problem is with the game.
Ask th game developer ... there may be patches or suggested settings etc.