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

ihf.exe - Entry Point Not Found


  • Please log in to reply
10 replies to this topic

#1 fastred04R1

fastred04R1

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:02:05 PM

Posted 17 December 2011 - 10:16 PM

Left my computer on earlier today when I went out and came back to a prompt on the screen saying

ihf.exe - Entry Point Not Found
The procedure entry point MSWSOCK.MigrateWinsockConfiguration could not be located in the dynamic link libraby WSOCK32.dll.

None of the programs I have tried to run will work and the computer won't even connect to the internet.

Please help...

BC AdBot (Login to Remove)

 


#2 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,490 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:05:05 PM

Posted 17 December 2011 - 10:56 PM

Hello fastred04R1
Can you download and eun these off a Flash drive or CD?

Save mbam-setup.exe to a flash,usb,jump drive or CD. Now transfer it to the infected machine, then install and run the program.
If you cannot transfer to or install on the infected machine, try running the setup (installation) file directly from the flash drive or CD by double-clicking on mbam-setup.exe so it will install on the hard drive.


Full instructions
Next run MBAM (MalwareBytes):

Please download Malwarebytes Anti-Malware and save it to your desktop.
Download Link 1 <<<== Use this one first.

Download Link 2MBAM may "make changes to your registry" as part of its disinfection routine. If using other security programs that detect registry changes (ie Spybot's Teatimer), they may interfere or alert you. Temporarily disable such programs or permit them to allow the changes.
  • Make sure you are connected to the Internet.
  • Double-click on mbam-setup.exe to install the application.
    For instructions with screenshots, please refer to the How to use Malwarebytes' Anti-Malware Guide.
  • When the installation begins, follow the prompts and do not make any changes to default settings.
  • When installation has finished, make sure you leave both of these checked:
    • Update Malwarebytes' Anti-Malware
    • Launch Malwarebytes' Anti-Malware
  • Then click Finish.
MBAM will automatically start and you will be asked to update the program before performing a scan.
  • If an update is found, the program will automatically update itself. Press the OK button to close that box and continue.
  • If you encounter any problems while downloading the definition updates, manually download them from here and just double-click on mbam-rules.exe to install.
On the Scanner tab:
  • Make sure the "Perform Quick Scan" option is selected.
  • Then click on the Scan button.
  • If asked to select the drives to scan, leave all the drives selected and click on the Start Scan button.
  • The scan will begin and "Scan in progress" will show at the top. It may take some time to complete so please be patient.
  • When the scan is finished, a message box will say "The scan completed successfully. Click 'Show Results' to display all objects found".
  • Click OK to close the message box and continue with the removal process.
Back at the main Scanner screen:
  • Click on the Show Results button to see a list of any malware that was found.
  • Make sure that everything is checked, and click Remove Selected.
  • When removal is completed, a log report will open in Notepad.
  • The log is automatically saved and can be viewed by clicking the Logs tab in MBAM.
  • Copy and paste the contents of that report in your next reply. Be sure to post the complete log to include the top portion which shows MBAM's database version and your operating system.
  • Exit MBAM when done.
Note: If MBAM encounters a file that is difficult to remove, you will be asked to reboot your computer so MBAM can proceed with the disinfection process. If asked to restart the computer, please do so immediately. Failure to reboot normally (not into safe mode) will prevent MBAM from removing all the malware.

Troubleshoot Malwarebytes' Anti-Malware
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 fastred04R1

fastred04R1
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:02:05 PM

Posted 18 December 2011 - 01:42 PM

I saved that file to a flash drive and tried to run it but the computer still pops up with the same prompt every time I try to run any program. I was able to open "My Computer" and select on the removable disk which pulls up the mbam-setup but when I click on it the same prompt pulls up on the screen every time. I even tried to go in and run it from the run option on the start menu and browsed to the removable disk but it still won't do anything.

#4 fastred04R1

fastred04R1
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:02:05 PM

Posted 18 December 2011 - 01:53 PM

I tried the suggestion in the other thread about having trouble running mbam and was able to change the extension and get the program to install but now it pops up with a prompt that says

An error has occurred. Please report this to our support team.
PROGRAM_ERROR_UPDATING (11004, 0, No address found)
The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for.

#5 fastred04R1

fastred04R1
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:02:05 PM

Posted 18 December 2011 - 02:00 PM

When I clicked ok on the prompt that I posted in the last reply the program started to run. I am now running the quick scan and will post a reply with the text log when the scan finishes.

#6 fastred04R1

fastred04R1
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:02:05 PM

Posted 18 December 2011 - 02:04 PM

Malwarebytes' Anti-Malware 1.51.2.1300
www.malwarebytes.org

Database version: 7622

Windows 5.1.2600 Service Pack 3
Internet Explorer 8.0.6001.18702

12/18/2011 12:00:41 PM
mbam-log-2011-12-18 (12-00-41).txt

Scan type: Quick scan
Objects scanned: 153295
Time elapsed: 4 minute(s), 25 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 1
Registry Data Items Infected: 6
Folders Infected: 0
Files Infected: 1

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
HKEY_CLASSES_ROOT\.exe\shell\open\command\(default) (Hijack.ExeFile) -> Value: (default) -> Quarantined and deleted successfully.

Registry Data Items Infected:
HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\FIREFOX.EXE\shell\open\command\(default) (Hijack.StartMenuInternet) -> Bad: ("C:\Documents and Settings\Owner\Local Settings\Application Data\ihf.exe" -a "C:\Program Files\Mozilla Firefox\firefox.exe") Good: (firefox.exe) -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\FIREFOX.EXE\shell\safemode\command\(default) (Hijack.StartMenuInternet) -> Bad: ("C:\Documents and Settings\Owner\Local Settings\Application Data\ihf.exe" -a "C:\Program Files\Mozilla Firefox\firefox.exe" -safe-mode) Good: (firefox.exe -safe-mode) -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\IEXPLORE.EXE\shell\open\command\(default) (Hijack.StartMenuInternet) -> Bad: ("C:\Documents and Settings\Owner\Local Settings\Application Data\ihf.exe" -a "C:\Program Files\Internet Explorer\iexplore.exe") Good: (iexplore.exe) -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\AntiVirusDisableNotify (PUM.Disabled.SecurityCenter) -> Bad: (1) Good: (0) -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\FirewallDisableNotify (PUM.Disabled.SecurityCenter) -> Bad: (1) Good: (0) -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\UpdatesDisableNotify (PUM.Disabled.SecurityCenter) -> Bad: (1) Good: (0) -> Quarantined and deleted successfully.

Folders Infected:
(No malicious items detected)

Files Infected:
c:\documents and settings\Owner\local settings\Temp\wpbt0.dll (Exploit.Drop) -> Quarantined and deleted successfully.

#7 fastred04R1

fastred04R1
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:02:05 PM

Posted 18 December 2011 - 02:08 PM

The computer rebooted after the program ran and said it successfully quarantined the infections but the same prompt original prompt still popped up when the computer finished rebooting.

#8 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,490 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:05:05 PM

Posted 18 December 2011 - 02:48 PM

Hello, good job.
Rerun MBAM (MalwareBytes) like this:

Open MBAM in normal/regular mode and click Update tab, select Check for Updates,when done
click Scanner tab,select FULL scan and scan (normal mode).
After scan click Remove Selected, Post new scan log and Reboot into normal mode.


>>>>
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.

>>>>


Reboot into Safe Mode with Networking
How to enter safe mode(XP/Vista)
Using the F8 Method
Restart your computer.
When the machine first starts again it will generally list some equipment that is installed in your machine, amount of memory, hard drives installed etc. At this point you should gently tap the F8 key repeatedly until you are presented with a Windows XP Advanced Options menu.
Select the option for Safe Mode with Networking using the arrow keys.
Then press enter on your keyboard to boot into Safe Mode
.


>>>> Download this file and doubleclick on it to run it. Allow the information to be merged with the registry.

Run RKill....


Download and Run RKill
  • Please download RKill by Grinler from one of the 4 links below and save it to your desktop.

    Link 1
    Link 2
    Link 3
    Link 4

  • Before we begin, you should disable your anti-malware softwares you have installed so they do not interfere RKill running as some anti-malware softwares detect RKill as malicious. Please refer to this page if you are not sure how.
  • Double-click on Rkill on your desktop to run it. (If you are using Windows Vista, please right-click on it and select Run As Administrator)
  • A black screen will appear and then disappear. Please do not worry, that is normal. This means that the tool has been successfully executed.
  • If nothing happens or if the tool does not run, please let me know in your next reply

Do not reboot your computer after running rkill as the malware programs will start again. Or if rebooting is required run it again.


If you continue having problems running rkill.com, you can download iExplore.exe or eXplorer.exe, which are renamed copies of rkill.com, and try them instead.



Next run Superantisypware (SAS):

Download and scan with SUPERAntiSpyware Free for Home Users
  • Double-click SUPERAntiSpyware.exe and use the default settings for installation.
  • An icon will be created on your desktop. Double-click that icon to launch the program.
  • If asked to update the program definitions, click "Yes". If not, update the definitions before scanning by selecting "Check for Updates". (If you encounter any problems while downloading the updates, manually download them from here. Double-click on the hyperlink for Download Installer and save SASDEFINITIONS.EXE to your desktop. Then double-click on SASDEFINITIONS.EXE to install the definitions.)
  • In the Main Menu, click the Preferences... button.
  • Click the Scanning Control tab.
  • Under Scanner Options make sure the following are checked (leave all others unchecked):
    • Close browsers before scanning.
    • Scan for tracking cookies.
    • Terminate memory threats before quarantining.
  • Click the "Close" button to leave the control center screen.
  • Back on the main screen, under "Scan for Harmful Software" click Scan your computer.
  • On the left, make sure you check C:\Fixed Drive.
  • On the right, under "Complete Scan", choose Perform Complete Scan.
  • Click "Next" to start the scan. Please be patient while it scans your computer.
  • After the scan is complete, a Scan Summary box will appear with potentially harmful items that were detected. Click "OK".
  • Make sure everything has a checkmark next to it and click "Next".
  • A notification will appear that "Quarantine and Removal is Complete". Click "OK" and then click the "Finish" button to return to the main menu.
  • If asked if you want to reboot, click "Yes".
  • To retrieve the removal information after reboot, launch SUPERAntispyware again.
    • Click Preferences, then click the Statistics/Logs tab.
    • Under Scanner Logs, double-click SUPERAntiSpyware Scan Log.
    • If there are several logs, click the current dated log and press View log. A text file will open in your default text editor.
    • Please copy and paste the Scan Log results in your next reply.
  • Click Close to exit the program.
If you have a problem downloading, installing or getting SAS to run, try downloading and using the [COLOR=blue]SUPERAntiSpyware Portable Scanner
instead. Save the randomly named file (i.e. SAS_1710895.COM) to a usb drive or CD and transfer to the infected computer. Then double-click on it to launch and scan. The file is randomly named to help keep malware from blocking the scanner.




Please ask any needed questions,post MBAM,TDSS,RKill and SAS logs and Let us know how the PC is running 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

#9 fastred04R1

fastred04R1
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:02:05 PM

Posted 18 December 2011 - 05:26 PM

I ran each of the 4 programs listed in the last reply. here are the logs from each

1. MBAM Log

Malwarebytes' Anti-Malware 1.51.2.1300
www.malwarebytes.org

Database version: 7622

Windows 5.1.2600 Service Pack 3 (Safe Mode)
Internet Explorer 8.0.6001.18702

12/18/2011 2:10:14 PM
mbam-log-2011-12-18 (14-10-14).txt

Scan type: Full scan (C:\|D:\|E:\|)
Objects scanned: 189205
Time elapsed: 19 minute(s), 56 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 0
Files Infected: 0

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:
(No malicious items detected)


2. TDSSKiller Log

13:34:39.0890 0248 TDSS rootkit removing tool 2.6.23.0 Dec 13 2011 10:39:31
13:34:39.0937 0248 ============================================================
13:34:39.0937 0248 Current date / time: 2011/12/18 13:34:39.0937
13:34:39.0937 0248 SystemInfo:
13:34:39.0937 0248
13:34:39.0937 0248 OS Version: 5.1.2600 ServicePack: 3.0
13:34:39.0937 0248 Product type: Workstation
13:34:39.0937 0248 ComputerName: HOME-73CD2638D7
13:34:39.0937 0248 UserName: Owner
13:34:39.0937 0248 Windows directory: C:\WINDOWS
13:34:39.0937 0248 System windows directory: C:\WINDOWS
13:34:39.0937 0248 Processor architecture: Intel x86
13:34:39.0937 0248 Number of processors: 1
13:34:39.0937 0248 Page size: 0x1000
13:34:39.0937 0248 Boot type: Normal boot
13:34:39.0937 0248 ============================================================
13:34:41.0609 0248 Initialize success
13:34:46.0187 1416 ============================================================
13:34:46.0187 1416 Scan started
13:34:46.0187 1416 Mode: Manual;
13:34:46.0187 1416 ============================================================
13:34:47.0921 1416 Scan interrupted by user!
13:34:47.0921 1416 Scan interrupted by user!
13:34:47.0921 1416 Scan interrupted by user!
13:34:47.0921 1416 ============================================================
13:34:47.0921 1416 Scan finished
13:34:47.0921 1416 ============================================================
13:34:47.0937 1428 Detected object count: 0
13:34:47.0937 1428 Actual detected object count: 0
13:34:50.0609 4056 ============================================================
13:34:50.0609 4056 Scan started
13:34:50.0609 4056 Mode: Manual;
13:34:50.0609 4056 ============================================================
13:34:50.0859 4056 Abiosdsk - ok
13:34:50.0890 4056 abp480n5 - ok
13:34:50.0984 4056 ACPI (8fd99680a539792a30e97944fdaecf17) C:\WINDOWS\system32\DRIVERS\ACPI.sys
13:34:51.0000 4056 ACPI - ok
13:34:51.0062 4056 ACPIEC (9859c0f6936e723e4892d7141b1327d5) C:\WINDOWS\system32\drivers\ACPIEC.sys
13:34:51.0062 4056 ACPIEC - ok
13:34:51.0125 4056 ADM8511 (b05f2367f62552a2de7e3c352b7b9885) C:\WINDOWS\system32\DRIVERS\ADM8511.SYS
13:34:51.0140 4056 ADM8511 - ok
13:34:51.0171 4056 adpu160m - ok
13:34:51.0234 4056 aec (8bed39e3c35d6a489438b8141717a557) C:\WINDOWS\system32\drivers\aec.sys
13:34:51.0250 4056 aec - ok
13:34:51.0343 4056 AFD (1e44bc1e83d8fd2305f8d452db109cf9) C:\WINDOWS\System32\drivers\afd.sys
13:34:51.0359 4056 AFD - ok
13:34:51.0390 4056 Aha154x - ok
13:34:51.0421 4056 aic78u2 - ok
13:34:51.0453 4056 aic78xx - ok
13:34:51.0500 4056 AliIde - ok
13:34:51.0531 4056 amsint - ok
13:34:51.0609 4056 ApfiltrService (090880e9bf20f928bc341f96d27c019e) C:\WINDOWS\system32\DRIVERS\Apfiltr.sys
13:34:51.0609 4056 ApfiltrService - ok
13:34:51.0656 4056 asc - ok
13:34:51.0687 4056 asc3350p - ok
13:34:51.0718 4056 asc3550 - ok
13:34:51.0781 4056 AsyncMac (b153affac761e7f5fcfa822b9c4e97bc) C:\WINDOWS\system32\DRIVERS\asyncmac.sys
13:34:51.0781 4056 AsyncMac - ok
13:34:51.0812 4056 atapi (9f3a2f5aa6875c72bf062c712cfa2674) C:\WINDOWS\system32\DRIVERS\atapi.sys
13:34:51.0812 4056 atapi - ok
13:34:51.0843 4056 Atdisk - ok
13:34:51.0984 4056 ati2mtag (2a6c99cfdc23c9c26d0e30b1c99748d4) C:\WINDOWS\system32\DRIVERS\ati2mtag.sys
13:34:52.0046 4056 ati2mtag - ok
13:34:52.0218 4056 Atmarpc (9916c1225104ba14794209cfa8012159) C:\WINDOWS\system32\DRIVERS\atmarpc.sys
13:34:52.0218 4056 Atmarpc - ok
13:34:52.0296 4056 audstub (d9f724aa26c010a217c97606b160ed68) C:\WINDOWS\system32\DRIVERS\audstub.sys
13:34:52.0296 4056 audstub - ok
13:34:52.0375 4056 AVGIDSDriver (4fa401b33c1b50c816486f6951244a14) C:\WINDOWS\system32\DRIVERS\AVGIDSDriver.Sys
13:34:52.0390 4056 AVGIDSDriver - ok
13:34:52.0421 4056 AVGIDSEH (69578bc9d43d614c6b3455db4af19762) C:\WINDOWS\system32\DRIVERS\AVGIDSEH.Sys
13:34:52.0421 4056 AVGIDSEH - ok
13:34:52.0453 4056 AVGIDSFilter (6df528406aa22201f392b9b19121cd6f) C:\WINDOWS\system32\DRIVERS\AVGIDSFilter.Sys
13:34:52.0468 4056 AVGIDSFilter - ok
13:34:52.0500 4056 AVGIDSShim (07eba0c11fa1d73b82ecc3255ddfe34d) C:\WINDOWS\system32\DRIVERS\AVGIDSShim.Sys
13:34:52.0500 4056 AVGIDSShim - ok
13:34:52.0593 4056 Avgldx86 (f4dbbc8d3c5338693da23c59a50f8abc) C:\WINDOWS\system32\DRIVERS\avgldx86.sys
13:34:52.0593 4056 Avgldx86 - ok
13:34:52.0640 4056 Avgmfx86 (1c77ef67f196466adc9924cb288afe87) C:\WINDOWS\system32\DRIVERS\avgmfx86.sys
13:34:52.0640 4056 Avgmfx86 - ok
13:34:52.0703 4056 Avgrkx86 (f2038ed7284b79dcef581468121192a9) C:\WINDOWS\system32\DRIVERS\avgrkx86.sys
13:34:52.0703 4056 Avgrkx86 - ok
13:34:52.0781 4056 Avgtdix (929cdadeee5b27b3d4aeecaa9e97642e) C:\WINDOWS\system32\DRIVERS\avgtdix.sys
13:34:52.0781 4056 Avgtdix - ok
13:34:52.0875 4056 b57w2k (2acf06176b9d011567d7f25b83ddd066) C:\WINDOWS\system32\DRIVERS\b57xp32.sys
13:34:52.0890 4056 b57w2k - ok
13:34:53.0000 4056 Beep (da1f27d85e0d1525f6621372e7b685e9) C:\WINDOWS\system32\drivers\Beep.sys
13:34:53.0000 4056 Beep - ok
13:34:53.0109 4056 BVRPMPR5 (248dfa5762dde38dfddbbd44149e9d7a) C:\WINDOWS\system32\drivers\BVRPMPR5.SYS
13:34:53.0109 4056 BVRPMPR5 - ok
13:34:53.0171 4056 cbidf2k (90a673fc8e12a79afbed2576f6a7aaf9) C:\WINDOWS\system32\drivers\cbidf2k.sys
13:34:53.0187 4056 cbidf2k - ok
13:34:53.0250 4056 CCDECODE (0be5aef125be881c4f854c554f2b025c) C:\WINDOWS\system32\DRIVERS\CCDECODE.sys
13:34:53.0250 4056 CCDECODE - ok
13:34:53.0281 4056 cd20xrnt - ok
13:34:53.0312 4056 Cdaudio (c1b486a7658353d33a10cc15211a873b) C:\WINDOWS\system32\drivers\Cdaudio.sys
13:34:53.0328 4056 Cdaudio - ok
13:34:53.0406 4056 Cdfs (c885b02847f5d2fd45a24e219ed93b32) C:\WINDOWS\system32\drivers\Cdfs.sys
13:34:53.0406 4056 Cdfs - ok
13:34:53.0453 4056 Cdrom (1f4260cc5b42272d71f79e570a27a4fe) C:\WINDOWS\system32\DRIVERS\cdrom.sys
13:34:53.0453 4056 Cdrom - ok
13:34:53.0484 4056 Changer - ok
13:34:53.0546 4056 CmBatt (0f6c187d38d98f8df904589a5f94d411) C:\WINDOWS\system32\DRIVERS\CmBatt.sys
13:34:53.0546 4056 CmBatt - ok
13:34:53.0578 4056 CmdIde - ok
13:34:53.0609 4056 Compbatt (6e4c9f21f0fae8940661144f41b13203) C:\WINDOWS\system32\DRIVERS\compbatt.sys
13:34:53.0609 4056 Compbatt - ok
13:34:53.0656 4056 Cpqarray - ok
13:34:53.0703 4056 dac2w2k - ok
13:34:53.0734 4056 dac960nt - ok
13:34:53.0781 4056 Disk (044452051f3e02e7963599fc8f4f3e25) C:\WINDOWS\system32\DRIVERS\disk.sys
13:34:53.0781 4056 Disk - ok
13:34:53.0875 4056 dmboot (d992fe1274bde0f84ad826acae022a41) C:\WINDOWS\system32\drivers\dmboot.sys
13:34:53.0921 4056 dmboot - ok
13:34:54.0015 4056 dmio (7c824cf7bbde77d95c08005717a95f6f) C:\WINDOWS\system32\drivers\dmio.sys
13:34:54.0015 4056 dmio - ok
13:34:54.0078 4056 dmload (e9317282a63ca4d188c0df5e09c6ac5f) C:\WINDOWS\system32\drivers\dmload.sys
13:34:54.0078 4056 dmload - ok
13:34:54.0140 4056 DMusic (8a208dfcf89792a484e76c40e5f50b45) C:\WINDOWS\system32\drivers\DMusic.sys
13:34:54.0156 4056 DMusic - ok
13:34:54.0187 4056 dpti2o - ok
13:34:54.0234 4056 drmkaud (8f5fcff8e8848afac920905fbd9d33c8) C:\WINDOWS\system32\drivers\drmkaud.sys
13:34:54.0234 4056 drmkaud - ok
13:34:54.0312 4056 Fastfat (38d332a6d56af32635675f132548343e) C:\WINDOWS\system32\drivers\Fastfat.sys
13:34:54.0312 4056 Fastfat - ok
13:34:54.0390 4056 Fdc (92cdd60b6730b9f50f6a1a0c1f8cdc81) C:\WINDOWS\system32\drivers\Fdc.sys
13:34:54.0390 4056 Fdc - ok
13:34:54.0468 4056 Fips (d45926117eb9fa946a6af572fbe1caa3) C:\WINDOWS\system32\drivers\Fips.sys
13:34:54.0468 4056 Fips - ok
13:34:54.0500 4056 Flpydisk (9d27e7b80bfcdf1cdd9b555862d5e7f0) C:\WINDOWS\system32\drivers\Flpydisk.sys
13:34:54.0515 4056 Flpydisk - ok
13:34:54.0562 4056 FltMgr (b2cf4b0786f8212cb92ed2b50c6db6b0) C:\WINDOWS\system32\drivers\fltmgr.sys
13:34:54.0562 4056 FltMgr - ok
13:34:54.0593 4056 Fs_Rec (3e1e2bd4f39b0e2b7dc4f4d2bcc2779a) C:\WINDOWS\system32\drivers\Fs_Rec.sys
13:34:54.0593 4056 Fs_Rec - ok
13:34:54.0640 4056 Ftdisk (6ac26732762483366c3969c9e4d2259d) C:\WINDOWS\system32\DRIVERS\ftdisk.sys
13:34:54.0640 4056 Ftdisk - ok
13:34:54.0718 4056 GEARAspiWDM (8182ff89c65e4d38b2de4bb0fb18564e) C:\WINDOWS\system32\DRIVERS\GEARAspiWDM.sys
13:34:54.0734 4056 GEARAspiWDM - ok
13:34:54.0765 4056 Gpc (0a02c63c8b144bd8c86b103dee7c86a2) C:\WINDOWS\system32\DRIVERS\msgpc.sys
13:34:54.0781 4056 Gpc - ok
13:34:54.0859 4056 GTIPCI21 (ca835331825599b938e37525796d3549) C:\WINDOWS\system32\DRIVERS\gtipci21.sys
13:34:54.0859 4056 GTIPCI21 - ok
13:34:54.0921 4056 hpn - ok
13:34:55.0000 4056 HSFHWICH (a84bbbdd125d370593004f6429f8445c) C:\WINDOWS\system32\DRIVERS\HSFHWICH.sys
13:34:55.0015 4056 HSFHWICH - ok
13:34:55.0171 4056 HSF_DPV (b678fa91cf4a1c19b462d8db04cd02ab) C:\WINDOWS\system32\DRIVERS\HSF_DPV.SYS
13:34:55.0234 4056 HSF_DPV - ok
13:34:55.0312 4056 HTTP (f80a415ef82cd06ffaf0d971528ead38) C:\WINDOWS\system32\Drivers\HTTP.sys
13:34:55.0328 4056 HTTP - ok
13:34:55.0359 4056 i2omgmt - ok
13:34:55.0390 4056 i2omp - ok
13:34:55.0453 4056 i8042prt (4a0b06aa8943c1e332520f7440c0aa30) C:\WINDOWS\system32\DRIVERS\i8042prt.sys
13:34:55.0453 4056 i8042prt - ok
13:34:55.0484 4056 Imapi (083a052659f5310dd8b6a6cb05edcf8e) C:\WINDOWS\system32\DRIVERS\imapi.sys
13:34:55.0500 4056 Imapi - ok
13:34:55.0531 4056 ini910u - ok
13:34:55.0593 4056 IntelIde (b5466a9250342a7aa0cd1fba13420678) C:\WINDOWS\system32\DRIVERS\intelide.sys
13:34:55.0593 4056 IntelIde - ok
13:34:55.0656 4056 intelppm (8c953733d8f36eb2133f5bb58808b66b) C:\WINDOWS\system32\DRIVERS\intelppm.sys
13:34:55.0656 4056 intelppm - ok
13:34:55.0718 4056 Ip6Fw (3bb22519a194418d5fec05d800a19ad0) C:\WINDOWS\system32\drivers\ip6fw.sys
13:34:55.0718 4056 Ip6Fw - ok
13:34:55.0765 4056 IpFilterDriver (731f22ba402ee4b62748adaf6363c182) C:\WINDOWS\system32\DRIVERS\ipfltdrv.sys
13:34:55.0765 4056 IpFilterDriver - ok
13:34:55.0812 4056 IpInIp (b87ab476dcf76e72010632b5550955f5) C:\WINDOWS\system32\DRIVERS\ipinip.sys
13:34:55.0828 4056 IpInIp - ok
13:34:55.0937 4056 IpNat (cc748ea12c6effde940ee98098bf96bb) C:\WINDOWS\system32\DRIVERS\ipnat.sys
13:34:55.0937 4056 IpNat - ok
13:34:56.0000 4056 IPSec (23c74d75e36e7158768dd63d92789a91) C:\WINDOWS\system32\DRIVERS\ipsec.sys
13:34:56.0000 4056 IPSec - ok
13:34:56.0062 4056 IRENUM (c93c9ff7b04d772627a3646d89f7bf89) C:\WINDOWS\system32\DRIVERS\irenum.sys
13:34:56.0062 4056 IRENUM - ok
13:34:56.0109 4056 isapnp (05a299ec56e52649b1cf2fc52d20f2d7) C:\WINDOWS\system32\DRIVERS\isapnp.sys
13:34:56.0109 4056 isapnp - ok
13:34:56.0140 4056 Kbdclass (463c1ec80cd17420a542b7f36a36f128) C:\WINDOWS\system32\DRIVERS\kbdclass.sys
13:34:56.0140 4056 Kbdclass - ok
13:34:56.0218 4056 kmixer (692bcf44383d056aed41b045a323d378) C:\WINDOWS\system32\drivers\kmixer.sys
13:34:56.0218 4056 kmixer - ok
13:34:56.0265 4056 KSecDD (b467646c54cc746128904e1654c750c1) C:\WINDOWS\system32\drivers\KSecDD.sys
13:34:56.0281 4056 KSecDD - ok
13:34:56.0312 4056 lbrtfdc - ok
13:34:56.0390 4056 MBAMProtector (69a6268d7f81e53d568ab4e7e991caf3) C:\WINDOWS\system32\drivers\mbam.sys
13:34:56.0390 4056 MBAMProtector - ok
13:34:56.0468 4056 mdmxsdk (3c318b9cd391371bed62126581ee9961) C:\WINDOWS\system32\DRIVERS\mdmxsdk.sys
13:34:56.0468 4056 mdmxsdk - ok
13:34:56.0531 4056 mnmdd (4ae068242760a1fb6e1a44bf4e16afa6) C:\WINDOWS\system32\drivers\mnmdd.sys
13:34:56.0531 4056 mnmdd - ok
13:34:56.0593 4056 Modem (dfcbad3cec1c5f964962ae10e0bcc8e1) C:\WINDOWS\system32\drivers\Modem.sys
13:34:56.0593 4056 Modem - ok
13:34:56.0640 4056 Mouclass (35c9e97194c8cfb8430125f8dbc34d04) C:\WINDOWS\system32\DRIVERS\mouclass.sys
13:34:56.0640 4056 Mouclass - ok
13:34:56.0687 4056 MountMgr (a80b9a0bad1b73637dbcbba7df72d3fd) C:\WINDOWS\system32\drivers\MountMgr.sys
13:34:56.0687 4056 MountMgr - ok
13:34:56.0718 4056 mraid35x - ok
13:34:56.0765 4056 MRxDAV (11d42bb6206f33fbb3ba0288d3ef81bd) C:\WINDOWS\system32\DRIVERS\mrxdav.sys
13:34:56.0781 4056 MRxDAV - ok
13:34:56.0875 4056 MRxSmb (7d304a5eb4344ebeeab53a2fe3ffb9f0) C:\WINDOWS\system32\DRIVERS\mrxsmb.sys
13:34:56.0890 4056 MRxSmb - ok
13:34:56.0984 4056 Msfs (c941ea2454ba8350021d774daf0f1027) C:\WINDOWS\system32\drivers\Msfs.sys
13:34:56.0984 4056 Msfs - ok
13:34:57.0046 4056 MSKSSRV (d1575e71568f4d9e14ca56b7b0453bf1) C:\WINDOWS\system32\drivers\MSKSSRV.sys
13:34:57.0046 4056 MSKSSRV - ok
13:34:57.0093 4056 MSPCLOCK (325bb26842fc7ccc1fcce2c457317f3e) C:\WINDOWS\system32\drivers\MSPCLOCK.sys
13:34:57.0093 4056 MSPCLOCK - ok
13:34:57.0140 4056 MSPQM (bad59648ba099da4a17680b39730cb3d) C:\WINDOWS\system32\drivers\MSPQM.sys
13:34:57.0140 4056 MSPQM - ok
13:34:57.0203 4056 mssmbios (af5f4f3f14a8ea2c26de30f7a1e17136) C:\WINDOWS\system32\DRIVERS\mssmbios.sys
13:34:57.0203 4056 mssmbios - ok
13:34:57.0281 4056 MSTEE (e53736a9e30c45fa9e7b5eac55056d1d) C:\WINDOWS\system32\drivers\MSTEE.sys
13:34:57.0281 4056 MSTEE - ok
13:34:57.0343 4056 Mup (de6a75f5c270e756c5508d94b6cf68f5) C:\WINDOWS\system32\drivers\Mup.sys
13:34:57.0343 4056 Mup - ok
13:34:57.0406 4056 NABTSFEC (5b50f1b2a2ed47d560577b221da734db) C:\WINDOWS\system32\DRIVERS\NABTSFEC.sys
13:34:57.0406 4056 NABTSFEC - ok
13:34:57.0484 4056 NDIS (1df7f42665c94b825322fae71721130d) C:\WINDOWS\system32\drivers\NDIS.sys
13:34:57.0484 4056 NDIS - ok
13:34:57.0531 4056 NdisIP (7ff1f1fd8609c149aa432f95a8163d97) C:\WINDOWS\system32\DRIVERS\NdisIP.sys
13:34:57.0546 4056 NdisIP - ok
13:34:57.0609 4056 NdisTapi (0109c4f3850dfbab279542515386ae22) C:\WINDOWS\system32\DRIVERS\ndistapi.sys
13:34:57.0609 4056 NdisTapi - ok
13:34:57.0687 4056 Ndisuio (f927a4434c5028758a842943ef1a3849) C:\WINDOWS\system32\DRIVERS\ndisuio.sys
13:34:57.0703 4056 Ndisuio - ok
13:34:57.0734 4056 NdisWan (edc1531a49c80614b2cfda43ca8659ab) C:\WINDOWS\system32\DRIVERS\ndiswan.sys
13:34:57.0734 4056 NdisWan - ok
13:34:57.0796 4056 NDProxy (9282bd12dfb069d3889eb3fcc1000a9b) C:\WINDOWS\system32\drivers\NDProxy.sys
13:34:57.0796 4056 NDProxy - ok
13:34:57.0843 4056 NetBIOS (5d81cf9a2f1a3a756b66cf684911cdf0) C:\WINDOWS\system32\DRIVERS\netbios.sys
13:34:57.0843 4056 NetBIOS - ok
13:34:57.0906 4056 NetBT (74b2b2f5bea5e9a3dc021d685551bd3d) C:\WINDOWS\system32\DRIVERS\netbt.sys
13:34:57.0906 4056 NetBT - ok
13:34:57.0984 4056 Npfs (3182d64ae053d6fb034f44b6def8034a) C:\WINDOWS\system32\drivers\Npfs.sys
13:34:57.0984 4056 Npfs - ok
13:34:58.0046 4056 Ntfs (78a08dd6a8d65e697c18e1db01c5cdca) C:\WINDOWS\system32\drivers\Ntfs.sys
13:34:58.0078 4056 Ntfs - ok
13:34:58.0187 4056 Null (73c1e1f395918bc2c6dd67af7591a3ad) C:\WINDOWS\system32\drivers\Null.sys
13:34:58.0187 4056 Null - ok
13:34:58.0265 4056 NwlnkFlt (b305f3fad35083837ef46a0bbce2fc57) C:\WINDOWS\system32\DRIVERS\nwlnkflt.sys
13:34:58.0265 4056 NwlnkFlt - ok
13:34:58.0296 4056 NwlnkFwd (c99b3415198d1aab7227f2c88fd664b9) C:\WINDOWS\system32\DRIVERS\nwlnkfwd.sys
13:34:58.0296 4056 NwlnkFwd - ok
13:34:58.0359 4056 Parport (5575faf8f97ce5e713d108c2a58d7c7c) C:\WINDOWS\system32\drivers\Parport.sys
13:34:58.0375 4056 Parport - ok
13:34:58.0390 4056 PartMgr (beb3ba25197665d82ec7065b724171c6) C:\WINDOWS\system32\drivers\PartMgr.sys
13:34:58.0406 4056 PartMgr - ok
13:34:58.0468 4056 ParVdm (70e98b3fd8e963a6a46a2e6247e0bea1) C:\WINDOWS\system32\drivers\ParVdm.sys
13:34:58.0468 4056 ParVdm - ok
13:34:58.0515 4056 PCI (a219903ccf74233761d92bef471a07b1) C:\WINDOWS\system32\DRIVERS\pci.sys
13:34:58.0515 4056 PCI - ok
13:34:58.0546 4056 PCIDump - ok
13:34:58.0593 4056 PCIIde (ccf5f451bb1a5a2a522a76e670000ff0) C:\WINDOWS\system32\drivers\PCIIde.sys
13:34:58.0593 4056 PCIIde - ok
13:34:58.0625 4056 Pcmcia (9e89ef60e9ee05e3f2eef2da7397f1c1) C:\WINDOWS\system32\DRIVERS\pcmcia.sys
13:34:58.0640 4056 Pcmcia - ok
13:34:58.0671 4056 PDCOMP - ok
13:34:58.0703 4056 PDFRAME - ok
13:34:58.0734 4056 PDRELI - ok
13:34:58.0765 4056 PDRFRAME - ok
13:34:58.0796 4056 perc2 - ok
13:34:58.0828 4056 perc2hib - ok
13:34:58.0921 4056 PptpMiniport (efeec01b1d3cf84f16ddd24d9d9d8f99) C:\WINDOWS\system32\DRIVERS\raspptp.sys
13:34:58.0921 4056 PptpMiniport - ok
13:34:58.0984 4056 PSched (09298ec810b07e5d582cb3a3f9255424) C:\WINDOWS\system32\DRIVERS\psched.sys
13:34:59.0000 4056 PSched - ok
13:34:59.0031 4056 Ptilink (80d317bd1c3dbc5d4fe7b1678c60cadd) C:\WINDOWS\system32\DRIVERS\ptilink.sys
13:34:59.0031 4056 Ptilink - ok
13:34:59.0078 4056 PxHelp20 (e42e3433dbb4cffe8fdd91eab29aea8e) C:\WINDOWS\system32\Drivers\PxHelp20.sys
13:34:59.0078 4056 PxHelp20 - ok
13:34:59.0109 4056 ql1080 - ok
13:34:59.0140 4056 Ql10wnt - ok
13:34:59.0171 4056 ql12160 - ok
13:34:59.0203 4056 ql1240 - ok
13:34:59.0250 4056 ql1280 - ok
13:34:59.0281 4056 RasAcd (fe0d99d6f31e4fad8159f690d68ded9c) C:\WINDOWS\system32\DRIVERS\rasacd.sys
13:34:59.0281 4056 RasAcd - ok
13:34:59.0343 4056 Rasl2tp (11b4a627bc9614b885c4969bfa5ff8a6) C:\WINDOWS\system32\DRIVERS\rasl2tp.sys
13:34:59.0359 4056 Rasl2tp - ok
13:34:59.0390 4056 RasPppoe (5bc962f2654137c9909c3d4603587dee) C:\WINDOWS\system32\DRIVERS\raspppoe.sys
13:34:59.0406 4056 RasPppoe - ok
13:34:59.0437 4056 Raspti (fdbb1d60066fcfbb7452fd8f9829b242) C:\WINDOWS\system32\DRIVERS\raspti.sys
13:34:59.0437 4056 Raspti - ok
13:34:59.0500 4056 Rdbss (7ad224ad1a1437fe28d89cf22b17780a) C:\WINDOWS\system32\DRIVERS\rdbss.sys
13:34:59.0515 4056 Rdbss - ok
13:34:59.0546 4056 RDPCDD (4912d5b403614ce99c28420f75353332) C:\WINDOWS\system32\DRIVERS\RDPCDD.sys
13:34:59.0546 4056 RDPCDD - ok
13:34:59.0609 4056 rdpdr (15cabd0f7c00c47c70124907916af3f1) C:\WINDOWS\system32\DRIVERS\rdpdr.sys
13:34:59.0625 4056 rdpdr - ok
13:34:59.0718 4056 RDPWD (fc105dd312ed64eb66bff111e8ec6eac) C:\WINDOWS\system32\drivers\RDPWD.sys
13:34:59.0718 4056 RDPWD - ok
13:34:59.0906 4056 redbook (f828dd7e1419b6653894a8f97a0094c5) C:\WINDOWS\system32\DRIVERS\redbook.sys
13:34:59.0937 4056 redbook - ok
13:35:00.0296 4056 s24trans (96b4494d4734970f47c566e098c4f527) C:\WINDOWS\system32\DRIVERS\s24trans.sys
13:35:00.0343 4056 s24trans - ok
13:35:00.0593 4056 Secdrv (90a3935d05b494a5a39d37e71f09a677) C:\WINDOWS\system32\DRIVERS\secdrv.sys
13:35:00.0609 4056 Secdrv - ok
13:35:00.0656 4056 serenum (0f29512ccd6bead730039fb4bd2c85ce) C:\WINDOWS\system32\DRIVERS\serenum.sys
13:35:00.0656 4056 serenum - ok
13:35:00.0687 4056 Serial (cca207a8896d4c6a0c9ce29a4ae411a7) C:\WINDOWS\system32\DRIVERS\serial.sys
13:35:00.0687 4056 Serial - ok
13:35:00.0750 4056 Sfloppy (8e6b8c671615d126fdc553d1e2de5562) C:\WINDOWS\system32\drivers\Sfloppy.sys
13:35:00.0750 4056 Sfloppy - ok
13:35:00.0796 4056 Simbad - ok
13:35:00.0875 4056 SLIP (866d538ebe33709a5c9f5c62b73b7d14) C:\WINDOWS\system32\DRIVERS\SLIP.sys
13:35:00.0875 4056 SLIP - ok
13:35:00.0921 4056 Sparrow - ok
13:35:00.0953 4056 splitter (ab8b92451ecb048a4d1de7c3ffcb4a9f) C:\WINDOWS\system32\drivers\splitter.sys
13:35:00.0953 4056 splitter - ok
13:35:01.0015 4056 sr (76bb022c2fb6902fd5bdd4f78fc13a5d) C:\WINDOWS\system32\DRIVERS\sr.sys
13:35:01.0015 4056 sr - ok
13:35:01.0109 4056 Srv (47ddfc2f003f7f9f0592c6874962a2e7) C:\WINDOWS\system32\DRIVERS\srv.sys
13:35:01.0125 4056 Srv - ok
13:35:01.0234 4056 STAC97 (305cc42945a713347f978d78566113f3) C:\WINDOWS\system32\drivers\STAC97.sys
13:35:01.0234 4056 STAC97 - ok
13:35:01.0281 4056 streamip (77813007ba6265c4b6098187e6ed79d2) C:\WINDOWS\system32\DRIVERS\StreamIP.sys
13:35:01.0281 4056 streamip - ok
13:35:01.0390 4056 swenum (3941d127aef12e93addf6fe6ee027e0f) C:\WINDOWS\system32\DRIVERS\swenum.sys
13:35:01.0390 4056 swenum - ok
13:35:01.0421 4056 swmidi (8ce882bcc6cf8a62f2b2323d95cb3d01) C:\WINDOWS\system32\drivers\swmidi.sys
13:35:01.0437 4056 swmidi - ok
13:35:01.0484 4056 symc810 - ok
13:35:01.0515 4056 symc8xx - ok
13:35:01.0546 4056 sym_hi - ok
13:35:01.0578 4056 sym_u3 - ok
13:35:01.0625 4056 sysaudio (8b83f3ed0f1688b4958f77cd6d2bf290) C:\WINDOWS\system32\drivers\sysaudio.sys
13:35:01.0625 4056 sysaudio - ok
13:35:01.0781 4056 Tcpip (9aefa14bd6b182d61e3119fa5f436d3d) C:\WINDOWS\system32\DRIVERS\tcpip.sys
13:35:01.0796 4056 Tcpip - ok
13:35:01.0875 4056 TDPIPE (6471a66807f5e104e4885f5b67349397) C:\WINDOWS\system32\drivers\TDPIPE.sys
13:35:01.0875 4056 TDPIPE - ok
13:35:01.0906 4056 TDTCP (c56b6d0402371cf3700eb322ef3aaf61) C:\WINDOWS\system32\drivers\TDTCP.sys
13:35:01.0906 4056 TDTCP - ok
13:35:01.0968 4056 TermDD (88155247177638048422893737429d9e) C:\WINDOWS\system32\DRIVERS\termdd.sys
13:35:01.0968 4056 TermDD - ok
13:35:02.0031 4056 TosIde - ok
13:35:02.0078 4056 Udfs (5787b80c2e3c5e2f56c2a233d91fa2c9) C:\WINDOWS\system32\drivers\Udfs.sys
13:35:02.0093 4056 Udfs - ok
13:35:02.0125 4056 UIUSys - ok
13:35:02.0156 4056 ultra - ok
13:35:02.0234 4056 Update (402ddc88356b1bac0ee3dd1580c76a31) C:\WINDOWS\system32\DRIVERS\update.sys
13:35:02.0250 4056 Update - ok
13:35:02.0312 4056 usbehci (65dcf09d0e37d4c6b11b5b0b76d470a7) C:\WINDOWS\system32\DRIVERS\usbehci.sys
13:35:02.0312 4056 usbehci - ok
13:35:02.0406 4056 usbhub (1ab3cdde553b6e064d2e754efe20285c) C:\WINDOWS\system32\DRIVERS\usbhub.sys
13:35:02.0406 4056 usbhub - ok
13:35:02.0484 4056 USBSTOR (a32426d9b14a089eaa1d922e0c5801a9) C:\WINDOWS\system32\DRIVERS\USBSTOR.SYS
13:35:02.0500 4056 USBSTOR - ok
13:35:02.0562 4056 usbuhci (26496f9dee2d787fc3e61ad54821ffe6) C:\WINDOWS\system32\DRIVERS\usbuhci.sys
13:35:02.0562 4056 usbuhci - ok
13:35:02.0609 4056 VgaSave (0d3a8fafceacd8b7625cd549757a7df1) C:\WINDOWS\System32\drivers\vga.sys
13:35:02.0609 4056 VgaSave - ok
13:35:02.0640 4056 ViaIde - ok
13:35:02.0687 4056 VolSnap (4c8fcb5cc53aab716d810740fe59d025) C:\WINDOWS\system32\drivers\VolSnap.sys
13:35:02.0687 4056 VolSnap - ok
13:35:02.0921 4056 w29n51 (f0608f3b5b6d16f4870e867f9d069b6b) C:\WINDOWS\system32\DRIVERS\w29n51.sys
13:35:03.0031 4056 w29n51 - ok
13:35:03.0109 4056 Wanarp (e20b95baedb550f32dd489265c1da1f6) C:\WINDOWS\system32\DRIVERS\wanarp.sys
13:35:03.0109 4056 Wanarp - ok
13:35:03.0140 4056 WDICA - ok
13:35:03.0203 4056 wdmaud (6768acf64b18196494413695f0c3a00f) C:\WINDOWS\system32\drivers\wdmaud.sys
13:35:03.0203 4056 wdmaud - ok
13:35:03.0328 4056 winachsf (0c5b9cf1bdf998750d9c5eeb5f8c55ac) C:\WINDOWS\system32\DRIVERS\HSF_CNXT.sys
13:35:03.0359 4056 winachsf - ok
13:35:03.0546 4056 WSTCODEC (c98b39829c2bbd34e454150633c62c78) C:\WINDOWS\system32\DRIVERS\WSTCODEC.SYS
13:35:03.0546 4056 WSTCODEC - ok
13:35:03.0625 4056 WudfPf (f15feafffbb3644ccc80c5da584e6311) C:\WINDOWS\system32\DRIVERS\WudfPf.sys
13:35:03.0625 4056 WudfPf - ok
13:35:03.0671 4056 WudfRd (28b524262bce6de1f7ef9f510ba3985b) C:\WINDOWS\system32\DRIVERS\wudfrd.sys
13:35:03.0671 4056 WudfRd - ok
13:35:03.0750 4056 MBR (0x1B8) (8f558eb6672622401da993e1e865c861) \Device\Harddisk0\DR0
13:35:03.0953 4056 \Device\Harddisk0\DR0 - ok
13:35:03.0968 4056 MBR (0x1B8) (5fb38429d5d77768867c76dcbdb35194) \Device\Harddisk1\DR6
13:35:03.0984 4056 \Device\Harddisk1\DR6 - ok
13:35:03.0984 4056 Boot (0x1200) (2431725b7ba1e2b0a2083232a068ba30) \Device\Harddisk0\DR0\Partition0
13:35:04.0000 4056 \Device\Harddisk0\DR0\Partition0 - ok
13:35:04.0000 4056 Boot (0x1200) (8c1ebc4e9f8e501049dac1dac4ae6ab8) \Device\Harddisk1\DR6\Partition0
13:35:04.0000 4056 \Device\Harddisk1\DR6\Partition0 - ok
13:35:04.0015 4056 ============================================================
13:35:04.0015 4056 Scan finished
13:35:04.0015 4056 ============================================================
13:35:04.0031 4020 Detected object count: 0
13:35:04.0031 4020 Actual detected object count: 0
13:36:30.0296 0232 Deinitialize success



3. RKill Log


This log file is located at C:\rkill.log.
Please post this only if requested to by the person helping you.
Otherwise you can close this log when you wish.

Rkill was run on 12/18/2011 at 13:48:15.
Operating System: Microsoft Windows XP


Processes terminated by Rkill or while it was running:



Rkill completed on 12/18/2011 at 13:48:18.



4. SAS log

SUPERAntiSpyware Scan Log
http://www.superantispyware.com

Generated 12/18/2011 at 02:52 PM

Application Version : 5.0.1142

Core Rules Database Version : 8064
Trace Rules Database Version: 5876

Scan type : Complete Scan
Total Scan Time : 00:34:38

Operating System Information
Windows XP Professional 32-bit, Service Pack 3 (Build 5.01.2600)
Administrator

Memory items scanned : 258
Memory threats detected : 0
Registry items scanned : 34950
Registry threats detected : 8
File items scanned : 39813
File threats detected : 686

Trojan.Agent/Gen-Falpdb
HKLM\System\ControlSet001\Services\AVGTDIX
C:\WINDOWS\SYSTEM32\DRIVERS\AVGTDIX.SYS
HKLM\System\ControlSet001\Enum\Root\LEGACY_AVGTDIX
HKLM\System\ControlSet002\Services\AVGTDIX
HKLM\System\ControlSet002\Enum\Root\LEGACY_AVGTDIX
HKLM\System\ControlSet003\Services\AVGTDIX
HKLM\System\ControlSet003\Enum\Root\LEGACY_AVGTDIX
HKLM\System\CurrentControlSet\Services\AVGTDIX
HKLM\System\CurrentControlSet\Enum\Root\LEGACY_AVGTDIX






I performed all of these tests while running the computer in safe mode.

Is there anything else I need to do or should this have fixed the problem?

#10 fastred04R1

fastred04R1
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:02:05 PM

Posted 18 December 2011 - 05:32 PM

Computer seems to be back up and running. Thank you very much for the help.

#11 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,490 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:05:05 PM

Posted 18 December 2011 - 09:30 PM

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 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 Start > 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 Start > 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 Users can refer to these links: Create a New Restore Point and Disk Cleanup.

Tips to protect yourself against malware and reduce the potential for re-infection:Avoid gaming sites, pirated software, cracking tools, keygens, and peer-to-peer (P2P) file sharing programs. They are a security risk which can make your computer susceptible to a smörgåsbord of malware infections, remote attacks, exposure of personal information, and identity theft. Many malicious worms and Trojans spread across P2P file sharing networks, gaming and underground sites. Users visiting such pages may see innocuous-looking banner ads containing code which can trigger pop-up ads and malicious Flash ads that install viruses, Trojans and spyware. Ads are a target for hackers because they offer a stealthy way to distribute malware to a wide range of Internet users. The best way to reduce the risk of infection is to avoid these types of web sites and not use any P2P applications. Read P2P Software User Advisories and Risks of File-Sharing Technology.

Keeping Autorun enabled on USB and other removable drives has become a significant security risk due to the increasing number of malware variants that can infect them and transfer the infection to your computer. To learn more about this risk, please read:
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