BSOD during Steam games - additional issues (non-BSOD)

In the last 48 hours I downloaded Skype and BOINC (Berkeley Open Infrastructure for Network Computing). I also updated my drivers for my AMD Radeon HD 6950 video cards (as part of attempting to resolve a BSOD related to ATI drivers.
When attempting to play any Call of Duty games on Steam, I will either get a black screen that then closes itself, or a BSOD. Also, when BOINC starts, I get a BSOD every time. I have uninstalled both BOINC and Skype since the issue started shortly after installing those two programs, updated my video drivers, performed repair installs on DX and VC++. Additionally, I deleted the "appcache" folder from Steam thinking that perhaps I had corrupted data there as the application will recreate that folder if it is missing. Lastly, I tried removing all local content for the games giving me issues and reinstalling them which when reinstalling COD:MW3 from disk causes a BSOD when I switch from Disk 1 to Disk 2. I have run out of ideas, and am hoping that the below files will assist someone in helping me.

*Update: While typing this post, my computer has done something new. An error message popped up stating that Windows Defender is turned off, and Microsoft Security Essentials is turned off. I just finished a full scan with MS Sec. Essentials before beginning this post or gathering the files, so it had to have shut off in the last 15 minutes while I was preparing this thread.*

*I also just discovered that VLC media player crashes immediately upon launch* I am leaning towards a graphics driver issue.

Code:

AODDriver2.sys              Thu Apr  5 15:23:37 2012 (4F7D6499)

(AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems. Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program. Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page) Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

GIGABYTE On/Off Charge driver - May cause BSOD on Win7/8 systems. Uninstall to test.

Code:

AppleCharger.sys            Mon Jan 10 15:57:29 2011 (4D2AD809)

   Information

Download

and install Revo Uninstaller.

• Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).

Based on the bugchecks, I would recommend you follow and complete the steps given below:

1. If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.

2. Uninstall your current antivirus software. It can be a cause of BSOD very often. Please remove it with its removal tool and use Microsoft Security Essentials in its place. Malwarebytes is a great combination with it. Go through this thread for more info.

3. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log

4. Run SFC /SCANNOW Command - System File Checker to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

5. Make scans with Kaspersky TDSskiller and ESET Online scanner.

6. Perform a Clean Start up, this will help avoid any problematic applications from bugging the system.

7. Use Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.

8. Use Crystal Disk Info to upload a screenshot of your Hard Drives (s). Test your Hard Drives (s) running a Hard Drive Diag.

9. Test and Diagnose RAM issues with RAM - Test with Memtest86+. Pay close attention to Part 3 of the tutorial "If you have errors" Take the test 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.

Update the ATI graphics driver from here: Download AMD Catalyst Drivers 13.9 Windows 7 - FileHippo.com (choose 64bit for yourself)

Code:

atikmpag.sys                Fri Mar 29 07:09:45 2013 (5154E9D9)
atikmdag.sys                Fri Mar 29 08:27:04 2013 (5154FBF8)

------------------------
To perform a clean install of a driver, follow this tutorial:

• How to Clean Left Over Driver Files with Driver Sweeper

Code:

Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Sun Sep 22 01:02:18.834 2013 (UTC + 6:00)
System Uptime: 0 days 0:01:22.334
BugCheck 116, {fffffa8010870010, fffff8800533dcf0, 0, 2}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+acf0 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Sun Sep 22 00:55:21.422 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:44.922
BugCheck 116, {fffffa800f3e7010, fffff88002f4acf0, 0, 2}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+acf0 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Sun Sep 22 00:43:39.832 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:57.332
BugCheck 116, {fffffa8010985360, fffff8800731fcf0, 0, 2}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+acf0 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Sun Sep 22 00:42:05.736 2013 (UTC + 6:00)
System Uptime: 0 days 20:26:08.236
BugCheck 116, {fffffa80127f54e0, fffff88002d6dcf0, 0, 2}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+acf0 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Try this on the Hitachi drive:
Try this too, download this: CrystalDiskInfo - Software - Crystal Dew World and open the program and follow the steps in this snip.

[img]https://www.sevenforums.com/attachmen...aldiskinfo.jpg[/img]

This may give you a little bit of time, but the drive should be replaced soon.

AMD Catalyst Control Center does cause BSOD often.

The CBS.log shows the following problems....

Code:

 Line 6531: 2013-09-23 18:39:44, Info                  CSI    00000322 [SR] Repairing 4 components
 Line 6532: 2013-09-23 18:39:44, Info                  CSI    00000323 [SR] Beginning Verify and Repair transaction
 Line 6535: 2013-09-23 18:39:45, Info                  CSI    00000325 [SR] Cannot repair member file [l:18{9}]"gulim.ttc" of Microsoft-Windows-Font-TrueType-Gulim, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 6538: 2013-09-23 18:39:45, Info                  CSI    00000327 [SR] Cannot repair member file [l:24{12}]"mingliub.ttc" of Microsoft-Windows-Font-TrueType-MingLiUB, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 6541: 2013-09-23 18:39:45, Info                  CSI    00000329 [SR] Cannot repair member file [l:24{12}]"msmincho.ttc" of Microsoft-Windows-Font-TrueType-MSMincho, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 6544: 2013-09-23 18:39:45, Info                  CSI    0000032b [SR] Cannot repair member file [l:24{12}]"photowiz.dll" of Microsoft-Windows-Photo-Printing-Wizard, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I can't think of any good reason why these would cause major problems - but I'll post a fix protocol when I can get to it (probably tomorrow, now)

Ooops! - this seems to have slipped through the net! - sorry for the delay.


I've uploaded a file - gf1aa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print theseinstructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, starttapping F8 - this should bring up the Advanced Boot Menu, at the top of whichshould be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\gf1aa
hit the enter key - if you get a 'NotFound' error try
DIR D:\gf1aa
or
DIR E:\gf1aa



The drive letter in use when you find the folder willneed to be substituted (for<drive>) into the followingcommand...



XCOPY<drive>:\gf1aa <drive>:\windows\winsxs /y /i /s /v /h



(e.g.XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time)andwhen the prompt returns, type
EXIT
and hit the Enter key to exit CommandPrompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in anElevated Command Prompt
then reboot and upload the new CBS.log file to your SkyDrive Public folder, andpost a new link