Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

McAfee Firewall won't stay turned on


  • Please log in to reply
7 replies to this topic

#1 Jeff231

Jeff231

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:02:20 AM

Posted 02 February 2012 - 10:24 PM

Hello,

My McAfee firewall won't stay turned on. When I click on it turns itself back off after a second or so. I'm pretty sure I have a virus although my computer is running normally. I have scanned with Malwarebytes and McAfee and nothing turns up. What are the next steps I should take in order to get my firewall back to working action?

Thank you.

BC AdBot (Login to Remove)

 


#2 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,416 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:20 AM

Posted 02 February 2012 - 11:14 PM

Hello and welcome. I moved this to the Am I Infected forum.
What is your Operating System?

Lets run one more scan and see.
I'd like us to scan your machine with ESET OnlineScan
  • Hold down Control and click on the following link to open ESET OnlineScan in a new window.
    ESET OnlineScan
  • Click the Posted Image button.
  • For alternate browsers only: (Microsoft Internet Explorer users can skip these steps)
    • Click on Posted Image to download the ESET Smart Installer. Save it to your desktop.
    • Double click on the Posted Image icon on your desktop.
  • Check Posted Image
  • Click the Posted Image button.
  • Accept any security warnings from your browser.
  • Under scan settings, check Posted Image and check Remove found threats
  • Click Advanced settings and select the following:
    • Scan potentially unwanted applications
    • Scan for potentially unsafe applications
    • Enable Anti-Stealth technology
  • ESET will then download updates for itself, install itself, and begin scanning your computer. Please be patient as this can take some time.
  • When the scan completes, push Posted Image
  • Push Posted Image, and save the file to your desktop using a unique name, such as ESETScan. Include the contents of this report in your next reply.
  • Push the Posted Image button.
  • Push Posted Image


NOTE: In some instances if no malware is found there will be no log produced.


Please download Farbar Service Scanner and run it on the computer with the issue.
  • Make sure the following options are checked:
    • Internet Services
    • Windows Firewall
    • System Restore
    • Security Center
    • Windows Update
  • Press "Scan".
  • It will create a log (FSS.txt) in the same directory the tool is run.
  • Please copy and paste the log to your reply.

How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#3 Jeff231

Jeff231
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:02:20 AM

Posted 03 February 2012 - 04:59 PM

I'm running Windows 7. Thank you for your help. Here are the logs:

ESETScan:


C:\Program Files (x86)\Application Updater\ApplicationUpdater.exe probably a variant of Win32/Adware.Toolbar.Dealio application cleaned by deleting - quarantined
C:\Program Files (x86)\Search Settings\SearchSettings.dll Win32/Adware.Toolbar.Dealio application cleaned by deleting - quarantined
C:\Program Files (x86)\Search Settings\SearchSettings.exe Win32/Adware.Toolbar.Dealio application cleaned by deleting - quarantined
C:\Program Files (x86)\Search Settings\SearchSettingsRes409.dll Win32/Adware.Toolbar.Dealio application cleaned by deleting - quarantined
C:\Windows\Installer\1c35e88.msi Win32/Adware.Toolbar.Dealio application deleted - quarantined


FSS:

Farbar Service Scanner Version: 02-02-2012
Ran by Jeff (administrator) on 03-02-2012 at 13:57:15
Microsoft Windows 7 Home Premium (X64)
Boot Mode: Normal
****************************************************************

Internet Services:
============

Connection Status:
==============
Localhost is accessible.
LAN connected.
Google IP is accessible.
Yahoo IP is accessible.


Windows Firewall:
=============
mpsdrv Service is not running. Checking service configuration:
The start type of mpsdrv service is OK.
The ImagePath of mpsdrv service is OK.

MpsSvc Service is not running. Checking service configuration:
Checking Start type: Attention! Unable to open MpsSvc registry key. The service key does not exist.
Checking ImagePath: Attention! Unable to open MpsSvc registry key. The service key does not exist.
Checking ServiceDll: Attention! Unable to open MpsSvc registry key. The service key does not exist.

bfe Service is not running. Checking service configuration:
Checking Start type: Attention! Unable to open bfe registry key. The service key does not exist.
Checking ImagePath: Attention! Unable to open bfe registry key. The service key does not exist.
Checking ServiceDll: Attention! Unable to open bfe registry key. The service key does not exist.


Firewall Disabled Policy:
==================


System Restore:
============

System Restore Disabled Policy:
========================


Security Center:
============
wscsvc Service is not running. Checking service configuration:
Checking Start type: Attention! Unable to open wscsvc registry key. The service key does not exist.
Checking ImagePath: Attention! Unable to open wscsvc registry key. The service key does not exist.
Checking ServiceDll: Attention! Unable to open wscsvc registry key. The service key does not exist.


Windows Update:
===========

File Check:
========
C:\Windows\System32\nsisvc.dll => MD5 is legit
C:\Windows\System32\drivers\nsiproxy.sys => MD5 is legit
C:\Windows\System32\dhcpcore.dll => MD5 is legit
C:\Windows\System32\drivers\afd.sys => MD5 is legit
C:\Windows\System32\drivers\tdx.sys => MD5 is legit
C:\Windows\System32\Drivers\tcpip.sys
[2011-08-25 13:47] - [2011-06-20 22:27] - 1896832 ____A (Microsoft Corporation) B9D87C7707F058AC652A398CD28DE14B

C:\Windows\System32\dnsrslvr.dll => MD5 is legit
C:\Windows\System32\mpssvc.dll
[2009-07-13 16:09] - [2009-07-13 17:41] - 0824832 ____A (Microsoft Corporation) AECAB449567D1846DAD63ECE49E893E3

C:\Windows\System32\bfe.dll
[2009-07-13 16:09] - [2009-07-13 17:40] - 0703488 ____A (Microsoft Corporation) 4992C609A6315671463E30F6512BC022

C:\Windows\System32\drivers\mpsdrv.sys => MD5 is legit
C:\Windows\System32\SDRSVC.dll
[2009-07-13 15:36] - [2009-07-13 17:41] - 0170496 ____A (Microsoft Corporation) 765A27C3279CE11D14CB9E4F5869FCA5

C:\Windows\System32\vssvc.exe
[2009-07-13 15:39] - [2009-07-13 17:39] - 1598976 ____A (Microsoft Corporation) 787898BF9FB6D7BD87A36E2D95C899BA

C:\Windows\System32\wscsvc.dll => MD5 is legit
C:\Windows\System32\wbem\WMIsvc.dll => MD5 is legit
C:\Windows\System32\wuaueng.dll
[2009-07-13 16:36] - [2009-07-13 17:41] - 2418176 ____A (Microsoft Corporation) 38340204A2D0228F1E87740FC5E554A7

C:\Windows\System32\qmgr.dll => MD5 is legit
C:\Windows\System32\es.dll => MD5 is legit
C:\Windows\System32\cryptsvc.dll => MD5 is legit
C:\Windows\System32\svchost.exe => MD5 is legit
C:\Windows\System32\rpcss.dll => MD5 is legit


**** End of log ****

#4 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,416 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:20 AM

Posted 03 February 2012 - 07:34 PM

Ok there are system files missing. So we need to see if yhere is a rootkit problem.

Please download TDSSKiller.zip and and extract it.
  • Run TDSSKiller.exe.
  • Click Start scan.
  • When it is finished the utility outputs a list of detected objects with description.
    The utility automatically selects an action (Cure or Delete) for malicious objects.
    The utility prompts the user to select an action to apply to suspicious objects (Skip, by default). Let the options as it is and click Continue
  • Let reboot if needed and tell me if the tool needed a reboot.
  • Click on Report and post the contents of the text file that will open.

    Note: By default, the utility outputs the log into system disk (it is usually the disk with installed operating system, C:\) root folder. The Log have a name like: TDSSKiller.Version_Date_Time_log.txt.



If TDSSKiller does not run, try renaming it. To do this, right-click on TDSSKiller.exe, select Rename and give it a random name with the .com file extension (i.e. 123abc.com). If you do not see the file extension, please refer to these[/color] instructions. In some cases it may be necessary to redownload TDSSKiller and randomly rename it before downloading and saving to the computer.



Download [color=red]aswMBR
to your desktop.
Double click the aswMBR.exe to run it.
Click the "Scan" button to start scan:
Posted Image

On completion of the scan click "Save log", save it to your desktop and post in your next reply:
Posted Image

NOTE. aswMBR will create MBR.dat file on your desktop. This is a copy of your MBR. Do NOT delete it.

Edited by boopme, 03 February 2012 - 07:34 PM.

How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#5 Jeff231

Jeff231
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:02:20 AM

Posted 04 February 2012 - 08:05 PM

Thank you for your reply. Here are the logs:

TDS:
16:59:57.0920 5708 TDSS rootkit removing tool 2.7.9.0 Feb 1 2012 09:28:49
16:59:58.0466 5708 ============================================================
16:59:58.0466 5708 Current date / time: 2012/02/04 16:59:58.0466
16:59:58.0466 5708 SystemInfo:
16:59:58.0466 5708
16:59:58.0466 5708 OS Version: 6.1.7600 ServicePack: 0.0
16:59:58.0466 5708 Product type: Workstation
16:59:58.0466 5708 ComputerName: JEFF-XPS
16:59:58.0466 5708 UserName: Jeff
16:59:58.0466 5708 Windows directory: C:\Windows
16:59:58.0466 5708 System windows directory: C:\Windows
16:59:58.0466 5708 Running under WOW64
16:59:58.0466 5708 Processor architecture: Intel x64
16:59:58.0466 5708 Number of processors: 8
16:59:58.0466 5708 Page size: 0x1000
16:59:58.0466 5708 Boot type: Normal boot
16:59:58.0466 5708 ============================================================
16:59:59.0043 5708 Drive \Device\Harddisk0\DR0 - Size: 0x4A85D56000 (298.09 Gb), SectorSize: 0x200, Cylinders: 0x9801, SectorsPerTrack: 0x3F, TracksPerCylinder: 0xFF, Type 'K0', Flags 0x00000040
16:59:59.0043 5708 \Device\Harddisk0\DR0:
16:59:59.0043 5708 MBR used
16:59:59.0043 5708 \Device\Harddisk0\DR0\Partition0: MBR, Type 0x7, StartLBA 0x139C5, BlocksNum 0x1D4C000
16:59:59.0043 5708 \Device\Harddisk0\DR0\Partition1: MBR, Type 0x7, StartLBA 0x1D5F9C5, BlocksNum 0x236CE8EB
16:59:59.0059 5708 Initialize success
16:59:59.0059 5708 ============================================================
17:00:30.0091 4296 ============================================================
17:00:30.0091 4296 Scan started
17:00:30.0091 4296 Mode: Manual;
17:00:30.0091 4296 ============================================================
17:00:30.0793 4296 1394ohci (1b00662092f9f9568b995902f0cc40d5) C:\Windows\system32\DRIVERS\1394ohci.sys
17:00:30.0793 4296 1394ohci - ok
17:00:30.0840 4296 ACPI (6f11e88748cdefd2f76aa215f97ddfe5) C:\Windows\system32\DRIVERS\ACPI.sys
17:00:30.0840 4296 ACPI - ok
17:00:30.0855 4296 AcpiPmi (63b05a0420ce4bf0e4af6dcc7cada254) C:\Windows\system32\DRIVERS\acpipmi.sys
17:00:30.0855 4296 AcpiPmi - ok
17:00:30.0902 4296 adfs (2f0683fd2df1d92e891caca14b45a8c1) C:\Windows\system32\drivers\adfs.sys
17:00:30.0933 4296 adfs - ok
17:00:31.0011 4296 adp94xx (2f6b34b83843f0c5118b63ac634f5bf4) C:\Windows\system32\DRIVERS\adp94xx.sys
17:00:31.0043 4296 adp94xx - ok
17:00:31.0074 4296 adpahci (597f78224ee9224ea1a13d6350ced962) C:\Windows\system32\DRIVERS\adpahci.sys
17:00:31.0074 4296 adpahci - ok
17:00:31.0105 4296 adpu320 (e109549c90f62fb570b9540c4b148e54) C:\Windows\system32\DRIVERS\adpu320.sys
17:00:31.0105 4296 adpu320 - ok
17:00:31.0152 4296 AFD (6ef20ddf3172e97d69f596fb90602f29) C:\Windows\system32\drivers\afd.sys
17:00:31.0152 4296 AFD - ok
17:00:31.0183 4296 agp440 (608c14dba7299d8cb6ed035a68a15799) C:\Windows\system32\DRIVERS\agp440.sys
17:00:31.0199 4296 agp440 - ok
17:00:31.0245 4296 aliide (5812713a477a3ad7363c7438ca2ee038) C:\Windows\system32\DRIVERS\aliide.sys
17:00:31.0261 4296 aliide - ok
17:00:31.0292 4296 amdide (1ff8b4431c353ce385c875f194924c0c) C:\Windows\system32\DRIVERS\amdide.sys
17:00:31.0292 4296 amdide - ok
17:00:31.0308 4296 AmdK8 (7024f087cff1833a806193ef9d22cda9) C:\Windows\system32\DRIVERS\amdk8.sys
17:00:31.0308 4296 AmdK8 - ok
17:00:31.0557 4296 amdkmdag (446a1aad34191665a8df6092bd8eb5a8) C:\Windows\system32\DRIVERS\atikmdag.sys
17:00:31.0838 4296 amdkmdag - ok
17:00:31.0994 4296 amdkmdap (f8f8a908fdb005a65ddf7238c814eea5) C:\Windows\system32\DRIVERS\atikmpag.sys
17:00:32.0041 4296 amdkmdap - ok
17:00:32.0103 4296 AmdPPM (1e56388b3fe0d031c44144eb8c4d6217) C:\Windows\system32\DRIVERS\amdppm.sys
17:00:32.0103 4296 AmdPPM - ok
17:00:32.0166 4296 amdsata (7a4b413614c055935567cf88a9734d38) C:\Windows\system32\DRIVERS\amdsata.sys
17:00:32.0181 4296 amdsata - ok
17:00:32.0228 4296 amdsbs (f67f933e79241ed32ff46a4f29b5120b) C:\Windows\system32\DRIVERS\amdsbs.sys
17:00:32.0244 4296 amdsbs - ok
17:00:32.0275 4296 amdxata (b4ad0cacbab298671dd6f6ef7e20679d) C:\Windows\system32\DRIVERS\amdxata.sys
17:00:32.0275 4296 amdxata - ok
17:00:32.0306 4296 AppID (42fd751b27fa0e9c69bb39f39e409594) C:\Windows\system32\drivers\appid.sys
17:00:32.0306 4296 AppID - ok
17:00:32.0369 4296 arc (c484f8ceb1717c540242531db7845c4e) C:\Windows\system32\DRIVERS\arc.sys
17:00:32.0384 4296 arc - ok
17:00:32.0400 4296 arcsas (019af6924aefe7839f61c830227fe79c) C:\Windows\system32\DRIVERS\arcsas.sys
17:00:32.0400 4296 arcsas - ok
17:00:32.0478 4296 AsyncMac (769765ce2cc62867468cea93969b2242) C:\Windows\system32\DRIVERS\asyncmac.sys
17:00:32.0478 4296 AsyncMac - ok
17:00:32.0509 4296 atapi (02062c0b390b7729edc9e69c680a6f3c) C:\Windows\system32\DRIVERS\atapi.sys
17:00:32.0509 4296 atapi - ok
17:00:32.0571 4296 AtiHDAudioService (4bf5bca6e2608cd8a00bc4a6673a9f47) C:\Windows\system32\drivers\AtihdW76.sys
17:00:32.0618 4296 AtiHDAudioService - ok
17:00:32.0665 4296 AtiHdmiService (3b9014fb7ce9e20fd726321c7db7d8b0) C:\Windows\system32\drivers\AtiHdmi.sys
17:00:32.0696 4296 AtiHdmiService - ok
17:00:32.0915 4296 atikmdag (446a1aad34191665a8df6092bd8eb5a8) C:\Windows\system32\DRIVERS\atikmdag.sys
17:00:32.0961 4296 atikmdag - ok
17:00:33.0024 4296 b06bdrv (3e5b191307609f7514148c6832bb0842) C:\Windows\system32\DRIVERS\bxvbda.sys
17:00:33.0024 4296 b06bdrv - ok
17:00:33.0055 4296 b57nd60a (b5ace6968304a3900eeb1ebfd9622df2) C:\Windows\system32\DRIVERS\b57nd60a.sys
17:00:33.0055 4296 b57nd60a - ok
17:00:33.0086 4296 Beep (16a47ce2decc9b099349a5f840654746) C:\Windows\system32\drivers\Beep.sys
17:00:33.0086 4296 Beep - ok
17:00:33.0117 4296 blbdrive (61583ee3c3a17003c4acd0475646b4d3) C:\Windows\system32\DRIVERS\blbdrive.sys
17:00:33.0117 4296 blbdrive - ok
17:00:33.0195 4296 bowser (19d20159708e152267e53b66677a4995) C:\Windows\system32\DRIVERS\bowser.sys
17:00:33.0195 4296 bowser - ok
17:00:33.0211 4296 BrFiltLo (f09eee9edc320b5e1501f749fde686c8) C:\Windows\system32\DRIVERS\BrFiltLo.sys
17:00:33.0211 4296 BrFiltLo - ok
17:00:33.0227 4296 BrFiltUp (b114d3098e9bdb8bea8b053685831be6) C:\Windows\system32\DRIVERS\BrFiltUp.sys
17:00:33.0242 4296 BrFiltUp - ok
17:00:33.0258 4296 Brserid (43bea8d483bf1870f018e2d02e06a5bd) C:\Windows\System32\Drivers\Brserid.sys
17:00:33.0273 4296 Brserid - ok
17:00:33.0289 4296 BrSerWdm (a6eca2151b08a09caceca35c07f05b42) C:\Windows\System32\Drivers\BrSerWdm.sys
17:00:33.0289 4296 BrSerWdm - ok
17:00:33.0305 4296 BrUsbMdm (b79968002c277e869cf38bd22cd61524) C:\Windows\System32\Drivers\BrUsbMdm.sys
17:00:33.0305 4296 BrUsbMdm - ok
17:00:33.0336 4296 BrUsbSer (a87528880231c54e75ea7a44943b38bf) C:\Windows\System32\Drivers\BrUsbSer.sys
17:00:33.0336 4296 BrUsbSer - ok
17:00:33.0351 4296 BthEnum (cf98190a94f62e405c8cb255018b2315) C:\Windows\system32\DRIVERS\BthEnum.sys
17:00:33.0367 4296 BthEnum - ok
17:00:33.0383 4296 BTHMODEM (9da669f11d1f894ab4eb69bf546a42e8) C:\Windows\system32\DRIVERS\bthmodem.sys
17:00:33.0383 4296 BTHMODEM - ok
17:00:33.0414 4296 BthPan (02dd601b708dd0667e1331fa8518e9ff) C:\Windows\system32\DRIVERS\bthpan.sys
17:00:33.0414 4296 BthPan - ok
17:00:33.0445 4296 BTHPORT (a51fa9d0e85d5adabef72e67f386309c) C:\Windows\system32\Drivers\BTHport.sys
17:00:33.0461 4296 BTHPORT - ok
17:00:33.0492 4296 BTHUSB (f740b9a16b2c06700f2130e19986bf3b) C:\Windows\system32\Drivers\BTHUSB.sys
17:00:33.0492 4296 BTHUSB - ok
17:00:33.0539 4296 btusbflt (2641a3fe3d7b0646308f33b67f3b5300) C:\Windows\system32\drivers\btusbflt.sys
17:00:33.0585 4296 btusbflt - ok
17:00:33.0632 4296 btwaudio (6bcfdc2b5b7f66d484486d4bd4b39a6b) C:\Windows\system32\drivers\btwaudio.sys
17:00:33.0679 4296 btwaudio - ok
17:00:33.0710 4296 btwavdt (82dc8b7c626e526681c1bebed2bc3ff9) C:\Windows\system32\drivers\btwavdt.sys
17:00:33.0741 4296 btwavdt - ok
17:00:33.0773 4296 btwl2cap (6149301dc3f81d6f9667a3fbac410975) C:\Windows\system32\DRIVERS\btwl2cap.sys
17:00:33.0819 4296 btwl2cap - ok
17:00:33.0866 4296 btwrchid (28e105ad3b79f440bf94780f507bf66a) C:\Windows\system32\DRIVERS\btwrchid.sys
17:00:33.0897 4296 btwrchid - ok
17:00:33.0960 4296 BVRPMPR5a64 (9887ca12f407d7fbc7f48f3678f5f0b6) C:\Windows\system32\drivers\BVRPMPR5a64.SYS
17:00:33.0991 4296 BVRPMPR5a64 - ok
17:00:34.0022 4296 cdfs (b8bd2bb284668c84865658c77574381a) C:\Windows\system32\DRIVERS\cdfs.sys
17:00:34.0022 4296 cdfs - ok
17:00:34.0069 4296 cdrom (83d2d75e1efb81b3450c18131443f7db) C:\Windows\system32\DRIVERS\cdrom.sys
17:00:34.0069 4296 cdrom - ok
17:00:34.0131 4296 cfwids (ed0263b2eb24f0f4e3898036fa1d28a1) C:\Windows\system32\drivers\cfwids.sys
17:00:34.0178 4296 cfwids - ok
17:00:34.0209 4296 circlass (d7cd5c4e1b71fa62050515314cfb52cf) C:\Windows\system32\DRIVERS\circlass.sys
17:00:34.0209 4296 circlass - ok
17:00:34.0256 4296 CLFS (fe1ec06f2253f691fe36217c592a0206) C:\Windows\system32\CLFS.sys
17:00:34.0256 4296 CLFS - ok
17:00:34.0303 4296 CmBatt (0840155d0bddf1190f84a663c284bd33) C:\Windows\system32\DRIVERS\CmBatt.sys
17:00:34.0303 4296 CmBatt - ok
17:00:34.0319 4296 cmdide (e19d3f095812725d88f9001985b94edd) C:\Windows\system32\DRIVERS\cmdide.sys
17:00:34.0334 4296 cmdide - ok
17:00:34.0350 4296 CNG (f95fd4cb7da00ba2a63ce9f6b5c053e1) C:\Windows\system32\Drivers\cng.sys
17:00:34.0365 4296 CNG - ok
17:00:34.0381 4296 Compbatt (102de219c3f61415f964c88e9085ad14) C:\Windows\system32\DRIVERS\compbatt.sys
17:00:34.0381 4296 Compbatt - ok
17:00:34.0428 4296 CompositeBus (f26b3a86f6fa87ca360b879581ab4123) C:\Windows\system32\DRIVERS\CompositeBus.sys
17:00:34.0428 4296 CompositeBus - ok
17:00:34.0506 4296 cpuz133 (95c88d25e211a4d52a82c53e5d93e634) C:\Windows\system32\drivers\cpuz133_x64.sys
17:00:34.0553 4296 cpuz133 - ok
17:00:34.0568 4296 crcdisk (1c827878a998c18847245fe1f34ee597) C:\Windows\system32\DRIVERS\crcdisk.sys
17:00:34.0584 4296 crcdisk - ok
17:00:34.0646 4296 CtClsFlt (ed5cf92396a62f4c15110dcdb5e854d9) C:\Windows\system32\DRIVERS\CtClsFlt.sys
17:00:34.0693 4296 CtClsFlt - ok
17:00:34.0740 4296 ctxusbm (ba8e5b2291c01ef71ca80e25f0c79d55) C:\Windows\system32\DRIVERS\ctxusbm.sys
17:00:34.0787 4296 ctxusbm - ok
17:00:34.0849 4296 dc3d (db0459afd124ce5ccb649e33f95d715f) C:\Windows\system32\DRIVERS\dc3d.sys
17:00:34.0896 4296 dc3d - ok
17:00:34.0958 4296 DfsC (9c253ce7311ca60fc11c774692a13208) C:\Windows\system32\Drivers\dfsc.sys
17:00:34.0958 4296 DfsC - ok
17:00:34.0989 4296 discache (13096b05847ec78f0977f2c0f79e9ab3) C:\Windows\system32\drivers\discache.sys
17:00:34.0989 4296 discache - ok
17:00:35.0021 4296 Disk (9819eee8b5ea3784ec4af3b137a5244c) C:\Windows\system32\DRIVERS\disk.sys
17:00:35.0021 4296 Disk - ok
17:00:35.0083 4296 Dot4 (b42ed0320c6e41102fde0005154849bb) C:\Windows\system32\DRIVERS\Dot4.sys
17:00:35.0099 4296 Dot4 - ok
17:00:35.0145 4296 Dot4Print (85135ad27e79b689335c08167d917cde) C:\Windows\system32\DRIVERS\Dot4Prt.sys
17:00:35.0145 4296 Dot4Print - ok
17:00:35.0161 4296 dot4usb (fd05a02b0370bc3000f402e543ca5814) C:\Windows\system32\DRIVERS\dot4usb.sys
17:00:35.0177 4296 dot4usb - ok
17:00:35.0208 4296 drmkaud (9b19f34400d24df84c858a421c205754) C:\Windows\system32\drivers\drmkaud.sys
17:00:35.0223 4296 drmkaud - ok
17:00:35.0255 4296 DXGKrnl (ebce0b0924835f635f620d19f0529dce) C:\Windows\System32\drivers\dxgkrnl.sys
17:00:35.0333 4296 DXGKrnl - ok
17:00:35.0411 4296 ebdrv (dc5d737f51be844d8c82c695eb17372f) C:\Windows\system32\DRIVERS\evbda.sys
17:00:35.0504 4296 ebdrv - ok
17:00:35.0551 4296 elxstor (0e5da5369a0fcaea12456dd852545184) C:\Windows\system32\DRIVERS\elxstor.sys
17:00:35.0567 4296 elxstor - ok
17:00:35.0613 4296 ErrDev (34a3c54752046e79a126e15c51db409b) C:\Windows\system32\DRIVERS\errdev.sys
17:00:35.0613 4296 ErrDev - ok
17:00:35.0645 4296 exfat (a510c654ec00c1e9bdd91eeb3a59823b) C:\Windows\system32\drivers\exfat.sys
17:00:35.0660 4296 exfat - ok
17:00:35.0723 4296 FACAP (2c1d443e14f376e8331f52f135dca9ef) C:\Windows\system32\DRIVERS\facap.sys
17:00:35.0754 4296 FACAP - ok
17:00:35.0785 4296 fastfat (0adc83218b66a6db380c330836f3e36d) C:\Windows\system32\drivers\fastfat.sys
17:00:35.0785 4296 fastfat - ok
17:00:35.0816 4296 fdc (d765d19cd8ef61f650c384f62fac00ab) C:\Windows\system32\DRIVERS\fdc.sys
17:00:35.0816 4296 fdc - ok
17:00:35.0832 4296 FileInfo (655661be46b5f5f3fd454e2c3095b930) C:\Windows\system32\drivers\fileinfo.sys
17:00:35.0832 4296 FileInfo - ok
17:00:35.0863 4296 Filetrace (5f671ab5bc87eea04ec38a6cd5962a47) C:\Windows\system32\drivers\filetrace.sys
17:00:35.0863 4296 Filetrace - ok
17:00:35.0910 4296 flpydisk (c172a0f53008eaeb8ea33fe10e177af5) C:\Windows\system32\DRIVERS\flpydisk.sys
17:00:35.0910 4296 flpydisk - ok
17:00:35.0957 4296 FltMgr (f7866af72abbaf84b1fa5aa195378c59) C:\Windows\system32\drivers\fltmgr.sys
17:00:35.0957 4296 FltMgr - ok
17:00:35.0988 4296 FsDepends (d43703496149971890703b4b1b723eac) C:\Windows\system32\drivers\FsDepends.sys
17:00:35.0988 4296 FsDepends - ok
17:00:36.0019 4296 Fs_Rec (e95ef8547de20cf0603557c0cf7a9462) C:\Windows\system32\drivers\Fs_Rec.sys
17:00:36.0019 4296 Fs_Rec - ok
17:00:36.0066 4296 FTDIBUS (82d4bd620f7e27ea268ea0e2f701a7ae) C:\Windows\system32\drivers\ftdibus.sys
17:00:36.0113 4296 FTDIBUS - ok
17:00:36.0128 4296 FTSER2K (1fa21ff2d7b50b528d8b73db34ad06bc) C:\Windows\system32\drivers\ftser2k.sys
17:00:36.0159 4296 FTSER2K - ok
17:00:36.0175 4296 fvevol (ae87ba80d0ec3b57126ed2cdc15b24ed) C:\Windows\system32\DRIVERS\fvevol.sys
17:00:36.0175 4296 fvevol - ok
17:00:36.0206 4296 gagp30kx (8c778d335c9d272cfd3298ab02abe3b6) C:\Windows\system32\DRIVERS\gagp30kx.sys
17:00:36.0206 4296 gagp30kx - ok
17:00:36.0253 4296 GEARAspiWDM (e403aacf8c7bb11375122d2464560311) C:\Windows\system32\DRIVERS\GEARAspiWDM.sys
17:00:36.0300 4296 GEARAspiWDM - ok
17:00:36.0331 4296 hcw85cir (f2523ef6460fc42405b12248338ab2f0) C:\Windows\system32\drivers\hcw85cir.sys
17:00:36.0331 4296 hcw85cir - ok
17:00:36.0347 4296 HDAudBus (0a49913402747a0b67de940fb42cbdbb) C:\Windows\system32\DRIVERS\HDAudBus.sys
17:00:36.0362 4296 HDAudBus - ok
17:00:36.0378 4296 HidBatt (78e86380454a7b10a5eb255dc44a355f) C:\Windows\system32\DRIVERS\HidBatt.sys
17:00:36.0378 4296 HidBatt - ok
17:00:36.0409 4296 HidBth (7fd2a313f7afe5c4dab14798c48dd104) C:\Windows\system32\DRIVERS\hidbth.sys
17:00:36.0409 4296 HidBth - ok
17:00:36.0440 4296 HidIr (0a77d29f311b88cfae3b13f9c1a73825) C:\Windows\system32\DRIVERS\hidir.sys
17:00:36.0440 4296 HidIr - ok
17:00:36.0471 4296 HidUsb (b3bf6b5b50006def50b66306d99fcf6f) C:\Windows\system32\DRIVERS\hidusb.sys
17:00:36.0471 4296 HidUsb - ok
17:00:36.0534 4296 HpSAMD (0886d440058f203eba0e1825e4355914) C:\Windows\system32\DRIVERS\HpSAMD.sys
17:00:36.0549 4296 HpSAMD - ok
17:00:36.0581 4296 HTTP (cee049cac4efa7f4e1e4ad014414a5d4) C:\Windows\system32\drivers\HTTP.sys
17:00:36.0581 4296 HTTP - ok
17:00:36.0596 4296 hwpolicy (f17766a19145f111856378df337a5d79) C:\Windows\system32\drivers\hwpolicy.sys
17:00:36.0596 4296 hwpolicy - ok
17:00:36.0627 4296 i8042prt (fa55c73d4affa7ee23ac4be53b4592d3) C:\Windows\system32\DRIVERS\i8042prt.sys
17:00:36.0627 4296 i8042prt - ok
17:00:36.0674 4296 iaStor (1d004cb1da6323b1f55caef7f94b61d9) C:\Windows\system32\DRIVERS\iaStor.sys
17:00:36.0674 4296 iaStor - ok
17:00:36.0705 4296 iaStorV (d83efb6fd45df9d55e9a1afc63640d50) C:\Windows\system32\DRIVERS\iaStorV.sys
17:00:36.0721 4296 iaStorV - ok
17:00:36.0768 4296 iirsp (5c18831c61933628f5bb0ea2675b9d21) C:\Windows\system32\DRIVERS\iirsp.sys
17:00:36.0783 4296 iirsp - ok
17:00:36.0815 4296 intelide (f00f20e70c6ec3aa366910083a0518aa) C:\Windows\system32\DRIVERS\intelide.sys
17:00:36.0815 4296 intelide - ok
17:00:36.0830 4296 intelppm (ada036632c664caa754079041cf1f8c1) C:\Windows\system32\DRIVERS\intelppm.sys
17:00:36.0846 4296 intelppm - ok
17:00:36.0877 4296 IpFilterDriver (722dd294df62483cecaae6e094b4d695) C:\Windows\system32\DRIVERS\ipfltdrv.sys
17:00:36.0877 4296 IpFilterDriver - ok
17:00:36.0908 4296 IPMIDRV (e2b4a4494db7cb9b89b55ca268c337c5) C:\Windows\system32\DRIVERS\IPMIDrv.sys
17:00:36.0908 4296 IPMIDRV - ok
17:00:36.0939 4296 IPNAT (af9b39a7e7b6caa203b3862582e9f2d0) C:\Windows\system32\drivers\ipnat.sys
17:00:36.0939 4296 IPNAT - ok
17:00:37.0002 4296 IRENUM (3abf5e7213eb28966d55d58b515d5ce9) C:\Windows\system32\drivers\irenum.sys
17:00:37.0002 4296 IRENUM - ok
17:00:37.0033 4296 isapnp (2f7b28dc3e1183e5eb418df55c204f38) C:\Windows\system32\DRIVERS\isapnp.sys
17:00:37.0033 4296 isapnp - ok
17:00:37.0064 4296 iScsiPrt (fa4d2557de56d45b0a346f93564be6e1) C:\Windows\system32\DRIVERS\msiscsi.sys
17:00:37.0064 4296 iScsiPrt - ok
17:00:37.0111 4296 itecir (8d990a44b4f2b68e2c56a3724ec3eb84) C:\Windows\system32\DRIVERS\itecir.sys
17:00:37.0142 4296 itecir - ok
17:00:37.0189 4296 k57nd60a (08dd34f74d65e1c8f238565570952630) C:\Windows\system32\DRIVERS\k57nd60a.sys
17:00:37.0236 4296 k57nd60a - ok
17:00:37.0251 4296 kbdclass (bc02336f1cba7dcc7d1213bb588a68a5) C:\Windows\system32\DRIVERS\kbdclass.sys
17:00:37.0267 4296 kbdclass - ok
17:00:37.0283 4296 kbdhid (6def98f8541e1b5dceb2c822a11f7323) C:\Windows\system32\DRIVERS\kbdhid.sys
17:00:37.0298 4296 kbdhid - ok
17:00:37.0314 4296 KSecDD (e8b6fcc9c83535c67f835d407620bd27) C:\Windows\system32\Drivers\ksecdd.sys
17:00:37.0314 4296 KSecDD - ok
17:00:37.0329 4296 KSecPkg (a8c63880ef6f4d3fec7b616b9c060215) C:\Windows\system32\Drivers\ksecpkg.sys
17:00:37.0329 4296 KSecPkg - ok
17:00:37.0345 4296 ksthunk (6869281e78cb31a43e969f06b57347c4) C:\Windows\system32\drivers\ksthunk.sys
17:00:37.0345 4296 ksthunk - ok
17:00:37.0392 4296 lltdio (1538831cf8ad2979a04c423779465827) C:\Windows\system32\DRIVERS\lltdio.sys
17:00:37.0392 4296 lltdio - ok
17:00:37.0439 4296 LSI_FC (1a93e54eb0ece102495a51266dcdb6a6) C:\Windows\system32\DRIVERS\lsi_fc.sys
17:00:37.0439 4296 LSI_FC - ok
17:00:37.0454 4296 LSI_SAS (1047184a9fdc8bdbff857175875ee810) C:\Windows\system32\DRIVERS\lsi_sas.sys
17:00:37.0454 4296 LSI_SAS - ok
17:00:37.0485 4296 LSI_SAS2 (30f5c0de1ee8b5bc9306c1f0e4a75f93) C:\Windows\system32\DRIVERS\lsi_sas2.sys
17:00:37.0485 4296 LSI_SAS2 - ok
17:00:37.0517 4296 LSI_SCSI (0504eacaff0d3c8aed161c4b0d369d4a) C:\Windows\system32\DRIVERS\lsi_scsi.sys
17:00:37.0517 4296 LSI_SCSI - ok
17:00:37.0548 4296 luafv (43d0f98e1d56ccddb0d5254cff7b356e) C:\Windows\system32\drivers\luafv.sys
17:00:37.0548 4296 luafv - ok
17:00:37.0641 4296 megasas (a55805f747c6edb6a9080d7c633bd0f4) C:\Windows\system32\DRIVERS\megasas.sys
17:00:37.0641 4296 megasas - ok
17:00:37.0657 4296 MegaSR (baf74ce0072480c3b6b7c13b2a94d6b3) C:\Windows\system32\DRIVERS\MegaSR.sys
17:00:37.0673 4296 MegaSR - ok
17:00:37.0719 4296 mfeapfk (ef3acfb7e3f82d5f7cde9ef5f0a4e2e2) C:\Windows\system32\drivers\mfeapfk.sys
17:00:37.0751 4296 mfeapfk - ok
17:00:37.0797 4296 mfeavfk (e7a60bdb4365b561d896019b82fb7dd0) C:\Windows\system32\drivers\mfeavfk.sys
17:00:37.0829 4296 mfeavfk - ok
17:00:37.0860 4296 mfeavfk01 - ok
17:00:37.0938 4296 mfefirek (670dffe55e2f9ab99d9169c428bcece9) C:\Windows\system32\drivers\mfefirek.sys
17:00:38.0000 4296 mfefirek - ok
17:00:38.0047 4296 mfehidk (1892616b7f9291fd77c3fa0a5811fe9f) C:\Windows\system32\drivers\mfehidk.sys
17:00:38.0063 4296 mfehidk - ok
17:00:38.0078 4296 mfenlfk (1721261c77f6e7a9e0cb51b7d9f31b60) C:\Windows\system32\DRIVERS\mfenlfk.sys
17:00:38.0125 4296 mfenlfk - ok
17:00:38.0156 4296 mferkdet (65776bd8029e409935b90de30bf99526) C:\Windows\system32\drivers\mferkdet.sys
17:00:38.0156 4296 mferkdet - ok
17:00:38.0172 4296 mfewfpk (4f17d8b85b903d96ef7033bb6ef50516) C:\Windows\system32\drivers\mfewfpk.sys
17:00:38.0219 4296 mfewfpk - ok
17:00:38.0250 4296 Modem (800ba92f7010378b09f9ed9270f07137) C:\Windows\system32\drivers\modem.sys
17:00:38.0250 4296 Modem - ok
17:00:38.0281 4296 monitor (b03d591dc7da45ece20b3b467e6aadaa) C:\Windows\system32\DRIVERS\monitor.sys
17:00:38.0281 4296 monitor - ok
17:00:38.0328 4296 mouclass (7d27ea49f3c1f687d357e77a470aea99) C:\Windows\system32\DRIVERS\mouclass.sys
17:00:38.0343 4296 mouclass - ok
17:00:38.0390 4296 mouhid (d3bf052c40b0c4166d9fd86a4288c1e6) C:\Windows\system32\DRIVERS\mouhid.sys
17:00:38.0390 4296 mouhid - ok
17:00:38.0421 4296 mountmgr (791af66c4d0e7c90a3646066386fb571) C:\Windows\system32\drivers\mountmgr.sys
17:00:38.0421 4296 mountmgr - ok
17:00:38.0437 4296 mpio (609d1d87649ecc19796f4d76d4c15cea) C:\Windows\system32\DRIVERS\mpio.sys
17:00:38.0437 4296 mpio - ok
17:00:38.0468 4296 mpsdrv (6c38c9e45ae0ea2fa5e551f2ed5e978f) C:\Windows\system32\drivers\mpsdrv.sys
17:00:38.0468 4296 mpsdrv - ok
17:00:38.0499 4296 MRxDAV (30524261bb51d96d6fcbac20c810183c) C:\Windows\system32\drivers\mrxdav.sys
17:00:38.0499 4296 MRxDAV - ok
17:00:38.0546 4296 mrxsmb (040d62a9d8ad28922632137acdd984f2) C:\Windows\system32\DRIVERS\mrxsmb.sys
17:00:38.0546 4296 mrxsmb - ok
17:00:38.0577 4296 mrxsmb10 (f0067552f8f9b33d7c59403ab808a3cb) C:\Windows\system32\DRIVERS\mrxsmb10.sys
17:00:38.0577 4296 mrxsmb10 - ok
17:00:38.0609 4296 mrxsmb20 (3c142d31de9f2f193218a53fe2632051) C:\Windows\system32\DRIVERS\mrxsmb20.sys
17:00:38.0609 4296 mrxsmb20 - ok
17:00:38.0640 4296 msahci (bccf16d5fb1109162380e3e28dc9e4e5) C:\Windows\system32\DRIVERS\msahci.sys
17:00:38.0640 4296 msahci - ok
17:00:38.0671 4296 msdsm (8d27b597229aed79430fb9db3bcbfbd0) C:\Windows\system32\DRIVERS\msdsm.sys
17:00:38.0671 4296 msdsm - ok
17:00:38.0718 4296 Msfs (aa3fb40e17ce1388fa1bedab50ea8f96) C:\Windows\system32\drivers\Msfs.sys
17:00:38.0718 4296 Msfs - ok
17:00:38.0733 4296 mshidkmdf (f9d215a46a8b9753f61767fa72a20326) C:\Windows\System32\drivers\mshidkmdf.sys
17:00:38.0749 4296 mshidkmdf - ok
17:00:38.0780 4296 msisadrv (d916874bbd4f8b07bfb7fa9b3ccae29d) C:\Windows\system32\DRIVERS\msisadrv.sys
17:00:38.0780 4296 msisadrv - ok
17:00:38.0827 4296 MSKSSRV (49ccf2c4fea34ffad8b1b59d49439366) C:\Windows\system32\drivers\MSKSSRV.sys
17:00:38.0827 4296 MSKSSRV - ok
17:00:38.0843 4296 MSPCLOCK (bdd71ace35a232104ddd349ee70e1ab3) C:\Windows\system32\drivers\MSPCLOCK.sys
17:00:38.0858 4296 MSPCLOCK - ok
17:00:38.0874 4296 MSPQM (4ed981241db27c3383d72092b618a1d0) C:\Windows\system32\drivers\MSPQM.sys
17:00:38.0874 4296 MSPQM - ok
17:00:38.0921 4296 MsRPC (89cb141aa8616d8c6a4610fa26c60964) C:\Windows\system32\drivers\MsRPC.sys
17:00:38.0921 4296 MsRPC - ok
17:00:38.0967 4296 mssmbios (0eed230e37515a0eaee3c2e1bc97b288) C:\Windows\system32\DRIVERS\mssmbios.sys
17:00:38.0967 4296 mssmbios - ok
17:00:38.0999 4296 MSTEE (2e66f9ecb30b4221a318c92ac2250779) C:\Windows\system32\drivers\MSTEE.sys
17:00:38.0999 4296 MSTEE - ok
17:00:39.0014 4296 MTConfig (7ea404308934e675bffde8edf0757bcd) C:\Windows\system32\DRIVERS\MTConfig.sys
17:00:39.0014 4296 MTConfig - ok
17:00:39.0030 4296 Mup (f9a18612fd3526fe473c1bda678d61c8) C:\Windows\system32\Drivers\mup.sys
17:00:39.0030 4296 Mup - ok
17:00:39.0061 4296 NativeWifiP (1ea3749c4114db3e3161156ffffa6b33) C:\Windows\system32\DRIVERS\nwifi.sys
17:00:39.0077 4296 NativeWifiP - ok
17:00:39.0123 4296 NDIS (cad515dbd07d082bb317d9928ce8962c) C:\Windows\system32\drivers\ndis.sys
17:00:39.0123 4296 NDIS - ok
17:00:39.0139 4296 NdisCap (9f9a1f53aad7da4d6fef5bb73ab811ac) C:\Windows\system32\DRIVERS\ndiscap.sys
17:00:39.0155 4296 NdisCap - ok
17:00:39.0186 4296 NdisTapi (30639c932d9fef22b31268fe25a1b6e5) C:\Windows\system32\DRIVERS\ndistapi.sys
17:00:39.0186 4296 NdisTapi - ok
17:00:39.0201 4296 Ndisuio (f105ba1e22bf1f2ee8f005d4305e4bec) C:\Windows\system32\DRIVERS\ndisuio.sys
17:00:39.0201 4296 Ndisuio - ok
17:00:39.0233 4296 NdisWan (557dfab9ca1fcb036ac77564c010dad3) C:\Windows\system32\DRIVERS\ndiswan.sys
17:00:39.0248 4296 NdisWan - ok
17:00:39.0264 4296 NDProxy (659b74fb74b86228d6338d643cd3e3cf) C:\Windows\system32\drivers\NDProxy.sys
17:00:39.0279 4296 NDProxy - ok
17:00:39.0311 4296 NetBIOS (86743d9f5d2b1048062b14b1d84501c4) C:\Windows\system32\DRIVERS\netbios.sys
17:00:39.0311 4296 NetBIOS - ok
17:00:39.0326 4296 NetBT (9162b273a44ab9dce5b44362731d062a) C:\Windows\system32\DRIVERS\netbt.sys
17:00:39.0326 4296 NetBT - ok
17:00:39.0482 4296 NETw5v64 (705283c02177809ca9fa7cc58a4f1e77) C:\Windows\system32\DRIVERS\NETw5v64.sys
17:00:39.0669 4296 NETw5v64 - ok
17:00:39.0701 4296 nfrd960 (77889813be4d166cdab78ddba990da92) C:\Windows\system32\DRIVERS\nfrd960.sys
17:00:39.0701 4296 nfrd960 - ok
17:00:39.0747 4296 NPF (351533acc2a069b94e80bbfc177e8fdf) C:\Windows\system32\drivers\npf.sys
17:00:39.0794 4296 NPF - ok
17:00:39.0825 4296 Npfs (1e4c4ab5c9b8dd13179bbdc75a2a01f7) C:\Windows\system32\drivers\Npfs.sys
17:00:39.0825 4296 Npfs - ok
17:00:39.0841 4296 nsiproxy (e7f5ae18af4168178a642a9247c63001) C:\Windows\system32\drivers\nsiproxy.sys
17:00:39.0841 4296 nsiproxy - ok
17:00:39.0857 4296 ntcdrdrv - ok
17:00:39.0919 4296 Ntfs (356698a13c4630d5b31c37378d469196) C:\Windows\system32\drivers\Ntfs.sys
17:00:39.0935 4296 Ntfs - ok
17:00:39.0950 4296 Null (9899284589f75fa8724ff3d16aed75c1) C:\Windows\system32\drivers\Null.sys
17:00:39.0966 4296 Null - ok
17:00:40.0013 4296 nvraid (3e38712941e9bb4ddbee00affe3fed3d) C:\Windows\system32\DRIVERS\nvraid.sys
17:00:40.0028 4296 nvraid - ok
17:00:40.0059 4296 nvstor (477dc4d6deb99be37084c9ac6d013da1) C:\Windows\system32\DRIVERS\nvstor.sys
17:00:40.0059 4296 nvstor - ok
17:00:40.0122 4296 nv_agp (270d7cd42d6e3979f6dd0146650f0e05) C:\Windows\system32\DRIVERS\nv_agp.sys
17:00:40.0122 4296 nv_agp - ok
17:00:40.0153 4296 ohci1394 (3589478e4b22ce21b41fa1bfc0b8b8a0) C:\Windows\system32\DRIVERS\ohci1394.sys
17:00:40.0169 4296 ohci1394 - ok
17:00:40.0215 4296 Parport (0086431c29c35be1dbc43f52cc273887) C:\Windows\system32\DRIVERS\parport.sys
17:00:40.0215 4296 Parport - ok
17:00:40.0231 4296 partmgr (7daa117143316c4a1537e074a5a9eaf0) C:\Windows\system32\drivers\partmgr.sys
17:00:40.0231 4296 partmgr - ok
17:00:40.0340 4296 pbfilter (7c0582921913d00180ec2b8518ba135c) C:\Program Files\PeerBlock\pbfilter.sys
17:00:40.0356 4296 pbfilter - ok
17:00:40.0403 4296 pci (f36f6504009f2fb0dfd1b17a116ad74b) C:\Windows\system32\DRIVERS\pci.sys
17:00:40.0403 4296 pci - ok
17:00:40.0434 4296 pciide (b5b8b5ef2e5cb34df8dcf8831e3534fa) C:\Windows\system32\DRIVERS\pciide.sys
17:00:40.0434 4296 pciide - ok
17:00:40.0465 4296 pcmcia (b2e81d4e87ce48589f98cb8c05b01f2f) C:\Windows\system32\DRIVERS\pcmcia.sys
17:00:40.0465 4296 pcmcia - ok
17:00:40.0481 4296 pcw (d6b9c2e1a11a3a4b26a182ffef18f603) C:\Windows\system32\drivers\pcw.sys
17:00:40.0481 4296 pcw - ok
17:00:40.0512 4296 PEAUTH (68769c3356b3be5d1c732c97b9a80d6e) C:\Windows\system32\drivers\peauth.sys
17:00:40.0527 4296 PEAUTH - ok
17:00:40.0605 4296 PptpMiniport (27cc19e81ba5e3403c48302127bda717) C:\Windows\system32\DRIVERS\raspptp.sys
17:00:40.0605 4296 PptpMiniport - ok
17:00:40.0621 4296 Processor (0d922e23c041efb1c3fac2a6f943c9bf) C:\Windows\system32\DRIVERS\processr.sys
17:00:40.0621 4296 Processor - ok
17:00:40.0652 4296 Psched (ee992183bd8eaefd9973f352e587a299) C:\Windows\system32\DRIVERS\pacer.sys
17:00:40.0652 4296 Psched - ok
17:00:40.0699 4296 PxHlpa64 (87b04878a6d59d6c79251dc960c674c1) C:\Windows\system32\Drivers\PxHlpa64.sys
17:00:40.0699 4296 PxHlpa64 - ok
17:00:40.0761 4296 ql2300 (a53a15a11ebfd21077463ee2c7afeef0) C:\Windows\system32\DRIVERS\ql2300.sys
17:00:40.0808 4296 ql2300 - ok
17:00:40.0824 4296 ql40xx (4f6d12b51de1aaeff7dc58c4d75423c8) C:\Windows\system32\DRIVERS\ql40xx.sys
17:00:40.0839 4296 ql40xx - ok
17:00:40.0855 4296 QWAVEdrv (76707bb36430888d9ce9d705398adb6c) C:\Windows\system32\drivers\qwavedrv.sys
17:00:40.0871 4296 QWAVEdrv - ok
17:00:40.0886 4296 RasAcd (5a0da8ad5762fa2d91678a8a01311704) C:\Windows\system32\DRIVERS\rasacd.sys
17:00:40.0886 4296 RasAcd - ok
17:00:40.0933 4296 RasAgileVpn (7ecff9b22276b73f43a99a15a6094e90) C:\Windows\system32\DRIVERS\AgileVpn.sys
17:00:40.0933 4296 RasAgileVpn - ok
17:00:40.0949 4296 Rasl2tp (87a6e852a22991580d6d39adc4790463) C:\Windows\system32\DRIVERS\rasl2tp.sys
17:00:40.0964 4296 Rasl2tp - ok
17:00:40.0980 4296 RasPppoe (855c9b1cd4756c5e9a2aa58a15f58c25) C:\Windows\system32\DRIVERS\raspppoe.sys
17:00:40.0980 4296 RasPppoe - ok
17:00:40.0995 4296 RasSstp (e8b1e447b008d07ff47d016c2b0eeecb) C:\Windows\system32\DRIVERS\rassstp.sys
17:00:41.0011 4296 RasSstp - ok
17:00:41.0027 4296 rdbss (3bac8142102c15d59a87757c1d41dce5) C:\Windows\system32\DRIVERS\rdbss.sys
17:00:41.0027 4296 rdbss - ok
17:00:41.0042 4296 rdpbus (302da2a0539f2cf54d7c6cc30c1f2d8d) C:\Windows\system32\DRIVERS\rdpbus.sys
17:00:41.0042 4296 rdpbus - ok
17:00:41.0073 4296 RDPCDD (cea6cc257fc9b7715f1c2b4849286d24) C:\Windows\system32\DRIVERS\RDPCDD.sys
17:00:41.0073 4296 RDPCDD - ok
17:00:41.0089 4296 RDPENCDD (bb5971a4f00659529a5c44831af22365) C:\Windows\system32\drivers\rdpencdd.sys
17:00:41.0089 4296 RDPENCDD - ok
17:00:41.0120 4296 RDPREFMP (216f3fa57533d98e1f74ded70113177a) C:\Windows\system32\drivers\rdprefmp.sys
17:00:41.0120 4296 RDPREFMP - ok
17:00:41.0151 4296 RDPWD (8a3e6bea1c53ea6177fe2b6eba2c80d7) C:\Windows\system32\drivers\RDPWD.sys
17:00:41.0151 4296 RDPWD - ok
17:00:41.0198 4296 rdyboost (634b9a2181d98f15941236886164ec8b) C:\Windows\system32\drivers\rdyboost.sys
17:00:41.0198 4296 rdyboost - ok
17:00:41.0261 4296 RFCOMM (3dd798846e2c28102b922c56e71b7932) C:\Windows\system32\DRIVERS\rfcomm.sys
17:00:41.0261 4296 RFCOMM - ok
17:00:41.0307 4296 rimspci (e20b1907fc72a3664ece21e3c20fc63d) C:\Windows\system32\DRIVERS\rimspe64.sys
17:00:41.0339 4296 rimspci - ok
17:00:41.0385 4296 risdpcie (a6da2b0c8f5bb3f9f5423cff8d6a02d9) C:\Windows\system32\DRIVERS\risdpe64.sys
17:00:41.0417 4296 risdpcie - ok
17:00:41.0432 4296 rixdpcie (6a1cd4674505e6791390a1ab71da1fbe) C:\Windows\system32\DRIVERS\rixdpe64.sys
17:00:41.0479 4296 rixdpcie - ok
17:00:41.0510 4296 rspndr (ddc86e4f8e7456261e637e3552e804ff) C:\Windows\system32\DRIVERS\rspndr.sys
17:00:41.0510 4296 rspndr - ok
17:00:41.0573 4296 RTHDMIAzAudService (c618475866f6a7129f64a55961c1bb8b) C:\Windows\system32\drivers\RtHDMIVX.sys
17:00:41.0619 4296 RTHDMIAzAudService - ok
17:00:41.0619 4296 RxFilter - ok
17:00:41.0651 4296 sbp2port (e3bbb89983daf5622c1d50cf49f28227) C:\Windows\system32\DRIVERS\sbp2port.sys
17:00:41.0651 4296 sbp2port - ok
17:00:41.0682 4296 scfilter (c94da20c7e3ba1dca269bc8460d98387) C:\Windows\system32\DRIVERS\scfilter.sys
17:00:41.0697 4296 scfilter - ok
17:00:41.0729 4296 secdrv (3ea8a16169c26afbeb544e0e48421186) C:\Windows\system32\drivers\secdrv.sys
17:00:41.0729 4296 secdrv - ok
17:00:41.0791 4296 Sentinel64 (84ac127242dd3ccde02f9a4673214b1f) C:\Windows\System32\Drivers\Sentinel64.sys
17:00:41.0838 4296 Sentinel64 - ok
17:00:41.0869 4296 Serenum (cb624c0035412af0debec78c41f5ca1b) C:\Windows\system32\DRIVERS\serenum.sys
17:00:41.0869 4296 Serenum - ok
17:00:41.0916 4296 Serial (c1d8e28b2c2adfaec4ba89e9fda69bd6) C:\Windows\system32\DRIVERS\serial.sys
17:00:41.0916 4296 Serial - ok
17:00:41.0947 4296 sermouse (1c545a7d0691cc4a027396535691c3e3) C:\Windows\system32\DRIVERS\sermouse.sys
17:00:41.0947 4296 sermouse - ok
17:00:42.0009 4296 sffdisk (a554811bcd09279536440c964ae35bbf) C:\Windows\system32\DRIVERS\sffdisk.sys
17:00:42.0025 4296 sffdisk - ok
17:00:42.0041 4296 sffp_mmc (ff414f0baefeba59bc6c04b3db0b87bf) C:\Windows\system32\DRIVERS\sffp_mmc.sys
17:00:42.0041 4296 sffp_mmc - ok
17:00:42.0056 4296 sffp_sd (178298f767fe638c9fedcbdef58bb5e4) C:\Windows\system32\DRIVERS\sffp_sd.sys
17:00:42.0087 4296 sffp_sd - ok
17:00:42.0134 4296 sfloppy (a9d601643a1647211a1ee2ec4e433ff4) C:\Windows\system32\DRIVERS\sfloppy.sys
17:00:42.0134 4296 sfloppy - ok
17:00:42.0197 4296 SilvrLnk (ab191e50da5dc1e69311742e3930a61e) C:\Windows\system32\DRIVERS\silvrlnk.sys
17:00:42.0243 4296 SilvrLnk - ok
17:00:42.0259 4296 SiSRaid2 (843caf1e5fde1ffd5ff768f23a51e2e1) C:\Windows\system32\DRIVERS\SiSRaid2.sys
17:00:42.0275 4296 SiSRaid2 - ok
17:00:42.0290 4296 SiSRaid4 (6a6c106d42e9ffff8b9fcb4f754f6da4) C:\Windows\system32\DRIVERS\sisraid4.sys
17:00:42.0290 4296 SiSRaid4 - ok
17:00:42.0306 4296 Smb (548260a7b8654e024dc30bf8a7c5baa4) C:\Windows\system32\DRIVERS\smb.sys
17:00:42.0321 4296 Smb - ok
17:00:42.0353 4296 spldr (b9e31e5cacdfe584f34f730a677803f9) C:\Windows\system32\drivers\spldr.sys
17:00:42.0353 4296 spldr - ok
17:00:42.0431 4296 sptd (602884696850c86434530790b110e8eb) C:\Windows\system32\Drivers\sptd.sys
17:00:42.0431 4296 Suspicious file (NoAccess): C:\Windows\system32\Drivers\sptd.sys. md5: 602884696850c86434530790b110e8eb
17:00:42.0431 4296 sptd ( LockedFile.Multi.Generic ) - warning
17:00:42.0431 4296 sptd - detected LockedFile.Multi.Generic (1)
17:00:42.0477 4296 Spyder2 (b9413b99dbb704e0f5824775a1118cc7) C:\Windows\system32\DRIVERS\Spyder2.sys
17:00:42.0524 4296 Spyder2 - ok
17:00:42.0571 4296 srv (2408c0366d96bcdf63e8f1c78e4a29c5) C:\Windows\system32\DRIVERS\srv.sys
17:00:42.0571 4296 srv - ok
17:00:42.0587 4296 srv2 (76548f7b818881b47d8d1ae1be9c11f8) C:\Windows\system32\DRIVERS\srv2.sys
17:00:42.0587 4296 srv2 - ok
17:00:42.0649 4296 srvnet (0af6e19d39c70844c5caa8fb0183c36e) C:\Windows\system32\DRIVERS\srvnet.sys
17:00:42.0649 4296 srvnet - ok
17:00:42.0696 4296 sscdbus (f4f1e1ff6986fe8914525af751ea3eac) C:\Windows\system32\DRIVERS\sscdbus.sys
17:00:42.0743 4296 sscdbus - ok
17:00:42.0789 4296 stexstor (f3817967ed533d08327dc73bc4d5542a) C:\Windows\system32\DRIVERS\stexstor.sys
17:00:42.0789 4296 stexstor - ok
17:00:42.0836 4296 STHDA (02e784fa49032f84964db90a3ed81890) C:\Windows\system32\DRIVERS\stwrt64.sys
17:00:42.0883 4296 STHDA - ok
17:00:42.0930 4296 swenum (d01ec09b6711a5f8e7e6564a4d0fbc90) C:\Windows\system32\DRIVERS\swenum.sys
17:00:42.0930 4296 swenum - ok
17:00:42.0992 4296 SynTP (1657b7442d5ce30533f5c4317716b468) C:\Windows\system32\DRIVERS\SynTP.sys
17:00:43.0039 4296 SynTP - ok
17:00:43.0133 4296 Tcpip (b9d87c7707f058ac652a398cd28de14b) C:\Windows\system32\drivers\tcpip.sys
17:00:43.0226 4296 Tcpip - ok
17:00:43.0289 4296 TCPIP6 (b9d87c7707f058ac652a398cd28de14b) C:\Windows\system32\DRIVERS\tcpip.sys
17:00:43.0289 4296 TCPIP6 - ok
17:00:43.0320 4296 tcpipreg (76d078af6f587b162d50210f761eb9ed) C:\Windows\system32\drivers\tcpipreg.sys
17:00:43.0320 4296 tcpipreg - ok
17:00:43.0367 4296 TDPIPE (3371d21011695b16333a3934340c4e7c) C:\Windows\system32\drivers\tdpipe.sys
17:00:43.0367 4296 TDPIPE - ok
17:00:43.0398 4296 TDTCP (e4245bda3190a582d55ed09e137401a9) C:\Windows\system32\drivers\tdtcp.sys
17:00:43.0398 4296 TDTCP - ok
17:00:43.0429 4296 tdx (079125c4b17b01fcaeebce0bcb290c0f) C:\Windows\system32\DRIVERS\tdx.sys
17:00:43.0445 4296 tdx - ok
17:00:43.0460 4296 TermDD (c448651339196c0e869a355171875522) C:\Windows\system32\DRIVERS\termdd.sys
17:00:43.0476 4296 TermDD - ok
17:00:43.0538 4296 TIEHDUSB (199c2e87d9a5ec58d0bcd94e893bf629) C:\Windows\system32\DRIVERS\tiehdusb.sys
17:00:43.0569 4296 TIEHDUSB - ok
17:00:43.0632 4296 Tpkd (c676b0f52f2b6483afb88f79cabb011e) C:\Windows\system32\drivers\Tpkd.sys
17:00:43.0632 4296 Tpkd - ok
17:00:43.0647 4296 tssecsrv (61b96c26131e37b24e93327a0bd1fb95) C:\Windows\system32\DRIVERS\tssecsrv.sys
17:00:43.0663 4296 tssecsrv - ok
17:00:43.0679 4296 tunnel (3836171a2cdf3af8ef10856db9835a70) C:\Windows\system32\DRIVERS\tunnel.sys
17:00:43.0694 4296 tunnel - ok
17:00:43.0710 4296 uagp35 (b4dd609bd7e282bfc683cec7eaaaad67) C:\Windows\system32\DRIVERS\uagp35.sys
17:00:43.0710 4296 uagp35 - ok
17:00:43.0757 4296 udfs (31ba4a33afab6a69ea092b18017f737f) C:\Windows\system32\DRIVERS\udfs.sys
17:00:43.0803 4296 udfs - ok
17:00:43.0835 4296 uliagpkx (4bfe1bc28391222894cbf1e7d0e42320) C:\Windows\system32\DRIVERS\uliagpkx.sys
17:00:43.0835 4296 uliagpkx - ok
17:00:43.0928 4296 UltraMonUtility (694bcf23662f97d987cf4c6739c35f8b) C:\Program Files (x86)\Common Files\Realtime Soft\UltraMonMirrorDrv\x64\UltraMonUtility.sys
17:00:43.0928 4296 UltraMonUtility - ok
17:00:43.0975 4296 umbus (eab6c35e62b1b0db0d1b48b671d3a117) C:\Windows\system32\DRIVERS\umbus.sys
17:00:43.0991 4296 umbus - ok
17:00:44.0006 4296 UmPass (b2e8e8cb557b156da5493bbddcc1474d) C:\Windows\system32\DRIVERS\umpass.sys
17:00:44.0006 4296 UmPass - ok
17:00:44.0069 4296 USBAAPL64 (aa33fc47ed58c34e6e9261e4f850b7eb) C:\Windows\system32\Drivers\usbaapl64.sys
17:00:44.0100 4296 USBAAPL64 - ok
17:00:44.0131 4296 usbaudio (77b01bc848298223a95d4ec23e1785a1) C:\Windows\system32\drivers\usbaudio.sys
17:00:44.0131 4296 usbaudio - ok
17:00:44.0162 4296 usbccgp (b26afb54a534d634523c4fb66765b026) C:\Windows\system32\DRIVERS\usbccgp.sys
17:00:44.0162 4296 usbccgp - ok
17:00:44.0178 4296 usbcir (af0892a803fdda7492f595368e3b68e7) C:\Windows\system32\DRIVERS\usbcir.sys
17:00:44.0193 4296 usbcir - ok
17:00:44.0209 4296 usbehci (cb490987a7f6928a04bb838e3bd8a936) C:\Windows\system32\DRIVERS\usbehci.sys
17:00:44.0240 4296 usbehci - ok
17:00:44.0271 4296 usbhub (18124ef0a881a00ee222d02a3ee30270) C:\Windows\system32\DRIVERS\usbhub.sys
17:00:44.0303 4296 usbhub - ok
17:00:44.0318 4296 usbohci (58e546bbaf87664fc57e0f6081e4f609) C:\Windows\system32\DRIVERS\usbohci.sys
17:00:44.0334 4296 usbohci - ok
17:00:44.0349 4296 usbprint (73188f58fb384e75c4063d29413cee3d) C:\Windows\system32\DRIVERS\usbprint.sys
17:00:44.0365 4296 usbprint - ok
17:00:44.0396 4296 usbscan (aaa2513c8aed8b54b189fd0c6b1634c0) C:\Windows\system32\DRIVERS\usbscan.sys
17:00:44.0396 4296 usbscan - ok
17:00:44.0412 4296 USBSTOR (080d3820da6c046be82fc8b45a893e83) C:\Windows\system32\DRIVERS\USBSTOR.SYS
17:00:44.0412 4296 USBSTOR - ok
17:00:44.0459 4296 usbuhci (81fb2216d3a60d1284455d511797db3d) C:\Windows\system32\DRIVERS\usbuhci.sys
17:00:44.0474 4296 usbuhci - ok
17:00:44.0490 4296 usbvideo (7cb8c573c6e4a2714402cc0a36eab4fe) C:\Windows\system32\Drivers\usbvideo.sys
17:00:44.0537 4296 usbvideo - ok
17:00:44.0552 4296 vdrvroot (c5c876ccfc083ff3b128f933823e87bd) C:\Windows\system32\DRIVERS\vdrvroot.sys
17:00:44.0552 4296 vdrvroot - ok
17:00:44.0583 4296 vga (da4da3f5e02943c2dc8c6ed875de68dd) C:\Windows\system32\DRIVERS\vgapnp.sys
17:00:44.0599 4296 vga - ok
17:00:44.0615 4296 VgaSave (53e92a310193cb3c03bea963de7d9cfc) C:\Windows\System32\drivers\vga.sys
17:00:44.0615 4296 VgaSave - ok
17:00:44.0661 4296 vhdmp (c82e748660f62a242b2dfac1442f22a4) C:\Windows\system32\DRIVERS\vhdmp.sys
17:00:44.0661 4296 vhdmp - ok
17:00:44.0693 4296 viaide (e5689d93ffe4e5d66c0178761240dd54) C:\Windows\system32\DRIVERS\viaide.sys
17:00:44.0693 4296 viaide - ok
17:00:44.0708 4296 volmgr (2b1a3dae2b4e70dbba822b7a03fbd4a3) C:\Windows\system32\DRIVERS\volmgr.sys
17:00:44.0708 4296 volmgr - ok
17:00:44.0755 4296 volmgrx (99b0cbb569ca79acaed8c91461d765fb) C:\Windows\system32\drivers\volmgrx.sys
17:00:44.0755 4296 volmgrx - ok
17:00:44.0771 4296 volsnap (58f82eed8ca24b461441f9c3e4f0bf5c) C:\Windows\system32\DRIVERS\volsnap.sys
17:00:44.0771 4296 volsnap - ok
17:00:44.0802 4296 vsmraid (5e2016ea6ebaca03c04feac5f330d997) C:\Windows\system32\DRIVERS\vsmraid.sys
17:00:44.0817 4296 vsmraid - ok
17:00:44.0833 4296 vwifibus (36d4720b72b5c5d9cb2b9c29e9df67a1) C:\Windows\System32\drivers\vwifibus.sys
17:00:44.0849 4296 vwifibus - ok
17:00:44.0880 4296 WacomPen (4e9440f4f152a7b944cb1663d3935a3e) C:\Windows\system32\DRIVERS\wacompen.sys
17:00:44.0880 4296 WacomPen - ok
17:00:44.0927 4296 WANARP (47ca49400643effd3f1c9a27e1d69324) C:\Windows\system32\DRIVERS\wanarp.sys
17:00:44.0942 4296 WANARP - ok
17:00:44.0942 4296 Wanarpv6 (47ca49400643effd3f1c9a27e1d69324) C:\Windows\system32\DRIVERS\wanarp.sys
17:00:44.0942 4296 Wanarpv6 - ok
17:00:44.0973 4296 Wd (72889e16ff12ba0f235467d6091b17dc) C:\Windows\system32\DRIVERS\wd.sys
17:00:44.0989 4296 Wd - ok
17:00:45.0005 4296 Wdf01000 (441bd2d7b4f98134c3a4f9fa570fd250) C:\Windows\system32\drivers\Wdf01000.sys
17:00:45.0020 4296 Wdf01000 - ok
17:00:45.0051 4296 WfpLwf (611b23304bf067451a9fdee01fbdd725) C:\Windows\system32\DRIVERS\wfplwf.sys
17:00:45.0051 4296 WfpLwf - ok
17:00:45.0067 4296 WIMMount (05ecaec3e4529a7153b3136ceb49f0ec) C:\Windows\system32\drivers\wimmount.sys
17:00:45.0083 4296 WIMMount - ok
17:00:45.0129 4296 WinUsb (4d52c872018af7e18d078978dcc3f6f2) C:\Windows\system32\DRIVERS\WinUsb.sys
17:00:45.0176 4296 WinUsb - ok
17:00:45.0192 4296 WmiAcpi (f6ff8944478594d0e414d3f048f0d778) C:\Windows\system32\DRIVERS\wmiacpi.sys
17:00:45.0192 4296 WmiAcpi - ok
17:00:45.0223 4296 ws2ifsl (6bcc1d7d2fd2453957c5479a32364e52) C:\Windows\system32\drivers\ws2ifsl.sys
17:00:45.0239 4296 ws2ifsl - ok
17:00:45.0270 4296 WSDPrintDevice (8d918b1db190a4d9b1753a66fa8c96e8) C:\Windows\system32\DRIVERS\WSDPrint.sys
17:00:45.0285 4296 WSDPrintDevice - ok
17:00:45.0317 4296 WudfPf (7cadc74271dd6461c452c271b30bd378) C:\Windows\system32\drivers\WudfPf.sys
17:00:45.0317 4296 WudfPf - ok
17:00:45.0348 4296 WUDFRd (3b197af0fff08aa66b6b2241ca538d64) C:\Windows\system32\DRIVERS\WUDFRd.sys
17:00:45.0348 4296 WUDFRd - ok
17:00:45.0379 4296 MBR (0x1B8) (5c616939100b85e558da92b899a0fc36) \Device\Harddisk0\DR0
17:00:45.0426 4296 \Device\Harddisk0\DR0 - ok
17:00:45.0426 4296 Boot (0x1200) (b312b499cf1fbbb0e1ea0d8a442b3878) \Device\Harddisk0\DR0\Partition0
17:00:45.0441 4296 \Device\Harddisk0\DR0\Partition0 - ok
17:00:45.0441 4296 Boot (0x1200) (d67adc0b2e566bf8f52b4ab7a2cf5dea) \Device\Harddisk0\DR0\Partition1
17:00:45.0441 4296 \Device\Harddisk0\DR0\Partition1 - ok
17:00:45.0441 4296 ============================================================
17:00:45.0441 4296 Scan finished
17:00:45.0441 4296 ============================================================
17:00:45.0457 6332 Detected object count: 1
17:00:45.0457 6332 Actual detected object count: 1
17:01:09.0607 6332 sptd ( LockedFile.Multi.Generic ) - skipped by user
17:01:09.0607 6332 sptd ( LockedFile.Multi.Generic ) - User select action: Skip


MBR Log:

aswMBR version 0.9.9.1532 Copyright© 2011 AVAST Software
Run date: 2012-02-04 17:03:12
-----------------------------
17:03:12.208 OS Version: Windows x64 6.1.7600
17:03:12.208 Number of processors: 8 586 0x1E05
17:03:12.208 ComputerName: JEFF-XPS UserName: Jeff
17:03:13.409 Initialize success
17:03:24.339 Disk 0 (boot) \Device\Harddisk0\DR0 -> \Device\Ide\IAAStorageDevice-1
17:03:24.354 Disk 0 Vendor: WDC_WD32 11.0 Size: 305245MB BusType: 3
17:03:24.385 Disk 0 MBR read successfully
17:03:24.385 Disk 0 MBR scan
17:03:24.385 Disk 0 Windows VISTA default MBR code
17:03:24.401 Disk 0 Partition 1 00 DE Dell Utility Dell 8.0 39 MB offset 63
17:03:24.448 Disk 0 Partition 2 80 (A) 07 HPFS/NTFS NTFS 15000 MB offset 80325
17:03:24.463 Disk 0 Partition 3 00 07 HPFS/NTFS NTFS 290205 MB offset 30800325
17:03:24.463 Service scanning
17:03:25.306 Service sptd C:\Windows\System32\Drivers\sptd.sys **LOCKED** 32
17:03:25.883 Modules scanning
17:03:25.883 Disk 0 trace - called modules:
17:03:25.899 ntoskrnl.exe CLASSPNP.SYS disk.sys iaStor.sys spky.sys hal.dll
17:03:25.899 1 nt!IofCallDriver -> \Device\Harddisk0\DR0[0xfffffa80063b8060]
17:03:25.914 3 CLASSPNP.SYS[fffff88000fa043f] -> nt!IofCallDriver -> \Device\Ide\IAAStorageDevice-1[0xfffffa8006253050]
17:03:25.914 Scan finished successfully
17:03:44.322 Disk 0 MBR has been saved successfully to "C:\Users\Jeff\Desktop\MBR.dat"
17:03:44.338 The log file has been saved successfully to "C:\Users\Jeff\Desktop\aswMBR.txt"

#6 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,416 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:20 AM

Posted 04 February 2012 - 09:24 PM

Download following firewall fix: http://download.bleepingcomputer.com/sUBs/MiniFixes/RestoreBFE.exe
Double click on downloaded file to run the fix.

Restart computer.

See if you can turn Windows firewall on now
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#7 Jeff231

Jeff231
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:02:20 AM

Posted 04 February 2012 - 10:36 PM

It worked! Thank you so much for your help.

#8 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,416 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:20 AM

Posted 05 February 2012 - 11:25 AM

You're welcome! If there are no more problems or signs of infection, you should Create a New Restore Point to prevent possible reinfection from an old one. Some of the malware you picked up could have been backed up, renamed and saved in System Restore. Since this is a protected directory your tools cannot access to delete these files, they sometimes can reinfect your system if you accidentally use an old restore point. Setting a new restore point AFTER cleaning your system will help prevent this and enable your computer to "roll-back" to a clean working state.

The easiest and safest way to do this is:
  • Go to Posted Image > Programs > Accessories > System Tools and click "System Restore".
  • Choose the radio button marked "Create a Restore Point" on the first screen then click "Next". Give the R.P. a name, then click "Create". The new point will be stamped with the current date and time. Keep a log of this so you can find it easily should you need to use System Restore.
  • Then use Disk Cleanup to remove all but the most recently created Restore Point.
  • Go to Posted Image > Run... and type: Cleanmgr
  • Click "Ok". Disk Cleanup will scan your files for several minutes, then open.
  • Click the "More Options" tab, then click the "Clean up" button under System Restore.
  • Click Ok. You will be prompted with "Are you sure you want to delete all but the most recent restore point?"
  • Click Yes, then click Ok.
  • Click Yes again when prompted with "Are you sure you want to perform these actions?"
  • Disk Cleanup will remove the files and close automatically.
Vista and Windows 7 users can refer to these links:
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users