BSOD While using GeForce GT 555M on all games

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 7 Home Premium 64bit
       #1

    BSOD While using GeForce GT 555M on all games


    The past few months I've been getting blue screens of death while playing any game after 5min - 30min, Ive updated my Nvidia drivers to the recommend but nothing has worked it was a clean install using driver sweeper and I've also tryed restoring computer to factory setting which also didn't work. Hope someone can help I've added my files.

    Update: The blue screen says something about nvkflt.sys and I have also disabled my Geforce Gt 555M in my drivers for the time being as it is a temporary fix until i can fix it permanently.
      My Computer


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

    The latest version of the display driver, that is the 320.49 WHQL is problematic in cases. 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
    • Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:


    If you are overclocking, Stop.

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Let us know the results.
    _____________________________________________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800d1714e0, fffff88004923714, ffffffffc000009a, 4}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvkflt.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvkflt.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvkflt.sys
    Probably caused by : nvkflt.sys ( nvkflt+31714 )
    
    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: fffffa800d1714e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88004923714, 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: 
    nvkflt+31714
    fffff880`04923714 4055            push    rbp
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`046fba48 fffff880`034a4054 : 00000000`00000116 fffffa80`0d1714e0 fffff880`04923714 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`046fba50 fffff880`03477867 : fffff880`04923714 fffffa80`0af42000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`046fba90 fffff880`034a3e63 : fffffa80`ffffd84d fffffa80`0af0b410 fffffa80`0d1714e0 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`046fbb40 fffff880`0357303d : fffffa80`066831b0 00000000`00000080 00000000`00000000 fffffa80`0af0b410 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`046fbbc0 fffff800`03569bae : 00000000`0211b42a fffffa80`0af32b50 fffffa80`057db040 fffffa80`0af32b50 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`046fbc00 fffff800`032bc8c6 : fffff800`03446e80 fffffa80`0af32b50 fffff800`03454cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`046fbc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvkflt+31714
    fffff880`04923714 4055            push    rbp
    
    SYMBOL_NAME:  nvkflt+31714
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvkflt
    
    IMAGE_NAME:  nvkflt.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51c417ad
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvkflt.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvkflt.sys
    
    Followup: MachineOwner
    ---------
    
    7: kd> lmvm nvkflt
    start             end                 module name
    fffff880`048f2000 fffff880`0493a000   nvkflt   T (no symbols)           
        Loaded symbol image file: nvkflt.sys
        Image path: \SystemRoot\system32\DRIVERS\nvkflt.sys
        Image name: nvkflt.sys
        Timestamp:        Fri Jun 21 14:36:53 2013 (51C417AD)
        CheckSum:         00052E7C
        ImageSize:        00048000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    7: kd> !sysinfo cpuspeed
    sysinfo: could not find necessary interfaces.
    sysinfo: note that mssmbios.sys must be loaded (XPSP2+).
      My Computer


  3. Posts : 6
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    Thanks for the reply, I've done all of the above and ran the Furmark for 20mins. There were no BSOD during this time, but to be sure it has been fixed I'll run some games over the next few hours which previously gave me BSOD, I'll post back with and update in a few hours.
      My Computer


  4. Posts : 6
    Windows 7 Home Premium 64bit
    Thread Starter
       #4

    Unfortunately this has not fixed the problem, I've just had another BSOD while playing Gary's Mod after 15mins. I've attcached the new files.
      My Computer


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

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    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.

    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
    Also let us know the wattage of the PSU.
    __________________________________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800b94b080, fffff88004e31704, ffffffffc000009a, 4}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvkflt.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvkflt.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvkflt.sys
    Probably caused by : nvkflt.sys ( nvkflt+31704 )
    
    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: fffffa800b94b080, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88004e31704, 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: 
    nvkflt+31704
    fffff880`04e31704 4055            push    rbp
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`02dcfa48 fffff880`05086054 : 00000000`00000116 fffffa80`0b94b080 fffff880`04e31704 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`02dcfa50 fffff880`05059867 : fffff880`04e31704 fffffa80`0a2f2000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`02dcfa90 fffff880`05085e63 : fffffa80`ffffd84d fffffa80`0a213410 fffffa80`0b94b080 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`02dcfb40 fffff880`0515503d : fffffa80`05c95b40 00000000`00000080 00000000`00000000 fffffa80`0a213410 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`02dcfbc0 fffff800`03523bae : 00000000`fffffc32 fffffa80`09cc6a00 fffffa80`057d9040 fffffa80`09cc6a00 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`02dcfc00 fffff800`032768c6 : fffff800`03400e80 fffffa80`09cc6a00 fffff800`0340ecc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`02dcfc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvkflt+31704
    fffff880`04e31704 4055            push    rbp
    
    SYMBOL_NAME:  nvkflt+31704
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvkflt
    
    IMAGE_NAME:  nvkflt.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51427b60
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvkflt.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvkflt.sys
    
    Followup: MachineOwner
    ---------
      My Computer


  6. Posts : 6
    Windows 7 Home Premium 64bit
    Thread Starter
       #6

    Thanks for the quick reply, I currently have Speccy running and I'll post its results after a few hours. I'm not sure what you want me to find out about my PSU I didn't even know what it was till I just wiki'd it :/ I don't know how to calculate the recommended on that website and don't know the wattage of my PSU. I replaced my battery last week as the old battery was apparently dead and wouldn't charge but my new battery came a few days ago but it won't charge either I thought it was just a dodgy battery but maybe there's not enough power being supplied to it? Is there anyway to test this.
      My Computer


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

    Sorry I missed that it is a laptop. My bad.

    No calculation is needed.

    If the battery is not being charged, and it was the same with the earlier one ... try changing the power adapter cord.
      My Computer


  8. Posts : 6
    Windows 7 Home Premium 64bit
    Thread Starter
       #8

    This is the speccy results after 2 hours of normal usage. Nothing gets hot only when I Furmark and it goes to 80dgrs max as fans kick in and it cools down to around 75dgrs etc..
      My Computer


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

    Make it sure that the battery is getting charged :)
    Apparently there is no other issue.
      My Computer


  10. Posts : 6
    Windows 7 Home Premium 64bit
    Thread Starter
       #10

    I've ordered a new AC Adapter cable as well as anew laptop battery hopefully this fixes the problem. I didn't know a battery problem could cause a Nvidia driver BSOD.
      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 23:44.
Find Us