AMD OverDrive
Code:
AODDriver2.sys Thu Apr 5 15:23:37 2012 (4F7D6499)
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known [COLOR=RED]BSOD[/COLOR] issues in Win7
(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
If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item. Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section. Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect. Sometimes the driver remains and continues to cause BSOD's.
To remove a stubborn software:
Msinfo32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter > Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post. Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).
If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "msinfo32 /nfo %USERPROFILE%\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back. Then zip up the .nfo file and upload/attach the .zip file with your next post.
systeminfo:
Please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "systeminfo.exe >%USERPROFILE%\Desktop\systeminfo.txt" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the syteminfo.txt file. If you have difficulties with making this work, please post back. Then zip up the .txt file and upload/attach the .zip file with your next post.
Scan your system with the following:
Microsoft Safety Scanner -
Microsoft Safety Scanner - System Requirements
Kaspersky TDSSKiller -
How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)
ESET online scanner -
One-time virus scanner free with ESET online scanner
Hard Drive/Storage
Post disk summary using CrystalDiskInfo software:
CrystalDiskInfo Standard Edition
- :info: For how to upload a screenshot or file, read here
Make a hard drive test from the hard drive manufacturers website:
Hard Drive Diagnostic Procedure
For errors on your Hard drive(s):
How to Run Disk Check in Windows 7
System Temperature
Ensure that there are no heat issues, For monitoring heat of the system use
Speccy or
HWMonitor
Please disable and uninstall all logitech software for the time being.
LVUSBS64.sys Sat Jul 26 21:06:36 2008 (488B3D7C)
Logitech Camera driver
Driver Reference Table - LVUSBS64.sys
lv302a64.sys Fri May 1 04:41:07 2009 (49FA2903)[/B][/COLOR]
Logitech Camera driver
Driver Reference Table - lv302a64.sys
lvrs64.sys Fri May 1 04:43:25 2009 (49FA298D)
Logitech Camera driver
http://www.carrona.org/drivers/driver.php?id=vrs64.sys
LV302V64.SYS Fri May 1 04:43:26 2009 (49FA298E)
Logitech Camera driver
Driver Reference Table - LV302V64.SYS
SFC /scannow to check windows for corruption:
How to Repair Windows 7 System Files with System File Checker
1. Click Start
2. In the search box, type
Command Prompt
3. In the list that appears, right-click on cmd.exe and choose
Run as administrator
4. In the command window that opens, type
sfc /scannow
and hit enter.
Memtest86+
Run Memtest86+ for at least 8-10 passes. It may take up to 20 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.
How to Test and Diagnose RAM Issues with Memtest86+
Note
Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.
Tip
Do this test overnight.
BSOD BUGCHECK SUMMARY
Code:
[FONT="Lucida Console"]Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sun Jun 16 12:57:48.005 2013 (UTC + 6:00)
System Uptime: 2 days 4:43:01.348
BugCheck A, {ffffffffffffff90, 0, 0, fffff800032f200d}
Probably caused by : hardware ( win32k!SURFACE::bDeleteSurface+3c8 )
BUGCHECK_STR: 0xA
PROCESS_NAME: lightroom.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri Jun 14 08:13:32.245 2013 (UTC + 6:00)
System Uptime: 0 days 1:25:18.587
BugCheck E3, {fffffa8010aad3f0, fffffa800a5a0440, 0, 2}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+19e63 )
BUGCHECK_STR: 0xE3
PROCESS_NAME: svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri Jun 14 06:47:32.949 2013 (UTC + 6:00)
System Uptime: 0 days 1:23:27.291
BugCheck C5, {fffffa80747d4178, 2, 1, fffff800033bb147}
Probably caused by : afd.sys ( afd+49cb1 )
BUGCHECK_STR: 0xC5_2
PROCESS_NAME: League of Lege
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]
