Windows crashing while playing Wolfenstein Enemy Territory

gazz · 23 Jan 2015

Hi... Can some one tell me what to do to repair the following errrors . It only happens when pb is enabled...on Enemy territory...it's crashing Windows, When the crash occurs the screen freezes and nothing works no Task manager no nothing, Have to hard reboot to get PC going again...

I can play Counterstrike global offence without any problems, while Enemy Territory is a way older game

Arc · 23 Jan 2015

Stop 0x116 is a display/graphics failure.

Update the display driver to the latest. Drivers - Download NVIDIA Drivers

When done, stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Let us know the results.
___________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8007ce84e0, fffff8800f1dc93c, 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+15393c )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8007ce84e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f1dc93c, 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+15393c
fffff880`0f1dc93c 48ff256d6d7200  jmp     qword ptr [nvlddmkm+0x87a6b0 (fffff880`0f9036b0)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`03508988 fffff880`03f59134 : 00000000`00000116 fffffa80`07ce84e0 fffff880`0f1dc93c 00000000`00000000 : nt!KeBugCheckEx
fffff880`03508990 fffff880`03f58e3e : fffff880`0f1dc93c fffffa80`07ce84e0 fffffa80`05826b20 fffffa80`04cd1010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`035089d0 fffff880`03e0ff13 : fffffa80`07ce84e0 00000000`00000000 fffffa80`05826b20 fffffa80`04cd1010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03508a00 fffff880`03e39cf1 : 00000000`ffffffff 00000000`0004287e 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03508ae0 fffff880`03e38437 : 00000000`00000102 00000000`00000000 00000000`0004287e 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`03508b10 fffff880`03e0b2d2 : ffffffff`ff676980 fffffa80`04cd1010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03508bb0 fffff880`03e37ff6 : 00000000`00000000 fffffa80`05cf6010 00000000`00000080 fffffa80`04cd1010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03508cc0 fffff800`02d1a14a : 00000000`fffffc32 fffffa80`0582eb50 fffffa80`0396d740 fffffa80`0582eb50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03508d00 fffff800`02a6dbc6 : fffff800`02bf9e80 fffffa80`0582eb50 fffff800`02c07cc0 fffff880`012e8af5 : nt!PspSystemThreadStartup+0x5a
fffff880`03508d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+15393c
fffff880`0f1dc93c 48ff256d6d7200  jmp     qword ptr [nvlddmkm+0x87a6b0 (fffff880`0f9036b0)]

SYMBOL_NAME:  nvlddmkm+15393c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53b4446a

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f089000 fffff880`0fd17000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 23:12:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

gazz · 24 Jan 2015

Arc said:

Stop 0x116 is a display/graphics failure.

Update the display driver to the latest. Drivers - Download NVIDIA Drivers

When done, stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Let us know the results.
___________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8007ce84e0, fffff8800f1dc93c, 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+15393c )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8007ce84e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f1dc93c, 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+15393c
fffff880`0f1dc93c 48ff256d6d7200  jmp     qword ptr [nvlddmkm+0x87a6b0 (fffff880`0f9036b0)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`03508988 fffff880`03f59134 : 00000000`00000116 fffffa80`07ce84e0 fffff880`0f1dc93c 00000000`00000000 : nt!KeBugCheckEx
fffff880`03508990 fffff880`03f58e3e : fffff880`0f1dc93c fffffa80`07ce84e0 fffffa80`05826b20 fffffa80`04cd1010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`035089d0 fffff880`03e0ff13 : fffffa80`07ce84e0 00000000`00000000 fffffa80`05826b20 fffffa80`04cd1010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03508a00 fffff880`03e39cf1 : 00000000`ffffffff 00000000`0004287e 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03508ae0 fffff880`03e38437 : 00000000`00000102 00000000`00000000 00000000`0004287e 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`03508b10 fffff880`03e0b2d2 : ffffffff`ff676980 fffffa80`04cd1010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03508bb0 fffff880`03e37ff6 : 00000000`00000000 fffffa80`05cf6010 00000000`00000080 fffffa80`04cd1010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03508cc0 fffff800`02d1a14a : 00000000`fffffc32 fffffa80`0582eb50 fffffa80`0396d740 fffffa80`0582eb50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03508d00 fffff800`02a6dbc6 : fffff800`02bf9e80 fffffa80`0582eb50 fffff800`02c07cc0 fffff880`012e8af5 : nt!PspSystemThreadStartup+0x5a
fffff880`03508d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+15393c
fffff880`0f1dc93c 48ff256d6d7200  jmp     qword ptr [nvlddmkm+0x87a6b0 (fffff880`0f9036b0)]

SYMBOL_NAME:  nvlddmkm+15393c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53b4446a

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f089000 fffff880`0fd17000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 23:12:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

What is stop 0x116 is a display/graphics failure? Do i have to delete something or what do you mean?

Update the display driver to the latest. Drivers - Download NVIDIA Drivers

I dont know what i should fill in at Product Series :s

I think i got GeForce GTS 250, so thats serie 200????

and then just download and install? or should i first delete or?

Edit: I just played with my sound disabled at Device manager.. I can play then normally but only without sounds.. Maybe any solutions about this?

Arc · 24 Jan 2015

Yes, Series 200.

No, delete not. Download the driver, double click on it to install it. There is no delete.

And what do me mean? Have I said anything about deleting anything till now?

rvcjew · 24 Jan 2015

You might want to try installing the latest punkbuster client PunkBuster Online Countermeasures , also enemy territory is very old i'm not sure pb even supports it anymore are you seeing servers refusing you access because you don't have it enabled, perhaps your version is too new compared to the server your trying to get on.

Also as arc suggested just download and run this as well it's the latest at the moment. Drivers | GeForce

ICIT2LOL · 25 Jan 2015

Some system specs would e good to save me from trawling back through System Info - See Your System Specs

The card series seems to be quite old so I am wondering if the problem might lie elsewhere

Anak · 26 Jan 2015

STOP 0x00000116: VIDEO_TDR_ERROR (go to top of page)

Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card (see Significant Posts section below)

Source: STOP 0x00000116: VIDEO_TDR_ERROR | BSOD Index

Notice the second cause, overheating.

When was, the last time you cleaned out the case?

To wit:

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.

Source, and also located at the corrona link in the first quote: BSOD

The overheating and checking the power supply unit as ICIT2LOL has suggested "I am wondering if the problem might lie elsewhere" are the two easiest areas to check before checking the Video driver, bad video card, or BIOS.

gazz · 27 Jan 2015

Arc said:

Stop 0x116 is a display/graphics failure.

Update the display driver to the latest. Drivers - Download NVIDIA Drivers

When done, stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Let us know the results.
___________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8007ce84e0, fffff8800f1dc93c, 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+15393c )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8007ce84e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f1dc93c, 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+15393c
fffff880`0f1dc93c 48ff256d6d7200  jmp     qword ptr [nvlddmkm+0x87a6b0 (fffff880`0f9036b0)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`03508988 fffff880`03f59134 : 00000000`00000116 fffffa80`07ce84e0 fffff880`0f1dc93c 00000000`00000000 : nt!KeBugCheckEx
fffff880`03508990 fffff880`03f58e3e : fffff880`0f1dc93c fffffa80`07ce84e0 fffffa80`05826b20 fffffa80`04cd1010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`035089d0 fffff880`03e0ff13 : fffffa80`07ce84e0 00000000`00000000 fffffa80`05826b20 fffffa80`04cd1010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03508a00 fffff880`03e39cf1 : 00000000`ffffffff 00000000`0004287e 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03508ae0 fffff880`03e38437 : 00000000`00000102 00000000`00000000 00000000`0004287e 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`03508b10 fffff880`03e0b2d2 : ffffffff`ff676980 fffffa80`04cd1010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03508bb0 fffff880`03e37ff6 : 00000000`00000000 fffffa80`05cf6010 00000000`00000080 fffffa80`04cd1010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03508cc0 fffff800`02d1a14a : 00000000`fffffc32 fffffa80`0582eb50 fffffa80`0396d740 fffffa80`0582eb50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03508d00 fffff800`02a6dbc6 : fffff800`02bf9e80 fffffa80`0582eb50 fffff800`02c07cc0 fffff880`012e8af5 : nt!PspSystemThreadStartup+0x5a
fffff880`03508d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+15393c
fffff880`0f1dc93c 48ff256d6d7200  jmp     qword ptr [nvlddmkm+0x87a6b0 (fffff880`0f9036b0)]

SYMBOL_NAME:  nvlddmkm+15393c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53b4446a

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f089000 fffff880`0fd17000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 23:12:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

So i downloaded ur TweakBit Driver Updated..

I have to do some updates, but then i need to register and buy the full version.. Is there no other way to update?

I downloaded nvidia drivers at this website Drivers | GeForce
after that i updated it.. when i open NVIDIA GeForce Experience i get this view:

Anak · 27 Jan 2015

Sorry, I don't read Dutch, is it? or German.

Have you tried the suggestions here in post #5, by rvcjew?

You're going to have to forget about games and punkbuster (pb) for a while until you stabilize your system, add at least another 2GB of RAM, oh, and what type of antivirus/malware do you use?

Once your stable, then you can add those game managers and games back until you have problems. Then you know what's causing the problems and proceed with a fix to run them, we're only shooting in the dark until you do.

gazz · 27 Jan 2015

Anak said:

Sorry, I don't read Dutch, is it? or German.

Have you tried the suggestions here in post #5, by rvcjew?

You're going to have to forget about games and punkbuster (pb) for a while until you stabilize your system, add at least another 2GB of RAM, oh, and what type of antivirus/malware do you use?

Once your stable, then you can add those game managers and games back until you have problems. Then you know what's causing the problems and proceed with a fix to run them, we're only shooting in the dark until you do.

Yes its Dutch, it says :Sorry, GeForce can not optimize games on this computer.

Well the fact is that Punkbuster does not support Wolfenstein Enemy Territory anymore, so there are no uodates available.

How can i add 2GB RAM? Dont know anything about this :S

I think its wierd cause Counter Strike Global Offence is a newer game then W;ET, and when I disable my soundcard i can play W:ET without any probs... So I think is something with the soundcard..