Solved Random BSODs after running AdwCleaner

[PeterG]

After picking up the "search.conduit" PUP, I ran AdwCleaner to get rid of it, and have been getting random BSODs ever since.

 

[koolkat77]

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\SF_08-02-2014 (1)\SF_08-02-2014\020814-7628-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`03262000 PsLoadedModuleList = 0xfffff800`034a6670
Debug session time: Sat Feb  8 22:45:25.632 2014 (UTC + 6:00)
System Uptime: 0 days 0:02:18.459
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a00fffc000, 0, fffff880081adc02, 0}

*** WARNING: Unable to verify timestamp for [COLOR="Blue"]acedrv09.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR="blue"]acedrv09.sys[/COLOR]
*** WARNING: Unable to verify timestamp for [COLOR="Red"]BHDrvx64.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR="Red"]BHDrvx64.sys[/COLOR]

Could not read faulting driver name
Probably caused by : acedrv09.sys ( acedrv09+4c02 )

Followup: MachineOwner
---------

Norton is a known cause of BSOD's. Please remove it and use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Reduce items at start-up: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Run a System file check (SFC): http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

acedrv09.sys driver belongs to the process Filter Driver ProtectDisc belonging to the software acedrv by Protect Software GmbH.

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Run Disk Check on your Hard Drive(s): http://www.sevenforums.com/tutorials/433-disk-check.html

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[PeterG]

Solved

Thanks for pointing out "acedrv09.sys"....After some more digging, I realized that I unsuccessfully tried to install a version of Magix Music Maker in compatibility mode. The driver "acedrv09.sys" was added into my system files and that was causing the BSODs.