display driver nvidia windows kernel .....  

Page 1 of 5 123 ... LastLast

  1. Posts : 15
    windows xp
       #1

    display driver nvidia windows kernel .....


    Hello everyone
    I recently installed windows 7 ultimate and i have some serious issues with it.
    at first when i installed it, and it booted for the first time into windows i got the BSOD everytime, only way i got passed it was to boot up with driver certification disabled. i was finally able to boot into windows 7.
    First thing i noticed was that everything responded very slow, if i clicked the start button it took up to 5 seconds for it to respond. still everything acts very slow.
    so after a while i got the error "display driver nvidia windows kernel mode driver 195.39 stopped responding and has recovered succesfully"
    so my screen starts to flicker black, and i get the BSOD once in a while.
    I can't run the performance test because my system freezes up.
    i tried upgrading/downgrading nvidia drivers, installed direct x disable aero and so on
    ive done alot of research on the web but i can't find any solutions to it.

    My system :

    gigabyte GA-MA790FX-DQ6 F3
    amd dual core 6000+
    4gb ram
    geforce 9800x2
    hdd 320gb

    thanks in advance
      My Computer


  2. Posts : 1,557
    XP, Seven, 2008R2
       #2

    195.39 is a beta driver. Try a stable one.

    compress and upload your minidumps here.
      My Computer


  3. Posts : 15
    windows xp
    Thread Starter
       #3

    i tried several drivers keep getting same error
    how do i compress and upload minidumps?

    thanks for the reply :)
      My Computer


  4. Posts : 1,557
    XP, Seven, 2008R2
       #4
      My Computer


  5. Posts : 15
    windows xp
    Thread Starter
       #5

    i have uploaded the minidump file(s)
    should have read the help first i'm sorry ; ;
      My Computer


  6. Posts : 5,747
    7600.20510 x86
       #6

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [E:\Temp\Rar$DI00.234\110409-20077-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02859000 PsLoadedModuleList = 0xfffff800`02a96e50
    Debug session time: Wed Nov  4 12:42:19.626 2009 (GMT-5)
    System Uptime: 0 days 0:01:47.437
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa80061904e0, fffff880047616c0, 0, d}
    
    *** 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+d06c0 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa80061904e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff880047616c0, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 000000000000000d, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+d06c0
    fffff880`047616c0 803db1899c0000  cmp     byte ptr [nvlddmkm+0xa99078 (fffff880`0512a078)],0
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`041442f8 fffff880`03aaecbc : 00000000`00000116 fffffa80`061904e0 fffff880`047616c0 00000000`00000000 : nt!KeBugCheckEx
    fffff880`04144300 fffff880`03aaea43 : fffff880`047616c0 fffffa80`061904e0 fffffa80`06228d50 fffffa80`061b2010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`04144340 fffff880`03b55f07 : fffffa80`061904e0 00000000`00000000 fffffa80`06228d50 fffffa80`061b2010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
    fffff880`04144370 fffff880`03b83d7e : fffffa80`ffffffff 00000000`00001a54 fffff880`041444c0 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`04144450 fffff880`03b69bb1 : fffffa80`0623b000 ffffffff`feced300 00000000`00000000 fffff880`04144600 : dxgmms1!VidSchWaitForCompletionEvent+0x196
    fffff880`04144490 fffff880`03b6caaf : 00000000`000000ff 00000000`00000000 fffff880`04144600 fffff8a0`01099010 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
    fffff880`04144590 fffff880`03b68c28 : fffff8a0`01099010 00000000`00000001 fffffa80`0623b000 fffff880`04144600 : dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7
    fffff880`041445d0 fffff880`03b68b0d : fffff8a0`01099010 00000000`000e0000 00000000`00070000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::FillAllocationInternal+0x34
    fffff880`04144760 fffff880`03b75029 : 00000000`00000000 fffffa80`067d88a0 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::FillAllocation+0xa9
    fffff880`041447d0 fffff880`03b67af3 : fffffa80`06244be0 fffff8a0`01099010 fffffa80`0623b000 fffff880`03b67600 : dxgmms1!VIDMM_MEMORY_SEGMENT::CommitResource+0xb5
    fffff880`041448b0 fffff880`03b64763 : 00000000`00000000 fffffa80`04086000 00000000`00000000 fffffa80`06437180 : dxgmms1!VIDMM_GLOBAL::PageInAllocations+0xbb
    fffff880`04144910 fffff880`03b7e65d : fffff880`00000000 fffff8a0`01c739c0 00000000`00000006 fffffa80`0642c2b0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xccf
    fffff880`04144ae0 fffff880`03b7e398 : fffff800`03ba8080 fffff880`03b7dd00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
    fffff880`04144cd0 fffff880`03b7de96 : 00000000`00000000 fffffa80`069cdbc0 00000000`00000080 fffffa80`061b2010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`04144d00 fffff800`02b6e166 : 00000000`fffffc32 fffffa80`061bc620 fffffa80`04006ae0 fffffa80`061bc620 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`04144d40 fffff800`028a9486 : fffff800`02a43e80 fffffa80`061bc620 fffff800`02a51c40 fffff880`01231534 : nt!PspSystemThreadStartup+0x5a
    fffff880`04144d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+d06c0
    fffff880`047616c0 803db1899c0000  cmp     byte ptr [nvlddmkm+0xa99078 (fffff880`0512a078)],0
    
    SYMBOL_NAME:  nvlddmkm+d06c0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a0c8387
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
    Video driver problems.

    Install from http://www.nvidia.com/Download/index.aspx?lang=en-us instead. Choose appropriately for your system. Either x86 32-bit or x64 64 bit depending on which version of Windows you've installed. (You have x64.)
      My Computer


  7. Posts : 1,557
    XP, Seven, 2008R2
       #7

    I've had problems like this before. They were usually due to the video card itself and/or power supply or voltage issues.

    In fact I have one system that behaves similarly right now. In order to prevent crashes I had to bump up the chipset voltage in the BIOS. It seems the motherboard is dying.
      My Computer


  8. Posts : 15
    windows xp
    Thread Starter
       #8

    thank you for the reply, but i installed my drivers from there and the error keeps coming any other suggestions? :)
      My Computer


  9. Posts : 15
    windows xp
    Thread Starter
       #9

    sup3rsprt said:
    I've had problems like this before. They were usually due to the video card itself and/or power supply or voltage issues.

    In fact I have one system that behaves similarly right now. In order to prevent crashes I had to bump up the chipset voltage in the BIOS. It seems the motherboard is dying.
    i owe a cooler master 1000watts
      My Computer


  10. Posts : 5,747
    7600.20510 x86
       #10

    Copy and paste sfc /scannow to elevated command prompt. Hit enter.

    Then from start menu search box, type system information. Hit enter. Then on screen that pops up, ctrl+s to save.
    Use Winrar on the saved file and then attach the .rar to a post.
      My Computer


 
Page 1 of 5 123 ... LastLast

  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 04:32.
Find Us