BSOD playing any games, ERROR nvlddmkm.sys


  1. Posts : 2
    windows 7 ultimate x64
       #1

    BSOD playing any games, ERROR nvlddmkm.sys


    Hi all,

    im using MSI GT60 laptop

    i7-3610QM
    GTX 675M

    i got this error ever since i updated my driver to 337.88 which is the latest driver.

    the BSOD is very random at times. some time instantly when i start my game sometime it could last 1-2 hours.

    games i am playing
    dragon nest
    dota 2

    what i have tried:
    i tried running a furmark test - no error
    i tired OCCT test - no error
    i tried memory test - no error
    i tried to reinstall windows - no help
    i tried to install older version (332.21) - no help
    i tried to clean my fan - no help
    i tried to set TdrDdiDelay - no help

    what else can i try? or is that a hardware failure?
    getting very annoyed by this error, please help! thanks!
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi gongwan.

    Are you overclocking?
    As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

    When you Tested with Furmark or OCCT, what GPU did the programs test? The primary GPU Intel HD 4000 or the Optimus controlled GPU GTX 675M?
    As per the settings, those stressing programs will run on the primary one, not on the nvidia GPU. Set the nvidia GPU as primary and run the tests again?

    Older version is a nice idea, but 332.21 is not the right choice. Install the NVIDIA DRIVERS 314.22WHQL only.

    • Uninstall All nvidia items in Control Panel > Programs and features
      • 3D Vision Control Driver
      • 3D Vision Driver
      • Graphics Driver
      • HD Audio Driver
      • PhysX
      • nvidia Update

      (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:


    Let us know the results.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800d9824e0, fffff8800fe5d0dc, ffffffffc000009a, 4}
    
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+9a30dc )
    
    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: fffffa800d9824e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800fe5d0dc, 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:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+9a30dc
    fffff880`0fe5d0dc 803d66e9eeff00  cmp     byte ptr [nvlddmkm+0x891a49 (fffff880`0fd4ba49)],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`058f2a48 fffff880`10160000 : 00000000`00000116 fffffa80`0d9824e0 fffff880`0fe5d0dc ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`058f2a50 fffff880`10133867 : fffff880`0fe5d0dc fffffa80`0bb31000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`058f2a90 fffff880`1015fe0f : fffffa80`ffffd84d 00000000`00000000 fffffa80`0d9824e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`058f2b40 fffff880`0f437ec1 : fffffa80`0d30a010 00000000`00000080 00000000`00000000 fffffa80`0bb2a010 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`058f2bc0 fffff800`03118e6a : 00000000`01268824 fffffa80`0bb4bb50 fffffa80`06989b30 fffffa80`0bb4bb50 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`058f2c00 fffff800`02e72f06 : fffff880`034a5180 fffffa80`0bb4bb50 fffff880`034b00c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`058f2c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+9a30dc
    fffff880`0fe5d0dc 803d66e9eeff00  cmp     byte ptr [nvlddmkm+0x891a49 (fffff880`0fd4ba49)],0
    
    SYMBOL_NAME:  nvlddmkm+9a30dc
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  52b326bc
    
    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
    ---------
    
    7: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f4ba000 fffff880`10103000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Thu Dec 19 22:32:52 2013 (52B326BC)
        CheckSum:         00C19112
        ImageSize:        00C49000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 2
    windows 7 ultimate x64
    Thread Starter
       #3

    hi arc,

    i am sure i did not overclock any hardwares.

    the computer is not hot, even if is in gaming mode it is still cooling. the snapshot of speecy is attached.

    after installing the 314.22 from the link u have given me (i have used the display driver uninstaller to remove the previous version), i run the furmark test with the setting you have mention, then it failed the test but pass the occt memory test. the latest log files are attached as well.

    thank you for your help!! please guide me~

    on a side note, ytd i tried 327.23 driver apparently i run dota 2 for the whole night till afternoon it did not blue screen so it last about almost 7 hours before i start dragon nest and it blue screens again.
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    gongwan said:
    after installing the 314.22 from the link u have given me (i have used the display driver uninstaller to remove the previous version), i run the furmark test with the setting you have mention, then it failed the test but pass the occt memory test. the latest log files are attached as well.
    The data does not reflect any BSOD with 314.22 WHQL installed. But you said that you have done it, depending on this information.

    The most vital information here is that the furmark test failed. So the GPU may be addressed as a failing one. In this situation it will be the best for you to change the GPU.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:03.
Find Us