none
NVIDIA Windows Kernel Mode Driver Crash (Game-specific)

    Question

  • GTX 770 OC

    Corsair RM 650

    i5-4670K CPU @ 3.40GHz
    16GB 2400MHz RAM
    2 TB Hybrid Drive by Seagate
    Audigy 5/RX Sound Card
    Windows 10 x64

    I pre-ordered Fallout 4, probably my most anticipated release yet, and I was devastated when this crash started happening. Just like my problem in Mortal Kombat X the game is utterly unplayable. This is one of the most frustrating things I have ever encountered with a computer. Both of these releases I have specifically purchased because they are among my favorite game series and I can't play them at all.

    I have a .dmp file, a dxdiag, an msinfo32 and a GPU-Z log. I can tell you right now that this is not a problem with drivers, BIOS updates, GPU temps or power consumption (at least from what MSI Afterburner graphs say) or the in-game graphics being to high. I've done just about everything that is within my knowledge and competency. I'll take as many ideas as I can.


    I did upgrade to Windows 10 during the time when Mortal Kombat X was experiencing this crash. I thought it would fix it but the problem remained despite the complete reformatting of my hard drive. 
    • Edited by Sitchruss Wednesday, November 11, 2015 10:53 PM
    Tuesday, July 28, 2015 9:07 AM

All replies

  •  
    We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  


    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask


    Wanikiya and Dyami--Team Zigzag

    Tuesday, July 28, 2015 10:19 AM
    Moderator
  • Hi,

    Please zip and upload the log files to your OneDrive and post the download here.

    Attached files:
    C:\Windows\LiveKernelReports\WATCHDOG\WD-20150725-0143.dmp
    C:\Windows\Temp\WER-3080021-0.sysdata.xml
    C:\Windows\Temp\WERFFC2.tmp.WERInternalMetadata.xml

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0bc2ffc2


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Proposed as answer by Roger LuModerator Monday, August 10, 2015 3:02 AM
    • Unproposed as answer by Sitchruss Wednesday, November 11, 2015 11:00 PM
    Wednesday, July 29, 2015 9:03 AM
    Moderator
  • Thanks Zig Zag and Roger Lu for trying to help, I eventually quit after a month of constant troubleshooting. However, this problem (or one very similar) has come up again in Fallout 4. The game is not playable once again, and again I am at a loss for what causes it. These are the only two games that this happens in which is the weirdest part. I've played a dozen other games during this time but all run perfectly. Its just these two. I read this article:

    https://forums.geforce.com/default/topic/389688/geforce-drivers/nvidia-statement-on-tdr-errors-display-driver-nvlddmkm-stopped-/

    The article seems like it has a lot of things that cause it but it still doesn't make sense why it only happens in these two games. I'm going to change up the post a bit and start asking for help again. I'll be posting the most recent dump file and whatever else we need.

    Wednesday, November 11, 2015 10:30 PM
  • https://onedrive.live.com/redir?resid=3AE3633B21D2BAE4!1279&authkey=!AGyj4sHPi2TMIRI&ithint=file%2cdmp
    Wednesday, November 11, 2015 10:55 PM
  • This crash was related to your nVidia video driver

    Completely remove the current driver and install the newest driver available.  For instructions on how to do that Read all about updating drivers by my partner JMH3143 here http://answers.microsoft.com/en-us/windows/wiki/windows_other-hardware/updating-a-driver/a5e6345e-af9b-4099-bef0-8d22254aa1c1?tm=1436753520149

    Microsoft (R) Windows Debugger Version 10.0.10563.566 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\WD-20151110-2258.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*E:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*E:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 10 Kernel Version 10240 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 10240.16545.amd64fre.th1.150930-1750
    Machine Name:
    Kernel base = 0xfffff801`2081b000 PsLoadedModuleList = 0xfffff801`20b40070
    Debug session time: Wed Nov 11 00:58:43.757 2015 (UTC - 5:00)
    System Uptime: 0 days 4:16:39.421
    Loading Kernel Symbols
    ..
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    .............................................................
    ................................................................
    ................................................................
    
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 141, {ffffe001e3a1e4c0, fffff800061c5d4c, 0, 1480}
    
    Unable to load image 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+165d4c )
    
    Followup:     MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_ENGINE_TIMEOUT_DETECTED (141)
    One of the the display engines failed to respond in timely fashion.
    (This code can never be used for a real bugcheck.)
    Arguments:
    Arg1: ffffe001e3a1e4c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff800061c5d4c, The pointer into responsible device driver module (e.g owner tag).
    Arg3: 0000000000000000, The secondary driver specific bucketing key.
    Arg4: 0000000000001480, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_P1: ffffe001e3a1e4c0
    
    BUGCHECK_P2: fffff800061c5d4c
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: 1480
    
    FAULTING_IP: 
    nvlddmkm+165d4c
    fffff800`061c5d4c ??              ???
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_ENGINE_TIMEOUT
    
    TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
    
    
    CPU_COUNT: 4
    
    CPU_MHZ: d48
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 3c
    
    CPU_STEPPING: 3
    
    BUGCHECK_STR:  0x141
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 10.0.10563.566 amd64fre
    
    STACK_TEXT:  
    ffffd000`224ec600 fffff800`050311d1 : ffffe001`e3a1e4c0 ffffd000`224ec7a0 ffffe001`e0f22000 ffffe001`e28fd830 : watchdog!WdDbgReportRecreate+0x104
    ffffd000`224ec650 fffff800`07609e7c : 00000000`00000000 00000000`00000000 ffffe001`e0f1f000 ffffe001`e0f1f000 : dxgkrnl!TdrUpdateDbgReport+0xe1
    ffffd000`224ec6a0 fffff800`07666eac : ffffe001`e0f1f000 00000000`00000000 00000000`00000001 ffffe001`e0f22001 : dxgmms2!VidSchiResetEngine+0x63c
    ffffd000`224ec980 fffff800`0763b0fc : ffffe001`e0f1f000 ffffd000`224ecb00 00000000`00000000 ffffe001`e0f22000 : dxgmms2!VidSchiResetEngines+0x84
    ffffd000`224ec9c0 fffff800`075f5cac : ffffe001`e0f22000 00000000`000f09cc 00000000`00000001 00000000`00000002 : dxgmms2!VidSchiCheckHwProgress+0x1378c
    ffffd000`224eca00 fffff800`07633463 : ffffe001`e0f22000 ffffd000`224ecbc8 ffffe001`de076780 ffffe001`00000000 : dxgmms2!VidSchiScheduleCommandToRun+0x33c
    ffffd000`224ecb90 fffff800`07633440 : ffffe001`e0f22000 00000000`00000000 ffffe001`dc690840 ffffe001`dc690800 : dxgmms2!VidSchiRun_PriorityTable+0x1f
    ffffd000`224ecbc0 fffff801`20901558 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiWorkerThread+0x80
    ffffd000`224ecc00 fffff801`2096e3c6 : fffff801`20b7e180 ffffe001`dd7c6840 fffff801`20bf4740 00000000`00000246 : nt!PspSystemThreadStartup+0x58
    ffffd000`224ecc60 00000000`00000000 : ffffd000`224ed000 ffffd000`224e7000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+165d4c
    fffff800`061c5d4c ??              ???
    
    SYMBOL_NAME:  nvlddmkm+165d4c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  563b692b
    
    FAILURE_BUCKET_ID:  LKD_0x141_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  LKD_0x141_IMAGE_nvlddmkm.sys
    
    PRIMARY_PROBLEM_CLASS:  LKD_0x141_IMAGE_nvlddmkm.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:lkd_0x141_image_nvlddmkm.sys
    
    FAILURE_ID_HASH:  {341dd0b3-9ebd-47a8-9de8-23f4b00fabbc}
    
    Followup:     MachineOwner
    ---------
    
    3: kd> lmvm nvlddmkm
    Browse full module list
    start             end                 module name
    fffff800`06060000 fffff800`06b57000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Browse all global symbols  functions  data
        Timestamp:        Thu Nov 05 09:35:23 2015 (563B692B)
        CheckSum:         00AC334E
        ImageSize:        00AF7000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Mini Kernel Dump does not contain unloaded driver list
    


    Wanikiya and Dyami--Team Zigzag Windows IT-PRO (MS-MVP)

    Thursday, November 12, 2015 12:14 AM
    Moderator
  • Hi, I forgot to mention that in the past for Mortal Kombat X I had used Display Driver Uninstaller to no avail. Nonetheless I followed your link and did the steps. Fallout 4 was running fine but as soon as it got to a loading screen it crashed after 30 seconds. Earlier when I was troubleshooting myself it crashed almost every time here. Only a couple times have I gotten past that loading screen and if it did it would crash shortly after. Here is another .dmp file:

    https://onedrive.live.com/redir?resid=3AE3633B21D2BAE4!1281&authkey=!AGcCYSVINBOdLug&ithint=file%2cdmp


    • Edited by Sitchruss Thursday, November 12, 2015 2:04 AM
    Thursday, November 12, 2015 1:59 AM
  • I found the problem!

    I need to get a new power supply. Thanks for the help everyone!

    Saturday, November 14, 2015 1:53 AM