Win 7 64-bit BSoD nvlddmkm.sys error


  1. Posts : 1
    windows 7 x64
       #1

    Win 7 64-bit BSoD nvlddmkm.sys error


    I have a Leadtek 9800gx2 on win 7x64 and when i'm playing 3D aplications such as games the bsod appears and I got the latest drivers installed. When I finish installing a video driver, the computer doesn't ask for a reboot. It just says installation finished.

    10x

    i've attached the dump file
      My Computer


  2. Posts : 11,840
    64-bit Windows 8.1 Pro
       #2

    Your .dmp blames nvkddkm.sys with a 0x116: VIDEO_TDR_ERROR .... Make sure that you completly remove all traces of your video cards driver, then reinstall... Read this thread for more information about your error... [2-Int] STOP 0x116: VIDEO_TDR_ERROR troubleshooting

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\060710-28938-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02a17000 PsLoadedModuleList = 0xfffff800`02c54e50
    Debug session time: Mon Jun  7 10:53:28.050 2010 (UTC - 4:00)
    System Uptime: 0 days 0:12:17.595
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa80053484e0, fffff880107e9d30, 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+76ad30 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa80053484e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff880107e9d30, 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+76ad30
    fffff880`107e9d30 803d81d5530000  cmp     byte ptr [nvlddmkm+0xca82b8 (fffff880`10d272b8)],0
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`05999b88 fffff880`04d13ef8 : 00000000`00000116 fffffa80`053484e0 fffff880`107e9d30 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`05999b90 fffff880`04ce7867 : fffff880`107e9d30 fffffa80`06a86000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`05999bd0 fffff880`04d13d07 : fffffa80`ffffd87b 00000000`00000000 fffffa80`053484e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`05999c80 fffff880`04de2ec1 : fffffa80`04bf0170 00000000`00000080 00000000`00000000 fffffa80`06a84010 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`05999d00 fffff800`02d2ca86 : 00000000`043b2d2e fffffa80`069e8060 fffffa80`03fed890 fffffa80`069e8060 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`05999d40 fffff800`02a65b06 : fffff800`02c01e80 fffffa80`069e8060 fffff800`02c0fc40 fffff880`01456534 : nt!PspSystemThreadStartup+0x5a
    fffff880`05999d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+76ad30
    fffff880`107e9d30 803d81d5530000  cmp     byte ptr [nvlddmkm+0xca82b8 (fffff880`10d272b8)],0
    
    SYMBOL_NAME:  nvlddmkm+76ad30
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bdbcc20
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
      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 06:14.
Find Us