BSOD driver display error

Page 1 of 2 12 LastLast

  1. Posts : 5
    Windows 7 Home Premium
       #1

    BSOD driver display error


    hey guys,

    Soz if you have seen this before i posted into the wrong section of the forum

    I have a toshiba laptop that i bought a couple of months ago and every now and again it freezes then a couple of seconds later the BSOD shows up saying the display driver has timed out. All my display drivers and BIOS is up to date and its frustrating when your in the middle of writing an assignment and it happens! BTW Graphics card is a nvidia GT230M 1GB running Windows 7 HP. Model number of laptop is a500/026. Any help appreciated. Details as follows

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.768.3
    Locale ID: 5129

    Additional information about the problem:
    BCCode: 116
    BCP1: FFFFFA800460C010
    BCP2: FFFFF88005294F90
    BCP3: FFFFFFFFC000009A
    BCP4: 0000000000000004
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address 032610-20124-01.dmp26/03/2010 6:11:12 p.m. 0x00000116fffffa80`0460c010fffff880`05294f90ffffffff`c000009a00000000`00000004dxgkrnl.sysdxgkrnl.sys +5cef8
      My Computer


  2. Posts : 13,354
    Windows 7 Professional x64
       #2

    Welcome!

    Could you please upload your dmps for analysis? https://www.sevenforums.com/crash-loc...d-problem.html

    Thanks,
    ~JK
      My Computer


  3. Posts : 5
    Windows 7 Home Premium
    Thread Starter
       #3

    hey JK,

    thanks for replying to my post heres the zip file.
      My Computer


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

    kiwiphantom said:
    hey JK,

    thanks for replying to my post heres the zip file.


    Couldnt be more obvious. Your video driver.

    Uninstall completely and install a fresh copy

    You might also want to run a system file check
    type cmd in search>right click and run as admin>sfc /scannow

    let us know the results

    Ken

    Code:
    011010-23868-01.dmp    1/10/2010 4:40:03 PM        0x00000116    fffffa80`075bd010    fffff880`04aa8490    00000000`00000000    00000000`00000002    dxgkrnl.sys    dxgkrnl.sys+5cef8                    x64        C:\Users\K\Desktop\Minidump\011010-23868-01.dmp    2    15    7600    
    021110-21496-01.dmp    2/11/2010 10:22:25 AM        0x00000116    fffffa80`044cd010    fffff880`0509af90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    x64        C:\Users\K\Desktop\Minidump\021110-21496-01.dmp    2    15    7600    
    021610-27877-01.dmp    2/16/2010 9:26:26 PM        0x00000116    fffffa80`042e5130    fffff880`05e7bf90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    x64        C:\Users\K\Desktop\Minidump\021610-27877-01.dmp    2    15    7600    
    021910-31824-01.dmp    2/19/2010 7:11:13 PM        0x00000116    fffffa80`040434e0    fffff880`050b0f90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    x64        C:\Users\K\Desktop\Minidump\021910-31824-01.dmp    2    15    7600    
    022110-16754-01.dmp    2/21/2010 10:00:34 PM        0x00000116    fffffa80`041ef3e0    fffff880`0504cf90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    x64        C:\Users\K\Desktop\Minidump\022110-16754-01.dmp    2    15    7600    
    032110-24866-01.dmp    3/21/2010 10:42:58 PM        0x00000116    fffffa80`06c23010    fffff880`05006f90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    x64        C:\Users\K\Desktop\Minidump\032110-24866-01.dmp    2    15    7600    
    032110-29983-01.dmp    3/21/2010 9:46:52 PM        0x00000116    fffffa80`03ed94e0    fffff880`0964df90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    x64        C:\Users\K\Desktop\Minidump\032110-29983-01.dmp    2    15    7600    
    032610-20124-01.dmp    3/26/2010 6:11:12 PM        0x00000116    fffffa80`0460c010    fffff880`05294f90    ffffffff`c000009a    00000000`00000004    dxgkrnl.sys    dxgkrnl.sys+5cef8                    x64        C:\Users\K\Desktop\Minidump\032610-20124-01.dmp    2    15    7600
      My Computer


  5. Posts : 13,354
    Windows 7 Professional x64
       #5

    Looks like your nVidia drivers are throwing fits. Try updating them from Device Manager, or visit the card manufacturer's site and download the latest drivers there.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Jonathan\Desktop\Minidump\032110-29983-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 (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`03465000 PsLoadedModuleList = 0xfffff800`036a2e50
    Debug session time: Sun Mar 21 04:44:38.480 2010 (GMT-4)
    System Uptime: 0 days 0:29:40.321
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8003ed94e0, fffff8800964df90, 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+5e7f90 )
    
    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: fffffa8003ed94e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800964df90, 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+5e7f90
    fffff880`0964df90 4053            push    rbx
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`067a2b48 fffff880`03effef8 : 00000000`00000116 fffffa80`03ed94e0 fffff880`0964df90 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`067a2b50 00000000`00000116 : fffffa80`03ed94e0 fffff880`0964df90 ffffffff`c000009a 00000000`00000004 : dxgkrnl+0x5cef8
    fffff880`067a2b58 fffffa80`03ed94e0 : fffff880`0964df90 ffffffff`c000009a 00000000`00000004 00000000`00000001 : 0x116
    fffff880`067a2b60 fffff880`0964df90 : ffffffff`c000009a 00000000`00000004 00000000`00000001 fffffa80`03ed94e0 : 0xfffffa80`03ed94e0
    fffff880`067a2b68 ffffffff`c000009a : 00000000`00000004 00000000`00000001 fffffa80`03ed94e0 fffff880`03ed3867 : nvlddmkm+0x5e7f90
    fffff880`067a2b70 00000000`00000004 : 00000000`00000001 fffffa80`03ed94e0 fffff880`03ed3867 fffff880`0964df90 : 0xffffffff`c000009a
    fffff880`067a2b78 00000000`00000001 : fffffa80`03ed94e0 fffff880`03ed3867 fffff880`0964df90 fffffa80`07482000 : 0x4
    fffff880`067a2b80 fffffa80`03ed94e0 : fffff880`03ed3867 fffff880`0964df90 fffffa80`07482000 00000000`00000000 : 0x1
    fffff880`067a2b88 fffff880`03ed3867 : fffff880`0964df90 fffffa80`07482000 00000000`00000000 ffffffff`c000009a : 0xfffffa80`03ed94e0
    fffff880`067a2b90 fffff880`0964df90 : fffffa80`07482000 00000000`00000000 ffffffff`c000009a ffffffff`ff676980 : dxgkrnl+0x30867
    fffff880`067a2b98 fffffa80`07482000 : 00000000`00000000 ffffffff`c000009a ffffffff`ff676980 fffffa80`07470010 : nvlddmkm+0x5e7f90
    fffff880`067a2ba0 00000000`00000000 : ffffffff`c000009a ffffffff`ff676980 fffffa80`07470010 00000000`00000000 : 0xfffffa80`07482000
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+5e7f90
    fffff880`0964df90 4053            push    rbx
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  nvlddmkm+5e7f90
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a6827e0
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
      My Computer


  6. Posts : 5
    Windows 7 Home Premium
    Thread Starter
       #6

    hey guys i just uninstalled and reinstalled the display drivers with the updated version. No problems yet.....but i will let you guys know if it happens again.

    EDIT: Cheers guys for you help
      My Computer


  7. Posts : 5
    Windows 7 Home Premium
    Thread Starter
       #7

    Right since ive uninstalled and reinstalled the drivers it is still occurring but on less frequent basis
      My Computer


  8. Posts : 13,354
    Windows 7 Professional x64
       #8

    Now we have a pretty good guess it is your nVidia drivers. Now it is time to monkey around and try different drivers until you get satisfactory results.
      My Computer


  9. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #9

    Kiwiphantom, Jonathan is right. I had a similar problem with Nvidia drivers. I had to try four or five drivers before I got it worked out. And the driver that worked best for me was not the latest driver. I did get all the drivers I tried from the Nvidia site.
      My Computer


  10. Posts : 5
    Windows 7 Home Premium
    Thread Starter
       #10

    thanks guys for the advice. now let the fun begin.....
      My Computer


 
Page 1 of 2 12 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 06:24.
Find Us