Solved BSOD caused by GPU? Causing significant problems

[daddyjames]

Hello,

I have had issues since I initially received my computer in 2009 with BSOD caused by conflicts between NVidia's driver and win7. In the past, I have successfully been able to find a fix. After the last update round (from Windows), things went awry.

I have been dealing with this for two days, run several sfc/scannow; uninstalled and reinstalled the updates; run chkdisk /f at startup; tried a previous restore point before the updates were installed (which is now gone, as I have had to do this several times); tried various version of the nVidia driver to no avail..
Anyways, things have gone from bad to worse . . . sometimes I get BSOD, sometimes it just shuts down the entire system.

I am about to give up, and wipe Windows off my system for good (I have Linux partitioned on one of the harddrives) but would like to see if I can get this resolved as I am in the middle of an extensive analysis.

I have several CBS log files attached also, if those help.

Thanks.

 

[Northernsoul55]

Hi,
Your dump files show a stop ox116 which is a Display or Graphics related BSOD.

[FONT=Verdana][COLOR=#323232][COLOR=#323232][FONT=Verdana]*******************************************************************************[/FONT][/COLOR]
[FONT=Verdana][COLOR=#323232]*                                                                             *[/COLOR][/FONT]
[FONT=Verdana][COLOR=#323232]*                        Bugcheck Analysis                                    *[/COLOR][/FONT]
[FONT=Verdana][COLOR=#323232]*                                                                             *[/COLOR][/FONT]
[FONT=Verdana][COLOR=#323232]*******************************************************************************[/COLOR][/FONT]
[COLOR=#323232][FONT=Verdana]Use !analyze -v to get detailed debugging information.[/FONT][/COLOR]
[COLOR=#323232][FONT=Verdana][COLOR=red]BugCheck 116[/COLOR], {fffffa800fe78010, fffff88006967198, 0, 2}[/FONT][/COLOR]
[COLOR=#323232][FONT=Verdana]Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2[/FONT][/COLOR]
[FONT=Verdana][COLOR=#323232]*** WARNING: Unable to verify timestamp for nvlddmkm.sys[/COLOR][/FONT]
[FONT=Verdana][COLOR=#323232]*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys[/COLOR][/FONT]
[FONT=Verdana][COLOR=#323232]Probably caused by :[COLOR=red] nvlddmkm.sys[/COLOR] ( nvlddmkm+139198 )[/COLOR][/FONT]
[COLOR=#323232][FONT=Verdana]Followup: MachineOwner[/FONT][/COLOR]
[FONT=Verdana][COLOR=#323232]---------[/COLOR][/FONT]
[COLOR=#323232][FONT=Verdana]0: kd> !analyze -v[/FONT][/COLOR]
[FONT=Verdana][COLOR=#323232]*******************************************************************************[/COLOR][/FONT]
[FONT=Verdana][COLOR=#323232]*                                                                             *[/COLOR][/FONT]
[FONT=Verdana][COLOR=#323232]*                        Bugcheck Analysis                                    *[/COLOR][/FONT]
[FONT=Verdana][COLOR=#323232]*                                                                             *[/COLOR][/FONT]
[FONT=Verdana][COLOR=#323232]*******************************************************************************[/COLOR][/FONT]
[COLOR=#323232][FONT=Verdana][COLOR=red]VIDEO_TDR_FAILURE (116)[/COLOR][/FONT]
[FONT=Verdana]Attempt to reset the display driver and recover from timeout failed.[/FONT][/COLOR][/COLOR][/FONT]

Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card.

As you have tried many Nividia drivers with no luck, please try this known stable driver:
Download and install: :ar: Driver Fusion.
Reboot the computer in :ar: Advanced Boot Options, safe mode.
Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
If it says the the free version of Driver Fusion cannot remove all the elements, stop there and follow
:ar: Drivers - Clean Left over Files after Uninstalling
Boot normally now. Go to: :ar: Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for: GeForce 306.23 Driver, dated 13.9.2012 and install it.
-----------------------------------------------------------------------------------------------

Also please read and follow this guide:
:ar: Video TDR 0x116 Troubleshooting
Also please ensure you have all the latest Windows updates installed.
Please remove all Norton programs, as Norton is well known to cause BSOD issues:
:ar:https://support.norton.com/sp/en/uk/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us

As an alternative:
Microsoft Security Essentials.
Recommended from a strict BSOD perspective, compatibility & stability
compared to other antiviruses/internet security software.

:ar: Microsoft Security Essentials - Microsoft Windows

   Note

Once downloaded, update and run a full system scan

Cheers
Dave

 

[daddyjames]

Dave

Dave,

Thanks! So far so good except that I am still having issues - now with Windows Defender and Windows update operating. And I am sure that there probably is more

Again, I have run chkdisk /f/r and scannow. chkdsk finds no problems. scannow indicates that there are corrupt files that it cannot fix.

Should this be started in a new thread?

 

[daddyjames]

Dave,

Thanks! So far so good except that I am still having issues - now with Windows Defender and Windows update operating. And I am sure that there probably is more

Again, I have run chkdisk /f/r and scannow. chkdsk finds no problems. scannow indicates that there are corrupt files that it cannot fix.

Should this be started in a new thread?

Ok spoke too soon. Computer just crashed, and shut down again without warning - even with all the steps I took. Although, I know that there are still issues remaining. Attached are the appropriate files.

 

[daddyjames]

OK, another update.

I downloaded and updated the driver for Intel Rapid Storage Technology (although Windows: Device Manager said I had the most recent driver, Intel's site said I didn't).

Installed it, and rebooted.

All systems appear to be go now. Windows Update and Defender are working now, and sfc/Scannow indicates that there are no more corrupt files. Keeping my fingers crossed . . .

 

[Northernsoul55]

Good work

Now lets see if the system remains stable, post back in a few days or so.
If you experience another crash, run the SF Tool and post up a new log.

cheers

Dave

 

[daddyjames]

Dave,

Nope, did not do the trick. Had several more instances of BSOD (same error - stop ox116). All I was doing each time was browsing on a single website - and it happened using either IE10 or Google Chrome.

Went back to the updates and uninstalled these three (I don't need them for the desktop, according to their descriptions), so I am not sure which one may be causing the issues.

Update for Windows 7 for x64-based Systems (KB2820331)
Update for Windows 7 for x64-based Systems (KB2813956)
Update for Windows 7 for x64-based Systems (KB2798162)

My suspicion is that it is KB2820331. Not sure that I am all that interested in figuring it out, as I have been dealing with this for the past three days.

So far this seems to have (finally) done the trick. Everything is now running fine (fingers crossed again). Will put the system through the paces and update you later today/tomorrow.

 

[Northernsoul55]

Ok, good news and thanks for the feedback.

I suspect you may BSOD again as the issue is either GPU drivers or the GPU itself.

If the stable nvidia driver you have installed fails and you are still getting STOP 0x116 errors
then perhaps it may be best to stress test the card:

Stress Test

Video Card - Stress Test with Furmark: :ar: Video Card - Stress Test with Furmark

Monitor temperature of the system during the tests :ar: HWMonitor
cheers
Dave

 

[daddyjames]

Dave,

Well, tried installing "Update for Windows 7 for x64-based Systems (KB2820331)". What a mistake. Here is the steps taken since.

(1) Update KB2820331 did not install. It got hung up while installing. Tried to stop it, to no avail. After a few hours, eventually surrendered, and turned off the computer.
(2) Rebooted into safe mode. Ran sfc/scannow - no surprise, there where corrupt files.
(3) Ran chkdsk /f/r - went through the entire process. 76 files need reparsing.
(4) Restarted into Safe mode and ran sfc/scannow: still corrupt files - same files/results as before.
(5) Tried restore to previous point (before I reinstalled any of the most recent updates).
(6) Successfully restored - during restart of windows, BSOD - stop ox116, of course.
(7) automatic reboot - successful, and system successfully restored to the previous point. None of the updates that I had previously installed have been installed.
(8) reinstalled the seven updates as before - everything appears fine.
(9) reboot - reran sfc/scannnow - still corrupt files.
(10) Tried to upload files using SF_Diagnostics_tools - no longer works. Gives the following error message attached below (Error Message . . .).
(11) repaired/updated Microsoft Visual C++ via MS website.
(12) Ran "Troubleshoot problems with installing updates" - MS Fix it - Problems were "resolved", but stupid me, did not note what those problems were - very tired.
(13) sfc/scannow - corrupt files still exist.
(14) Restart - normally.
(15) SF_Diagnostic_Tools still won't run - Visual Basic Error, same error as before (attached).
(16) Opened properties on SF_Diagnostic_Tools - Says that this program comes from another computer and may be blocked.
(17) Hit "Unblock" and "Apply". Interestingly enough, I believe that this is what KB2820331 is supposed to do? However, according to Windows Update, it is not installed. And because I restored to a point before I had installed it, it should not be installed.
(18) SF_Diagnostic_Tools still won't run - same error as before (attached).
(19) Ran sfc/scannow - still corrupt files, same results as the previous two attempts.
(20) Removed the execute file for SF_Diagnostics.
(21) Re-downloaded and transferred over to desktop. Tried to collect data again - same bug as before.
(22) Reran Windows Update "Troubleshoot problems with installing updates" - MS Fix it.
(23) Problems found/fixed: Windows Update error 0x80070057 (2013-5-27-T12-34-57P) Fixed.
(24) Not doing anything else at the moment.

System is "stable", but still has the corrupt files.

Not getting any BSODs at the moment - surprising since previously it would happen while posting replies to the forum (no reflection on the forum, just illustrative of the sensitivity of the problems I am/was experiencing).

Any thoughts?
I have attached the last CBS file (CBS(13).zip) and the error message generated by the SF_Diagnostics_Tool for further information. Still cannot generate any files using the SF_Diagnostics_Tool.

<sigh>









.

 

[Northernsoul55]

Hi,

I think we need to sort out those corrupt files and update issues.

I will ask Tom982 to assist you with these issues as they are not my field of expertise, but his.

Cheers

Dave

 

[tom982]

Hi daddyjames, welcome to the forums!

Firstly, let me just say thank you for taking the time to write up what you have already tried in so much detail! It's a big timesaver for me as I know exactly where to take this now.


Your CBS log indicates one file as corrupt, although I don't believe it to be an issue as it is a configuration file. .inf and .ini files are very often flagged by SFC as corrupt when in fact they have just been modified (a great example is when you add a sidebar gadget, settings.ini gets detected as 'corrupt' when it isn't.). But, just in case it is, we'll fix this issue anyway:

2013-05-27 05:01:42, Info                  CSI    00000311 [SR] Repairing 1 components
2013-05-27 05:01:42, Info                  CSI    00000312 [SR] Beginning Verify and Repair transaction
2013-05-27 05:01:42, Info                  CSI    00000313 [SR] Cannot repair member file [l:16{8}]"apps.inf" of Microsoft-Windows-shell32, Version = 6.1.7601.17859, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-05-27 05:01:43, Info                  CSI    00000314 [SR] Unable to repair \SystemRoot\WinSxS\Manifests\\[l:16{8}]"apps.inf"
2013-05-27 05:01:43, Info                  CSI    00000315 [SR] Cannot repair member file [l:16{8}]"apps.inf" of Microsoft-Windows-shell32, Version = 6.1.7601.17859, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-05-27 05:01:43, Info                  CSI    00000316 [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2691442~31bf3856ad364e35~amd64~~6.1.1.3.2691442-4_neutral_GDR"
2013-05-27 05:01:43, Info                  CSI    00000317 Repair results created:

I've got to leave for work in about 10 minutes so I'll have to post a fix when I get back. Should be roughly 7pm BST.


Whilst I'm out, can you download and install the System Update Readiness Tool please? Keep it on your Desktop for future use, should we need it.


Download System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2013] from Official Microsoft Download Center


When it finishes running, post the log please:


C:\Windows\Logs\CBS\CheckSUR.persist.log

Tom

 

[daddyjames]

@Northernsoul55 (aka Dave)

Thanks for your help, and for passing me along. Have a good summer. Cheers.

@Tom982 (aka Tom)

Hi and hope you had a great day at work.

Downloaded and installed the software. Not sure how to "keep it on the desktop" - unless you are referring to the download - as it gave me no option to install it to a particular location. Attached is the CheckSUR.persist.log.

Apparently there were 11 corrupt files, and two that could not be fixed:

servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum

servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum

 

[tom982]

Hi daddyjames,

Sorry for the confusion, yes I simply meant for you to keep the downloaded file on your Desktop but it doesn't matter now as we don't need to run it again.

Your CheckSUR log shows that the System Update Readiness Tool corrected a few problems:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 19.0
2013-05-28 05:05


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x00000000    servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum        Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
(f)    CBS MUM Corrupt    0x00000000    servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum        Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)    CSI Payload File Missing    0x00000000    msfeeds.mof    amd64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_10.2.9200.16540_none_ddc23b3caae81b6e    
(fix)    CSI Payload File Missing    CSI File Replaced    File: msfeeds.mof From: C:\Windows\winsxs\amd64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_10.2.9200.16521_none_ddc023e0aaea0261\msfeeds.mof
(f)    CSI Payload File Missing    0x00000000    msfeeds.mof    wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_10.2.9200.16540_none_e816e58edf48dd69    
(fix)    CSI Payload File Missing    CSI File Replaced    File: msfeeds.mof From: C:\Windows\winsxs\amd64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_10.2.9200.16521_none_ddc023e0aaea0261\msfeeds.mof
(f)    CSI Payload File Missing    0x00000000    apps.inf    amd64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.17859_none_ca28f7c128b75dec    
(fix)    CSI Payload File Missing    CSI File Replaced    File: apps.inf From: C:\Windows\winsxs\amd64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.16385_none_c81e1c852bacf466\apps.inf
(f)    CSI Payload File Missing    0x00000000    msfeeds.mof    wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_9.4.8112.20580_none_df212fd95aca175d    
(fix)    CSI Payload File Missing    CSI File Replaced    File: msfeeds.mof From: C:\Windows\winsxs\amd64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_10.2.9200.16521_none_ddc023e0aaea0261\msfeeds.mof
(f)    CSI Payload File Missing    0x00000000    apps.inf    amd64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.22015_none_cad9ab3641b85bd8    
(fix)    CSI Payload File Missing    CSI File Replaced    File: apps.inf From: C:\Windows\winsxs\amd64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.16385_none_c81e1c852bacf466\apps.inf
(f)    CSI Payload File Missing    0x00000000    msfeeds.mof    amd64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_10.2.9200.20644_none_c6e96994c497fd98    
(fix)    CSI Payload File Missing    CSI File Replaced    File: msfeeds.mof From: C:\Windows\winsxs\amd64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_10.2.9200.16521_none_ddc023e0aaea0261\msfeeds.mof
(f)    CSI Payload File Missing    0x00000000    msfeeds.mof    wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_10.2.9200.20644_none_d13e13e6f8f8bf93    
(fix)    CSI Payload File Missing    CSI File Replaced    File: msfeeds.mof From: C:\Windows\winsxs\amd64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_10.2.9200.16521_none_ddc023e0aaea0261\msfeeds.mof
(f)    CSI Payload File Missing    0x00000000    apps.inf    amd64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.17038_none_c85710852b81d6e2    
(fix)    CSI Payload File Missing    CSI File Replaced    File: apps.inf From: C:\Windows\winsxs\amd64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.16385_none_c81e1c852bacf466\apps.inf
(f)    CSI Payload File Missing    0x00000000    msfeeds.mof    amd64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_9.4.8112.20580_none_d4cc858726695562    
(fix)    CSI Payload File Missing    CSI File Replaced    File: msfeeds.mof From: C:\Windows\winsxs\amd64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_10.2.9200.16521_none_ddc023e0aaea0261\msfeeds.mof

Summary:
Seconds executed: 576
 Found 11 errors
 Fixed 9 errors
  CSI Payload File Missing Total count: 9
  Fixed: CSI Payload File Missing.  Total count: 9
  CBS MUM Corrupt Total count: 2

Unavailable repair files:
    servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
    servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
    servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
    servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat

The errors that it couldn't fix are nothing to worry about and are merely a bug in the way that the SURT detects package names

Is Windows Update working now? If not, could you upload your CBS log again please:

C:\Windows\Logs\CBS\CBS.log

Tom

 

[daddyjames]

Tom,

Mixed results with Windows Update.

The first test was to install the latest Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.151.1103.0)

Installation date: ‎5/‎28/‎2013 4:07 PM
Installation status: Successful


The second was to try to install one of the updates that I had removed and hidden (see previous post):
First I restored the update, then attempted to install.
The first attempt failed.

Update for Windows 7 for x64-based Systems (KB2798162)
Installation date: ‎5/‎28/‎2013 4:39 PM
Installation status: Failed
Error details: Code 80246007

So, I tried again. The second attempt was successful (but I have not restarted the computer yet, and will assume that the error code blow is because of that?):

Update for Windows 7 for x64-based Systems (KB2798162)
Installation date: ‎5/‎28/‎2013 4:43 PM
Installation status: Pending
Error details: Code 80242014

So, I will restart the computer, do the scannow, and upload the CBS.log.

 

[daddyjames]

Tom,

Good news! The computer was successfully configured for the update that I did install. Full disclosure, I inadvertantly did a chkdsk /f/r on the reboot (I had probably put in the command at some point and not restarted the computer).

The results from scannow came up clean.

C:\Windows\system32>sfc/scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

For the moment all is good. I am still hesitant to install Update KB2820331 at the moment (I have this one also hidden). I have other things to do that should have been finished days ago.

The computer is running smoothly, and no BSODs anymore. Obviously, if this should change, I'll be back.

Since everything appears to be good, I can mark it as solved.

Unless you would rather wait until I have the time, and the courage, to try and install the KB2820331 Update to see what happens.

Let me know.

 

[Northernsoul55]

Hi,

Good your computer seems more stable but I would suggest waiting a few days or so
before marking solved, just to be certain.

(Thanks Tom for the invaluable help m8 )

Cheers

Dave

 

[daddyjames]

Dave,

Ok, I will keep you updated.

James

 

[daddyjames]

Dave,

I do have another issue - not a BSOD - so if another thread needs to be started let me know.

I tried to reinstall a program downloaded from the internet - a game for my kid. During the rollbacks, it was removed.

It did not install properly, and I cannot uninstall it as I get the following error when I try to remove it from the control panel:

Error Code: -5009 : 0x8000ffff
Error Information:
>Kernel\TextSubstitution.cpp (860)
>Kernel\IScriptWrapper.cpp (19)
>Kernel\ObjectWrapper.cpp (162)
>Kernel\ObjectWrapper.cpp (557)
>Kernel\Component.cpp (1230)
>Kernel\CABFile.cpp (433)
>SetupNew\setup.cpp (871)

It also indicates that the Install Wizard is still "busy". I have contacted the vendor, and am waiting a response from them.
Again, if I should open another thread - in another forum, let me know. Appreciate the time you have spent helping me deal with the problems I have been having.

 

[Northernsoul55]

No problem, I will help if I can

For uninstall issues try:

Revo Uninstaller
Download and install Revo Uninstaller free from here:
:ar: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).
Let me know how you get on.
Cheers
Dave

 

[daddyjames]

Dave,

Just wanted to give you an update.

Everything is going well. No more BSODs and the computer is actually running much better than it has run in the past. Have not tried to install KB2820331, and don't think I ever will, given the track record I have had with it.

Not going to say that it was the source of my problems, however not willing to spend the time to fix things again if it was.

Thank you very much for your, and Tom's, assistance. Appreciate it very much.

As far as I am concerned, this thread can be marked as solved.

Cheers!