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

[iwiivi]

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.

 

[koolkat77]

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.

• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html
• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

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:

• Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase
• Help protect your PC with Microsoft Security Essentials
• Malwarebytes Free

   Note

1. :info: Do not start the trial version of MalwareBytes
2. 

You may also take a look at:

• Good & Free System Security Combination

Make scans with -

• TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US
• Online Virus Scanner Eset

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 rb:
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

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

• http://www.sevenforums.com/tutorials/433-disk-check.html

Upload a screenshot using:

• CrystalDiskInfo

:tip: For how to upload a screenshot or file, read here​

Test your Hard Drive by running:

• Hard Drive Diagnostic Procedure

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to part 3 of the tutorial "If you have errors"
• :tip: 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:

• http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

[B]*******************************************************************************
*                                                                             *
*                        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
[/B]

 

[YoYo155]

Welcome to 7F .

Your bugchecks indeed point to an nVidia driver:

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.

FAULTING_IP: 
[COLOR=Red][B][U]nvlddmkm[/U][/B][/COLOR]+13b010

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_[COLOR=Red][U][B]nvlddmkm.sys[/B][/U][/COLOR]

By looking at the stack we can see the drivers involved
at the time of the crash:

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

• Driver Reference Table - nvlddmkm.sys
• Driver Reference Table - dxgmms1.sys
• Driver Reference Table - dxgkrnl.sys

By using the lmvm command we get more information about the driver:

fffff880`05a54000 fffff880`06535000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR=Red][U][B]Sun May 12 22:09:45 2013[/B][/U][/COLOR] (518FE8F9)

You're using version 320.18 which is known to be buggy.

Name    NVIDIA GeForce GT 555M
Driver Version    9.18.1[COLOR=Red][U][B]3.2018[/B][/U][/COLOR]

• Uninstall the nVidia display drivers and software using:
  • How do I uninstall my NVIDIA display drivers?
  • Follow though with a pass of Driver Sweeper.
• Install a stable release:
  • Download 314.22
    When installing select Custom Settings and uncheck:
    
    3D Vision (all of them).
    HD Audio.
    Nvidia Updates.
    
    Do check Preform a clean installation.

• Update DirectX | Download

• Cleanup your startup by following this this tutorial.
  • http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

• Remove Microsoft Virtual PC 2004 (Virtualiation Client):

VMNetSrv.sys [COLOR=Red][U][B]Wed Jan 24 14:05:46 2007[/B][/U][/COLOR]
vmm.sys      [COLOR=Red][U][B]Sun Feb 18 10:11:21 2007[/B][/U][/COLOR]

• Driver Reference Table - VMNetSrv.sys
• Driver Reference Table - vmm.sys

• Remove ATK WMIACPI Utility (ATKACPI driver and hotkey-related utilities):

    Image path: atkwmiacpi64.sys
    Image name: atkwmiacpi64.sys
    Timestamp:        [COLOR=Blue][U][B]Wed May 25 14:04:09 2011[/B][/U][/COLOR] (4DDCE229)

• Driver Reference Table - atkwmiacpi64.sys

​

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 .

 

[iwiivi]

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.

 

[YoYo155]

Keep us updated !

 

[iwiivi]

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.

 

[YoYo155]

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

 

[iwiivi]

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

 

[YoYo155]

Upload the new files using a new pass of SFDT.

 

[iwiivi]

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).

 

[koolkat77]

Sorry to bump, have you followed anything from my post?

 

[YoYo155]

Sorry to bump, have you followed anything from my post?

iwiivi, did you^ ?

Also the new file doesn't contain new dumps unfortunately, Check in the minidump folder
zip and upload them manually if present.

C:\Windows\minidump

 

[iwiivi]

Yeah, KoolKat. Like I said in my previous post yesterday I've swapped out Avast for MSSE and such. I've also checked my system with SFC once and It said that It didn't manage to fix everything so i'll be doing that again a couple of time later tonight, that is as far as I got with your post unfortunately since I have several thing I need to take care of.

tl;dr I've done everything up until the Disk Check, all antivirus scans negative, SFC didnt fix everything.

And about the dumps, since my the privilege and ownership of files is a little iffy on my computer, I had to copy them by hand from that same folder so I'm afraid that it's all I have.

 

[YoYo155]

Yeah, KoolKat. Like I said in my previous post yesterday I've swapped out Avast for MSSE and such. I've also checked my system with SFC once and It said that It didn't manage to fix everything so i'll be doing that again a couple of time later tonight, that is as far as I got with your post unfortunately since I have several thing I need to take care of.

tl;dr I've done everything up until the Disk Check, all antivirus scans negative, SFC didnt fix everything.

And about the dumps, since my the privilege and ownership of files is a little iffy on my computer, I had to copy them by hand from that same folder so I'm afraid that it's all I have.

As far as I'm concerned you can treat mine and koolkat77's posts as one,
they are as important (if not more).

That's disappointing, did you happen to catch the stop-code i.e 0x00000116 / 0x00000117 / 0x0000003b?
I recommend you complete the steps suggested as they are based upon experience.

 

[iwiivi]

I've treated the posts as one so far as they both indeed looked important and I've done bits of both as some of them were easy to do with the time I had. I can give you something even better with regards to the error I had. I'll complete the rest of the steps as soon as I can.

P.S. I had an BSOD related to the memory management yesterday which looked different to the TDR one in the picture.

 

[YoYo155]

That points the finger again at a driver used by your GPU.

Test if the PC is getting hot:

• Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.

Did you test the RAM yet?

 

[iwiivi]

Haven't done the RAM test. My PC gets to about 70 - 85 degrees since I have SpeedFan on most of the time to check my temps. I'm not sure if that is ok.

P.S. Should I use both Prime95 and Furmark at the same time and then get the temp readings?

 

[YoYo155]

Haven't done the RAM test. My PC gets to about 70 - 85 degrees since I have SpeedFan on most of the time to check my temps. I'm not sure if that is ok.

P.S. Should I use both Prime95 and Furmark at the same time and then get the temp readings?

Those temperatures are very hot!

Check your PC for dust accumulation
and clogged fans (especially between the heatsink fins [the metal part of the fan])

You could run at the same time in-order to get maximum stability and temperature readings
but I urge not to do so considering your current situation.

Also I recommend using Speccy, it gives a more accurate reading on a broader range of components.

 

[iwiivi]

I've tried lowering my temps in many ways but It seems that nothing helps. Cooling pads, dust cleaning...

Ill do the stress test later when I can access the laptop and post the results asap. Oh and those temps I mentioned were of my laptop under stress.

 

[YoYo155]

Test the as described at koolkat77's post and share the results.

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to part 3 of the tutorial "If you have errors"
• :tip: 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.

I must insist about reading the temperatures with Speccy please.