Playing video games, BSOD nvkflt.sys (if not mistaking).

Page 1 of 3 123 LastLast

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

    Playing video games, BSOD nvkflt.sys (if not mistaking).


    Hello.

    I've had this laptop for a while now and got used to its quirks. For the past year I've had to live with a BSOD that has made my life living hell.

    The Laptop:
    Asus N55SF
    More specifications are given in the files attached.

    The BSOD.
    So firstly I was having BSODs due to my old nvidia drivers that came with the laptop which I fixed by getting the new ones. However this error which seems to be related to the nvkflt.sys driver has been around for a year. It appears randomly locks up my computer for a second or two and crashes it. On the top of the BSOD it says that it tried to recover from driver failure but failed. Since I've read so many posts about it, I know that that is a natural action from windows if the video drivers fail.

    I've tried:
    Complete nvidia driver re-installs.
    Warranty repair (Basically they just re-installed the default windows version full out bloatware and fixed my screen 2 times.)
    Updating most drivers I could find that were available for update.
    Sorta tried driver verifier but it kept crashing my windows before it started and giving me a BSOD about HIDClass (I think that was the case).

    The Attachments
    A long time ago I wanted to post about this issue here but didn't have the time to do it and I had compiled a collection of data and info about my laptop via the SF diagnostics tool that I had at the time and I believe I followed the rules that were posted here for posting for these sort of thing. When I tried using the current tool I didn't manage to get all of the info due to errors. I do believe that It was because I had my user profiles modified (which might be important in some way for the BSOD) so they saved to my secondary partition. Therefore I've included all I could get from my old attempt and the recent one in the attachments.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome to Seven Forums.

    You have too many items at start up. This may cause the system to load slower. Free up the start-up, nothing except the antivirus is usually needed.

    Avast is often a cause of BSOD's. Please remove and replace it with Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:

       Note
    1. Do not start the trial version of MalwareBytes

    You may also take a look at:

    Make scans with -

    Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

    Click on the
    Type CMD on Search
    Left click and Run as Administrator
    Type SFC /scannow

    Full tutorial here:

    Run Disk Check on your hard disk for file system errors and bad sectors on it:

    Upload a screenshot using:

    For how to upload a screenshot or file, read here

    Test your Hard Drive by running:

    Test and Diagnose RAM Issues with Memtest86+:

       Tip

    • Pay close attention to part 3 of the tutorial "If you have errors"
    • Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.


    Go through this thread for more information on your bugcheck:

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 117, {fffffa800da12310, fffff88005b8f010, 0, 0}
    
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    *** WARNING: Unable to verify timestamp for dxgmms1.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
    Unable to load image 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+13b010 )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_TIMEOUT_DETECTED (117)
    The display driver failed to respond in timely fashion.
    (This code can never be used for real bugcheck).
    Arguments:
    Arg1: fffffa800da12310, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88005b8f010, The pointer into responsible device driver module (e.g owner tag).
    Arg3: 0000000000000000, The secondary driver specific bucketing key.
    Arg4: 0000000000000000, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+13b010
    fffff880`05b8f010 ??              ???
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
    
    TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x117
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`0738a4f0 fffff880`04c6a5f7 : fffffa80`0da12310 fffff880`04cb6e93 fffffa80`0da12310 fffff880`04c38843 : watchdog!WdDbgReportRecreate+0xa3
    fffff880`0738aa10 fffff880`04c6b2bc : fffff8a0`0e77b300 fffff8a0`0e77b300 00000000`00000080 fffffa80`0da12310 : dxgkrnl!TdrUpdateDbgReport+0xcb
    fffff880`0738aa60 fffff880`04c3f6b3 : 00000000`00000001 fffffa80`0bcb1000 00000000`00000000 fffff880`04d0e2d5 : dxgkrnl!TdrCollectDbgInfoStage2+0x220
    fffff880`0738aa90 fffff880`04c6be0f : fffffa80`0bc04a58 00000000`00000000 fffffa80`0da12310 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0xef
    fffff880`0738ab40 fffff880`04d3aec1 : fffffa80`0da98860 00000000`00000080 00000000`00000000 fffffa80`0bc04410 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`0738abc0 fffffa80`0da98860 : 00000000`00000080 00000000`00000000 fffffa80`0bc04410 fffff800`033f2e80 : dxgmms1+0x37ec1
    fffff880`0738abc8 00000000`00000080 : 00000000`00000000 fffffa80`0bc04410 fffff800`033f2e80 00000000`00000000 : 0xfffffa80`0da98860
    fffff880`0738abd0 00000000`00000000 : fffffa80`0bc04410 fffff800`033f2e80 00000000`00000000 00000000`00000001 : 0x80
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+13b010
    fffff880`05b8f010 ??              ???
    
    SYMBOL_NAME:  nvlddmkm+13b010
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  518fe8f9
    
    FAILURE_BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
    
    4: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`05a54000 fffff880`06535000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Mon May 13 01:09:45 2013 (518FE8F9)
        CheckSum:         00AB6DED
        ImageSize:        00AE1000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Mini Kernel Dump does not contain unloaded driver list
    
      My Computer


  3. Posts : 3,056
    Windows 10
       #3

    Welcome to 7F :) .

    Your bugchecks indeed point to an nVidia driver:
    Code:
    VIDEO_TDR_TIMEOUT_DETECTED (117)
    
    Arguments:
    Arg1: fffffa800da12310, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88005b8f010, The pointer into responsible device driver module (e.g owner tag).
    Arg3: 0000000000000000, The secondary driver specific bucketing key.
    Arg4: 0000000000000000, Optional internal context dependent data.

    • The display driver failed to respond in timely fashion.
    Code:
    FAULTING_IP: 
    nvlddmkm+13b010
    
    FAILURE_BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys



    By looking at the stack we can see the drivers involved

    at the time of the crash:

    Code:
    fffff880`0738a4f8  fffff880`04c2e8a0 dxgkrnl!g_TdrConfig
    fffff880`0738a510  fffff880`05b8f010 nvlddmkm+0x13b010
    fffff880`0738a5d0  fffff880`04c2e8a0 dxgkrnl!g_TdrConfig
    fffff880`0738aa08  fffff880`04c6a5f7 dxgkrnl!TdrUpdateDbgReport+0xcb
    fffff880`0738aa18  fffff880`04cb6e93 dxgkrnl!DmmCollectTdrDiagInfo+0x143
    fffff880`0738aa28  fffff880`04c38843 dxgkrnl!DxgkCollectCoreDbgInfo+0x9b
    fffff880`0738aa58  fffff880`04c6b2bc dxgkrnl!TdrCollectDbgInfoStage2+0x220
    fffff880`0738aa88  fffff880`04c3f6b3 dxgkrnl!DXGADAPTER::Reset+0xef
    fffff880`0738aaa8  fffff880`04d0e2d5 dxgmms1!VidSchiScheduleCommandToRun+0x1e9
    fffff880`0738ab10  fffff880`04d3adc0 dxgmms1!VidSchiWorkerThread
    fffff880`0738ab38  fffff880`04c6be0f dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`0738ab98  fffff880`04d3adc0 dxgmms1!VidSchiWorkerThread
    fffff880`0738abb8  fffff880`04d3aec1 dxgmms1!VidSchiWorkerThread+0x101


    By using the lmvm command we get more information about the driver:
    Code:
    fffff880`05a54000 fffff880`06535000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sun May 12 22:09:45 2013 (518FE8F9)
    You're using version 320.18 which is known to be buggy.
    Code:
    Name    NVIDIA GeForce GT 555M
    Driver Version    9.18.13.2018











    • Remove Microsoft Virtual PC 2004 (Virtualiation Client):

    Code:
    VMNetSrv.sys Wed Jan 24 14:05:46 2007
    vmm.sys      Sun Feb 18 10:11:21 2007
    • Remove ATK WMIACPI Utility (ATKACPI driver and hotkey-related utilities):

    Code:
        Image path: atkwmiacpi64.sys
        Image name: atkwmiacpi64.sys
        Timestamp:        Wed May 25 14:04:09 2011 (4DDCE229)


    Although no evidence point to a problem with Avast in particular
    I do recommend removing the software using the Uninstall Utility and installing MSSE instead.


    Edit:
    I just can't leave for a second .
      My Computer


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

    There is a lot to take in. I'll make sure to do all of this and report back when I'm done. Thanks for the quick responses.
      My Computer


  5. Posts : 3,056
    Windows 10
       #5

    Keep us updated :) !
      My Computer


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

    Hey YoYo,

    So far I've:

    1.Installed the drivers you recommended,
    2.Did all of the first part of KoolKats post (Related to anti virus software and scans)
    3.Deleted loads of bloatware.
    4.Ran SFC /Scannow once so far. (Had errors that It did not fix and trying for a second time atm)
    5.Updated DX from the link you've posted
    6.Deleted the Virtual PC and ATK software.

    Tried playing Bioshock, ran smoothly, but still got a BSOD. Will try the few steps I've not done yet later on.
      My Computer


  7. Posts : 3,056
    Windows 10
       #7

    Good progress :) ,
    Once you're done with the rest of the steps upload a new instance of the SFDT .zip file.
      My Computer


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

    Um. Just had a Memory Management BSOD as well. Will prioritize memtest tomorrow.
      My Computer


  9. Posts : 3,056
    Windows 10
       #9

    Upload the new files using a new pass of SFDT.
      My Computer


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

    There are todays minidumps and all the data I could get with the SFDT. (Didn't do any steps after the ones I posted yesterday).
      My Computer


 
Page 1 of 3 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 14:26.
Find Us