reztreib

New Member
Joined
May 15, 2013
Messages
8
Hello, I have a 4 month old HP Pavilion DV7 with windows 7 64 bit (latest updates installed 4/12/13). Today random/multiple audio streams started playing at startup, and after a few minutes the BSOD. Rebooted in safe mode, and ran malware which quarantined/removed what appears to be a virus. Rebooted in normal mode and audio streams/BSOD continue. Also tried system restore to 4/13/13 (earliest restore point), and audio streams/BSOD persist after reboot. Attached last two minidump files created by BSOD. Any help or advice would be appreciated to get rid of whatever is causing this would sure be appreciated.
 


Attachments

Solution
Uninstall both AMD/ATI items from Control Panel...Programs...Uninstall a program. Then continue to follow the instructions here:
Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Link Removed (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: Link Removed

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 "Un-install". Reboot for changes to take affect.
...
Malware removal comes first.
We can work BSOD problems - but we're not trained to remove malware, so it may not work.
Start by following the instructions here: Malware Removal Posting Instructions - Sysnative Forums

If the BSOD's continue after the malware removal, they'll refer you back to the BSOD experts.
Please provide this info then: Link Removed


Good luck!
 


Thanks John - I had a great experience with Corrine (sysnative.com) and everything was found/quarantined. I do still get the BSOD though after about a minute so have been referred back now.

I executed your instructions for BSOD and attached files. Because of the BSOD, this has been run in Windows Safe Mode with Networking. Thanks for any assistance to come, the forums have been fantastic.

(1) WF7 Diagnostic Tool.zip attached
(2) CPU-Z was able to download and run and attached screenshots. FYI, the app runs, but when you first open it there a CPU-Z Error screen that comes up that says "The error code 0x43C (1084) occurred during initialization. Do you want to display the error log file? If you select yes, here is the log file for the CPU-Z driver:
[bInitDriver] path = C:\Users\Biertzer\AppData\Local\Temp\
[bInitDriver] GetCurrentDirectory = C:\Users\Biertzer\Downloads\cpu-z_1.64-64bits-en
[bInitDriver] GetModuleFileName = C:\Users\Biertzer\Downloads\cpu-z_1.64-64bits-en\cpuz_x64.exe
[vGetOSVersion] m_iOSVersion = 2 (6.1)
[vGetOSVersion] m_bIsAMD64 = 0
[bInitDriver] m_hDriverMutex = C0
[bInitDriver] m_szPath_2 = C:\Users\Biertzer\AppData\Local\Temp\\cpuz136\
[bInitDriver] m_szFilename = cpuz136_x64.sys
[WinNT_bInstallDriver 10:32:13] szMachineName = BIERTZER-HP
[bExtract_SYS] Extract C:\Users\Biertzer\AppData\Local\Temp\\cpuz136\\cpuz136_x64.sys
[WinNT_bCreateService] szDestName = C:\Users\Biertzer\AppData\Local\Temp\\cpuz136\cpuz136_x64.sys
[WinNT_bStartService] StartService failed, error code = 1084
[bDeleteFile 10:32:13] DeleteFile returned = 1 (error = 0)
[bDeleteFile 10:32:13] RemoveDirectory C:\Users\Biertzer\AppData\Local\Temp\\cpuz136\ returned = 1 (error = 0)
[bInitDriver] bInitDriver returned 1084
[vCloseDriver 10:32:13] WaitForSingleObject error = 0
[WinNT_dwStopService] OpenService failed, errorcode = 1060
[WinNT_dwDeleteService] Openservice failed, errorcode = 1060
[vCloseDriver] CloseHandle(mutex) = 1

(3) RAMMon. I downloaded the link and when I run it I get the following RAMMon ERROR message: Unable to download DirectIo Driver. Unexpected Error.

(4) Also I mistakenly downloaded/ran RegCleanPro when I was on the CPU-Z download page (the ad download tricked me!), so attached those results as well anyway - I have not clicked on "fix issues" though.

Thanks
 


Attachments

  • CPU_Z.webp
    CPU_Z.webp
    125.9 KB · Views: 535
  • RCPscanlog.xml
    RCPscanlog.xml
    100.3 KB · Views: 1,318
  • W7F_17-05-2013 (2).zip
    W7F_17-05-2013 (2).zip
    832.1 KB · Views: 563
  • W7F_17-05-2013 (3).zip
    W7F_17-05-2013 (3).zip
    871.9 KB · Views: 782
  • W7F_17-05-2013.zip
    W7F_17-05-2013.zip
    435.2 KB · Views: 410
Last edited:
MSINFO32.nfo is missing some info (network adapter and drives). I don't know if it's a problem with the system or just with the report generated. Please do this:
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.

AMD OverDrive (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 Windows systems.
Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Link Removed (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: Link Removed

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 "Un-install". Reboot for changes to take affect.
Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Because this was an infection, please test your Norton/Symantec protection by doing this:
Anti-Virus Removal:
Please do the following:
- download a free anti-virus for testing purposes: Link Removed If using Windows 8, enable Windows Defender and the Windows Firewall instead.
- un-install the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN
- IMMEDIATELY install and update the free anti-virus (if using Win8, enable Windows Defender), then check to ensure that the Windows Firewall is turned on.
- perform a full system scan to ensure that no malware has snuck onto your system while the anti-virus was malfunctioning.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.
Once you've rule out the Norton, feel free to re-install it if you wish. Make sure to get the latest version from the Norton website.

If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions: Link Removed

Analysis:
The following is for informational purposes only.
Code:
[FONT=lucida console]**************************Fri May 17 12:05:46.910 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051713-29343-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:01:44.299[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+487ed )[/B]
BugCheck [B]1E, {ffffffffc0000005, fffffa80067693ef, 0, 7efa003c}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa80067693ef, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000000007efa003c, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  MMLoadDrv.exe
FAILURE_BUCKET_ID: [B]X64_0x1E_c0000005_R_nt!_??_::FNODOBFM::_string_+487ed[/B]
  BIOS Version                  F.06
  BIOS Release Date             04/30/2012
  Manufacturer                  Hewlett-Packard
  Product Name                  HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu May 16 18:30:08.151 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051613-24523-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:03:08.540[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!ObpCreateHandle+29a )[/B]
BugCheck [B]1E, {ffffffffc0000005, fffff80002fc0bba, 1, 18}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002fc0bba, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000018, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  MMLoadDrv.exe
FAILURE_BUCKET_ID: [B]X64_0x1E_c0000005_R_nt!ObpCreateHandle+29a[/B]
  BIOS Version                  F.06
  BIOS Release Date             04/30/2012
  Manufacturer                  Hewlett-Packard
  Product Name                  HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed May 15 22:45:24.220 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051613-26192-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:03:52.999[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!ObpCreateHandle+29a )[/B]
BugCheck [B]1E, {ffffffffc0000005, fffff80002fcebba, 1, 18}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002fcebba, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000018, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  MMLoadDrv.exe
FAILURE_BUCKET_ID: [B]X64_0x1E_c0000005_R_nt!ObpCreateHandle+29a[/B]
  BIOS Version                  F.06
  BIOS Release Date             04/30/2012
  Manufacturer                  Hewlett-Packard
  Product Name                  HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed May 15 22:24:10.310 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051513-27409-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:04:08.073[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+487ed )[/B]
BugCheck [B]1E, {ffffffffc0000005, fffffa80066f6610, 0, 7fffffa8000}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa80066f6610, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000007fffffa8000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  Smc.exe
FAILURE_BUCKET_ID: [B]X64_0x1E_c0000005_R_nt!_??_::FNODOBFM::_string_+487ed[/B]
  BIOS Version                  F.06
  BIOS Release Date             04/30/2012
  Manufacturer                  Hewlett-Packard
  Product Name                  HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 14 23:58:07.212 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\011413-23774-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]1 days 5:19:25.007[/B]
*** WARNING: Unable to verify timestamp for amd_xata.sys
*** ERROR: Module load completed but symbols could not be loaded for amd_xata.sys
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
Probably caused by :[B]amd_xata.sys ( amd_xata+7f59 )[/B]
BugCheck [B]1000009F, {4, 258, fffffa8004ec9b50, fffff80000ba2740}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8004ec9b50, The thread currently holding on to the Pnp lock.
Arg4: fffff80000ba2740, nt!TRIAGE_9F_PNP on Win7
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x9F_4_amd_xata+7f59[/B]
  BIOS Version                  F.06
  BIOS Release Date             04/30/2012
  Manufacturer                  Hewlett-Packard
  Product Name                  HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[FONT=lucida console]**************************Fri May 17 12:05:46.910 2013 (UTC - 4:00)**************************
amdiox64.sys                Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdsata.sys                 Thu Mar 18 20:45:17 2010 (4BA2C91D)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
clwvd.sys                   Tue Jul 27 21:13:47 2010 (4C4F844B)
[B]AODDriver2.sys              Tue Sep  6 03:11:44 2011 (4E65C7B0)[/B]
Rt64win7.sys                Tue Sep 27 10:50:33 2011 (4E81E2B9)
Sftvollh.sys                Fri Sep 30 12:42:46 2011 (4E85F186)
Sftplaylh.sys               Fri Sep 30 12:43:05 2011 (4E85F199)
Sftfslh.sys                 Fri Sep 30 12:43:06 2011 (4E85F19A)
SynTP.sys                   Thu Oct 13 22:34:52 2011 (4E979FCC)
amdhub30.sys                Tue Oct 25 21:16:23 2011 (4EA75F67)
amdxhc.sys                  Tue Oct 25 21:16:25 2011 (4EA75F69)
SRTSPX64.SYS                Tue Nov 15 17:30:55 2011 (4EC2E81F)
AtihdW76.sys                Tue Dec  6 04:14:25 2011 (4EDDDCF1)
amd_sata.sys                Mon Dec 12 15:52:00 2011 (4EE66970)
amd_xata.sys                Mon Dec 12 15:52:03 2011 (4EE66973)
usbfilter.sys               Wed Dec 14 02:44:02 2011 (4EE853C2)
appexDrv.sys                Wed Dec 28 20:36:14 2011 (4EFBC40E)
athrx.sys                   Tue Jan 10 23:47:50 2012 (4F0D1476)
amdkmpfd.sys                Tue Jan 17 22:01:36 2012 (4F163610)
atikmpag.sys                Thu Jan 26 17:52:42 2012 (4F21D93A)
atikmdag.sys                Thu Jan 26 18:30:33 2012 (4F21E219)
RtsP2Stor.sys               Wed Jun 13 06:08:36 2012 (4FD866A4)
Teefer.sys                  Tue Jul 17 08:58:52 2012 (5005618C)
SYMNETS.SYS                 Fri Jul 20 22:07:07 2012 (500A0ECB)
SYMDS64.SYS                 Mon Jul 23 18:58:38 2012 (500DD71E)
Ironx64.SYS                 Mon Jul 23 20:34:50 2012 (500DEDAA)
stwrt64.sys                 Tue Jul 24 04:05:57 2012 (500E5765)
eeCtrl64.sys                Tue Jul 31 19:36:51 2012 (50186C13)
ccSetx64.sys                Thu Aug 16 17:18:11 2012 (502D6393)
SYMEVENT64x86.SYS           Wed Aug 22 01:33:18 2012 (50346F1E)
IDSvia64.sys                Tue Aug 28 22:48:40 2012 (503D8308)
hpdskflt.sys                Mon Sep 24 11:31:14 2012 (50607CC2)
Accelerometer.sys           Mon Sep 24 11:31:45 2012 (50607CE1)
SYMEFA64.SYS                Wed Oct  3 15:00:06 2012 (506C8B36)
SysPlant.sys                Sat Nov  3 09:53:53 2012 (509521F1)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu May 16 18:30:08.151 2013 (UTC - 4:00)**************************
Sftredirlh.sys              Fri Sep 30 12:43:14 2011 (4E85F1A2)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed May 15 22:24:10.310 2013 (UTC - 4:00)**************************
BHDrvx64.sys                Wed Apr 10 01:39:03 2013 (5164FAF7)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 14 23:58:07.212 2013 (UTC - 4:00)**************************
SYMEVENT64x86.SYS           Wed May  4 23:16:30 2011 (4DC2168E)
Accelerometer.sys           Fri May 13 14:47:02 2011 (4DCD7CA6)
hpdskflt.sys                Fri May 13 14:47:02 2011 (4DCD7CA6)
SYMDS64.SYS                 Mon May 16 18:15:03 2011 (4DD1A1E7)
SYMNETS.SYS                 Wed Jul 20 22:24:22 2011 (4E278DD6)
SYMEFA64.SYS                Thu Jul 21 20:22:02 2011 (4E28C2AA)
Ironx64.SYS                 Fri Jul 22 21:24:42 2011 (4E2A22DA)
SRTSP64.SYS                 Tue Aug  2 16:29:54 2011 (4E385E42)
SRTSPX64.SYS                Tue Aug  2 16:30:01 2011 (4E385E49)
ccSetx64.sys                Mon Aug  8 17:47:34 2011 (4E405976)
EraserUtilRebootDrv.sys     Tue Jul 31 19:36:50 2012 (50186C12)
EX64.SYS                    Wed Sep  5 18:31:45 2012 (5047D2D1)
ENG64.SYS                   Wed Sep  5 18:33:39 2012 (5047D343)
BHDrvx64.sys                Fri Oct 19 00:40:41 2012 (5080D9C9)
[/FONT]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Teefer.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
 


Last edited:
Attached is the zipped MSINFO32 file TEST.NFO (I needed to use your run as administrator to get the full report)

Link Removed

Quick question, for the AMD/ATI Video stuff, I found 2 programs called AMD Catalyst Manager (published by AMD) and AMD Quick Stream (published by AppEx Networks). Do I remove both or just the one by AMD? Also can you clarify how to tell if it is overclocking and how to remove it if it is happening. Thx
 


Uninstall both AMD/ATI items from Control Panel...Programs...Uninstall a program. Then continue to follow the instructions here:
Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Link Removed (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: Link Removed

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 "Un-install". Reboot for changes to take affect.
Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

As this seems to be a HP Notebook, there's just not any way to easily overclock it. The overclock statement is a part of "canned" speech that I use just in case I haven't noticed overclocking in any of the reports. I re-checked and don't see any sign of overclocking on your system.

There are problems with these devices:
Microsoft Virtual WiFi Miniport Adapter {5D624F94-8850-40C3-A3FA-A4FD2080BAF3}\VWIFIMP\5&13D27D04&0&01 This device is disabled.
Security Processor Loader Driver ROOT\LEGACY_SPLDR\0000 This device is not present, is not working properly, or does not have all its drivers installed.
The first device is disabled. Is this deliberate (did you do it)? If so, why?
Also, the Security Processor Loader Driver issue is typically seen on systems that have damage from virus infections. I'd suggest that you run a couple of the free scans here to see if the system is still infected: Link Removed If it is, please post back so we can get the virus' dealt with first.
 


Solution
No Virus, and the BSOD has not come back so far. Thanks for your help, this forum has been a lifesaver.
 


Back
Top