Game Crashing my Computer and Not Working

[Supertyrone]

PRO Username: SuperTyron

Have you looked at the FAQ to solve your issue?: Yes

On which server issue happened: RED

 

What have you done before the problem was there?

Not much, I only had to re-download PRO because of the update.

 

What have you already tried to solve the problem?

- Reinstalling and re-downloading PRO

- Tried the 32-Bit version of PRO (even though my computer is 64-Bit)

- Upgraded to Windows 10, and re-downloaded PRO, though I switched back to Windows 8 for other reasons.

- Tried compatibility mode to Windows 7

 

Description and Message

So I'm currently working with a Windows 8.1 laptop, and the game client crashes my computer. The client opens up and usually gets stuck on the loading screens after loading a few things. The program then stops responding and usually causes my computer to get the blue screen with "Video TDR Failure." Occasionally, I manage to get past the loading screens and get to log on, but the client and computer just crashes not much later. I believe that my drivers are up to date, at least my Intel integrated graphics and Nvidia graphics card, but if not up to date drivers is probably the problem, I will check again for the other drivers.

 

It would be much appreciated if I could get some help on this, thanks![/i]

[Marcylene]

156336 So I'm currently working with a Windows 8.1 laptop, and the game client crashes my computer. The client opens up and usually gets stuck on the loading screens after loading a few things. The program then stops responding and usually causes my computer to get the blue screen with "Video TDR Failure." Occasionally, I manage to get past the loading screens and get to log on, but the client and computer just crashes not much later. I believe that my drivers are up to date, at least my Intel integrated graphics and Nvidia graphics card, but if not up to date drivers is probably the problem, I will check again for the other drivers.

 

Let's try to solve the problem!

 

1. Can you play another games with your NVIDIA graphics card?

2. Have you updated your NVIDIA graphics properly?

 

Try with this! https://www.nvidia.es/Download/index.aspx

Hope it helps, after updating it all, reboot your system and try again with the 64bits version :Grin:

[Mercyknifed]

Did you make sure your all of your drivers are up to date?

 

Try using this to update them: https://tinyurl.com/gssqskj

[Supertyrone]

156336 So I'm currently working with a Windows 8.1 laptop, and the game client crashes my computer. The client opens up and usually gets stuck on the loading screens after loading a few things. The program then stops responding and usually causes my computer to get the blue screen with "Video TDR Failure." Occasionally, I manage to get past the loading screens and get to log on, but the client and computer just crashes not much later. I believe that my drivers are up to date, at least my Intel integrated graphics and Nvidia graphics card, but if not up to date drivers is probably the problem, I will check again for the other drivers.

 

Let's try to solve the problem!

 

1. Can you play another games with your NVIDIA graphics card?

2. Have you updated your NVIDIA graphics properly?

 

Try with this!

Hope it helps, after updating it all, reboot your system and try again with the 64bits version :Grin:

 

Sorry for the late update. So I tried this, my NVIDIA graphics card was indeed a little out of date so I updated it using GeForce experience, which says it's Version 365.10 I believe for my Nvidia GT 745M.

 

However, I'm still having the same issue with the game crashing along with my computer. I set the game to run on the Nvidia graphics card on the Nvidia control panel as well, hoping that may have been the issue. I also updated my Intel Integrated Graphics driver, but it was to no avail. I also tried using Driver Booster 3 and updated some other drivers as the other person suggested, but none of this seemed to fix the problem. If there's anything else I could try, please let me know.

 

Thanks.

[Jollyolly]

If you can find a way to upload your 'MEMORY' file located in C:/Windows, I'll be happy to debug it further. Otherwise there is so many reasons this could be happening, and without debugging, trial and error could take ages to figure out the underlying issue.

[Supertyrone]

Ignore this one mesage

[Supertyrone]

157699 If you can find a way to upload your 'MEMORY' file located in C:/Windows, I'll be happy to debug it further. Otherwise there is so many reasons this could be happening, and without debugging, trial and error could take ages to figure out the underlying issue.

 

I managed to open the file but couldn't find a way to upload it. Here's what it says from Windows debugger.

 

Microsoft ® Windows Debugger Version 10.0.10586.567 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

 

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 10586 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 10586.212.amd64fre.th2_release_sec.160328-1908

Machine Name:

Kernel base = 0xfffff802`c761b000 PsLoadedModuleList = 0xfffff802`c78f9cd0

Debug session time: Mon May 9 21:01:31.533 2016 (UTC - 4:00)

System Uptime: 0 days 0:23:03.329

Loading Kernel Symbols

...............................................................

................................................................

.....................................................

Loading User Symbols

 

Loading unloaded module list

.........

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 116, {ffffe000145034c0, fffff800370dfa10, ffffffffc000009a, 4}

 

Page 10e0d3 not present in the dump file. Type ".hh dbgerr004" for details

Page 10e0d3 not present in the dump file. Type ".hh dbgerr004" for details

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Page 1100 not present in the dump file. Type ".hh dbgerr004" for details

Page 1100 not present in the dump file. Type ".hh dbgerr004" for details

Page 1100 not present in the dump file. Type ".hh dbgerr004" for details

Probably caused by : nvlddmkm.sys ( nvlddmkm+b8fa10 )

 

Followup: MachineOwner

---------

[Jollyolly]

In the same program you just opened that in, use the !analyze -v command and re-paste it all in a spoiler. :)

[Supertyrone]

In the same program you just opened that in, use the !analyze -v command and re-paste it all in a spoiler. :)

 

Here it is!

 

Microsoft ® Windows Debugger Version 10.0.10586.567 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

 

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 10586 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 10586.212.amd64fre.th2_release_sec.160328-1908

Machine Name:

Kernel base = 0xfffff802`c761b000 PsLoadedModuleList = 0xfffff802`c78f9cd0

Debug session time: Mon May 9 21:01:31.533 2016 (UTC - 4:00)

System Uptime: 0 days 0:23:03.329

Loading Kernel Symbols

...............................................................

................................................................

.....................................................

Loading User Symbols

 

Loading unloaded module list

.........

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 116, {ffffe000145034c0, fffff800370dfa10, ffffffffc000009a, 4}

 

Page 10e0d3 not present in the dump file. Type ".hh dbgerr004" for details

Page 10e0d3 not present in the dump file. Type ".hh dbgerr004" for details

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Page 1100 not present in the dump file. Type ".hh dbgerr004" for details

Page 1100 not present in the dump file. Type ".hh dbgerr004" for details

Page 1100 not present in the dump file. Type ".hh dbgerr004" for details

Probably caused by : nvlddmkm.sys ( nvlddmkm+b8fa10 )

 

Followup: MachineOwner

---------

 

6: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

VIDEO_TDR_FAILURE (116)

Attempt to reset the display driver and recover from timeout failed.

Arguments:

Arg1: ffffe000145034c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff800370dfa10, 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:

------------------

 

Page 1100 not present in the dump file. Type ".hh dbgerr004" for details

Page 1100 not present in the dump file. Type ".hh dbgerr004" for details

Page 1100 not present in the dump file. Type ".hh dbgerr004" for details

 

DUMP_CLASS: 1

 

DUMP_QUALIFIER: 401

 

BUILD_VERSION_STRING: 10586.212.amd64fre.th2_release_sec.160328-1908

 

SYSTEM_MANUFACTURER: LENOVO

 

SYSTEM_PRODUCT_NAME: 20250

 

SYSTEM_SKU: LENOVO_MT_20250

 

SYSTEM_VERSION: Lenovo Z710

 

BIOS_VENDOR: LENOVO

 

BIOS_VERSION: 7FCN35WW

 

BIOS_DATE: 09/02/2013

 

BASEBOARD_MANUFACTURER: LENOVO

 

BASEBOARD_PRODUCT: Durian 7A1

 

BASEBOARD_VERSION: 31900003Std

 

DUMP_TYPE: 1

 

BUGCHECK_P1: ffffe000145034c0

 

BUGCHECK_P2: fffff800370dfa10

 

BUGCHECK_P3: ffffffffc000009a

 

BUGCHECK_P4: 4

 

FAULTING_IP:

nvlddmkm+b8fa10

fffff800`370dfa10 48ff2541faeaff jmp qword ptr [nvlddmkm+0xa3f458 (fffff800`36f8f458)]

 

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

 

CPU_COUNT: 8

 

CPU_MHZ: 95a

 

CPU_VENDOR: GenuineIntel

 

CPU_FAMILY: 6

 

CPU_MODEL: 3c

 

CPU_STEPPING: 3

 

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

 

BUGCHECK_STR: 0x116

 

PROCESS_NAME: System

 

CURRENT_IRQL: 0

 

ANALYSIS_SESSION_HOST: ANDREW-LAPTOP

 

ANALYSIS_SESSION_TIME: 05-09-2016 23:26:13.0554

 

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

 

STACK_TEXT:

ffffd000`204e6a58 fffff800`35536f4c : 00000000`00000116 ffffe000`145034c0 fffff800`370dfa10 ffffffff`c000009a : nt!KeBugCheckEx

ffffd000`204e6a60 fffff800`35522767 : fffff800`370dfa10 ffffe000`10dca200 ffffe000`10dc4260 ffffe000`10dca288 : dxgkrnl!TdrBugcheckOnTimeout+0xec

ffffd000`204e6aa0 fffff800`35522b8b : ffffe000`10dc4260 ffffe000`145034c0 ffffe000`10dc42c8 ffffe000`10dc42c8 : dxgkrnl!ADAPTER_RENDER::Reset+0x153

ffffd000`204e6ad0 fffff800`35536785 : ffffe000`0cde0150 00000000`00000000 ffffe000`00000000 ffffe000`12b72c80 : dxgkrnl!DXGADAPTER::Reset+0x233

ffffd000`204e6b20 fffff800`355368db : 00000000`00000200 fffff802`c79ae340 ffffe000`1bc6ef20 fffff802`c76a1a60 : dxgkrnl!TdrResetFromTimeout+0x15

ffffd000`204e6b50 fffff802`c766c6a9 : ffffe000`1258d800 fffff800`35536880 ffffe000`15b09b80 fffff802`000b8000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x5b

ffffd000`204e6b80 fffff802`c76fe895 : 00000000`00000000 00000000`00000080 ffffe000`072a3040 ffffe000`1258d800 : nt!ExpWorkerThread+0xe9

ffffd000`204e6c10 fffff802`c7762906 : fffff802`c7938180 ffffe000`1258d800 fffff802`c76fe854 00000000`00000246 : nt!PspSystemThreadStartup+0x41

ffffd000`204e6c60 00000000`00000000 : ffffd000`204e7000 ffffd000`204e1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

 

 

STACK_COMMAND: kb

 

THREAD_SHA1_HASH_MOD_FUNC: 56a150c818aff348d17e35fc9e822916b6c0190b

 

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: baa4671d20933e04df5fd6499e0a0821fa07570c

 

THREAD_SHA1_HASH_MOD: 3225689ea8bf23dca00cdfd517975e0703e07271

 

FOLLOWUP_IP:

nvlddmkm+b8fa10

fffff800`370dfa10 48ff2541faeaff jmp qword ptr [nvlddmkm+0xa3f458 (fffff800`36f8f458)]

 

FAULT_INSTR_CODE: 4125ff48

 

SYMBOL_NAME: nvlddmkm+b8fa10

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: nvlddmkm

 

IMAGE_NAME: nvlddmkm.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP: 57209fba

 

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

 

BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

 

PRIMARY_PROBLEM_CLASS: 0x116_IMAGE_nvlddmkm.sys

 

TARGET_TIME: 2016-05-10T01:01:31.000Z

 

OSBUILD: 10586

 

OSSERVICEPACK: 0

 

SERVICEPACK_NUMBER: 0

 

OS_REVISION: 0

 

SUITE_MASK: 784

 

PRODUCT_TYPE: 1

 

OSPLATFORM_TYPE: x64

 

OSNAME: Windows 10

 

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

 

OS_LOCALE:

 

USER_LCID: 0

 

OSBUILD_TIMESTAMP: 2016-03-29 02:19:02

 

BUILDDATESTAMP_STR: 160328-1908

 

BUILDLAB_STR: th2_release_sec

 

BUILDOSVER_STR: 10.0.10586.212.amd64fre.th2_release_sec.160328-1908

 

ANALYSIS_SESSION_ELAPSED_TIME: bdc

 

ANALYSIS_SOURCE: KM

 

FAILURE_ID_HASH_STRING: km:0x116_image_nvlddmkm.sys

 

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

 

Followup: MachineOwner

---------

 

[Jollyolly]

Judging by that it is most definitely your Nvidia drivers. I recommend completely removing all Nvidia software from your laptop and reinstall them. You can do this in Safe Mode or without Safe Mode, up to you. Uninstall anything Nvidia related in your Add/Remove programs, then delete C:/NVIDIA if it still exists.

 

Then go ahead and run the dependencies checker since you're running 8.1 by going here:

https://support.microsoft.com/en-us/mats/program_install_and_uninstall

 

After that is done, restart your computer and reinstall your Nvidia drivers, but I highly recommend to /not/ use GeForce Experience as it's known to cause problems like this, and has actually caused me to have the same problem a few months ago.

 

Report back once you've finished these steps, and let me know how things run.