Solved BSOD while playing games, video_tdr_failure - nvlddmkm.sys

Ktors

New Member
Messages
6
Hi!

I'm having major issues with my GPU while playing games on my MSI GT60 0ND. I've tried several different drivers, from the one that came with the computer when I bought it, the one I could download from MSI's own webpage, to the newest from Nvidia. I was wondering whether you could see something in the dumpfiles that could indicate the source of the problem.

The problem started about a year after the buy (which coincidentally was when the warranty ran out). It started out with a few BSOD's from time to time, and has now progressed to the point where the computer will BSOD shortly after playing. The problem started after I upgraded to Windows 8.1, but still persists now that I've downgraded back to 8, although it seemed like the problem was gone for a few days. The last BSOD happened while playing Hearthstone, after about half an hour of playing (which is longer than it usually takes).

I've tried several tips from forums ranging from official Windows-forums, Nvidia-forums, MSI-forums, as well as some others whose names I can't recall, but to no avail.

Is this a software-related problem, or is the GPU simply shot?

Computer specs:
Computer: MSI GT60
CPU: Intel Core i7-3630QM
Graphics Card: Nvidia GeForce GTX 675M / 2GB GDDR5
Ram: DDRIII 12GB (4GB * 3)
HDD: 750GB 7200RPM

Thanks in advance for any help/assistance.
 

My Computer

System One

  • OS
    Windows 8
All your dumpfiles are related to your Nvdia videocard
Probably caused by : dxgkrnl.sys ( dxgkrnl! ?? ::NNGAKEGL::`string'+2eb2e )VIDEO_DXGKRNL_FATAL_ERROR (113)
Probably caused by : pci.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+8f0b2c )VIDEO_TDR_FAILURE (116)

For more info about this kind of problems see Video TDR Timeout - 0x116 + 0x117 - Sysnative Forums

But i also found this driver NTIO_lib64.sys driver, are you using/overclocking with MSI Afterburner.
MSI Afterburner (along with Riva Tunerand EVGA Precision) are known to cause BSOD's in some Windows systems (it'sdriver is usually RTCore64.sys or NTIOlib_64.sys). Please un-install it immediately!

Also found a older driver for PowerDVD, which version are you using. Check if it is compatible with windows 8/8.1. Upgrade?
 

My Computer

System One

  • OS
    windows 8.1
    Computer type
    PC/Desktop
    System Manufacturer/Model
    self build
    CPU
    Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
    Motherboard
    Asrock P55 Pro
    Memory
    DDR3 Team--Elite-1333 8 gb
    Graphics Card(s)
    Sapphire R9 280x
    Sound Card
    Realtek Alc 855
    Monitor(s) Displays
    Acer V233H
    Screen Resolution
    1920 x 1020
    Hard Drives
    Samsung evo 850 SSd
    Seagate ST 320 gb
    Samsung HD 750 gb
    Seagate ST 3000gb
    PSU
    OCZ Stealth 600 watt
    Case
    Antec 300
    Mouse
    Speedlink Ledos and Nexus
Thanks for the quick answer.

I don't have Afterburner, at least I can't seem to find it. I did find MSI's VGA overclocker, which is now uninstalled. I tried playing WOW, but got another BSOD after about 30 seconds. (Ktors1.zip).

Then I downloaded the latest driver for PowerDVD10, and decided to run a stress test of my system using AIDA64. The test showed that the cores of my CPU reached pretty high temperatures, before it started testing the GPU, which immediately caused a BSOD. (Ktors2.zip)

Then I did a SFC Scan in CMD, ran WOW again, which resulted in a BSOD again after about 30 seconds. This time, right before the BSOD I got the error message "Windows Nvidia Kernel Mode Driver Stopped Responding" (Ktors3.zip).

I checked the compatability of the apps I have with a Windows Upgrade-tool, which didn't seem to find anything out of the ordinary.

Could there be a link between the high temperatures in the CPU and the BSOD that I saw using AIDA?

I'm going to open up the laptop and see if there is dust-buildup that I might remove (the warranty is expired anyway, so not worried about that).

Please tell me if you can find anything new in the dump-files.
 

My Computer

System One

  • OS
    Windows 8
All your 3 new dumpfiles are again bugcheck 116
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa801f644010, fffff880060f0b2c, ffffffffc000009a, 4}
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+8f0b2c )
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: fffffa801f644010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880060f0b2c, 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:
------------------
[COLOR=#FF0000]
OVERLAPPED_MODULE: Address regions for 'rikvm_38F51D56' and 'rikvm_38F51D' overlap[/COLOR][COLOR=#000000][/COLOR]
FAULTING_IP: 
nvlddmkm+8f0b2c
fffff880`060f0b2c 803dd609f0ff00  cmp     byte ptr [nvlddmkm+0x7f1509 (fffff880`05ff1509)],0
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.16384 (debuggers(dbg).130821-1623) amd64fre
STACK_TEXT:  
fffff880`08f23a98 fffff880`04b81b7b : 00000000`00000116 fffffa80`1f644010 fffff880`060f0b2c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`08f23aa0 fffff880`04b716c1 : fffff880`060f0b2c fffffa80`0ef3b070 fffffa80`1f644010 00000000`00000001 : dxgkrnl!TdrBugcheckOnTimeout+0xef
fffff880`08f23ae0 fffff880`04b71a30 : fffffa80`0ef3b070 fffff880`08f23b60 fffffa80`1f644010 fffffa80`1f644010 : dxgkrnl!ADAPTER_RENDER::Reset+0x141
fffff880`08f23b30 fffff880`04b800c9 : 00000000`00000100 fffffa80`0eb2d758 00000000`00000000 fffff880`04c8057c : dxgkrnl!DXGADAPTER::Reset+0x260
fffff880`08f23ba0 fffff880`04c8069a : fffffa80`1cd97580 00000000`00000080 fffffa80`1e24ca20 fffffa80`0eb2d010 : dxgkrnl!TdrResetFromTimeout+0x15
fffff880`08f23bd0 fffff800`8c89d075 : fffffa80`0eb272c0 fffffa80`0eb2d010 fffff800`8cbc2880 00000000`0274098c : dxgmms1!VidSchiWorkerThread+0x11e
fffff880`08f23c10 fffff800`8c9513b6 : fffff800`8cb68180 fffffa80`0eb272c0 fffff800`8cbc2880 fffffa80`099de040 : nt!PspSystemThreadStartup+0x59
fffff880`08f23c60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
nvlddmkm+8f0b2c
fffff880`060f0b2c 803dd609f0ff00  cmp     byte ptr [nvlddmkm+0x7f1509 (fffff880`05ff1509)],0
SYMBOL_NAME:  nvlddmkm+8f0b2c
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME:  nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  521fbf80
FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys
BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:0x116_image_nvlddmkm.sys
FAILURE_ID_HASH:  {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Followup: MachineOwner
The dumpfile mentioned
OVERLAPPED_MODULE: Address regions for 'rikvm_38F51D56' and 'rikvm_38F51D' overlap
This again points to problems with PowerDVD
According to Cyberlink only PowerDVd12 and above is compatible see here Windows 8 Guarantee

Please uninstall PowerDVd10 and upgrade at least to PowerDVd12

Yes, overheating can cause BSOD.
Also check if your thermal pasta of your CPU is not dried out.

Run Prime95 to test your Graphiccard

Download and Tutorial Prime95
http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html
 

My Computer

System One

  • OS
    windows 8.1
    Computer type
    PC/Desktop
    System Manufacturer/Model
    self build
    CPU
    Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
    Motherboard
    Asrock P55 Pro
    Memory
    DDR3 Team--Elite-1333 8 gb
    Graphics Card(s)
    Sapphire R9 280x
    Sound Card
    Realtek Alc 855
    Monitor(s) Displays
    Acer V233H
    Screen Resolution
    1920 x 1020
    Hard Drives
    Samsung evo 850 SSd
    Seagate ST 320 gb
    Samsung HD 750 gb
    Seagate ST 3000gb
    PSU
    OCZ Stealth 600 watt
    Case
    Antec 300
    Mouse
    Speedlink Ledos and Nexus
So I uninstalled PowerDVD, cleaned a good bit of dust from my fan, but due to my lacking of thermal pasta, I coulnd't open up all the way to the CPU and chipset.

The computer does run smoother and cooler, but when I played WOW today, the Windows Nvidia Kernel-crash happened again, this time, however, without the BSOD. I monitored the temperatures of the CPU and GPU while playing, and they didn't get all that much hotter while I was playing, keeping steady at 55-ish, with spikes into the 60's.

Do I collect data on the 0x117 the same way I did with the 0x116?
 

My Computer

System One

  • OS
    Windows 8
In the latest dumpfie the NTIO_lib64.sys driver is still present.
This driver can also be a part of MSI Live update. Have you this app installed.

I suggest updating the Nvdiadriver again to the latest version now your system runs smoother.
 

My Computer

System One

  • OS
    windows 8.1
    Computer type
    PC/Desktop
    System Manufacturer/Model
    self build
    CPU
    Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
    Motherboard
    Asrock P55 Pro
    Memory
    DDR3 Team--Elite-1333 8 gb
    Graphics Card(s)
    Sapphire R9 280x
    Sound Card
    Realtek Alc 855
    Monitor(s) Displays
    Acer V233H
    Screen Resolution
    1920 x 1020
    Hard Drives
    Samsung evo 850 SSd
    Seagate ST 320 gb
    Samsung HD 750 gb
    Seagate ST 3000gb
    PSU
    OCZ Stealth 600 watt
    Case
    Antec 300
    Mouse
    Speedlink Ledos and Nexus
That is strange... I don't have either Afterburner nor MSI Live update. Do you know how I can find the file that uses that process?

I had another BSOD today, after playing Hearthstone for about an hour or so... temperatures were stable in the 60's, both the CPU and the GPU. I'll try doing a clean install of the newest Nvidia driver, and see if that resolve the problem.

It almost seem like the lower/higher the strain of the GPU, the longer/shorter time it takes for the GPU driver to crash.

I've read on forums that some people have suggested the Antivirus program as a possible source of problems; I personally use BitDefender, are there any known compatablility issues with this program?
 

My Computer

System One

  • OS
    Windows 8
I know about compatabilty problems with some Antivirus/internet security programs. (AVG, Avast, Norton) maybe also with Bitdefender. You could uninstall it as a test. While testing, use Windows Defender and the Windows Firewall to keep from being infected .

But searching on MSI GT60 and your NVIDIA GeForce GTX 675M i found that there are more people with this Video TDR problems.
https://forums.geforce.com/default/...failure-nvlddmkm-sys-quot-help-plz-/?offset=5
https://forums.geforce.com/default/topic/715526/help-video-tdr-failure-gtx-675m-msi-gt70/?offset=7

There seems to be no specific solution, but there are some tips and ideas from some people.

Concerning the NTIO_lib64.sys driver it is still present also in your new dumpfile(bugcheck 116 again.)
I suspect it is part of the MSI utilities which came with your system.
 

My Computer

System One

  • OS
    windows 8.1
    Computer type
    PC/Desktop
    System Manufacturer/Model
    self build
    CPU
    Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
    Motherboard
    Asrock P55 Pro
    Memory
    DDR3 Team--Elite-1333 8 gb
    Graphics Card(s)
    Sapphire R9 280x
    Sound Card
    Realtek Alc 855
    Monitor(s) Displays
    Acer V233H
    Screen Resolution
    1920 x 1020
    Hard Drives
    Samsung evo 850 SSd
    Seagate ST 320 gb
    Samsung HD 750 gb
    Seagate ST 3000gb
    PSU
    OCZ Stealth 600 watt
    Case
    Antec 300
    Mouse
    Speedlink Ledos and Nexus
Thanks for the tip! I have, however, gone through those forums myself. Extensively. I did a clean install of the newest Nvidia driver, and managed to play WoW on High setting for quite a while! The GPU Diode and VRM1, but not the VRM2, reached very high temperatures (between 90 and 100 C), but it didn't crash. That is, until I decided to try and put the graphics on Ultra High, which subsequently froze the game after 5 seconds. After I terminated the wow process in the task manager, the following error message popped up; "Application WoW.exe has been blocked from accessing graphics hardware". The temperatures of the system were all pretty decent at the time when this happened (70-ish). After about 10 seconds I got the nvlddmkm BSOD.

What do you make of this? The GTX 675M should run a game like that without a problem on the highest setting, I've even played Skyrim on the highest setting on this computer before the problems rose.
 

My Computer

System One

  • OS
    Windows 8
Turns out the GPU itself was the problem; sent the laptop in for repair, MSI switched out the card with an upgrade for free, now everything is working fine.
 

My Computer

System One

  • OS
    Windows 8
Back
Top