BSOD caused by GPU? Causing significant problems

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.

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 said:

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.

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

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.

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>









.