Windows 8 and 8.1 Forums


BSOD- TDR_Video_failure and MSI GT70

  1. #1


    Posts : 1
    Windows 8

    BSOD- TDR_Video_failure and MSI GT70


    Hello! I've seen others post about the same issue so it looks like I'm not alone. I've got an almost 1 year old MSI GT70 and have never had a problem until about 3 weeks ago. I had noticed some games weren't playing as well as they had been and my FPS wasn't quite up to par but then, while playing a beta for a new game (Everquest Landmark), I got my first BSOD error stating a "TDR_Video_Failure". I reinstalled drivers and went back to the original driver that came with the system and then when it still occurred I even restored the pc to "out of box" condition. I am still getting the error. The other symptoms I'm noticing are that my "Turbo" quick button no longer works and occasionally my manual fan turns itself on right before a crash. I have gotten other errors as well during the BSOD crash including a "power_state_failure" and I believe one other. My system is still under warranty and I will RMA it and send it back for repair if you can't find the issue but I thought it was at least worth a try since it looks like so many are encountering the same issues. I'm hoping maybe it's software related and can save me ten days of waiting for them to fix this and sent it back. SF Diagnostic tool dump file is attached. Let me know if you need any more information! Thanks in advance for whatever miracles you work!!

      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    The Qualcomm Atheros Killer Service/KillerNetManager is known to cause BSOD's. Please follow the workaround instructions here:
    First, open the Run dialog (Win + R keys) and type in "services.msc" (without the quotes) and press Enter
    Scroll down and locate the "Qualcomm Atheros Killer Service" and right click on it. Select "Stop"
    Right click on it again and this time select "Properties"
    In the dropdown box for "Startup type", select "Disabled", then click on the "OK" button at the bottom of the window

    Next, open Task Manager (right click on TaskBar and select "Task Manager")
    Click on the "More details" dropdown (if present)
    Click on the "Startup" tab
    Scroll down and locate the "KillerNetManager" entry, right click on it and select "Disable"
    There may also be an Install Shield (with the Killer gaming K next to it), if so Right click on it and select "Disable"
    Finally, restart the system in order for the changes to take affect.
    At times the Killer Network Manager will continue to load. If so, it's usually listed in the MSINFO32...Software Environment...Startup Programs section. If it is, please try this:
    It may be that the instructions aren't stopping everything.
    In some cases, there's a program running out of the Program Files/Program Files (x86) directory.
    "c:\program files\qualcomm atheros\killer network manager\killer~1.exe" (NOTE: killer~1.exe is most likely killernetmanager.exe)
    In other cases, there's a program running out of c:\windows\installer\{Long string of letters, numbers, and dashes}\networkmanager.exe_130c27d738f34c89bddf21bcfd74b56d.exe (the long string of letters and numbers may change)

    Here's some things to try
    1) Please see if there are any entries in the Startup tab of Task Manager that are related to Qualcomm/Atheros/Killer Network Manager (and NOT the card itself) and disable them (please let us know what you find) Be careful as the wrong selection can disable the network card.
    2) Check in "msconfig" for any entries that aren't in the Startup tab of Task Manager. Let us know if you find any Qualcomm/Atheros/Killer entries there (we'll disable them differently if they are there).
    3) Locate the "c:\program files\qualcomm atheros\killer network manager\killer~1.exe" and rename the .exe to .BAD (the killer~1 is actually a filename that starts with killer and ends with .exe) There will be an error in event viewer, but it'll stop the bugger from loading.
    4) Locate the "c:\windows\installer\{Long string of letters, numbers, and dashes}\networkmanager.exe_130c27d738f34c89bddf21bcfd74b56d.exe" entry and rename the .exe to .BAD (the long string of letters and numbers may change)

    Just FYI - here are the MSI workaround instructions: MSI USA
    There are a large number of Live Kernel Events in the WER section of MSINFO32,
    Please do the following:
    - open Event Viewer (run eventvwr.msc from the "Run" dialog))
    - expand the Custom Views category (left click on the > next to the words "Custom Views")
    - right click on Administrative Events
    - select "Save all Events in Custom View as..."
    - save the file as Admin.evtx
    - zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
    - upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

    While waiting for a reply, please monitor your temps with this free utility: HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
    P.S. - Live Kernel Events can also be caused by forcing a shutdown by holding the power switch down, so please avoid doing this (if possible). If not, then note how often that you do it.

    TDR errors are related to your video drivers. Please:
    - download a fresh copy of the latest, Win8 compatible video drivers for your system from the MSI Support website
    - uninstall the current video drivers from your system
    - install the freshly downloaded video drivers
    - monitor for further BSOD's

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

    MBfilt64.sys Thu Jul 30 23:40:32 2009 (4A7267B0)
    Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver) - Was found in the latest Win8 version available from Realtek on 07Sep2013
    http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys

    ctxusbm.sys Mon Sep 7 14:09:28 2009 (4AA54C58)
    Citrix ICA Client USB Monitor Driver
    http://www.carrona.org/drivers/driver.php?id=ctxusbm.sys

    NTIOLib_X64.sys Sun Jan 17 21:31:59 2010 (4B53C81F)
    MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5
    http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys

    e22w8x64.sys Tue Jul 10 12:29:50 2012 (4FFC587E)
    Killer Networks Ethernet Card. Driver dated Mon Dec 3 10:42:37 2012 (? and earlier) has Qualcomm Atheros Killer Service BSOD issue. Workaround here: MSI USA[br]
    http://www.carrona.org/drivers/driver.php?id=e22w8x64.sys

    If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions: Driver Verifier Settings



    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Fri Mar  7 17:55:44.480 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\030714-19406-01.dmp]
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
    System Uptime:0 days 0:13:39.243
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    *** 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 )
    BugCheck 116, {fffffa80128a8010, fffff88005d63b2c, ffffffffc000009a, 4}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: fffffa80128a8010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88005d63b2c, 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.
    BUGCHECK_STR:  0x116
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
    CPUID:        "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
    MaxSpeed:     2400
    CurrentSpeed: 2395
      BIOS Version                  E1762IMS.50T
      BIOS Release Date             11/08/2012
      Manufacturer                  Micro-Star International Co., Ltd.
      Product Name                  GT70
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Mar  7 17:41:33.359 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\030714-27250-01.dmp]
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
    System Uptime:0 days 0:10:49.123
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    *** 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 )
    BugCheck 116, {fffffa800b55a010, fffff880063ceb2c, ffffffffc000009a, 4}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: fffffa800b55a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff880063ceb2c, 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.
    BUGCHECK_STR:  0x116
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
    CPUID:        "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
    MaxSpeed:     2400
    CurrentSpeed: 2395
      BIOS Version                  E1762IMS.50T
      BIOS Release Date             11/08/2012
      Manufacturer                  Micro-Star International Co., Ltd.
      Product Name                  GT70
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Mar  7 00:43:40.108 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\030714-20109-01.dmp]
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:0 days 23:06:47.467
    *** 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+df9e3 )
    BugCheck 50, {fffff88800b7bff8, 1, fffff880062e29e3, 2}
    BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
    Arguments: 
    Arg1: fffff88800b7bff8, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff880062e29e3, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000002, (reserved)
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: AV_nvlddmkm+df9e3
    CPUID:        "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
    MaxSpeed:     2400
    CurrentSpeed: 2395
      BIOS Version                  E1762IMS.50T
      BIOS Release Date             11/08/2012
      Manufacturer                  Micro-Star International Co., Ltd.
      Product Name                  GT70
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Mar  6 01:35:59.582 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\030614-21484-01.dmp]
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    System Uptime:0 days 3:42:39.559
    Probably caused by :pci.sys
    BugCheck 9F, {3, fffffa800b980880, fffff800da01e7f0, fffffa800ac564f0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800b980880, Physical Device Object of the stack
    Arg3: fffff800da01e7f0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: fffffa800ac564f0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys
    CPUID:        "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
    MaxSpeed:     2400
    CurrentSpeed: 2395
      BIOS Version                  E1762IMS.50T
      BIOS Release Date             11/08/2012
      Manufacturer                  Micro-Star International Co., Ltd.
      Product Name                  GT70
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Fri Mar  7 17:55:44.480 2014 (UTC - 5:00)**************************
    MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
    ctxusbm.sys                 Mon Sep  7 14:09:28 2009 (4AA54C58)
    NTIOLib_X64.sys             Sun Jan 17 21:31:59 2010 (4B53C81F)
    rikvm_38F51D56.sys          Mon May 14 03:49:40 2012 (4FB0B914)
    IntcDAud.sys                Tue Jun 19 10:40:51 2012 (4FE08F73)
    HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
    RtsPStor.sys                Tue Jul  3 21:52:57 2012 (4FF3A1F9)
    e22w8x64.sys                Tue Jul 10 12:29:50 2012 (4FFC587E)
    RTKVHD64.sys                Tue Jul 24 05:42:48 2012 (500E6E18)
    iBtFltCoex.sys              Tue Jul 24 06:03:05 2012 (500E72D9)
    intelppm.sys                Wed Jul 25 22:26:48 2012 (5010AAE8)
    SynTP.sys                   Fri Aug 24 19:20:26 2012 (50380C3A)
    btmaux.sys                  Mon Aug 27 00:21:13 2012 (503AF5B9)
    btmhsf.sys                  Wed Aug 29 00:21:50 2012 (503D98DE)
    iaStorA.sys                 Sat Sep  1 21:01:24 2012 (5042AFE4)
    dump_iaStorA.sys            Sat Sep  1 21:01:24 2012 (5042AFE4)
    igdkmd64.sys                Sun Sep  2 23:33:39 2012 (50442513)
    bwcW8x64.sys                Mon Sep 24 16:37:14 2012 (5060C47A)
    nvlddmkm.sys                Thu Aug 29 17:39:12 2013 (521FBF80)
    nvpciflt.sys                Thu Aug 29 17:39:37 2013 (521FBF99)
    NETwew00.sys                Thu Oct 31 10:01:47 2013 (527262CB)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Mar  7 00:43:40.108 2014 (UTC - 5:00)**************************
    pcwiz_x64.sys               Sat Aug 11 03:48:20 2012 (50260E44)
    nvlddmkm.sys                Tue Aug 28 03:52:38 2012 (503C78C6)
    nvpciflt.sys                Tue Aug 28 03:53:07 2012 (503C78E3)
    
    http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
    http://www.carrona.org/drivers/driver.php?id=ctxusbm.sys
    http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
    http://www.carrona.org/drivers/driver.php?id=rikvm_38F51D56.sys
    http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=RtsPStor.sys
    http://www.carrona.org/drivers/driver.php?id=e22w8x64.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=iBtFltCoex.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=SynTP.sys
    http://www.carrona.org/drivers/driver.php?id=btmaux.sys
    http://www.carrona.org/drivers/driver.php?id=btmhsf.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=bwcW8x64.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=nvpciflt.sys
    http://www.carrona.org/drivers/driver.php?id=NETwew00.sys
    http://www.carrona.org/drivers/driver.php?id=pcwiz_x64.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=nvpciflt.sys
      My System SpecsSystem Spec

BSOD- TDR_Video_failure and MSI GT70
Related Threads
Hi There! Recently while booting my computer up from being off for quite a while, it noticed it hung at the windows 8 login screen. From there I tried to reboot, only for it it blue screen on the desktop. The blue screen error message was "tdr_video_failure". Just before it blue screened, I...
Msi gt70 onc - bsod in BSOD Crashes and Debugging
Hi, I have owned my MSI GT70 for about 1.5 years. About 1 month ago I have been getting BSOD whenever I play any games. I have updated all my graphic, network drivers etc... My knowledge on how to fix these sorts of issues if very limited therefore would greatly appreciate any help you are...
BSOD Code 116 On MSI GT70 on Windows 7 in BSOD Crashes and Debugging
Hi Guys of recently i have been experience Constant BSOD. I read on forums that it had to do with the Killer Network. I know Im a Windows 7 User and this is Windows 8. But i really need help , Im on the brick of Selling my Gaming laptop and purchasing a New laptop but i refuse to throw in the...
MSI GT70 often random BSOD's in BSOD Crashes and Debugging
Hi, I have a MSI GT70 20D-039US DRAGON EDITION 2 and get random crashs since the first day I have it. I upgraded my laptop to win8.1 after the first crash and it didn't work and then i have updated all my drivers to latest from MSI Global GT70 Dragon Edition 2 and also killer network...
My laptop is about 2 months old now and when ever I play games I usually get a BSOD crash within half to an hour every time. I personally have no clue how to fix these problems or read a dumb file correctly. I have added an attachment with my latest crash logs any help would be much appreciated....
New msi GT70 2OC random BSOD in BSOD Crashes and Debugging
I bought this PC on january, and since then I got random BSOD at various moments, I already tryed to restore the computer, I already did this https://www.eightforums.com/bsod-crashes-debugging/34791-new-msi-gt70-random-bsod-s.html and i still got a lot of BSOD, my drivers are updated.
Solved New MSI GT70 random BSOD's in BSOD Crashes and Debugging
Hi, I have a new GT70 2OD 058au (less than 2 weeks old). I ran updates the day I received the computer which included updating to Windows 8.1. I have been getting BSODs randomly most days since I got the computer, sometimes with different codes and while doing different tasks. I have...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook