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

IE 8 using large amount of memory


  • This topic is locked This topic is locked
9 replies to this topic

#1 MartyL

MartyL

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:12:46 PM

Posted 26 September 2011 - 09:34 PM

First I guess I should give you background info.

HP d530 PC
Intel P4 @ 3GHz
1 Gig of DDR 133MHz Ram
Western Digital 250 GB EIDE hard drive

XP Professional (SP3)
Internet Explorer 8

ISP - Verizon FIOS with 25 Mbps up and down (I am not a gamer. They gave me a speed increase free for not leaving after we had issues).


Tonight I had a problem where I was looking at a Google site with many pictures(of mops. Not a typo, mops). At first I could scroll down the page normally. Then the scrolling got painfully slow and the cooling fan sped up noticeably. I opened Task Manager to look at running proceses and saw two instances of iexplore.exe even though I only had one instance open (only one tab). One instance was using about 20 meg ( I don't really remember exactly how much). The other instance was using over 100 meg.

My first question is should there be two instances showing up in Task Manager when I only have one instance of IE open (only one tab)?

Presuming two instances is not the problem my second question is should IE be using that much memory? Before I came here I shut down IE for about 5 minutes. I have opened Task Manager several times while I was typing this and every time I showed one instance of IE using 16 meg of memory.

An interesting note - while I was typing this I went back to the top to fill in the background info. In the process I opened up a second tab here on IE to look up some info. I checked Task Manager and now have three instances of iexplore.exe. One is using 17 meg. One is using 33 meg and one is using 84 meg. I closed the 2nd tab so that only one tab was open I still had three instances of iexplore.exe running with pretty much the same memory usage. I closed Task manager and reopened it. There were still three instances of iexplore.exe running. I closed Task Manager again and reopened it. There were now only two instances of iexplore.exe running. One was using 17 meg and the other was using 84 meg.

I know pretty much nothing about how IE should or shouldn't use memory. I didn't used to have this problem. I can't say that it started tonight. I have noticed slower IE before and multiple instances of it in Task Manager but I have never had it slow my PC down so much before.

I have run Malwarebytes, Super AntiSpyware and Microsoft Security Essentials all within the past few weeks and nothing was found. I will run them all again but would like to know if all of this is "normal" or if I should be concerned.

Thank you kindly in advance for your assistance.

BC AdBot (Login to Remove)

 


#2 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,078 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:01:46 PM

Posted 27 September 2011 - 03:49 PM

It looks like a malware.. 1 ie explore per window open.

Please download the TDSS Rootkit Removing Tool (TDSSKiller.exe) and save it to your Desktop. <-Important!!!
Be sure to download TDSSKiller.exe (v2.5.6.0) from Kaspersky's website and not TDSSKiller.zip which appears to be an older version 2.3.2.2 of the tool.
  • Double-click on TDSSKiller.exe to run the tool for known TDSS variants.
    Vista/Windows 7 users right-click and select Run As Administrator.
  • 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 How to change the file extension.
  • Click the Start Scan button.
  • Do not use the computer during the scan
  • If the scan completes with nothing found, click Close to exit.
  • If malicious objects are found, they will show in the Scan results - Select action for found objects and offer three options.
  • Ensure Cure (default) is selected, then click Continue > Reboot now to finish the cleaning process.
  • A log file named TDSSKiller_version_date_time_log.txt (i.e. TDSSKiller.2.4.0.0_27.07.2010_09.o7.26_log.txt) will be created and saved to the root directory (usually Local Disk C:).
  • Copy and paste the contents of that file in your next reply.


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. [color=green]In some cases it may be necessary to redownload TDSSKiller and randomly rename it before downloading and saving to the computer.
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 MartyL

MartyL
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:12:46 PM

Posted 27 September 2011 - 05:35 PM

Here is the log file:

18:27:12.0343 4044 TDSS rootkit removing tool 2.6.2.0 Sep 26 2011 18:56:43
18:27:12.0578 4044 ============================================================
18:27:12.0578 4044 Current date / time: 2011/09/27 18:27:12.0578
18:27:12.0578 4044 SystemInfo:
18:27:12.0578 4044
18:27:12.0578 4044 OS Version: 5.1.2600 ServicePack: 3.0
18:27:12.0578 4044 Product type: Workstation
18:27:12.0578 4044 ComputerName: MARTY-HOME
18:27:12.0578 4044 UserName: Marty
18:27:12.0578 4044 Windows directory: C:\NEWXP
18:27:12.0578 4044 System windows directory: C:\NEWXP
18:27:12.0578 4044 Processor architecture: Intel x86
18:27:12.0578 4044 Number of processors: 2
18:27:12.0578 4044 Page size: 0x1000
18:27:12.0578 4044 Boot type: Normal boot
18:27:12.0578 4044 ============================================================
18:27:14.0593 4044 Initialize success
18:27:19.0031 3988 ============================================================
18:27:19.0031 3988 Scan started
18:27:19.0031 3988 Mode: Manual;
18:27:19.0031 3988 ============================================================
18:27:21.0359 3988 Abiosdsk - ok
18:27:21.0390 3988 abp480n5 - ok
18:27:21.0484 3988 ACPI (8fd99680a539792a30e97944fdaecf17) C:\NEWXP\system32\DRIVERS\ACPI.sys
18:27:21.0500 3988 ACPI - ok
18:27:21.0546 3988 ACPIEC (9859c0f6936e723e4892d7141b1327d5) C:\NEWXP\system32\drivers\ACPIEC.sys
18:27:21.0546 3988 ACPIEC - ok
18:27:21.0562 3988 adpu160m - ok
18:27:21.0625 3988 aeaudio (e696e749bedcda8b23757b8b5ea93780) C:\NEWXP\system32\drivers\aeaudio.sys
18:27:21.0625 3988 aeaudio - ok
18:27:21.0718 3988 aec (8bed39e3c35d6a489438b8141717a557) C:\NEWXP\system32\drivers\aec.sys
18:27:21.0718 3988 aec - ok
18:27:21.0796 3988 AFD (355556d9e580915118cd7ef736653a89) C:\NEWXP\System32\drivers\afd.sys
18:27:21.0812 3988 AFD - ok
18:27:21.0828 3988 Aha154x - ok
18:27:21.0843 3988 aic78u2 - ok
18:27:21.0875 3988 aic78xx - ok
18:27:21.0906 3988 AliIde - ok
18:27:21.0937 3988 amsint - ok
18:27:21.0953 3988 asc - ok
18:27:21.0984 3988 asc3350p - ok
18:27:22.0000 3988 asc3550 - ok
18:27:22.0109 3988 AsyncMac (b153affac761e7f5fcfa822b9c4e97bc) C:\NEWXP\system32\DRIVERS\asyncmac.sys
18:27:22.0109 3988 AsyncMac - ok
18:27:22.0140 3988 atapi (9f3a2f5aa6875c72bf062c712cfa2674) C:\NEWXP\system32\DRIVERS\atapi.sys
18:27:22.0140 3988 atapi - ok
18:27:22.0187 3988 Atdisk - ok
18:27:22.0234 3988 Atmarpc (9916c1225104ba14794209cfa8012159) C:\NEWXP\system32\DRIVERS\atmarpc.sys
18:27:22.0234 3988 Atmarpc - ok
18:27:22.0296 3988 audstub (d9f724aa26c010a217c97606b160ed68) C:\NEWXP\system32\DRIVERS\audstub.sys
18:27:22.0296 3988 audstub - ok
18:27:22.0375 3988 b57w2k (5175e788bcd1cb7345ab21f3e14369d2) C:\NEWXP\system32\DRIVERS\b57xp32.sys
18:27:22.0375 3988 b57w2k - ok
18:27:22.0468 3988 Beep (da1f27d85e0d1525f6621372e7b685e9) C:\NEWXP\system32\drivers\Beep.sys
18:27:22.0468 3988 Beep - ok
18:27:22.0546 3988 Blfp (9b53d428de0a2566a03499d7aa48dec4) C:\NEWXP\system32\DRIVERS\baspxp32.sys
18:27:22.0546 3988 Blfp - ok
18:27:22.0625 3988 BUFADPT (28d8d2902e88c59c0f15bd88e318e7ef) C:\NEWXP\system32\BUFADPT.SYS
18:27:22.0640 3988 BUFADPT - ok
18:27:22.0703 3988 cbidf2k (90a673fc8e12a79afbed2576f6a7aaf9) C:\NEWXP\system32\drivers\cbidf2k.sys
18:27:22.0703 3988 cbidf2k - ok
18:27:22.0765 3988 CCDECODE (0be5aef125be881c4f854c554f2b025c) C:\NEWXP\system32\DRIVERS\CCDECODE.sys
18:27:22.0796 3988 CCDECODE - ok
18:27:22.0875 3988 cd20xrnt - ok
18:27:22.0953 3988 Cdaudio (c1b486a7658353d33a10cc15211a873b) C:\NEWXP\system32\drivers\Cdaudio.sys
18:27:22.0953 3988 Cdaudio - ok
18:27:23.0000 3988 Cdfs (c885b02847f5d2fd45a24e219ed93b32) C:\NEWXP\system32\drivers\Cdfs.sys
18:27:23.0015 3988 Cdfs - ok
18:27:23.0062 3988 Cdrom (1f4260cc5b42272d71f79e570a27a4fe) C:\NEWXP\system32\DRIVERS\cdrom.sys
18:27:23.0062 3988 Cdrom - ok
18:27:23.0078 3988 Changer - ok
18:27:23.0140 3988 CmdIde - ok
18:27:23.0171 3988 Cpqarray - ok
18:27:23.0203 3988 dac2w2k - ok
18:27:23.0234 3988 dac960nt - ok
18:27:23.0296 3988 Disk (044452051f3e02e7963599fc8f4f3e25) C:\NEWXP\system32\DRIVERS\disk.sys
18:27:23.0312 3988 Disk - ok
18:27:23.0375 3988 DLABMFSM (a53723176d0002feb486eff8e17812f2) C:\NEWXP\system32\DLA\DLABMFSM.SYS
18:27:23.0375 3988 DLABMFSM - ok
18:27:23.0390 3988 DLABOIOM (d4587063acea776699251e177d719586) C:\NEWXP\system32\DLA\DLABOIOM.SYS
18:27:23.0390 3988 DLABOIOM - ok
18:27:23.0421 3988 DLACDBHM (5230cdb7e715f3a3b4a882e254cdd35d) C:\NEWXP\system32\Drivers\DLACDBHM.SYS
18:27:23.0421 3988 DLACDBHM - ok
18:27:23.0453 3988 DLADResM (c950c2e7b9ed1a4fc4a2ac7ec044f1d6) C:\NEWXP\system32\DLA\DLADResM.SYS
18:27:23.0453 3988 DLADResM - ok
18:27:23.0468 3988 DLAIFS_M (24400137e387a24410c52a591f3cfb4d) C:\NEWXP\system32\DLA\DLAIFS_M.SYS
18:27:23.0484 3988 DLAIFS_M - ok
18:27:23.0500 3988 DLAOPIOM (29a303feceb28641ecebdae89eb71c63) C:\NEWXP\system32\DLA\DLAOPIOM.SYS
18:27:23.0500 3988 DLAOPIOM - ok
18:27:23.0531 3988 DLAPoolM (c93e33a22a1ae0c5508f3fb1f6d0a50c) C:\NEWXP\system32\DLA\DLAPoolM.SYS
18:27:23.0531 3988 DLAPoolM - ok
18:27:23.0562 3988 DLARTL_M (77fe51f0f8d86804cb81f6ef6bfb86dd) C:\NEWXP\system32\Drivers\DLARTL_M.SYS
18:27:23.0562 3988 DLARTL_M - ok
18:27:23.0578 3988 DLAUDFAM (b953498c35a31e5ac98f49adbcf3e627) C:\NEWXP\system32\DLA\DLAUDFAM.SYS
18:27:23.0593 3988 DLAUDFAM - ok
18:27:23.0609 3988 DLAUDF_M (4897704c093c1f59ce58fc65e1e1ef1e) C:\NEWXP\system32\DLA\DLAUDF_M.SYS
18:27:23.0625 3988 DLAUDF_M - ok
18:27:23.0703 3988 dmboot (d992fe1274bde0f84ad826acae022a41) C:\NEWXP\system32\drivers\dmboot.sys
18:27:23.0718 3988 dmboot - ok
18:27:23.0781 3988 dmio (7c824cf7bbde77d95c08005717a95f6f) C:\NEWXP\system32\drivers\dmio.sys
18:27:23.0781 3988 dmio - ok
18:27:23.0843 3988 dmload (e9317282a63ca4d188c0df5e09c6ac5f) C:\NEWXP\system32\drivers\dmload.sys
18:27:23.0843 3988 dmload - ok
18:27:23.0906 3988 DMusic (8a208dfcf89792a484e76c40e5f50b45) C:\NEWXP\system32\drivers\DMusic.sys
18:27:23.0906 3988 DMusic - ok
18:27:24.0000 3988 Dot4 (3e4b043f8bc6be1d4820cc6c9c500306) C:\NEWXP\system32\DRIVERS\Dot4.sys
18:27:24.0015 3988 Dot4 - ok
18:27:24.0046 3988 Dot4Print (77ce63a8a34ae23d9fe4c7896d1debe7) C:\NEWXP\system32\DRIVERS\Dot4Prt.sys
18:27:24.0046 3988 Dot4Print - ok
18:27:24.0125 3988 dot4usb (6ec3af6bb5b30e488a0c559921f012e1) C:\NEWXP\system32\DRIVERS\dot4usb.sys
18:27:24.0125 3988 dot4usb - ok
18:27:24.0140 3988 dpti2o - ok
18:27:24.0171 3988 drmkaud (8f5fcff8e8848afac920905fbd9d33c8) C:\NEWXP\system32\drivers\drmkaud.sys
18:27:24.0171 3988 drmkaud - ok
18:27:24.0203 3988 DRVMCDB (c00440385cf9f3d142917c63f989e244) C:\NEWXP\system32\Drivers\DRVMCDB.SYS
18:27:24.0203 3988 DRVMCDB - ok
18:27:24.0234 3988 DRVNDDM (ffc371525aa55d1bae18715ebcb8797c) C:\NEWXP\system32\Drivers\DRVNDDM.SYS
18:27:24.0234 3988 DRVNDDM - ok
18:27:24.0281 3988 Fastfat (38d332a6d56af32635675f132548343e) C:\NEWXP\system32\drivers\Fastfat.sys
18:27:24.0296 3988 Fastfat - ok
18:27:24.0343 3988 Fdc (92cdd60b6730b9f50f6a1a0c1f8cdc81) C:\NEWXP\system32\DRIVERS\fdc.sys
18:27:24.0343 3988 Fdc - ok
18:27:24.0375 3988 Fips (d45926117eb9fa946a6af572fbe1caa3) C:\NEWXP\system32\drivers\Fips.sys
18:27:24.0375 3988 Fips - ok
18:27:24.0406 3988 Flpydisk (9d27e7b80bfcdf1cdd9b555862d5e7f0) C:\NEWXP\system32\DRIVERS\flpydisk.sys
18:27:24.0406 3988 Flpydisk - ok
18:27:24.0453 3988 FltMgr (b2cf4b0786f8212cb92ed2b50c6db6b0) C:\NEWXP\system32\drivers\fltmgr.sys
18:27:24.0468 3988 FltMgr - ok
18:27:24.0578 3988 Fs_Rec (3e1e2bd4f39b0e2b7dc4f4d2bcc2779a) C:\NEWXP\system32\drivers\Fs_Rec.sys
18:27:24.0593 3988 Fs_Rec - ok
18:27:24.0609 3988 Ftdisk (6ac26732762483366c3969c9e4d2259d) C:\NEWXP\system32\DRIVERS\ftdisk.sys
18:27:24.0609 3988 Ftdisk - ok
18:27:24.0703 3988 Gpc (0a02c63c8b144bd8c86b103dee7c86a2) C:\NEWXP\system32\DRIVERS\msgpc.sys
18:27:24.0703 3988 Gpc - ok
18:27:24.0734 3988 hidusb (ccf82c5ec8a7326c3066de870c06daf1) C:\NEWXP\system32\DRIVERS\hidusb.sys
18:27:24.0734 3988 hidusb - ok
18:27:24.0765 3988 hpn - ok
18:27:24.0843 3988 HPZid412 (30ca91e657cede2f95359d6ef186f650) C:\NEWXP\system32\DRIVERS\HPZid412.sys
18:27:24.0843 3988 HPZid412 - ok
18:27:24.0875 3988 HPZipr12 (efd31afa752aa7c7bbb57bcbe2b01c78) C:\NEWXP\system32\DRIVERS\HPZipr12.sys
18:27:24.0875 3988 HPZipr12 - ok
18:27:24.0921 3988 HPZius12 (7ac43c38ca8fd7ed0b0a4466f753e06e) C:\NEWXP\system32\DRIVERS\HPZius12.sys
18:27:24.0921 3988 HPZius12 - ok
18:27:25.0000 3988 HTTP (f80a415ef82cd06ffaf0d971528ead38) C:\NEWXP\system32\Drivers\HTTP.sys
18:27:25.0015 3988 HTTP - ok
18:27:25.0031 3988 i2omgmt - ok
18:27:25.0062 3988 i2omp - ok
18:27:25.0093 3988 i8042prt (4a0b06aa8943c1e332520f7440c0aa30) C:\NEWXP\system32\DRIVERS\i8042prt.sys
18:27:25.0093 3988 i8042prt - ok
18:27:25.0234 3988 ialm (9a883c3c4d91292c0d09de7c728e781c) C:\NEWXP\system32\DRIVERS\ialmnt5.sys
18:27:25.0296 3988 ialm - ok
18:27:25.0375 3988 Imapi (083a052659f5310dd8b6a6cb05edcf8e) C:\NEWXP\system32\DRIVERS\imapi.sys
18:27:25.0375 3988 Imapi - ok
18:27:25.0406 3988 ini910u - ok
18:27:25.0437 3988 IntelIde (b5466a9250342a7aa0cd1fba13420678) C:\NEWXP\system32\DRIVERS\intelide.sys
18:27:25.0437 3988 IntelIde - ok
18:27:25.0500 3988 intelppm (8c953733d8f36eb2133f5bb58808b66b) C:\NEWXP\system32\DRIVERS\intelppm.sys
18:27:25.0500 3988 intelppm - ok
18:27:25.0546 3988 Ip6Fw (3bb22519a194418d5fec05d800a19ad0) C:\NEWXP\system32\drivers\ip6fw.sys
18:27:25.0562 3988 Ip6Fw - ok
18:27:25.0609 3988 IpFilterDriver (731f22ba402ee4b62748adaf6363c182) C:\NEWXP\system32\DRIVERS\ipfltdrv.sys
18:27:25.0609 3988 IpFilterDriver - ok
18:27:25.0640 3988 IpInIp (b87ab476dcf76e72010632b5550955f5) C:\NEWXP\system32\DRIVERS\ipinip.sys
18:27:25.0640 3988 IpInIp - ok
18:27:25.0703 3988 IpNat (cc748ea12c6effde940ee98098bf96bb) C:\NEWXP\system32\DRIVERS\ipnat.sys
18:27:25.0703 3988 IpNat - ok
18:27:25.0718 3988 IPSec (23c74d75e36e7158768dd63d92789a91) C:\NEWXP\system32\DRIVERS\ipsec.sys
18:27:25.0734 3988 IPSec - ok
18:27:25.0781 3988 IRENUM (c93c9ff7b04d772627a3646d89f7bf89) C:\NEWXP\system32\DRIVERS\irenum.sys
18:27:25.0781 3988 IRENUM - ok
18:27:25.0828 3988 isapnp (05a299ec56e52649b1cf2fc52d20f2d7) C:\NEWXP\system32\DRIVERS\isapnp.sys
18:27:25.0828 3988 isapnp - ok
18:27:25.0859 3988 Kbdclass (463c1ec80cd17420a542b7f36a36f128) C:\NEWXP\system32\DRIVERS\kbdclass.sys
18:27:25.0859 3988 Kbdclass - ok
18:27:25.0890 3988 kbdhid (9ef487a186dea361aa06913a75b3fa99) C:\NEWXP\system32\DRIVERS\kbdhid.sys
18:27:25.0890 3988 kbdhid - ok
18:27:25.0921 3988 kmixer (692bcf44383d056aed41b045a323d378) C:\NEWXP\system32\drivers\kmixer.sys
18:27:25.0937 3988 kmixer - ok
18:27:25.0984 3988 KSecDD (b467646c54cc746128904e1654c750c1) C:\NEWXP\system32\drivers\KSecDD.sys
18:27:25.0984 3988 KSecDD - ok
18:27:26.0062 3988 lbrtfdc - ok
18:27:26.0156 3988 LVPr2Mon (8be71d7edb8c7494913722059f760dd0) C:\NEWXP\system32\DRIVERS\LVPr2Mon.sys
18:27:26.0156 3988 LVPr2Mon - ok
18:27:26.0218 3988 LVRS (b6e1ccd6572984adcae68439afd07011) C:\NEWXP\system32\DRIVERS\lvrs.sys
18:27:26.0234 3988 LVRS - ok
18:27:26.0406 3988 LVUVC (6c42815dd57e397f0cd988304b5eb4b3) C:\NEWXP\system32\DRIVERS\lvuvc.sys
18:27:26.0546 3988 LVUVC - ok
18:27:26.0578 3988 MBAMProtector (69a6268d7f81e53d568ab4e7e991caf3) C:\NEWXP\system32\drivers\mbam.sys
18:27:26.0593 3988 MBAMProtector - ok
18:27:26.0656 3988 mnmdd (4ae068242760a1fb6e1a44bf4e16afa6) C:\NEWXP\system32\drivers\mnmdd.sys
18:27:26.0656 3988 mnmdd - ok
18:27:26.0734 3988 Modem (dfcbad3cec1c5f964962ae10e0bcc8e1) C:\NEWXP\system32\drivers\Modem.sys
18:27:26.0734 3988 Modem - ok
18:27:26.0781 3988 Mouclass (35c9e97194c8cfb8430125f8dbc34d04) C:\NEWXP\system32\DRIVERS\mouclass.sys
18:27:26.0781 3988 Mouclass - ok
18:27:26.0921 3988 mouhid (b1c303e17fb9d46e87a98e4ba6769685) C:\NEWXP\system32\DRIVERS\mouhid.sys
18:27:26.0921 3988 mouhid - ok
18:27:26.0968 3988 MountMgr (a80b9a0bad1b73637dbcbba7df72d3fd) C:\NEWXP\system32\drivers\MountMgr.sys
18:27:26.0968 3988 MountMgr - ok
18:27:27.0031 3988 MpFilter (fee0baded54222e9f1dae9541212aab1) C:\NEWXP\system32\DRIVERS\MpFilter.sys
18:27:27.0046 3988 MpFilter - ok
18:27:27.0234 3988 MpKsl3498e9e8 (5f53edfead46fa7adb78eee9ecce8fdf) c:\Documents and Settings\All Users.NEWXP\Application Data\Microsoft\Microsoft Antimalware\Definition Updates\{64E04350-80F9-4E25-AA2D-5557EDC9D1B4}\MpKsl3498e9e8.sys
18:27:27.0250 3988 MpKsl3498e9e8 - ok
18:27:27.0250 3988 MpKsl372a9a72 - ok
18:27:27.0265 3988 MpKsl590c4e1f - ok
18:27:27.0281 3988 MpKsla4d45dbb - ok
18:27:27.0296 3988 MpKsld3ffb146 - ok
18:27:27.0312 3988 MpKslf1daf532 - ok
18:27:27.0359 3988 mraid35x - ok
18:27:27.0453 3988 mrtRate (6075de2ad531f6e30c9995dfda22001f) C:\NEWXP\system32\drivers\mrtRate.sys
18:27:27.0468 3988 mrtRate - ok
18:27:27.0500 3988 MRxDAV (11d42bb6206f33fbb3ba0288d3ef81bd) C:\NEWXP\system32\DRIVERS\mrxdav.sys
18:27:27.0515 3988 MRxDAV - ok
18:27:27.0625 3988 MRxSmb (7d304a5eb4344ebeeab53a2fe3ffb9f0) C:\NEWXP\system32\DRIVERS\mrxsmb.sys
18:27:27.0656 3988 MRxSmb - ok
18:27:27.0718 3988 Msfs (c941ea2454ba8350021d774daf0f1027) C:\NEWXP\system32\drivers\Msfs.sys
18:27:27.0734 3988 Msfs - ok
18:27:27.0781 3988 MSKSSRV (d1575e71568f4d9e14ca56b7b0453bf1) C:\NEWXP\system32\drivers\MSKSSRV.sys
18:27:27.0796 3988 MSKSSRV - ok
18:27:27.0828 3988 MSPCLOCK (325bb26842fc7ccc1fcce2c457317f3e) C:\NEWXP\system32\drivers\MSPCLOCK.sys
18:27:27.0828 3988 MSPCLOCK - ok
18:27:27.0890 3988 MSPQM (bad59648ba099da4a17680b39730cb3d) C:\NEWXP\system32\drivers\MSPQM.sys
18:27:27.0890 3988 MSPQM - ok
18:27:27.0937 3988 mssmbios (af5f4f3f14a8ea2c26de30f7a1e17136) C:\NEWXP\system32\DRIVERS\mssmbios.sys
18:27:27.0937 3988 mssmbios - ok
18:27:28.0000 3988 MSTEE (e53736a9e30c45fa9e7b5eac55056d1d) C:\NEWXP\system32\drivers\MSTEE.sys
18:27:28.0015 3988 MSTEE - ok
18:27:28.0078 3988 Mup (de6a75f5c270e756c5508d94b6cf68f5) C:\NEWXP\system32\drivers\Mup.sys
18:27:28.0078 3988 Mup - ok
18:27:28.0140 3988 NABTSFEC (5b50f1b2a2ed47d560577b221da734db) C:\NEWXP\system32\DRIVERS\NABTSFEC.sys
18:27:28.0171 3988 NABTSFEC - ok
18:27:28.0250 3988 NDIS (1df7f42665c94b825322fae71721130d) C:\NEWXP\system32\drivers\NDIS.sys
18:27:28.0250 3988 NDIS - ok
18:27:28.0406 3988 NdisIP (7ff1f1fd8609c149aa432f95a8163d97) C:\NEWXP\system32\DRIVERS\NdisIP.sys
18:27:28.0421 3988 NdisIP - ok
18:27:28.0484 3988 NdisTapi (0109c4f3850dfbab279542515386ae22) C:\NEWXP\system32\DRIVERS\ndistapi.sys
18:27:28.0484 3988 NdisTapi - ok
18:27:28.0562 3988 Ndisuio (f927a4434c5028758a842943ef1a3849) C:\NEWXP\system32\DRIVERS\ndisuio.sys
18:27:28.0562 3988 Ndisuio - ok
18:27:28.0578 3988 NdisWan (edc1531a49c80614b2cfda43ca8659ab) C:\NEWXP\system32\DRIVERS\ndiswan.sys
18:27:28.0593 3988 NdisWan - ok
18:27:28.0640 3988 NDProxy (9282bd12dfb069d3889eb3fcc1000a9b) C:\NEWXP\system32\drivers\NDProxy.sys
18:27:28.0640 3988 NDProxy - ok
18:27:28.0671 3988 NetBIOS (5d81cf9a2f1a3a756b66cf684911cdf0) C:\NEWXP\system32\DRIVERS\netbios.sys
18:27:28.0671 3988 NetBIOS - ok
18:27:28.0734 3988 NetBT (74b2b2f5bea5e9a3dc021d685551bd3d) C:\NEWXP\system32\DRIVERS\netbt.sys
18:27:28.0750 3988 NetBT - ok
18:27:28.0812 3988 Npfs (3182d64ae053d6fb034f44b6def8034a) C:\NEWXP\system32\drivers\Npfs.sys
18:27:28.0812 3988 Npfs - ok
18:27:28.0859 3988 Ntfs (78a08dd6a8d65e697c18e1db01c5cdca) C:\NEWXP\system32\drivers\Ntfs.sys
18:27:28.0859 3988 Ntfs - ok
18:27:28.0953 3988 NuidFltr (cf7e041663119e09d2e118521ada9300) C:\NEWXP\system32\DRIVERS\NuidFltr.sys
18:27:28.0953 3988 NuidFltr - ok
18:27:29.0046 3988 Null (73c1e1f395918bc2c6dd67af7591a3ad) C:\NEWXP\system32\drivers\Null.sys
18:27:29.0046 3988 Null - ok
18:27:29.0109 3988 NwlnkFlt (b305f3fad35083837ef46a0bbce2fc57) C:\NEWXP\system32\DRIVERS\nwlnkflt.sys
18:27:29.0109 3988 NwlnkFlt - ok
18:27:29.0140 3988 NwlnkFwd (c99b3415198d1aab7227f2c88fd664b9) C:\NEWXP\system32\DRIVERS\nwlnkfwd.sys
18:27:29.0140 3988 NwlnkFwd - ok
18:27:29.0203 3988 PalmUSBD (dc450992eba6f914080c1f7fbeeed72c) C:\NEWXP\system32\drivers\PalmUSBD.sys
18:27:29.0203 3988 PalmUSBD - ok
18:27:29.0250 3988 Parport (5575faf8f97ce5e713d108c2a58d7c7c) C:\NEWXP\system32\DRIVERS\parport.sys
18:27:29.0265 3988 Parport - ok
18:27:29.0328 3988 PartMgr (beb3ba25197665d82ec7065b724171c6) C:\NEWXP\system32\drivers\PartMgr.sys
18:27:29.0328 3988 PartMgr - ok
18:27:29.0390 3988 ParVdm (70e98b3fd8e963a6a46a2e6247e0bea1) C:\NEWXP\system32\drivers\ParVdm.sys
18:27:29.0390 3988 ParVdm - ok
18:27:29.0421 3988 PCI (a219903ccf74233761d92bef471a07b1) C:\NEWXP\system32\DRIVERS\pci.sys
18:27:29.0421 3988 PCI - ok
18:27:29.0437 3988 PCIDump - ok
18:27:29.0484 3988 PCIIde (ccf5f451bb1a5a2a522a76e670000ff0) C:\NEWXP\system32\DRIVERS\pciide.sys
18:27:29.0500 3988 PCIIde - ok
18:27:29.0531 3988 Pcmcia (9e89ef60e9ee05e3f2eef2da7397f1c1) C:\NEWXP\system32\drivers\Pcmcia.sys
18:27:29.0531 3988 Pcmcia - ok
18:27:29.0562 3988 PDCOMP - ok
18:27:29.0578 3988 PDFRAME - ok
18:27:29.0609 3988 PDRELI - ok
18:27:29.0625 3988 PDRFRAME - ok
18:27:29.0656 3988 perc2 - ok
18:27:29.0671 3988 perc2hib - ok
18:27:29.0843 3988 PORTMON - ok
18:27:29.0921 3988 PptpMiniport (efeec01b1d3cf84f16ddd24d9d9d8f99) C:\NEWXP\system32\DRIVERS\raspptp.sys
18:27:29.0921 3988 PptpMiniport - ok
18:27:29.0968 3988 PSched (09298ec810b07e5d582cb3a3f9255424) C:\NEWXP\system32\DRIVERS\psched.sys
18:27:29.0968 3988 PSched - ok
18:27:30.0015 3988 Ptilink (80d317bd1c3dbc5d4fe7b1678c60cadd) C:\NEWXP\system32\DRIVERS\ptilink.sys
18:27:30.0031 3988 Ptilink - ok
18:27:30.0046 3988 PxHelp20 (feffcfdc528764a04c8ed63d5fa6e711) C:\NEWXP\system32\Drivers\PxHelp20.sys
18:27:30.0062 3988 PxHelp20 - ok
18:27:30.0078 3988 ql1080 - ok
18:27:30.0093 3988 Ql10wnt - ok
18:27:30.0125 3988 ql12160 - ok
18:27:30.0156 3988 ql1240 - ok
18:27:30.0171 3988 ql1280 - ok
18:27:30.0203 3988 RasAcd (fe0d99d6f31e4fad8159f690d68ded9c) C:\NEWXP\system32\DRIVERS\rasacd.sys
18:27:30.0203 3988 RasAcd - ok
18:27:30.0265 3988 Rasl2tp (11b4a627bc9614b885c4969bfa5ff8a6) C:\NEWXP\system32\DRIVERS\rasl2tp.sys
18:27:30.0265 3988 Rasl2tp - ok
18:27:30.0328 3988 RasPppoe (5bc962f2654137c9909c3d4603587dee) C:\NEWXP\system32\DRIVERS\raspppoe.sys
18:27:30.0328 3988 RasPppoe - ok
18:27:30.0359 3988 Raspti (fdbb1d60066fcfbb7452fd8f9829b242) C:\NEWXP\system32\DRIVERS\raspti.sys
18:27:30.0359 3988 Raspti - ok
18:27:30.0421 3988 Rdbss (7ad224ad1a1437fe28d89cf22b17780a) C:\NEWXP\system32\DRIVERS\rdbss.sys
18:27:30.0421 3988 Rdbss - ok
18:27:30.0437 3988 RDPCDD (4912d5b403614ce99c28420f75353332) C:\NEWXP\system32\DRIVERS\RDPCDD.sys
18:27:30.0453 3988 RDPCDD - ok
18:27:30.0484 3988 rdpdr (15cabd0f7c00c47c70124907916af3f1) C:\NEWXP\system32\DRIVERS\rdpdr.sys
18:27:30.0484 3988 rdpdr - ok
18:27:30.0546 3988 RDPWD (fc105dd312ed64eb66bff111e8ec6eac) C:\NEWXP\system32\drivers\RDPWD.sys
18:27:30.0546 3988 RDPWD - ok
18:27:30.0609 3988 redbook (f828dd7e1419b6653894a8f97a0094c5) C:\NEWXP\system32\DRIVERS\redbook.sys
18:27:30.0609 3988 redbook - ok
18:27:30.0718 3988 RimUsb (92d33f76769a028ddc54a863eb7de4a2) C:\NEWXP\system32\Drivers\RimUsb.sys
18:27:30.0718 3988 RimUsb - ok
18:27:30.0781 3988 RimVSerPort (2c4fb2e9f039287767c384e46ee91030) C:\NEWXP\system32\DRIVERS\RimSerial.sys
18:27:30.0781 3988 RimVSerPort - ok
18:27:30.0843 3988 ROOTMODEM (d8b0b4ade32574b2d9c5cc34dc0dbbe7) C:\NEWXP\system32\Drivers\RootMdm.sys
18:27:30.0843 3988 ROOTMODEM - ok
18:27:30.0968 3988 SABProcEnum - ok
18:27:31.0109 3988 SASDIFSV (39763504067962108505bff25f024345) C:\Program Files\SUPERAntiSpyware\SASDIFSV.SYS
18:27:31.0109 3988 SASDIFSV - ok
18:27:31.0171 3988 SASKUTIL (77b9fc20084b48408ad3e87570eb4a85) C:\Program Files\SUPERAntiSpyware\SASKUTIL.SYS
18:27:31.0171 3988 SASKUTIL - ok
18:27:31.0343 3988 Secdrv (90a3935d05b494a5a39d37e71f09a677) C:\NEWXP\system32\DRIVERS\secdrv.sys
18:27:31.0343 3988 Secdrv - ok
18:27:31.0421 3988 serenum (0f29512ccd6bead730039fb4bd2c85ce) C:\NEWXP\system32\DRIVERS\serenum.sys
18:27:31.0421 3988 serenum - ok
18:27:31.0437 3988 Serial (cca207a8896d4c6a0c9ce29a4ae411a7) C:\NEWXP\system32\DRIVERS\serial.sys
18:27:31.0437 3988 Serial - ok
18:27:31.0546 3988 Sfloppy (8e6b8c671615d126fdc553d1e2de5562) C:\NEWXP\system32\drivers\Sfloppy.sys
18:27:31.0546 3988 Sfloppy - ok
18:27:31.0578 3988 Simbad - ok
18:27:31.0656 3988 SLIP (866d538ebe33709a5c9f5c62b73b7d14) C:\NEWXP\system32\DRIVERS\SLIP.sys
18:27:31.0671 3988 SLIP - ok
18:27:31.0781 3988 smwdm (fa3368a7039f5abaa4b933703ac34763) C:\NEWXP\system32\drivers\smwdm.sys
18:27:31.0812 3988 smwdm - ok
18:27:31.0843 3988 Sparrow - ok
18:27:31.0875 3988 splitter (ab8b92451ecb048a4d1de7c3ffcb4a9f) C:\NEWXP\system32\drivers\splitter.sys
18:27:31.0875 3988 splitter - ok
18:27:31.0968 3988 sr (76bb022c2fb6902fd5bdd4f78fc13a5d) C:\NEWXP\system32\DRIVERS\sr.sys
18:27:31.0968 3988 sr - ok
18:27:32.0062 3988 Srv (47ddfc2f003f7f9f0592c6874962a2e7) C:\NEWXP\system32\DRIVERS\srv.sys
18:27:32.0078 3988 Srv - ok
18:27:32.0125 3988 streamip (77813007ba6265c4b6098187e6ed79d2) C:\NEWXP\system32\DRIVERS\StreamIP.sys
18:27:32.0156 3988 streamip - ok
18:27:32.0218 3988 swenum (3941d127aef12e93addf6fe6ee027e0f) C:\NEWXP\system32\DRIVERS\swenum.sys
18:27:32.0218 3988 swenum - ok
18:27:32.0250 3988 swmidi (8ce882bcc6cf8a62f2b2323d95cb3d01) C:\NEWXP\system32\drivers\swmidi.sys
18:27:32.0250 3988 swmidi - ok
18:27:32.0281 3988 symc810 - ok
18:27:32.0312 3988 symc8xx - ok
18:27:32.0328 3988 sym_hi - ok
18:27:32.0359 3988 sym_u3 - ok
18:27:32.0390 3988 sysaudio (8b83f3ed0f1688b4958f77cd6d2bf290) C:\NEWXP\system32\drivers\sysaudio.sys
18:27:32.0390 3988 sysaudio - ok
18:27:32.0484 3988 Tcpip (9aefa14bd6b182d61e3119fa5f436d3d) C:\NEWXP\system32\DRIVERS\tcpip.sys
18:27:32.0500 3988 Tcpip - ok
18:27:32.0562 3988 TDPIPE (6471a66807f5e104e4885f5b67349397) C:\NEWXP\system32\drivers\TDPIPE.sys
18:27:32.0562 3988 TDPIPE - ok
18:27:32.0593 3988 TDTCP (c56b6d0402371cf3700eb322ef3aaf61) C:\NEWXP\system32\drivers\TDTCP.sys
18:27:32.0593 3988 TDTCP - ok
18:27:32.0640 3988 TermDD (88155247177638048422893737429d9e) C:\NEWXP\system32\DRIVERS\termdd.sys
18:27:32.0640 3988 TermDD - ok
18:27:32.0687 3988 TosIde - ok
18:27:32.0734 3988 Udfs (5787b80c2e3c5e2f56c2a233d91fa2c9) C:\NEWXP\system32\drivers\Udfs.sys
18:27:32.0734 3988 Udfs - ok
18:27:32.0750 3988 ultra - ok
18:27:32.0875 3988 Update (402ddc88356b1bac0ee3dd1580c76a31) C:\NEWXP\system32\DRIVERS\update.sys
18:27:32.0890 3988 Update - ok
18:27:33.0046 3988 usbaudio (e919708db44ed8543a7c017953148330) C:\NEWXP\system32\drivers\usbaudio.sys
18:27:33.0093 3988 usbaudio - ok
18:27:33.0109 3988 usbbus - ok
18:27:33.0203 3988 usbccgp (173f317ce0db8e21322e71b7e60a27e8) C:\NEWXP\system32\DRIVERS\usbccgp.sys
18:27:33.0234 3988 usbccgp - ok
18:27:33.0250 3988 UsbDiag - ok
18:27:33.0312 3988 usbehci (65dcf09d0e37d4c6b11b5b0b76d470a7) C:\NEWXP\system32\DRIVERS\usbehci.sys
18:27:33.0328 3988 usbehci - ok
18:27:33.0343 3988 usbhub (1ab3cdde553b6e064d2e754efe20285c) C:\NEWXP\system32\DRIVERS\usbhub.sys
18:27:33.0343 3988 usbhub - ok
18:27:33.0359 3988 USBModem - ok
18:27:33.0421 3988 usbprint (a717c8721046828520c9edf31288fc00) C:\NEWXP\system32\DRIVERS\usbprint.sys
18:27:33.0421 3988 usbprint - ok
18:27:33.0500 3988 usbscan (a0b8cf9deb1184fbdd20784a58fa75d4) C:\NEWXP\system32\DRIVERS\usbscan.sys
18:27:33.0500 3988 usbscan - ok
18:27:33.0531 3988 USBSTOR (a32426d9b14a089eaa1d922e0c5801a9) C:\NEWXP\system32\DRIVERS\USBSTOR.SYS
18:27:33.0546 3988 USBSTOR - ok
18:27:33.0578 3988 usbuhci (26496f9dee2d787fc3e61ad54821ffe6) C:\NEWXP\system32\DRIVERS\usbuhci.sys
18:27:33.0578 3988 usbuhci - ok
18:27:33.0625 3988 usbvideo (63bbfca7f390f4c49ed4b96bfb1633e0) C:\NEWXP\system32\Drivers\usbvideo.sys
18:27:33.0640 3988 usbvideo - ok
18:27:33.0656 3988 VgaSave (0d3a8fafceacd8b7625cd549757a7df1) C:\NEWXP\System32\drivers\vga.sys
18:27:33.0656 3988 VgaSave - ok
18:27:33.0687 3988 ViaIde - ok
18:27:33.0718 3988 VolSnap (4c8fcb5cc53aab716d810740fe59d025) C:\NEWXP\system32\drivers\VolSnap.sys
18:27:33.0718 3988 VolSnap - ok
18:27:33.0796 3988 Wanarp (e20b95baedb550f32dd489265c1da1f6) C:\NEWXP\system32\DRIVERS\wanarp.sys
18:27:33.0796 3988 Wanarp - ok
18:27:33.0953 3988 Wdf01000 (d918617b46457b9ac28027722e30f647) C:\NEWXP\system32\DRIVERS\Wdf01000.sys
18:27:33.0984 3988 Wdf01000 - ok
18:27:34.0000 3988 WDICA - ok
18:27:34.0031 3988 wdmaud (6768acf64b18196494413695f0c3a00f) C:\NEWXP\system32\drivers\wdmaud.sys
18:27:34.0031 3988 wdmaud - ok
18:27:34.0187 3988 WpdUsb (1385e5aa9c9821790d33a9563b8d2dd0) C:\NEWXP\system32\Drivers\wpdusb.sys
18:27:34.0187 3988 WpdUsb - ok
18:27:34.0296 3988 WSTCODEC (c98b39829c2bbd34e454150633c62c78) C:\NEWXP\system32\DRIVERS\WSTCODEC.SYS
18:27:34.0312 3988 WSTCODEC - ok
18:27:34.0375 3988 MBR (0x1B8) (8f558eb6672622401da993e1e865c861) \Device\Harddisk0\DR0
18:27:34.0531 3988 \Device\Harddisk0\DR0 - ok
18:27:34.0546 3988 Boot (0x1200) (b3c2f3adc460d439484893ebc7e02e34) \Device\Harddisk0\DR0\Partition0
18:27:34.0546 3988 \Device\Harddisk0\DR0\Partition0 - ok
18:27:34.0546 3988 ============================================================
18:27:34.0546 3988 Scan finished
18:27:34.0546 3988 ============================================================
18:27:34.0578 1744 Detected object count: 0
18:27:34.0578 1744 Actual detected object count: 0

#4 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,078 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:01:46 PM

Posted 27 September 2011 - 07:59 PM

OK, I was pretty confident that was going to be it. Let's run these.

Run TFC by OT (Temp File Cleaner)
Please download TFC by Old Timer and save it to your desktop.
alternate download link

Save any unsaved work. TFC will close ALL open programs including your browser!
Double-click on TFC.exe to run it. If you are using Vista, right-click on the file and choose Run As Administrator.
Click the Start button to begin the cleaning process and let it run uninterrupted to completion.
Important! If TFC prompts you to reboot, please do so immediately. If not prompted, manually reboot the machine anyway to ensure a complete clean.

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

MartyL
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:12:46 PM

Posted 29 September 2011 - 07:15 AM

Hi,

Here are the results of the ESET Scan.

C:\32 Gig Thumb Drive\Techs\Boca Upgrade Files\Boca Printer\Orioles\bocatest.exe a variant of Win32/RemoteAdmin.NetCat.AB application deleted - quarantined
C:\32 Gig Thumb Drive\Techs\Boca Upgrade Files\Boca Printer\Orioles\customer.CAB a variant of Win32/RemoteAdmin.NetCat.AB application deleted - quarantined
C:\32 Gig Thumb Drive\Techs\Boca Upgrade Files\Boca Printer\Orioles\netcat.exe a variant of Win32/RemoteAdmin.NetCat.AB application cleaned by deleting - quarantined
C:\Documents and Settings\computer user\My Documents\Downloads\speedupmypc3plc.exe Win32/SpeedUpMyPC application deleted - quarantined
C:\Downloads\TimeLeft\cnet_timeleft_cn_exe.exe a variant of Win32/InstallCore.C application cleaned by deleting - quarantined
C:\Kingston 8 Gig\Enoch\Miscellaneous\IP Scanner\ipscan.exe Win32/NetTool.Portscan.C application cleaned by deleting - quarantined
C:\Kingston 8 Gig\Techs\Boca Upgrade Files\Boca Printer\Orioles\bocatest.exe a variant of Win32/RemoteAdmin.NetCat.AB application deleted - quarantined
C:\Kingston 8 Gig\Techs\Boca Upgrade Files\Boca Printer\Orioles\customer.CAB a variant of Win32/RemoteAdmin.NetCat.AB application deleted - quarantined
C:\Kingston 8 Gig\Techs\Boca Upgrade Files\Boca Printer\Orioles\netcat.exe a variant of Win32/RemoteAdmin.NetCat.AB application cleaned by deleting - quarantined
C:\System Volume Information\_restore{8C2EB45A-730B-453A-B1D6-5ECBEEE89CA1}\RP357\A0037139.exe a variant of Win32/RemoteAdmin.NetCat.AB application deleted - quarantined
C:\System Volume Information\_restore{8C2EB45A-730B-453A-B1D6-5ECBEEE89CA1}\RP357\A0037140.exe a variant of Win32/RemoteAdmin.NetCat.AB application cleaned by deleting - quarantined
C:\System Volume Information\_restore{8C2EB45A-730B-453A-B1D6-5ECBEEE89CA1}\RP357\A0037141.exe Win32/SpeedUpMyPC application deleted - quarantined
C:\System Volume Information\_restore{8C2EB45A-730B-453A-B1D6-5ECBEEE89CA1}\RP357\A0037142.exe a variant of Win32/InstallCore.C application cleaned by deleting - quarantined
C:\System Volume Information\_restore{8C2EB45A-730B-453A-B1D6-5ECBEEE89CA1}\RP357\A0037143.exe Win32/NetTool.Portscan.C application cleaned by deleting - quarantined
C:\System Volume Information\_restore{8C2EB45A-730B-453A-B1D6-5ECBEEE89CA1}\RP357\A0037144.exe a variant of Win32/RemoteAdmin.NetCat.AB application deleted - quarantined
C:\System Volume Information\_restore{8C2EB45A-730B-453A-B1D6-5ECBEEE89CA1}\RP357\A0037145.exe a variant of Win32/RemoteAdmin.NetCat.AB application cleaned by deleting - quarantined

#6 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,078 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:01:46 PM

Posted 29 September 2011 - 09:18 PM

How is it now? Your flash drive was also infected.If it was put in another PC that one is most likely infected 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 MartyL

MartyL
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:12:46 PM

Posted 29 September 2011 - 10:08 PM

I currently have IE opened to this site. That is all and in Task Manager there are still two instances of iexplore.exe. One is using 17 meg and the other is using 43 meg. It isn't choking my system like before but there are still two instances. If it helps, if I open an instance of Firefox, even with three tabs open there is only one instance of firefox.exe open in Task Manager. If I open a second tab in IE I get a third instance of iexplore.exe. If I open a third tab I still have three instances of iexplore.exe. When I close two tabs it takes about a minute for the third instance of iexplore.exe to go away.

#8 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,078 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:01:46 PM

Posted 29 September 2011 - 10:21 PM

Hi, Marty, As I read some arguments that after IE8 there is a possibility that this is normal due to improper closing of the browser(not by you).

I am not buying it though. So I suggest you post a dds log and be checked thoroughly.

We need a deeper look. Please go here....
Preparation Guide ,do steps 6 - 9.

Create a DDS log and post it in the new topic explained in step 9,which is here Virus, Trojan, Spyware, and Malware Removal Logs and not in this topic,thanks.
If Gmer won't run,skip it and move on.
Let me know if that went well.
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 MartyL

MartyL
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:12:46 PM

Posted 01 October 2011 - 01:26 AM

Hi Boopme,

I did as you requested. Defogger ran fine. DDS apparently ran fine but when it created the log files I did something wrong and didn't get the log files so I reran it. It ran fine. GMER seemed to run fine but had an issue. I walked away from it after it started and after somewhere between 15 and 30 minutes my PC rebooted on it's own. I then reran GMER and after several hours it finished. I posted the DDS log with a Topic of "DDS log requested from "Am I infected..." forum."

I am guessing that someone else will be helping me from this point on so I will take this opportunity to thank you very kindly for your time and assistance. If you like I will post you as to the final results.

Sincerely,

MartyL

#10 Orange Blossom

Orange Blossom

    OBleepin Investigator


  • Moderator
  • 36,911 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Bloomington, IN
  • Local time:01:46 PM

Posted 01 October 2011 - 02:56 AM

Hello,

Now that you have posted a log here: http://www.bleepingcomputer.com/forums/topic421359.html you should NOT make further changes to your computer (install/uninstall programs, use special fix tools, delete files, edit the registry, etc) unless advised by a MRT Team member, nor should you ask for help elsewhere. Doing so can result in system changes which may not show in the log you already posted. Further, any modifications you make on your own may cause confusion for the helper assisting you and could complicate the malware removal process which would extend the time it takes to clean your computer.

From this point on the MRT Team should be the only members that you take advice from, until they have verified your log as clean.

Please be patient. It may take a while to get a response because the MRT Team members are EXTREMELY busy working logs posted before yours. They are volunteers who will help you out as soon as possible. Once you have made your post and are waiting, please DO NOT make another reply until it has been responded to by a member of the MRT Team. Generally the staff checks the forum for postings that have 0 replies as this makes it easier for them to identify those who have not been helped. If you post another response there will be 1 reply. A team member, looking for a new log to work may assume another MRT Team member is already assisting you and not open the thread to respond.

Please be patient. It may take several days to get a response but your log will be reviewed and answered as soon as possible. I advise checking your topic once a day for responses as the e-mail notification system is unreliable.

If HelpBot replies to your topic, PLEASE follow Step One so it will report your topic to the team members.

To avoid confusion, I am closing this topic. Good luck with your log.

Orange Blossom :cherry:
Help us help you. If HelpBot replies, you MUST follow step 1 in its reply so we know you need help.

Orange Blossom

An ounce of prevention is worth a pound of cure

SpywareBlaster, WinPatrol Plus, ESET Smart Security, Malwarebytes' Anti-Malware, NoScript Firefox ext., Norton noscript




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users