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

Please Help Me Get Rid of a Nasty Virus!!!


  • Please log in to reply
7 replies to this topic

#1 pepperbc

pepperbc

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:10:46 AM

Posted 14 October 2011 - 01:40 PM

Hello! I recently got quite a nasty virus on my computer and do not know how to fix it. It hid all my files, refuses to let me access the Internet, and won't let me open any program. I also have no audio; it claims that I have no speakers, regardless of whether try to use my computer's speakers or my headphones. Using Safe Mode with Networking, I was able to unhide my files. I was also able to unhide programs, such as Microsoft Word, but it won't let me open any of these programs. I was unable to unhide my original Malwarebytes program. Whenever I try to reinstall Malwarebytes through a flashdrive, I get through all of the installation until the very end. Then a notice pops up that "Acess is denied", and then "Error: Setup was not completed. Please correct the problem and run Setup again". None of the forms of Rkill work either; however, nothing pops up when I run it. The regular RKill screen comes up for the blink of an eye, but before anything happens, it is shut right back down. I also tried to install Malwarebytes onto my flash drive, rather than just downloading the set-up and then installing to my computer, and run it directly from the flash drive. It did in fact run and found one minor virus. Unfortunately, it apparently didn't find, or was blocked from finding, the virus which is causing my problems as absolutely nothing changed in my computer. I don't know how it is blocking my Internet. I tried looking though Tools->Internet Options->Proxy Server and that wasn't the problem. Any possible help, even what exactly this virus is, would be greatly appreciated!! I admit that I have no clue what I'm dealing with here; I've never dealt with a virus that has blocked literally everything on my computer like this, there was always some way to circumvent it. Thank you for your time and help!!

BC AdBot (Login to Remove)

 


#2 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,058 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:12:46 PM

Posted 14 October 2011 - 02:07 PM

Hello and welcome.
Your may be bundling the ZeroAccess rootkit along with the rogue malware. This rootkit will terminate any process that scans one of the items it is protecting in the Windows Registry or the file system. It will then change the permissions on that program so that when you attempt to run it again you will receive an access denied message. If you are infected with this Rootkit, then the following guide will not be able to remove the infection unless you first remove the rootkit. You can attempt to remove the rootkit using TDSSKiller as outlined below.

Please download the TDSS Rootkit Removing Tool (TDSSKiller.exe) and save it to your Desktop. <-Important!!!
Be sure to download TDSSKiller.exe (v2.6.4.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. 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 start Windows 7 in Safe Mode

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


Please click Start > Run, type inetcpl.cpl in the runbox and press enter.
Click the Connections tab and click the LAN settings option.
Verify if "Use a proxy..." is checked, if so, UNcheck it and click OK/OK to exit.


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


Now run MBAM (MalwareBytes):

Please download Malwarebytes Anti-Malware and save it to your desktop.
Download Link 1
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.
[color=green]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 pepperbc

pepperbc
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:10:46 AM

Posted 14 October 2011 - 10:48 PM

Here is the log of the TDSS.

01:52:47.0437 1420 TDSS rootkit removing tool 2.6.9.0 Oct 14 2011 11:33:24
01:52:47.0562 1420 ============================================================
01:52:47.0562 1420 Current date / time: 2002/01/07 01:52:47.0562
01:52:47.0562 1420 SystemInfo:
01:52:47.0562 1420
01:52:47.0562 1420 OS Version: 5.1.2600 ServicePack: 3.0
01:52:47.0562 1420 Product type: Workstation
01:52:47.0562 1420 ComputerName: YOUR-C2M9Q2LBPX
01:52:47.0562 1420 UserName: Annika
01:52:47.0562 1420 Windows directory: C:\WINDOWS
01:52:47.0562 1420 System windows directory: C:\WINDOWS
01:52:47.0562 1420 Processor architecture: Intel x86
01:52:47.0562 1420 Number of processors: 2
01:52:47.0562 1420 Page size: 0x1000
01:52:47.0562 1420 Boot type: Safe boot with network
01:52:47.0562 1420 ============================================================
01:52:48.0812 1420 Initialize success
01:52:52.0750 1452 ============================================================
01:52:52.0750 1452 Scan started
01:52:52.0750 1452 Mode: Manual;
01:52:52.0750 1452 ============================================================
01:52:53.0171 1452 9eb22451 (8f2bb1827cac01aee6a16e30a1260199) C:\WINDOWS\1361359518:1632492462.exe
01:52:53.0796 1452 Suspicious file (Hidden): C:\WINDOWS\1361359518:1632492462.exe. md5: 8f2bb1827cac01aee6a16e30a1260199
01:52:53.0796 1452 9eb22451 ( HiddenFile.Multi.Generic ) - warning
01:52:53.0796 1452 9eb22451 - detected HiddenFile.Multi.Generic (1)
01:52:53.0828 1452 Abiosdsk - ok
01:52:53.0859 1452 abp480n5 - ok
01:52:53.0937 1452 ACPI (8fd99680a539792a30e97944fdaecf17) C:\WINDOWS\system32\DRIVERS\ACPI.sys
01:52:53.0953 1452 ACPI - ok
01:52:53.0984 1452 ACPIEC (9859c0f6936e723e4892d7141b1327d5) C:\WINDOWS\system32\DRIVERS\ACPIEC.sys
01:52:53.0984 1452 ACPIEC - ok
01:52:54.0015 1452 adpu160m - ok
01:52:54.0093 1452 aec (8bed39e3c35d6a489438b8141717a557) C:\WINDOWS\system32\drivers\aec.sys
01:52:54.0109 1452 aec - ok
01:52:54.0156 1452 AFD (7e775010ef291da96ad17ca4b17137d7) C:\WINDOWS\System32\drivers\afd.sys
01:52:54.0156 1452 AFD - ok
01:52:54.0171 1452 Aha154x - ok
01:52:54.0203 1452 aic78u2 - ok
01:52:54.0234 1452 aic78xx - ok
01:52:54.0343 1452 AliIde - ok
01:52:54.0453 1452 Ambfilt (f6af59d6eee5e1c304f7f73706ad11d8) C:\WINDOWS\system32\drivers\Ambfilt.sys
01:52:54.0531 1452 Ambfilt - ok
01:52:54.0578 1452 amsint - ok
01:52:54.0718 1452 AR5416 (e0ee769d14128014965e03b433f5f46e) C:\WINDOWS\system32\DRIVERS\athw.sys
01:52:54.0796 1452 AR5416 - ok
01:52:54.0812 1452 asc - ok
01:52:54.0843 1452 asc3350p - ok
01:52:54.0875 1452 asc3550 - ok
01:52:54.0984 1452 AsusACPI (12415a4b61ded200fe9932b47a35fa42) C:\WINDOWS\system32\DRIVERS\ASUSACPI.sys
01:52:54.0984 1452 AsusACPI - ok
01:52:55.0031 1452 AsyncMac (b153affac761e7f5fcfa822b9c4e97bc) C:\WINDOWS\system32\DRIVERS\asyncmac.sys
01:52:55.0031 1452 AsyncMac - ok
01:52:55.0078 1452 atapi (9f3a2f5aa6875c72bf062c712cfa2674) C:\WINDOWS\system32\DRIVERS\atapi.sys
01:52:55.0093 1452 atapi - ok
01:52:55.0109 1452 Atdisk - ok
01:52:55.0156 1452 Atmarpc (9916c1225104ba14794209cfa8012159) C:\WINDOWS\system32\DRIVERS\atmarpc.sys
01:52:55.0156 1452 Atmarpc - ok
01:52:55.0218 1452 audstub (d9f724aa26c010a217c97606b160ed68) C:\WINDOWS\system32\DRIVERS\audstub.sys
01:52:55.0218 1452 audstub - ok
01:52:55.0281 1452 Beep (da1f27d85e0d1525f6621372e7b685e9) C:\WINDOWS\system32\drivers\Beep.sys
01:52:55.0281 1452 Beep - ok
01:52:55.0359 1452 btaudio - ok
01:52:55.0390 1452 BTDriver - ok
01:52:55.0421 1452 BTWDNDIS - ok
01:52:55.0453 1452 btwhid - ok
01:52:55.0500 1452 BTWUSB - ok
01:52:55.0562 1452 cbidf2k (90a673fc8e12a79afbed2576f6a7aaf9) C:\WINDOWS\system32\drivers\cbidf2k.sys
01:52:55.0562 1452 cbidf2k - ok
01:52:55.0593 1452 CCDECODE (0be5aef125be881c4f854c554f2b025c) C:\WINDOWS\system32\DRIVERS\CCDECODE.sys
01:52:55.0593 1452 CCDECODE - ok
01:52:55.0609 1452 cd20xrnt - ok
01:52:55.0703 1452 Cdaudio (c1b486a7658353d33a10cc15211a873b) C:\WINDOWS\system32\drivers\Cdaudio.sys
01:52:55.0703 1452 Cdaudio - ok
01:52:55.0734 1452 Cdfs (c885b02847f5d2fd45a24e219ed93b32) C:\WINDOWS\system32\drivers\Cdfs.sys
01:52:55.0750 1452 Cdfs - ok
01:52:55.0796 1452 Cdrom (1f4260cc5b42272d71f79e570a27a4fe) C:\WINDOWS\system32\DRIVERS\cdrom.sys
01:52:55.0796 1452 Cdrom - ok
01:52:55.0812 1452 Changer - ok
01:52:55.0921 1452 CmBatt (0f6c187d38d98f8df904589a5f94d411) C:\WINDOWS\system32\DRIVERS\CmBatt.sys
01:52:55.0921 1452 CmBatt - ok
01:52:55.0937 1452 CmdIde - ok
01:52:55.0984 1452 Compbatt (6e4c9f21f0fae8940661144f41b13203) C:\WINDOWS\system32\DRIVERS\compbatt.sys
01:52:55.0984 1452 Compbatt - ok
01:52:56.0046 1452 Cpqarray - ok
01:52:56.0093 1452 dac2w2k - ok
01:52:56.0125 1452 dac960nt - ok
01:52:56.0171 1452 Disk (044452051f3e02e7963599fc8f4f3e25) C:\WINDOWS\system32\DRIVERS\disk.sys
01:52:56.0171 1452 Disk - ok
01:52:56.0265 1452 dmboot (d992fe1274bde0f84ad826acae022a41) C:\WINDOWS\system32\drivers\dmboot.sys
01:52:56.0312 1452 dmboot - ok
01:52:56.0328 1452 dmio (7c824cf7bbde77d95c08005717a95f6f) C:\WINDOWS\system32\drivers\dmio.sys
01:52:56.0343 1452 dmio - ok
01:52:56.0375 1452 dmload (e9317282a63ca4d188c0df5e09c6ac5f) C:\WINDOWS\system32\drivers\dmload.sys
01:52:56.0375 1452 dmload - ok
01:52:56.0453 1452 DMusic (8a208dfcf89792a484e76c40e5f50b45) C:\WINDOWS\system32\drivers\DMusic.sys
01:52:56.0453 1452 DMusic - ok
01:52:56.0500 1452 dpti2o - ok
01:52:56.0562 1452 drmkaud (8f5fcff8e8848afac920905fbd9d33c8) C:\WINDOWS\system32\drivers\drmkaud.sys
01:52:56.0562 1452 drmkaud - ok
01:52:56.0671 1452 Fastfat (38d332a6d56af32635675f132548343e) C:\WINDOWS\system32\drivers\Fastfat.sys
01:52:56.0671 1452 Fastfat - ok
01:52:56.0718 1452 Fdc (92cdd60b6730b9f50f6a1a0c1f8cdc81) C:\WINDOWS\system32\drivers\Fdc.sys
01:52:56.0718 1452 Fdc - ok
01:52:56.0734 1452 Fips (d45926117eb9fa946a6af572fbe1caa3) C:\WINDOWS\system32\drivers\Fips.sys
01:52:56.0750 1452 Fips - ok
01:52:56.0781 1452 Flpydisk (9d27e7b80bfcdf1cdd9b555862d5e7f0) C:\WINDOWS\system32\drivers\Flpydisk.sys
01:52:56.0781 1452 Flpydisk - ok
01:52:56.0812 1452 FltMgr (b2cf4b0786f8212cb92ed2b50c6db6b0) C:\WINDOWS\system32\DRIVERS\fltMgr.sys
01:52:56.0828 1452 FltMgr - ok
01:52:56.0921 1452 fssfltr (c6ee3a87fe609d3e1db9dbd072a248de) C:\WINDOWS\system32\DRIVERS\fssfltr_tdi.sys
01:52:56.0921 1452 fssfltr - ok
01:52:56.0953 1452 Fs_Rec (3e1e2bd4f39b0e2b7dc4f4d2bcc2779a) C:\WINDOWS\system32\drivers\Fs_Rec.sys
01:52:56.0968 1452 Fs_Rec - ok
01:52:57.0015 1452 Ftdisk (6ac26732762483366c3969c9e4d2259d) C:\WINDOWS\system32\DRIVERS\ftdisk.sys
01:52:57.0031 1452 Ftdisk - ok
01:52:57.0078 1452 GEARAspiWDM (8182ff89c65e4d38b2de4bb0fb18564e) C:\WINDOWS\system32\DRIVERS\GEARAspiWDM.sys
01:52:57.0078 1452 GEARAspiWDM - ok
01:52:57.0109 1452 Gpc (0a02c63c8b144bd8c86b103dee7c86a2) C:\WINDOWS\system32\DRIVERS\msgpc.sys
01:52:57.0109 1452 Gpc - ok
01:52:57.0156 1452 HDAudBus (573c7d0a32852b48f3058cfd8026f511) C:\WINDOWS\system32\DRIVERS\HDAudBus.sys
01:52:57.0156 1452 HDAudBus - ok
01:52:57.0265 1452 HidUsb (ccf82c5ec8a7326c3066de870c06daf1) C:\WINDOWS\system32\DRIVERS\hidusb.sys
01:52:57.0265 1452 HidUsb - ok
01:52:57.0296 1452 hpn - ok
01:52:57.0406 1452 HPZid412 (d03d10f7ded688fecf50f8fbf1ea9b8a) C:\WINDOWS\system32\DRIVERS\HPZid412.sys
01:52:57.0406 1452 HPZid412 - ok
01:52:57.0437 1452 HPZipr12 (89f41658929393487b6b7d13c8528ce3) C:\WINDOWS\system32\DRIVERS\HPZipr12.sys
01:52:57.0437 1452 HPZipr12 - ok
01:52:57.0500 1452 HPZius12 (abcb05ccdbf03000354b9553820e39f8) C:\WINDOWS\system32\DRIVERS\HPZius12.sys
01:52:57.0500 1452 HPZius12 - ok
01:52:57.0546 1452 HTTP (f80a415ef82cd06ffaf0d971528ead38) C:\WINDOWS\system32\Drivers\HTTP.sys
01:52:57.0562 1452 HTTP - ok
01:52:57.0593 1452 i2omgmt - ok
01:52:57.0625 1452 i2omp - ok
01:52:57.0671 1452 i8042prt (4a0b06aa8943c1e332520f7440c0aa30) C:\WINDOWS\system32\DRIVERS\i8042prt.sys
01:52:57.0671 1452 i8042prt - ok
01:52:57.0921 1452 ialm (0f68e2ec713f132ffb19e45415b09679) C:\WINDOWS\system32\DRIVERS\igxpmp32.sys
01:52:58.0078 1452 ialm - ok
01:52:58.0125 1452 iaStor (8ef427c54497c5f8a7a645990e4278c7) C:\WINDOWS\system32\drivers\iaStor.sys
01:52:58.0140 1452 iaStor - ok
01:52:58.0203 1452 Imapi (083a052659f5310dd8b6a6cb05edcf8e) C:\WINDOWS\system32\DRIVERS\imapi.sys
01:52:58.0203 1452 Imapi - ok
01:52:58.0250 1452 ini910u - ok
01:52:58.0468 1452 IntcAzAudAddService (9037c8bd3e896d7f2803a171fdeaeef4) C:\WINDOWS\system32\drivers\RtkHDAud.sys
01:52:58.0656 1452 IntcAzAudAddService - ok
01:52:58.0671 1452 IntelIde - ok
01:52:58.0750 1452 intelppm (8c953733d8f36eb2133f5bb58808b66b) C:\WINDOWS\system32\DRIVERS\intelppm.sys
01:52:58.0750 1452 intelppm - ok
01:52:58.0781 1452 Ip6Fw (3bb22519a194418d5fec05d800a19ad0) C:\WINDOWS\system32\DRIVERS\Ip6Fw.sys
01:52:58.0781 1452 Ip6Fw - ok
01:52:58.0812 1452 IpFilterDriver (731f22ba402ee4b62748adaf6363c182) C:\WINDOWS\system32\DRIVERS\ipfltdrv.sys
01:52:58.0812 1452 IpFilterDriver - ok
01:52:58.0843 1452 IpInIp (b87ab476dcf76e72010632b5550955f5) C:\WINDOWS\system32\DRIVERS\ipinip.sys
01:52:58.0843 1452 IpInIp - ok
01:52:58.0890 1452 IpNat (cc748ea12c6effde940ee98098bf96bb) C:\WINDOWS\system32\DRIVERS\ipnat.sys
01:52:58.0890 1452 IpNat - ok
01:52:58.0953 1452 IPSec (23c74d75e36e7158768dd63d92789a91) C:\WINDOWS\system32\DRIVERS\ipsec.sys
01:52:58.0953 1452 IPSec - ok
01:52:59.0000 1452 IRENUM (c93c9ff7b04d772627a3646d89f7bf89) C:\WINDOWS\system32\DRIVERS\irenum.sys
01:52:59.0000 1452 IRENUM - ok
01:52:59.0046 1452 isapnp (05a299ec56e52649b1cf2fc52d20f2d7) C:\WINDOWS\system32\DRIVERS\isapnp.sys
01:52:59.0046 1452 isapnp - ok
01:52:59.0062 1452 Kbdclass (463c1ec80cd17420a542b7f36a36f128) C:\WINDOWS\system32\DRIVERS\kbdclass.sys
01:52:59.0078 1452 Kbdclass - ok
01:52:59.0125 1452 kmixer (692bcf44383d056aed41b045a323d378) C:\WINDOWS\system32\drivers\kmixer.sys
01:52:59.0140 1452 kmixer - ok
01:52:59.0171 1452 KSecDD (b467646c54cc746128904e1654c750c1) C:\WINDOWS\system32\drivers\KSecDD.sys
01:52:59.0171 1452 KSecDD - ok
01:52:59.0203 1452 L1c (6c8658587e91ea25b0fd2e71781ad228) C:\WINDOWS\system32\DRIVERS\l1c51x86.sys
01:52:59.0218 1452 L1c - ok
01:52:59.0265 1452 lbrtfdc - ok
01:52:59.0343 1452 MBAMSwissArmy - ok
01:52:59.0421 1452 mnmdd (4ae068242760a1fb6e1a44bf4e16afa6) C:\WINDOWS\system32\drivers\mnmdd.sys
01:52:59.0421 1452 mnmdd - ok
01:52:59.0468 1452 Modem (dfcbad3cec1c5f964962ae10e0bcc8e1) C:\WINDOWS\system32\drivers\Modem.sys
01:52:59.0468 1452 Modem - ok
01:52:59.0578 1452 Monfilt (9fa7207d1b1adead88ae8eed9cdbbaa5) C:\WINDOWS\system32\drivers\Monfilt.sys
01:52:59.0625 1452 Monfilt - ok
01:52:59.0671 1452 Mouclass (35c9e97194c8cfb8430125f8dbc34d04) C:\WINDOWS\system32\DRIVERS\mouclass.sys
01:52:59.0671 1452 Mouclass - ok
01:52:59.0734 1452 mouhid (b1c303e17fb9d46e87a98e4ba6769685) C:\WINDOWS\system32\DRIVERS\mouhid.sys
01:52:59.0734 1452 mouhid - ok
01:52:59.0765 1452 MountMgr (a80b9a0bad1b73637dbcbba7df72d3fd) C:\WINDOWS\system32\drivers\MountMgr.sys
01:52:59.0765 1452 MountMgr - ok
01:52:59.0781 1452 mraid35x - ok
01:52:59.0828 1452 MRxDAV (11d42bb6206f33fbb3ba0288d3ef81bd) C:\WINDOWS\system32\DRIVERS\mrxdav.sys
01:52:59.0828 1452 MRxDAV - ok
01:52:59.0890 1452 MRxSmb (f3aefb11abc521122b67095044169e98) C:\WINDOWS\system32\DRIVERS\mrxsmb.sys
01:52:59.0921 1452 MRxSmb - ok
01:52:59.0984 1452 Msfs (c941ea2454ba8350021d774daf0f1027) C:\WINDOWS\system32\drivers\Msfs.sys
01:53:00.0000 1452 Msfs - ok
01:53:00.0046 1452 MSKSSRV (d1575e71568f4d9e14ca56b7b0453bf1) C:\WINDOWS\system32\drivers\MSKSSRV.sys
01:53:00.0046 1452 MSKSSRV - ok
01:53:00.0078 1452 MSPCLOCK (325bb26842fc7ccc1fcce2c457317f3e) C:\WINDOWS\system32\drivers\MSPCLOCK.sys
01:53:00.0078 1452 MSPCLOCK - ok
01:53:00.0109 1452 MSPQM (bad59648ba099da4a17680b39730cb3d) C:\WINDOWS\system32\drivers\MSPQM.sys
01:53:00.0109 1452 MSPQM - ok
01:53:00.0140 1452 mssmbios (af5f4f3f14a8ea2c26de30f7a1e17136) C:\WINDOWS\system32\DRIVERS\mssmbios.sys
01:53:00.0156 1452 mssmbios - ok
01:53:00.0187 1452 MSTEE (e53736a9e30c45fa9e7b5eac55056d1d) C:\WINDOWS\system32\drivers\MSTEE.sys
01:53:00.0187 1452 MSTEE - ok
01:53:00.0250 1452 Mup (2f625d11385b1a94360bfc70aaefdee1) C:\WINDOWS\system32\drivers\Mup.sys
01:53:00.0250 1452 Mup - ok
01:53:00.0281 1452 NABTSFEC (5b50f1b2a2ed47d560577b221da734db) C:\WINDOWS\system32\DRIVERS\NABTSFEC.sys
01:53:00.0281 1452 NABTSFEC - ok
01:53:00.0343 1452 NDIS (1df7f42665c94b825322fae71721130d) C:\WINDOWS\system32\drivers\NDIS.sys
01:53:00.0359 1452 NDIS - ok
01:53:00.0390 1452 NdisIP (7ff1f1fd8609c149aa432f95a8163d97) C:\WINDOWS\system32\DRIVERS\NdisIP.sys
01:53:00.0390 1452 NdisIP - ok
01:53:00.0437 1452 NdisTapi (1ab3d00c991ab086e69db84b6c0ed78f) C:\WINDOWS\system32\DRIVERS\ndistapi.sys
01:53:00.0437 1452 NdisTapi - ok
01:53:00.0453 1452 Ndisuio (f927a4434c5028758a842943ef1a3849) C:\WINDOWS\system32\DRIVERS\ndisuio.sys
01:53:00.0468 1452 Ndisuio - ok
01:53:00.0500 1452 NdisWan (edc1531a49c80614b2cfda43ca8659ab) C:\WINDOWS\system32\DRIVERS\ndiswan.sys
01:53:00.0500 1452 NdisWan - ok
01:53:00.0531 1452 NDProxy (6215023940cfd3702b46abc304e1d45a) C:\WINDOWS\system32\drivers\NDProxy.sys
01:53:00.0531 1452 NDProxy - ok
01:53:00.0593 1452 NetBIOS (5d81cf9a2f1a3a756b66cf684911cdf0) C:\WINDOWS\system32\DRIVERS\netbios.sys
01:53:00.0609 1452 NetBIOS - ok
01:53:00.0640 1452 NetBT (20e150224235dc1b154b4df58fd73680) C:\WINDOWS\system32\DRIVERS\netbt.sys
01:53:00.0640 1452 Suspicious file (Forged): C:\WINDOWS\system32\DRIVERS\netbt.sys. Real md5: 20e150224235dc1b154b4df58fd73680, Fake md5: 74b2b2f5bea5e9a3dc021d685551bd3d
01:53:00.0640 1452 NetBT ( Rootkit.Win32.ZAccess.h ) - infected
01:53:00.0640 1452 NetBT - detected Rootkit.Win32.ZAccess.h (0)
01:53:00.0765 1452 Npfs (3182d64ae053d6fb034f44b6def8034a) C:\WINDOWS\system32\drivers\Npfs.sys
01:53:00.0765 1452 Npfs - ok
01:53:00.0828 1452 Ntfs (78a08dd6a8d65e697c18e1db01c5cdca) C:\WINDOWS\system32\drivers\Ntfs.sys
01:53:00.0859 1452 Ntfs - ok
01:53:00.0906 1452 Null (73c1e1f395918bc2c6dd67af7591a3ad) C:\WINDOWS\system32\drivers\Null.sys
01:53:00.0921 1452 Null - ok
01:53:00.0953 1452 NwlnkFlt (b305f3fad35083837ef46a0bbce2fc57) C:\WINDOWS\system32\DRIVERS\nwlnkflt.sys
01:53:00.0953 1452 NwlnkFlt - ok
01:53:00.0984 1452 NwlnkFwd (c99b3415198d1aab7227f2c88fd664b9) C:\WINDOWS\system32\DRIVERS\nwlnkfwd.sys
01:53:01.0000 1452 NwlnkFwd - ok
01:53:01.0078 1452 Parport (5575faf8f97ce5e713d108c2a58d7c7c) C:\WINDOWS\system32\drivers\Parport.sys
01:53:01.0078 1452 Parport - ok
01:53:01.0109 1452 PartMgr (beb3ba25197665d82ec7065b724171c6) C:\WINDOWS\system32\drivers\PartMgr.sys
01:53:01.0125 1452 PartMgr - ok
01:53:01.0156 1452 ParVdm (70e98b3fd8e963a6a46a2e6247e0bea1) C:\WINDOWS\system32\drivers\ParVdm.sys
01:53:01.0156 1452 ParVdm - ok
01:53:01.0218 1452 PCI (a219903ccf74233761d92bef471a07b1) C:\WINDOWS\system32\DRIVERS\pci.sys
01:53:01.0218 1452 PCI - ok
01:53:01.0250 1452 PCIDump - ok
01:53:01.0281 1452 PCIIde (ccf5f451bb1a5a2a522a76e670000ff0) C:\WINDOWS\system32\DRIVERS\pciide.sys
01:53:01.0281 1452 PCIIde - ok
01:53:01.0343 1452 Pcmcia (9e89ef60e9ee05e3f2eef2da7397f1c1) C:\WINDOWS\system32\drivers\Pcmcia.sys
01:53:01.0359 1452 Pcmcia - ok
01:53:01.0375 1452 PDCOMP - ok
01:53:01.0390 1452 PDFRAME - ok
01:53:01.0421 1452 PDRELI - ok
01:53:01.0453 1452 PDRFRAME - ok
01:53:01.0484 1452 perc2 - ok
01:53:01.0515 1452 perc2hib - ok
01:53:01.0656 1452 PptpMiniport (efeec01b1d3cf84f16ddd24d9d9d8f99) C:\WINDOWS\system32\DRIVERS\raspptp.sys
01:53:01.0656 1452 PptpMiniport - ok
01:53:01.0703 1452 PSched (09298ec810b07e5d582cb3a3f9255424) C:\WINDOWS\system32\DRIVERS\psched.sys
01:53:01.0703 1452 PSched - ok
01:53:01.0718 1452 Ptilink (80d317bd1c3dbc5d4fe7b1678c60cadd) C:\WINDOWS\system32\DRIVERS\ptilink.sys
01:53:01.0734 1452 Ptilink - ok
01:53:01.0750 1452 ql1080 - ok
01:53:01.0781 1452 Ql10wnt - ok
01:53:01.0812 1452 ql12160 - ok
01:53:01.0843 1452 ql1240 - ok
01:53:01.0875 1452 ql1280 - ok
01:53:01.0906 1452 RasAcd (fe0d99d6f31e4fad8159f690d68ded9c) C:\WINDOWS\system32\DRIVERS\rasacd.sys
01:53:01.0906 1452 RasAcd - ok
01:53:01.0953 1452 Rasl2tp (11b4a627bc9614b885c4969bfa5ff8a6) C:\WINDOWS\system32\DRIVERS\rasl2tp.sys
01:53:01.0953 1452 Rasl2tp - ok
01:53:02.0015 1452 RasPppoe (5bc962f2654137c9909c3d4603587dee) C:\WINDOWS\system32\DRIVERS\raspppoe.sys
01:53:02.0015 1452 RasPppoe - ok
01:53:02.0062 1452 Raspti (fdbb1d60066fcfbb7452fd8f9829b242) C:\WINDOWS\system32\DRIVERS\raspti.sys
01:53:02.0062 1452 Raspti - ok
01:53:02.0125 1452 Rdbss (7ad224ad1a1437fe28d89cf22b17780a) C:\WINDOWS\system32\DRIVERS\rdbss.sys
01:53:02.0125 1452 Rdbss - ok
01:53:02.0171 1452 RDPCDD (4912d5b403614ce99c28420f75353332) C:\WINDOWS\system32\DRIVERS\RDPCDD.sys
01:53:02.0171 1452 RDPCDD - ok
01:53:02.0250 1452 RDPWD (6728e45b66f93c08f11de2e316fc70dd) C:\WINDOWS\system32\drivers\RDPWD.sys
01:53:02.0265 1452 RDPWD - ok
01:53:02.0343 1452 redbook (f828dd7e1419b6653894a8f97a0094c5) C:\WINDOWS\system32\DRIVERS\redbook.sys
01:53:02.0343 1452 redbook - ok
01:53:02.0500 1452 Secdrv (90a3935d05b494a5a39d37e71f09a677) C:\WINDOWS\system32\DRIVERS\secdrv.sys
01:53:02.0500 1452 Secdrv - ok
01:53:02.0578 1452 Serial (cca207a8896d4c6a0c9ce29a4ae411a7) C:\WINDOWS\system32\drivers\Serial.sys
01:53:02.0578 1452 Serial - ok
01:53:02.0656 1452 Sfloppy (8e6b8c671615d126fdc553d1e2de5562) C:\WINDOWS\system32\drivers\Sfloppy.sys
01:53:02.0656 1452 Sfloppy - ok
01:53:02.0703 1452 Simbad - ok
01:53:02.0750 1452 SLIP (866d538ebe33709a5c9f5c62b73b7d14) C:\WINDOWS\system32\DRIVERS\SLIP.sys
01:53:02.0750 1452 SLIP - ok
01:53:02.0796 1452 Sparrow - ok
01:53:02.0859 1452 splitter (ab8b92451ecb048a4d1de7c3ffcb4a9f) C:\WINDOWS\system32\drivers\splitter.sys
01:53:02.0859 1452 splitter - ok
01:53:02.0921 1452 sr (76bb022c2fb6902fd5bdd4f78fc13a5d) C:\WINDOWS\system32\DRIVERS\sr.sys
01:53:02.0921 1452 sr - ok
01:53:02.0984 1452 SRS_PremiumSound_Service (0bd44aa4743a9dbd2c638d699a7fd438) C:\WINDOWS\system32\drivers\srs_PremiumSound_i386.sys
01:53:03.0000 1452 SRS_PremiumSound_Service - ok
01:53:03.0046 1452 Srv (89220b427890aa1dffd1a02648ae51c3) C:\WINDOWS\system32\DRIVERS\srv.sys
01:53:03.0062 1452 Srv - ok
01:53:03.0125 1452 streamip (77813007ba6265c4b6098187e6ed79d2) C:\WINDOWS\system32\DRIVERS\StreamIP.sys
01:53:03.0140 1452 streamip - ok
01:53:03.0187 1452 swenum (3941d127aef12e93addf6fe6ee027e0f) C:\WINDOWS\system32\DRIVERS\swenum.sys
01:53:03.0187 1452 swenum - ok
01:53:03.0250 1452 swmidi (8ce882bcc6cf8a62f2b2323d95cb3d01) C:\WINDOWS\system32\drivers\swmidi.sys
01:53:03.0250 1452 swmidi - ok
01:53:03.0281 1452 symc810 - ok
01:53:03.0312 1452 symc8xx - ok
01:53:03.0343 1452 sym_hi - ok
01:53:03.0359 1452 sym_u3 - ok
01:53:03.0421 1452 SynTP (a10d781153bb23036b474ffedb448266) C:\WINDOWS\system32\DRIVERS\SynTP.sys
01:53:03.0421 1452 SynTP - ok
01:53:03.0453 1452 sysaudio (8b83f3ed0f1688b4958f77cd6d2bf290) C:\WINDOWS\system32\drivers\sysaudio.sys
01:53:03.0453 1452 sysaudio - ok
01:53:03.0546 1452 Tcpip (9aefa14bd6b182d61e3119fa5f436d3d) C:\WINDOWS\system32\DRIVERS\tcpip.sys
01:53:03.0562 1452 Tcpip - ok
01:53:03.0593 1452 TDPIPE (6471a66807f5e104e4885f5b67349397) C:\WINDOWS\system32\drivers\TDPIPE.sys
01:53:03.0593 1452 TDPIPE - ok
01:53:03.0640 1452 TDTCP (c56b6d0402371cf3700eb322ef3aaf61) C:\WINDOWS\system32\drivers\TDTCP.sys
01:53:03.0640 1452 TDTCP - ok
01:53:03.0687 1452 TermDD (88155247177638048422893737429d9e) C:\WINDOWS\system32\DRIVERS\termdd.sys
01:53:03.0687 1452 TermDD - ok
01:53:03.0734 1452 TosIde - ok
01:53:03.0812 1452 Udfs (5787b80c2e3c5e2f56c2a233d91fa2c9) C:\WINDOWS\system32\drivers\Udfs.sys
01:53:03.0828 1452 Udfs - ok
01:53:03.0843 1452 ultra - ok
01:53:03.0906 1452 Update (402ddc88356b1bac0ee3dd1580c76a31) C:\WINDOWS\system32\DRIVERS\update.sys
01:53:03.0921 1452 Update - ok
01:53:04.0000 1452 USBAAPL (5c2bdc152bbab34f36473deaf7713f22) C:\WINDOWS\system32\Drivers\usbaapl.sys
01:53:04.0000 1452 USBAAPL - ok
01:53:04.0031 1452 usbccgp (173f317ce0db8e21322e71b7e60a27e8) C:\WINDOWS\system32\DRIVERS\usbccgp.sys
01:53:04.0031 1452 usbccgp - ok
01:53:04.0078 1452 usbehci (65dcf09d0e37d4c6b11b5b0b76d470a7) C:\WINDOWS\system32\DRIVERS\usbehci.sys
01:53:04.0078 1452 usbehci - ok
01:53:04.0109 1452 usbhub (1ab3cdde553b6e064d2e754efe20285c) C:\WINDOWS\system32\DRIVERS\usbhub.sys
01:53:04.0109 1452 usbhub - ok
01:53:04.0171 1452 usbprint (a717c8721046828520c9edf31288fc00) C:\WINDOWS\system32\DRIVERS\usbprint.sys
01:53:04.0171 1452 usbprint - ok
01:53:04.0203 1452 usbscan (a0b8cf9deb1184fbdd20784a58fa75d4) C:\WINDOWS\system32\DRIVERS\usbscan.sys
01:53:04.0203 1452 usbscan - ok
01:53:04.0234 1452 usbstor (a32426d9b14a089eaa1d922e0c5801a9) C:\WINDOWS\system32\DRIVERS\USBSTOR.SYS
01:53:04.0234 1452 usbstor - ok
01:53:04.0265 1452 usbuhci (26496f9dee2d787fc3e61ad54821ffe6) C:\WINDOWS\system32\DRIVERS\usbuhci.sys
01:53:04.0265 1452 usbuhci - ok
01:53:04.0312 1452 usbvideo (63bbfca7f390f4c49ed4b96bfb1633e0) C:\WINDOWS\system32\Drivers\usbvideo.sys
01:53:04.0312 1452 usbvideo - ok
01:53:04.0375 1452 uvclf (c019889035cdc1a06f2febc93cbb6897) C:\WINDOWS\system32\DRIVERS\uvclf.sys
01:53:04.0390 1452 uvclf - ok
01:53:04.0406 1452 VgaSave (0d3a8fafceacd8b7625cd549757a7df1) C:\WINDOWS\System32\drivers\vga.sys
01:53:04.0406 1452 VgaSave - ok
01:53:04.0437 1452 ViaIde - ok
01:53:04.0484 1452 VolSnap (4c8fcb5cc53aab716d810740fe59d025) C:\WINDOWS\system32\drivers\VolSnap.sys
01:53:04.0500 1452 VolSnap - ok
01:53:04.0562 1452 Wanarp (e20b95baedb550f32dd489265c1da1f6) C:\WINDOWS\system32\DRIVERS\wanarp.sys
01:53:04.0562 1452 Wanarp - ok
01:53:04.0625 1452 Wdf01000 (bbcfeab7e871cddac2d397ee7fa91fdc) C:\WINDOWS\system32\Drivers\wdf01000.sys
01:53:04.0640 1452 Wdf01000 - ok
01:53:04.0656 1452 WDICA - ok
01:53:04.0718 1452 wdmaud (6768acf64b18196494413695f0c3a00f) C:\WINDOWS\system32\drivers\wdmaud.sys
01:53:04.0734 1452 wdmaud - ok
01:53:04.0984 1452 WSTCODEC (c98b39829c2bbd34e454150633c62c78) C:\WINDOWS\system32\DRIVERS\WSTCODEC.SYS
01:53:05.0000 1452 WSTCODEC - ok
01:53:05.0078 1452 WudfPf (f15feafffbb3644ccc80c5da584e6311) C:\WINDOWS\system32\DRIVERS\WudfPf.sys
01:53:05.0078 1452 WudfPf - ok
01:53:05.0109 1452 WudfRd (28b524262bce6de1f7ef9f510ba3985b) C:\WINDOWS\system32\DRIVERS\wudfrd.sys
01:53:05.0109 1452 WudfRd - ok
01:53:05.0234 1452 MBR (0x1B8) (6f9a1d528242bc09104b85e0becf5554) \Device\Harddisk0\DR0
01:53:05.0234 1452 \Device\Harddisk0\DR0 ( Rootkit.Boot.SST.a ) - infected
01:53:05.0234 1452 \Device\Harddisk0\DR0 - detected Rootkit.Boot.SST.a (0)
01:53:05.0250 1452 MBR (0x1B8) (ddae9d649db12f6aff24483f2c298989) \Device\Harddisk1\DR4
01:53:05.0265 1452 \Device\Harddisk1\DR4 - ok
01:53:05.0281 1452 Boot (0x1200) (eb8cf641e180c13235e105956ea1f22d) \Device\Harddisk0\DR0\Partition0
01:53:05.0281 1452 \Device\Harddisk0\DR0\Partition0 - ok
01:53:05.0312 1452 Boot (0x1200) (e81015ef1096851afc0eaf2908743dcb) \Device\Harddisk1\DR4\Partition0
01:53:05.0312 1452 \Device\Harddisk1\DR4\Partition0 - ok
01:53:05.0328 1452 ============================================================
01:53:05.0328 1452 Scan finished
01:53:05.0328 1452 ============================================================
01:53:05.0453 1444 Detected object count: 3
01:53:05.0453 1444 Actual detected object count: 3
01:53:16.0781 1444 9eb22451 ( HiddenFile.Multi.Generic ) - skipped by user
01:53:16.0781 1444 9eb22451 ( HiddenFile.Multi.Generic ) - User select action: Skip
01:53:24.0296 1444 Backup copy found, using it..
01:53:24.0296 1444 C:\WINDOWS\system32\DRIVERS\netbt.sys - will be cured on reboot
01:53:24.0296 1444 NetBT ( Rootkit.Win32.ZAccess.h ) - User select action: Cure
01:53:24.0359 1444 \Device\Harddisk0\DR0 ( Rootkit.Boot.SST.a ) - will be cured on reboot
01:53:24.0359 1444 \Device\Harddisk0\DR0 - ok
01:53:24.0359 1444 \Device\Harddisk0\DR0 ( Rootkit.Boot.SST.a ) - User select action: Cure
01:53:27.0093 1412 Deinitialize success

After using the TDSS Rootkit Removing Tool, I was able to use Malwarebytes and it did get rid of most of my problems.
However, I still don't have any audio or Internet and it often is still telling me that "Access is denied." I am getting a new pop-up warning this time, "Missing Asus ACPI Driver. Please install Asus ACPI driver." Is this a real warning, or is it just another fake one?
Thank you so much!

#4 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,058 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:12:46 PM

Posted 15 October 2011 - 08:05 PM

I think running SFC should fix those files.

Please run SFC (System File Checker)
Please run System File Checker sfc /scannow... For more information on this tool see How To Use Sfc.exe To Repair System Files

NOTE for Vista/WIN 7 users..The command needs to be run from an Elevated Command Prompt.Click Start, type cmd into the Start/Search box,
right-click cmd.exe in the list above and select 'Run as Administrator'


You will need your operating system CD handy.

Open Windows Task Manager....by pressing CTRL+SHIFT+ESC

Then click File.. then New Task(Run)

In the box that opens type sfc /scannow ......There is a space between c and /

Click OK
Let it run and insert the CD when asked.
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 pepperbc

pepperbc
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:10:46 AM

Posted 17 October 2011 - 01:31 PM

So I ran the SFC and nothing happened, but obviously something is still wrong with my computer. I decided to insert the operating system CD anyway, and when I did it, too, told me that the driver was missing so I let it reinstall the driver. When I restarted the computer, it wouldn't load in normal mode or any version of safe mode. Eventually, it came up with the blue screen and informed me that in order to proceed with turning on my computer, I needed to uninstall the driver as it was potentially dangerous to my computer. (Is the virus causing this?) However, as it wouldn't even let me load in safe mode, I didn't know how to do that. Eventually, I had the idea to unplug my external CD drive (which was still plugged in from the SFC)and then try to reboot and it started up fine. I then tried to plug in my external CD drive again, and it wouldn't recognize that it was there in any of my USB ports.
What should I do now???

#6 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,058 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:12:46 PM

Posted 17 October 2011 - 02:46 PM

Let.s try one more scan and be sure there is no malware. I believe the meesages are rreal and you will probably need to ask about the ASUS issue in XP or internal Hardware.. But lets be sure malware is not inhibiting repair.


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

#7 pepperbc

pepperbc
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:10:46 AM

Posted 17 October 2011 - 05:48 PM

Thank you so much for all your help!!!
I'm definitely rid of all malware now. :)
(Though I still have my driver problem, but I'll figure that out)
Again, thank you!

#8 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,058 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:12:46 PM

Posted 17 October 2011 - 07:42 PM

You'tr welcome. Ask that in the other fotum,they will figure it out.
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