BSOD - Nvlddmkm.sys Windows 7 32-Bit


  1. Posts : 3
    Windows 7 32-bit
       #1

    BSOD - Nvlddmkm.sys Windows 7 32-Bit


    Computer on for a while it blue screens saying Nvlddmkm.sys caused the problem... Someone please help, attached is the Minidump.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    Farese2 said:
    Computer on for a while it blue screens saying Nvlddmkm.sys caused the problem... Someone please help, attached is the Minidump.
    Blue screen view is sort of correct. this one is caused by your video driver. You need tao use their un-install tool to remove all traces of the current driver and then install a fresh copy.

    Let us know if you need help with theis

    Ken

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\050410-22947-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;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0x82c19000 PsLoadedModuleList = 0x82d61810
    Debug session time: Tue May  4 22:12:34.561 2010 (GMT-4)
    System Uptime: 0 days 5:34:41.794
    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
    Loading unloaded module list
    ..............
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: 87485008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: 9110ea50, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 00000002, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    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
    
    FAULTING_IP: 
    nvlddmkm+eaa50
    9110ea50 55              push    ebp
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    8f635b74 91bbaadb 00000116 87485008 9110ea50 nt!KeBugCheckEx+0x1e
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8f635b98 91bbb8fa 9110ea50 00000000 00000002 dxgkrnl+0x8cadb
    8f635bbc 9060692c 00000000 00000102 874fe788 dxgkrnl+0x8d8fa
    8f635c34 90630a32 fffffcfb 0013a387 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
    8f635c5c 90631153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
    8f635c98 9060d8f0 8f635c90 86226388 85c45dd0 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
    8f635d28 906324b7 874fe788 82c553f1 874fe788 dxgmms1!VidSchiScheduleCommandToRun+0xaa
    8f635d3c 90632573 874fe788 00000000 87508b48 dxgmms1!VidSchiRun_PriorityTable+0xf
    8f635d50 82e276bb 874fe788 bb8ce7da 00000000 dxgmms1!VidSchiWorkerThread+0x7f
    8f635d90 82cd90f9 906324f4 874fe788 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+eaa50
    9110ea50 55              push    ebp
    
    SYMBOL_NAME:  nvlddmkm+eaa50
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bb7df30
    
    FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 3
    Windows 7 32-bit
    Thread Starter
       #3

    Which software do u prefer to remove all traces of the driver, ive used driver cleaner pro, but i dont feel it gets it all, do i have to go in safe mode?
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    Farese2 said:
    Which software do u prefer to remove all traces of the driver, ive used driver cleaner pro, but i dont feel it gets it all, do i have to go in safe mode?

    If I am not mistaken, nvidia makes an uninstall tool. use it to remove all the current driver, control panel, etc. then install just the driver.


    Good luck

    Ken
      My Computer


  5. Posts : 3
    Windows 7 32-bit
    Thread Starter
       #5

    Thanks, one last thing, The drivers i had installed were the newest ones... should i try a new beta driver? or what? or should i roll back to the previous one?
      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 03:16.
Find Us