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.


PC won't boot, hard drive suspected

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

#1 inm8num2


  • Members
  • 67 posts
  • Local time:08:22 PM

Posted 10 January 2011 - 08:51 PM


Last night I left my desktop computer for 30-40 minutes and when I came back it appeared to be frozen/stuck in the screen saver. There was a signal on the monitor (i.e. the screen image was "blank" rather than off or "black"). I rebooted to find that after the DELL screen, nothing happens.

I tested a couple different video cards and the motherboard recognizes them before POST, so I don't think that's an issue. I suspect the hard drive, since the diagnostic code in the rear of the PC shows 4 green lights, meaning that hardware is functioning. I switched power supplies but the problem persists, so that shouldn't be an issue either.

I've removed my desktop hard drive and used an external enclosure to access it on a different PC. Everything is there and I can navigate around except for certain system folders that deny me access (even though I'm logged into the alternate PC as an administrator).

I attempted to essentially copy ALL the files to another blank 3.5" hard drive and see if that can somehow work, but due to access restrictions I can't copy everything (I have backed up my personal files/data). I'm unsure how to clone the drive because I essentially want to copy everything file for file rather than have a stripped down restore image. It's an old PC and any reinstallation/restore would cost me a lot of time and effort in installing old programs, etc.

The hard drive seems to be functioning well in the external enclosure, except that while I was copying various files to the secondary hard drive Symantic Antivirus popped up and found two corrupt files with Trojan.ADH:

DpiSca.exe (in WINDOWS folder) - this is a virus installer according to internet search
smitRem.exe (an anti-virus tool)

So, I'm not sure what to do from here. Again the drive seems to be okay otherwise, and I'm not sure how those files might have been corrupted or if they're the reason my desktop PC can't boot. Any help is GREATLY appreciated, and thanks for reading this long post.

BC AdBot (Login to Remove)


#2 boopme


    To Insanity and Beyond

  • Global Moderator
  • 72,740 posts
  • Gender:Male
  • Location:NJ USA
  • Local time:12:22 AM

Posted 11 January 2011 - 12:58 AM

Hello let's try a FULL scan with MBAM so it scans all drives.

Next 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 FULL 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 inm8num2

  • Topic Starter

  • Members
  • 67 posts
  • Local time:08:22 PM

Posted 11 January 2011 - 02:53 AM

Dear boopme,

Thank you for your reply. I have used an external enclosure to connect my affected desktop hard drive to my laptop and scan with MBAM.

When I connected the drive my laptop's Microsoft Security Essentials detected multiple threats and automatically removed/quarantined some files associated with a Trojan and Exploit:Java. One in particular is "Trojan:Dos\Alureon.A", which affected the Master Boot Record (MBR). Microsoft Security Essentials automatically deleted some of these files while quarantining others. I now understand why I can't boot, but is there any way to restore this without formatting/reinstalling XP on my hard drive? I lack the OS/Recovery discs and it would be a painstaking process for many reasons.

MBAM result is below. Again, please note that my affected PC (Win XP SP3) can't be used, so I have used an external enclosure to scan the hard drive with my laptop (Win 7).

Malwarebytes' Anti-Malware

Database version: 5502

Windows 6.1.7600
Internet Explorer 8.0.7600.16385

1/11/2011 11:53:08 PM
mbam-log-2011-01-11 (23-53-08).txt

Scan type: Full scan (E:\|)
Objects scanned: 217238
Time elapsed: 47 minute(s), 26 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: 2

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:
e:\system volume information\_restore{92e646dd-6671-4fbf-89fe-1f22c423604f}\RP1475\A0125511.exe (Trojan.Agent) -> Quarantined and deleted successfully.
e:\WINDOWS\temp\B9.tmp (Trojan.Agent) -> Quarantined and deleted successfully.

Edited by inm8num2, 11 January 2011 - 04:11 AM.

#4 boopme


    To Insanity and Beyond

  • Global Moderator
  • 72,740 posts
  • Gender:Male
  • Location:NJ USA
  • Local time:12:22 AM

Posted 11 January 2011 - 01:32 PM

Hello. Aleuron is aTDSS infection. This tool if we can run it wil find it and replace the files ,If they still exist on the drive.

Please download the TDSS Rootkit Removing Tool (TDSSKiller.exe) and save it to your Desktop. <-Important!!!
Be sure to download TDSSKiller.exe (v2.4.0.0) from Kaspersky's website and not TDSSKiller.zip which appears to be an older version 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. 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.

Now if possible,To check for and confirm the MBR rootkit.

Please download mbr.exe and save it to the root directory, usually C:\ <- (Important!).
  • Go to Start > Run and type: cmd.exe
  • press Ok.
  • At the command prompt type: c:\mbr.exe >>"C:\mbr.log"
  • press Enter.
  • The process is automatic...a black DOS window will open and quickly disappear. This is normal.
  • A log file named mbr.log will be created and saved to the root of the system drive (usually C:\).
  • Copy and paste the results of the mbr.log in your next reply.
If you have a problem using the command prompt, you can just double-click on mbr.exe to run the tool.
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 inm8num2

  • Topic Starter

  • Members
  • 67 posts
  • Local time:08:22 PM

Posted 11 January 2011 - 04:36 PM


I followed your instructions with my affected hard drive connected to another PC via external enclosure.

TDSS Killer results and mbr.log follow. TDSSKiller I ran from the alternate PC but it appears to have still scanned the external hard drive and detected the rootkit. Please note that for mbr.exe, I loaded this to the external hard drive root directory (F:\) and ran the command except changing the drive letter, e.g.:

f:\mbr.exe >>"F:\mbr.log"

EDIT: it appears that MBR only scanned the hard drive on the PC I'm using, not the external hard drive which has the infection. I am not sure how to run mbr.exe for the external hard drive, and if you can provide instructions that would be very helpful.

2011/01/11 13:37:48.0359 TDSS rootkit removing tool Dec 16 2010 09:46:46
2011/01/11 13:37:48.0359 ================================================================================
2011/01/11 13:37:48.0359 SystemInfo:
2011/01/11 13:37:48.0359
2011/01/11 13:37:48.0359 OS Version: 5.1.2600 ServicePack: 3.0
2011/01/11 13:37:48.0359 Product type: Workstation
2011/01/11 13:37:48.0359 ComputerName: LINPC1
2011/01/11 13:37:48.0359 UserName: mon
2011/01/11 13:37:48.0359 Windows directory: C:\WINDOWS
2011/01/11 13:37:48.0359 System windows directory: C:\WINDOWS
2011/01/11 13:37:48.0359 Processor architecture: Intel x86
2011/01/11 13:37:48.0359 Number of processors: 2
2011/01/11 13:37:48.0359 Page size: 0x1000
2011/01/11 13:37:48.0359 Boot type: Normal boot
2011/01/11 13:37:48.0359 ================================================================================
2011/01/11 13:37:48.0750 Initialize success
2011/01/11 13:38:06.0328 ================================================================================
2011/01/11 13:38:06.0328 Scan started
2011/01/11 13:38:06.0328 Mode: Manual;
2011/01/11 13:38:06.0328 ================================================================================
2011/01/11 13:38:06.0625 \HardDisk2 - detected Rootkit.Win32.TDSS.tdl4 (0)
2011/01/11 13:38:06.0640 ================================================================================
2011/01/11 13:38:06.0640 Scan finished
2011/01/11 13:38:06.0640 ================================================================================
2011/01/11 13:38:06.0671 Detected object count: 1
2011/01/11 13:38:13.0515 \HardDisk2 - processing error
2011/01/11 13:38:19.0140 Rootkit.Win32.TDSS.tdl4(\HardDisk2) - User select action: Cure
2011/01/11 13:38:24.0343 ================================================================================
2011/01/11 13:38:24.0343 Scan started
2011/01/11 13:38:24.0343 Mode: Manual;
2011/01/11 13:38:24.0343 ================================================================================
2011/01/11 13:38:25.0703 ACPI (8fd99680a539792a30e97944fdaecf17) C:\WINDOWS\system32\DRIVERS\ACPI.sys
2011/01/11 13:38:25.0750 ACPIEC (9859c0f6936e723e4892d7141b1327d5) C:\WINDOWS\system32\drivers\ACPIEC.sys
2011/01/11 13:38:25.0828 aec (8bed39e3c35d6a489438b8141717a557) C:\WINDOWS\system32\drivers\aec.sys
2011/01/11 13:38:25.0875 AFD (7e775010ef291da96ad17ca4b17137d7) C:\WINDOWS\System32\drivers\afd.sys
2011/01/11 13:38:26.0000 akshasp (4ed4ce78a42070cb041c208ca53ed70a) C:\WINDOWS\system32\DRIVERS\akshasp.sys
2011/01/11 13:38:26.0031 aksusb (2fa8cbcbd795014267be5f60bb8474c0) C:\WINDOWS\system32\DRIVERS\aksusb.sys
2011/01/11 13:38:26.0109 Alidevice (2f17c06cda54bfbe13c4046b19055f7b) C:\WINDOWS\system32\drivers\Alidevice.sys
2011/01/11 13:38:26.0281 AsyncMac (b153affac761e7f5fcfa822b9c4e97bc) C:\WINDOWS\system32\DRIVERS\asyncmac.sys
2011/01/11 13:38:26.0296 atapi (9f3a2f5aa6875c72bf062c712cfa2674) C:\WINDOWS\system32\DRIVERS\atapi.sys
2011/01/11 13:38:26.0421 ati2mtag (03621f7f968ff63713943405deb777f9) C:\WINDOWS\system32\DRIVERS\ati2mtag.sys
2011/01/11 13:38:26.0468 Atmarpc (9916c1225104ba14794209cfa8012159) C:\WINDOWS\system32\DRIVERS\atmarpc.sys
2011/01/11 13:38:26.0531 audstub (d9f724aa26c010a217c97606b160ed68) C:\WINDOWS\system32\DRIVERS\audstub.sys
2011/01/11 13:38:26.0609 Beep (da1f27d85e0d1525f6621372e7b685e9) C:\WINDOWS\system32\drivers\Beep.sys
2011/01/11 13:38:26.0671 cbidf2k (90a673fc8e12a79afbed2576f6a7aaf9) C:\WINDOWS\system32\drivers\cbidf2k.sys
2011/01/11 13:38:26.0750 Cdaudio (c1b486a7658353d33a10cc15211a873b) C:\WINDOWS\system32\drivers\Cdaudio.sys
2011/01/11 13:38:26.0812 Cdfs (c885b02847f5d2fd45a24e219ed93b32) C:\WINDOWS\system32\drivers\Cdfs.sys
2011/01/11 13:38:26.0828 Cdrom (1f4260cc5b42272d71f79e570a27a4fe) C:\WINDOWS\system32\DRIVERS\cdrom.sys
2011/01/11 13:38:26.0890 cercsr6 (84853b3fd012251690570e9e7e43343f) C:\WINDOWS\system32\drivers\cercsr6.sys
2011/01/11 13:38:27.0046 cvintdrv (310c5ec0b4278211089f0a5e915d025f) C:\WINDOWS\system32\drivers\cvintdrv.sys
2011/01/11 13:38:27.0171 Disk (044452051f3e02e7963599fc8f4f3e25) C:\WINDOWS\system32\DRIVERS\disk.sys
2011/01/11 13:38:27.0281 DLABOIOM (e2d0de31442390c35e3163c87cb6a9eb) C:\WINDOWS\system32\DLA\DLABOIOM.SYS
2011/01/11 13:38:27.0390 DLACDBHM (d979bebcf7edcc9c9ee1857d1a68c67b) C:\WINDOWS\system32\Drivers\DLACDBHM.SYS
2011/01/11 13:38:27.0406 DLADResN (83545593e297f50a8e2524b4c071a153) C:\WINDOWS\system32\DLA\DLADResN.SYS
2011/01/11 13:38:27.0453 DLAIFS_M (96e01d901cdc98c7817155cc057001bf) C:\WINDOWS\system32\DLA\DLAIFS_M.SYS
2011/01/11 13:38:27.0468 DLAOPIOM (0a60a39cc5e767980a31ca5d7238dfa9) C:\WINDOWS\system32\DLA\DLAOPIOM.SYS
2011/01/11 13:38:27.0531 DLAPoolM (9fe2b72558fc808357f427fd83314375) C:\WINDOWS\system32\DLA\DLAPoolM.SYS
2011/01/11 13:38:27.0546 DLARTL_N (7ee0852ae8907689df25049dcd2342e8) C:\WINDOWS\system32\Drivers\DLARTL_N.SYS
2011/01/11 13:38:27.0578 DLAUDFAM (f08e1dafac457893399e03430a6a1397) C:\WINDOWS\system32\DLA\DLAUDFAM.SYS
2011/01/11 13:38:27.0609 DLAUDF_M (e7d105ed1e694449d444a9933df8e060) C:\WINDOWS\system32\DLA\DLAUDF_M.SYS
2011/01/11 13:38:27.0671 dmboot (d992fe1274bde0f84ad826acae022a41) C:\WINDOWS\system32\drivers\dmboot.sys
2011/01/11 13:38:27.0734 dmio (7c824cf7bbde77d95c08005717a95f6f) C:\WINDOWS\system32\drivers\dmio.sys
2011/01/11 13:38:27.0765 dmload (e9317282a63ca4d188c0df5e09c6ac5f) C:\WINDOWS\system32\drivers\dmload.sys
2011/01/11 13:38:27.0812 DMusic (8a208dfcf89792a484e76c40e5f50b45) C:\WINDOWS\system32\drivers\DMusic.sys
2011/01/11 13:38:27.0875 drmkaud (8f5fcff8e8848afac920905fbd9d33c8) C:\WINDOWS\system32\drivers\drmkaud.sys
2011/01/11 13:38:27.0890 DRVMCDB (fd0f95981fef9073659d8ec58e40aa3c) C:\WINDOWS\system32\Drivers\DRVMCDB.SYS
2011/01/11 13:38:27.0906 DRVNDDM (b4869d320428cdc5ec4d7f5e808e99b5) C:\WINDOWS\system32\Drivers\DRVNDDM.SYS
2011/01/11 13:38:27.0953 e1express (5b75bbf89d8341f424171df7ad9dc465) C:\WINDOWS\system32\DRIVERS\e1e5132.sys
2011/01/11 13:38:28.0078 eeCtrl (089296aedb9b72b4916ac959752bdc89) C:\Program Files\Common Files\Symantec Shared\EENGINE\eeCtrl.sys
2011/01/11 13:38:28.0109 EraserUtilRebootDrv (850259334652d392e33ee3412562e583) C:\Program Files\Common Files\Symantec Shared\EENGINE\EraserUtilRebootDrv.sys
2011/01/11 13:38:28.0156 Fastfat (38d332a6d56af32635675f132548343e) C:\WINDOWS\system32\drivers\Fastfat.sys
2011/01/11 13:38:28.0203 Fdc (92cdd60b6730b9f50f6a1a0c1f8cdc81) C:\WINDOWS\system32\drivers\Fdc.sys
2011/01/11 13:38:28.0218 Fips (d45926117eb9fa946a6af572fbe1caa3) C:\WINDOWS\system32\drivers\Fips.sys
2011/01/11 13:38:28.0250 Flpydisk (9d27e7b80bfcdf1cdd9b555862d5e7f0) C:\WINDOWS\system32\drivers\Flpydisk.sys
2011/01/11 13:38:28.0281 FltMgr (b2cf4b0786f8212cb92ed2b50c6db6b0) C:\WINDOWS\system32\drivers\fltmgr.sys
2011/01/11 13:38:28.0343 FsVga (455f778ee14368468560bd7cb8c854d0) C:\WINDOWS\system32\DRIVERS\fsvga.sys
2011/01/11 13:38:28.0406 Fs_Rec (3e1e2bd4f39b0e2b7dc4f4d2bcc2779a) C:\WINDOWS\system32\drivers\Fs_Rec.sys
2011/01/11 13:38:28.0421 Ftdisk (6ac26732762483366c3969c9e4d2259d) C:\WINDOWS\system32\DRIVERS\ftdisk.sys
2011/01/11 13:38:28.0484 GEARAspiWDM (8182ff89c65e4d38b2de4bb0fb18564e) C:\WINDOWS\system32\DRIVERS\GEARAspiWDM.sys
2011/01/11 13:38:28.0578 GenericMount (29c3d2a2398b980a73043fa3688e2f30) C:\WINDOWS\system32\DRIVERS\GenericMount.sys
2011/01/11 13:38:28.0640 Gpc (0a02c63c8b144bd8c86b103dee7c86a2) C:\WINDOWS\system32\DRIVERS\msgpc.sys
2011/01/11 13:38:28.0703 gpibclsb (2a954128fcfed41e7ad289e70bdb7004) C:\WINDOWS\System32\Drivers\gpibclsb.sys
2011/01/11 13:38:28.0734 gpibclsd (31b923554cbe9c451518f32acb8da049) C:\WINDOWS\System32\Drivers\gpibclsd.sys
2011/01/11 13:38:28.0812 Hardlock (d64a40b94602158e40527ae95e7a9193) C:\WINDOWS\system32\drivers\hardlock.sys
2011/01/11 13:38:28.0859 Haspnt (2dd25f060dc9f79b5cdf33d90ed93669) C:\WINDOWS\system32\drivers\Haspnt.sys
2011/01/11 13:38:28.0906 HDAudBus (573c7d0a32852b48f3058cfd8026f511) C:\WINDOWS\system32\DRIVERS\HDAudBus.sys
2011/01/11 13:38:28.0953 hidusb (ccf82c5ec8a7326c3066de870c06daf1) C:\WINDOWS\system32\DRIVERS\hidusb.sys
2011/01/11 13:38:29.0046 HSFHWBS2 (77e4ff0b73bc0aeaaf39bf0c8104231f) C:\WINDOWS\system32\DRIVERS\HSFHWBS2.sys
2011/01/11 13:38:29.0093 HSF_DP (60e1604729a15ef4a3b05f298427b3b1) C:\WINDOWS\system32\DRIVERS\HSF_DP.sys
2011/01/11 13:38:29.0171 HTTP (f80a415ef82cd06ffaf0d971528ead38) C:\WINDOWS\system32\Drivers\HTTP.sys
2011/01/11 13:38:29.0250 i8042prt (4a0b06aa8943c1e332520f7440c0aa30) C:\WINDOWS\system32\drivers\i8042prt.sys
2011/01/11 13:38:29.0343 iastor (309c4d86d989fb1fcf64bd30dc81c51b) C:\WINDOWS\system32\DRIVERS\iaStor.sys
2011/01/11 13:38:29.0406 Imapi (083a052659f5310dd8b6a6cb05edcf8e) C:\WINDOWS\system32\DRIVERS\imapi.sys
2011/01/11 13:38:29.0515 intelppm (8c953733d8f36eb2133f5bb58808b66b) C:\WINDOWS\system32\DRIVERS\intelppm.sys
2011/01/11 13:38:29.0546 Ip6Fw (3bb22519a194418d5fec05d800a19ad0) C:\WINDOWS\system32\drivers\ip6fw.sys
2011/01/11 13:38:29.0609 IpFilterDriver (731f22ba402ee4b62748adaf6363c182) C:\WINDOWS\system32\DRIVERS\ipfltdrv.sys
2011/01/11 13:38:29.0625 IpInIp (b87ab476dcf76e72010632b5550955f5) C:\WINDOWS\system32\DRIVERS\ipinip.sys
2011/01/11 13:38:29.0656 IpNat (cc748ea12c6effde940ee98098bf96bb) C:\WINDOWS\system32\DRIVERS\ipnat.sys
2011/01/11 13:38:29.0781 IPSec (23c74d75e36e7158768dd63d92789a91) C:\WINDOWS\system32\DRIVERS\ipsec.sys
2011/01/11 13:38:29.0796 IRENUM (c93c9ff7b04d772627a3646d89f7bf89) C:\WINDOWS\system32\DRIVERS\irenum.sys
2011/01/11 13:38:29.0843 isapnp (05a299ec56e52649b1cf2fc52d20f2d7) C:\WINDOWS\system32\DRIVERS\isapnp.sys
2011/01/11 13:38:29.0890 Kbdclass (463c1ec80cd17420a542b7f36a36f128) C:\WINDOWS\system32\DRIVERS\kbdclass.sys
2011/01/11 13:38:29.0937 kbdhid (9ef487a186dea361aa06913a75b3fa99) C:\WINDOWS\system32\DRIVERS\kbdhid.sys
2011/01/11 13:38:29.0984 kmixer (692bcf44383d056aed41b045a323d378) C:\WINDOWS\system32\drivers\kmixer.sys
2011/01/11 13:38:30.0015 KSecDD (b467646c54cc746128904e1654c750c1) C:\WINDOWS\system32\drivers\KSecDD.sys
2011/01/11 13:38:30.0093 MCSTRM (5bb01b9f582259d1fb7653c5c1da3653) C:\WINDOWS\system32\drivers\MCSTRM.sys
2011/01/11 13:38:30.0140 mdmxsdk (eeaea6514ba7c9d273b5e87c4e1aab30) C:\WINDOWS\system32\DRIVERS\mdmxsdk.sys
2011/01/11 13:38:30.0203 mnmdd (4ae068242760a1fb6e1a44bf4e16afa6) C:\WINDOWS\system32\drivers\mnmdd.sys
2011/01/11 13:38:30.0265 Modem (dfcbad3cec1c5f964962ae10e0bcc8e1) C:\WINDOWS\system32\drivers\Modem.sys
2011/01/11 13:38:30.0281 MODEMCSA (1992e0d143b09653ab0f9c5e04b0fd65) C:\WINDOWS\system32\drivers\MODEMCSA.sys
2011/01/11 13:38:30.0328 Mouclass (35c9e97194c8cfb8430125f8dbc34d04) C:\WINDOWS\system32\DRIVERS\mouclass.sys
2011/01/11 13:38:30.0343 mouhid (b1c303e17fb9d46e87a98e4ba6769685) C:\WINDOWS\system32\DRIVERS\mouhid.sys
2011/01/11 13:38:30.0375 MountMgr (a80b9a0bad1b73637dbcbba7df72d3fd) C:\WINDOWS\system32\drivers\MountMgr.sys
2011/01/11 13:38:30.0421 MRxDAV (11d42bb6206f33fbb3ba0288d3ef81bd) C:\WINDOWS\system32\DRIVERS\mrxdav.sys
2011/01/11 13:38:30.0484 MRxSmb (f3aefb11abc521122b67095044169e98) C:\WINDOWS\system32\DRIVERS\mrxsmb.sys
2011/01/11 13:38:30.0515 Msfs (c941ea2454ba8350021d774daf0f1027) C:\WINDOWS\system32\drivers\Msfs.sys
2011/01/11 13:38:30.0562 MSKSSRV (d1575e71568f4d9e14ca56b7b0453bf1) C:\WINDOWS\system32\drivers\MSKSSRV.sys
2011/01/11 13:38:30.0593 MSPCLOCK (325bb26842fc7ccc1fcce2c457317f3e) C:\WINDOWS\system32\drivers\MSPCLOCK.sys
2011/01/11 13:38:30.0609 MSPQM (bad59648ba099da4a17680b39730cb3d) C:\WINDOWS\system32\drivers\MSPQM.sys
2011/01/11 13:38:30.0640 mssmbios (af5f4f3f14a8ea2c26de30f7a1e17136) C:\WINDOWS\system32\DRIVERS\mssmbios.sys
2011/01/11 13:38:30.0671 Mup (2f625d11385b1a94360bfc70aaefdee1) C:\WINDOWS\system32\drivers\Mup.sys
2011/01/11 13:38:30.0906 NAVENG (c8ef74e4d8105b1d02d58ea4734cf616) C:\PROGRA~1\COMMON~1\SYMANT~1\VIRUSD~1\20110107.003\naveng.sys
2011/01/11 13:38:30.0968 NAVEX15 (94b3164055d821a62944d9fe84036470) C:\PROGRA~1\COMMON~1\SYMANT~1\VIRUSD~1\20110107.003\navex15.sys
2011/01/11 13:38:31.0015 NDIS (1df7f42665c94b825322fae71721130d) C:\WINDOWS\system32\drivers\NDIS.sys
2011/01/11 13:38:31.0046 NdisTapi (1ab3d00c991ab086e69db84b6c0ed78f) C:\WINDOWS\system32\DRIVERS\ndistapi.sys
2011/01/11 13:38:31.0062 Ndisuio (f927a4434c5028758a842943ef1a3849) C:\WINDOWS\system32\DRIVERS\ndisuio.sys
2011/01/11 13:38:31.0093 NdisWan (edc1531a49c80614b2cfda43ca8659ab) C:\WINDOWS\system32\DRIVERS\ndiswan.sys
2011/01/11 13:38:31.0218 NDProxy (9282bd12dfb069d3889eb3fcc1000a9b) C:\WINDOWS\system32\drivers\NDProxy.sys
2011/01/11 13:38:31.0265 NetBIOS (5d81cf9a2f1a3a756b66cf684911cdf0) C:\WINDOWS\system32\DRIVERS\netbios.sys
2011/01/11 13:38:31.0328 NetBT (74b2b2f5bea5e9a3dc021d685551bd3d) C:\WINDOWS\system32\DRIVERS\netbt.sys
2011/01/11 13:38:31.0421 niarbk (5d249c5365f819f70882570a1746c9d2) C:\WINDOWS\system32\drivers\niarbk.dll
2011/01/11 13:38:31.0484 nibffrk (ec11f3561e9ef42b515839c5feed393b) C:\WINDOWS\system32\drivers\nibffrk.dll
2011/01/11 13:38:31.0546 nicdrk (0b52273104c596e074ca3a4c2598b7d1) C:\WINDOWS\system32\drivers\nicdrk.dll
2011/01/11 13:38:31.0625 Nidaq32k (c67114fcecf18815f941b4b36f1e8a88) C:\WINDOWS\system32\drivers\Nidaq32k.sys
2011/01/11 13:38:31.0687 nidimk (be4af05c8d9176a65b2854e7a1da752b) C:\WINDOWS\system32\drivers\nidimk.dll
2011/01/11 13:38:31.0703 nidmmk (b972a71f7a017ad903441ce67a975ed3) C:\WINDOWS\system32\drivers\nidmmk.dll
2011/01/11 13:38:31.0765 niefrk (4a35e701784c531a08cfca56c6747d0e) C:\WINDOWS\system32\drivers\niefrk.dll
2011/01/11 13:38:31.0812 niesrk (4cac59a952b94deb7069f2a9317de3a5) C:\WINDOWS\system32\drivers\niesrk.dll
2011/01/11 13:38:31.0859 nimdbgk (bece36c7b7da09094429f1e9e709ff32) C:\WINDOWS\system32\drivers\nimdbgk.dll
2011/01/11 13:38:31.0875 nimdsk (dd4b89019ab1eca5c04757e2f7d8a9e4) C:\WINDOWS\system32\drivers\nimdsk.dll
2011/01/11 13:38:31.0921 nimru2k (e4c17fb235ebbd2f20af90cf44a20c96) C:\WINDOWS\system32\drivers\nimru2k.dll
2011/01/11 13:38:31.0953 nimsdrk (2629398513a4aae6bef8ad0172ce4d0b) C:\WINDOWS\system32\drivers\nimsdrk.dll
2011/01/11 13:38:31.0968 nimslk (3d4932d65a3af9e2860dd1cebfac1997) C:\WINDOWS\system32\drivers\nimslk.dll
2011/01/11 13:38:32.0015 nimsrlk (145eace35b5c7ac30e0bbf2ff8f10733) C:\WINDOWS\system32\drivers\nimsrlk.dll
2011/01/11 13:38:32.0031 nimstsk (f0ac440b493382b8e739d60a967aa947) C:\WINDOWS\system32\drivers\nimstsk.dll
2011/01/11 13:38:32.0093 nimxdfk (28255779375de01792e254bd3eabf4da) C:\WINDOWS\system32\drivers\nimxdfk.dll
2011/01/11 13:38:32.0140 nimxpk (f5be8eec3fb351285faf255ea9c54ab1) C:\WINDOWS\system32\drivers\nimxpk.dll
2011/01/11 13:38:32.0187 niorbk (79b4624620cce9cc8decbf5ed7898f2c) C:\WINDOWS\system32\drivers\niorbk.dll
2011/01/11 13:38:32.0265 NIPALK (4dd5446e2bcc3b78301149ff6dcfa4ee) C:\WINDOWS\system32\drivers\NIPALK.sys
2011/01/11 13:38:32.0390 nipxirmk (e58b22c89cc8d3c7a511f03148a1eab9) C:\WINDOWS\system32\drivers\nipxirmk.dll
2011/01/11 13:38:32.0453 niscdk (05786fe7b84c71d1f5dfa367bd80ea7d) C:\WINDOWS\system32\drivers\niscdk.dll
2011/01/11 13:38:32.0531 nispdk (0a0213189e5e2904712b089459c81cd9) C:\WINDOWS\system32\drivers\nispdk.dll
2011/01/11 13:38:32.0546 nistc2k (a213760f5751c0ea13f403a5982ff00b) C:\WINDOWS\system32\drivers\nistc2k.dll
2011/01/11 13:38:32.0578 nistck (c517992eb204652f4d5c0fc67e3d49c1) C:\WINDOWS\system32\drivers\nistck.dll
2011/01/11 13:38:32.0609 nistcrk (cb373d04081d2ef11835ea4203d42776) C:\WINDOWS\system32\drivers\nistcrk.dll
2011/01/11 13:38:32.0671 niswdk (4f0a4b84668c1f012fbb305cc9463dda) C:\WINDOWS\system32\drivers\niswdk.dll
2011/01/11 13:38:32.0734 NiViPxiK (03fef45c218f67b8f0d189639268e87d) C:\WINDOWS\system32\drivers\NiViPxiK.sys
2011/01/11 13:38:32.0796 Npfs (3182d64ae053d6fb034f44b6def8034a) C:\WINDOWS\system32\drivers\Npfs.sys
2011/01/11 13:38:32.0859 Ntfs (78a08dd6a8d65e697c18e1db01c5cdca) C:\WINDOWS\system32\drivers\Ntfs.sys
2011/01/11 13:38:32.0937 Null (73c1e1f395918bc2c6dd67af7591a3ad) C:\WINDOWS\system32\drivers\Null.sys
2011/01/11 13:38:33.0000 NwlnkFlt (b305f3fad35083837ef46a0bbce2fc57) C:\WINDOWS\system32\DRIVERS\nwlnkflt.sys
2011/01/11 13:38:33.0015 NwlnkFwd (c99b3415198d1aab7227f2c88fd664b9) C:\WINDOWS\system32\DRIVERS\nwlnkfwd.sys
2011/01/11 13:38:33.0078 Parport (5575faf8f97ce5e713d108c2a58d7c7c) C:\WINDOWS\system32\drivers\Parport.sys
2011/01/11 13:38:33.0093 PartMgr (beb3ba25197665d82ec7065b724171c6) C:\WINDOWS\system32\drivers\PartMgr.sys
2011/01/11 13:38:33.0156 ParVdm (70e98b3fd8e963a6a46a2e6247e0bea1) C:\WINDOWS\system32\drivers\ParVdm.sys
2011/01/11 13:38:33.0171 PCI (a219903ccf74233761d92bef471a07b1) C:\WINDOWS\system32\DRIVERS\pci.sys
2011/01/11 13:38:33.0250 PCIIde (ccf5f451bb1a5a2a522a76e670000ff0) C:\WINDOWS\system32\DRIVERS\pciide.sys
2011/01/11 13:38:33.0296 Pcmcia (9e89ef60e9ee05e3f2eef2da7397f1c1) C:\WINDOWS\system32\drivers\Pcmcia.sys
2011/01/11 13:38:33.0515 PptpMiniport (efeec01b1d3cf84f16ddd24d9d9d8f99) C:\WINDOWS\system32\DRIVERS\raspptp.sys
2011/01/11 13:38:33.0562 PSched (09298ec810b07e5d582cb3a3f9255424) C:\WINDOWS\system32\DRIVERS\psched.sys
2011/01/11 13:38:33.0625 Ptilink (80d317bd1c3dbc5d4fe7b1678c60cadd) C:\WINDOWS\system32\DRIVERS\ptilink.sys
2011/01/11 13:38:33.0671 PxHelp20 (7c81ae3c9b82ba2da437ed4d31bc56cf) C:\WINDOWS\system32\Drivers\PxHelp20.sys
2011/01/11 13:38:33.0812 RasAcd (fe0d99d6f31e4fad8159f690d68ded9c) C:\WINDOWS\system32\DRIVERS\rasacd.sys
2011/01/11 13:38:33.0937 Rasl2tp (11b4a627bc9614b885c4969bfa5ff8a6) C:\WINDOWS\system32\DRIVERS\rasl2tp.sys
2011/01/11 13:38:34.0015 RasPppoe (5bc962f2654137c9909c3d4603587dee) C:\WINDOWS\system32\DRIVERS\raspppoe.sys
2011/01/11 13:38:34.0031 Raspti (fdbb1d60066fcfbb7452fd8f9829b242) C:\WINDOWS\system32\DRIVERS\raspti.sys
2011/01/11 13:38:34.0078 Rdbss (7ad224ad1a1437fe28d89cf22b17780a) C:\WINDOWS\system32\DRIVERS\rdbss.sys
2011/01/11 13:38:34.0109 RDPCDD (4912d5b403614ce99c28420f75353332) C:\WINDOWS\system32\DRIVERS\RDPCDD.sys
2011/01/11 13:38:34.0140 rdpdr (15cabd0f7c00c47c70124907916af3f1) C:\WINDOWS\system32\DRIVERS\rdpdr.sys
2011/01/11 13:38:34.0187 RDPWD (6728e45b66f93c08f11de2e316fc70dd) C:\WINDOWS\system32\drivers\RDPWD.sys
2011/01/11 13:38:34.0218 redbook (f828dd7e1419b6653894a8f97a0094c5) C:\WINDOWS\system32\DRIVERS\redbook.sys
2011/01/11 13:38:34.0406 SAVRT (cdb565c093b0105086cc630b32f9e6e6) C:\Program Files\Symantec Client Security\Symantec AntiVirus\savrt.sys
2011/01/11 13:38:34.0421 SAVRTPEL (1042cb5a003f9aed8d6cec56a0fc6c49) C:\Program Files\Symantec Client Security\Symantec AntiVirus\Savrtpel.sys
2011/01/11 13:38:34.0531 Secdrv (90a3935d05b494a5a39d37e71f09a677) C:\WINDOWS\system32\DRIVERS\secdrv.sys
2011/01/11 13:38:34.0578 Sentinel (412a3a8a9043616b9246bfefc376e933) C:\WINDOWS\System32\Drivers\SENTINEL.SYS
2011/01/11 13:38:34.0640 serenum (0f29512ccd6bead730039fb4bd2c85ce) C:\WINDOWS\system32\DRIVERS\serenum.sys
2011/01/11 13:38:34.0656 Serial (cca207a8896d4c6a0c9ce29a4ae411a7) C:\WINDOWS\system32\DRIVERS\serial.sys
2011/01/11 13:38:34.0703 Sfloppy (8e6b8c671615d126fdc553d1e2de5562) C:\WINDOWS\system32\drivers\Sfloppy.sys
2011/01/11 13:38:34.0796 snapman (85bada660d57bc5aef52b11cabd6d8f9) C:\WINDOWS\system32\DRIVERS\snapman.sys
2011/01/11 13:38:34.0859 SNTNLUSB (054c6d41933b3bdb09dca17de08a97b2) C:\WINDOWS\system32\DRIVERS\SNTNLUSB.SYS
2011/01/11 13:38:34.0921 SONYPVU1 (a1eceeaa5c5e74b2499eb51d38185b84) C:\WINDOWS\system32\DRIVERS\SONYPVU1.SYS
2011/01/11 13:38:35.0000 SPBBCDrv (677b10906838d3bfb1c07ac9087e4bf7) C:\Program Files\Common Files\Symantec Shared\SPBBC\SPBBCDrv.sys
2011/01/11 13:38:35.0031 splitter (ab8b92451ecb048a4d1de7c3ffcb4a9f) C:\WINDOWS\system32\drivers\splitter.sys
2011/01/11 13:38:35.0078 sr (76bb022c2fb6902fd5bdd4f78fc13a5d) C:\WINDOWS\system32\DRIVERS\sr.sys
2011/01/11 13:38:35.0171 Srv (0f6aefad3641a657e18081f52d0c15af) C:\WINDOWS\system32\DRIVERS\srv.sys
2011/01/11 13:38:35.0234 STHDA (352b663a81402be7cd7bd4ea27c9998c) C:\WINDOWS\system32\drivers\sthda.sys
2011/01/11 13:38:35.0375 swenum (3941d127aef12e93addf6fe6ee027e0f) C:\WINDOWS\system32\DRIVERS\swenum.sys
2011/01/11 13:38:35.0406 swmidi (8ce882bcc6cf8a62f2b2323d95cb3d01) C:\WINDOWS\system32\drivers\swmidi.sys
2011/01/11 13:38:35.0531 SYMDNS (82235a78777a8f0a5d6cc66a5c118b59) C:\WINDOWS\System32\Drivers\SYMDNS.SYS
2011/01/11 13:38:35.0593 SymEvent (3c6790d26d03fe5163e2bec490e51a7e) C:\Program Files\Symantec\SYMEVENT.SYS
2011/01/11 13:38:35.0640 SYMFW (fe7d95fb4c45855dccdd7be530b96982) C:\WINDOWS\System32\Drivers\SYMFW.SYS
2011/01/11 13:38:35.0656 SYMIDS (fa3dbbcc7a26a4a2636dfcca06689689) C:\WINDOWS\System32\Drivers\SYMIDS.SYS
2011/01/11 13:38:35.0765 SYMIDSCO (2133d1f879b280121b0e6a7d34b24a02) C:\PROGRA~1\COMMON~1\SYMANT~1\SymcData\SCFIDS~1\20101230.001\symidsco.sys
2011/01/11 13:38:35.0781 SYMNDIS (6497b01f6acee837ec2469bb2b5ee910) C:\WINDOWS\System32\Drivers\SYMNDIS.SYS
2011/01/11 13:38:35.0859 SYMREDRV (5314e345dfc068504cfb2676d3b2ca39) C:\WINDOWS\System32\Drivers\SYMREDRV.SYS
2011/01/11 13:38:35.0906 symsnap (a5cf31080e99718949bcc38c83f13452) C:\WINDOWS\system32\DRIVERS\symsnap.sys
2011/01/11 13:38:35.0968 SYMTDI (8cd0a1478256240249b8ee88e6f25e94) C:\WINDOWS\System32\Drivers\SYMTDI.SYS
2011/01/11 13:38:36.0062 sysaudio (8b83f3ed0f1688b4958f77cd6d2bf290) C:\WINDOWS\system32\drivers\sysaudio.sys
2011/01/11 13:38:36.0140 Tcpip (9aefa14bd6b182d61e3119fa5f436d3d) C:\WINDOWS\system32\DRIVERS\tcpip.sys
2011/01/11 13:38:36.0234 TDPIPE (6471a66807f5e104e4885f5b67349397) C:\WINDOWS\system32\drivers\TDPIPE.sys
2011/01/11 13:38:36.0312 tdrpman273 (431801fcc97034e04a6eff81136578d7) C:\WINDOWS\system32\DRIVERS\tdrpm273.sys
2011/01/11 13:38:36.0343 TDTCP (c56b6d0402371cf3700eb322ef3aaf61) C:\WINDOWS\system32\drivers\TDTCP.sys
2011/01/11 13:38:36.0406 TermDD (88155247177638048422893737429d9e) C:\WINDOWS\system32\DRIVERS\termdd.sys
2011/01/11 13:38:36.0515 Udfs (5787b80c2e3c5e2f56c2a233d91fa2c9) C:\WINDOWS\system32\drivers\Udfs.sys
2011/01/11 13:38:36.0687 UnlockerDriver5 (bb879dcfd22926efbeb3298129898cbb) C:\Program Files\Unlocker\UnlockerDriver5.sys
2011/01/11 13:38:36.0750 Update (402ddc88356b1bac0ee3dd1580c76a31) C:\WINDOWS\system32\DRIVERS\update.sys
2011/01/11 13:38:36.0937 usbaudio (e919708db44ed8543a7c017953148330) C:\WINDOWS\system32\drivers\usbaudio.sys
2011/01/11 13:38:37.0000 usbccgp (173f317ce0db8e21322e71b7e60a27e8) C:\WINDOWS\system32\DRIVERS\usbccgp.sys
2011/01/11 13:38:37.0031 usbehci (65dcf09d0e37d4c6b11b5b0b76d470a7) C:\WINDOWS\system32\DRIVERS\usbehci.sys
2011/01/11 13:38:37.0046 usbhub (1ab3cdde553b6e064d2e754efe20285c) C:\WINDOWS\system32\DRIVERS\usbhub.sys
2011/01/11 13:38:37.0109 usbscan (a0b8cf9deb1184fbdd20784a58fa75d4) C:\WINDOWS\system32\DRIVERS\usbscan.sys
2011/01/11 13:38:37.0125 USBSTOR (a32426d9b14a089eaa1d922e0c5801a9) C:\WINDOWS\system32\DRIVERS\USBSTOR.SYS
2011/01/11 13:38:37.0187 usbuhci (26496f9dee2d787fc3e61ad54821ffe6) C:\WINDOWS\system32\DRIVERS\usbuhci.sys
2011/01/11 13:38:37.0218 VgaSave (0d3a8fafceacd8b7625cd549757a7df1) C:\WINDOWS\System32\drivers\vga.sys
2011/01/11 13:38:37.0281 VolSnap (4c8fcb5cc53aab716d810740fe59d025) C:\WINDOWS\system32\drivers\VolSnap.sys
2011/01/11 13:38:37.0328 VProEventMonitor (ef3506b04eb9124240b35148eaacbaa5) C:\WINDOWS\system32\DRIVERS\vproeventmonitor.sys
2011/01/11 13:38:37.0390 Wanarp (e20b95baedb550f32dd489265c1da1f6) C:\WINDOWS\system32\DRIVERS\wanarp.sys
2011/01/11 13:38:37.0453 Wdf01000 (d918617b46457b9ac28027722e30f647) C:\WINDOWS\system32\Drivers\wdf01000.sys
2011/01/11 13:38:37.0515 wdmaud (6768acf64b18196494413695f0c3a00f) C:\WINDOWS\system32\drivers\wdmaud.sys
2011/01/11 13:38:37.0578 WimFltr (090a2b8f055343815556a01f725f6c35) C:\WINDOWS\system32\DRIVERS\wimfltr.sys
2011/01/11 13:38:37.0656 winachsf (f59ed5a43b988a18ef582bb07b2327a7) C:\WINDOWS\system32\DRIVERS\HSF_CNXT.sys
2011/01/11 13:38:37.0812 WpdUsb (cf4def1bf66f06964dc0d91844239104) C:\WINDOWS\system32\Drivers\wpdusb.sys
2011/01/11 13:38:37.0890 WudfPf (f15feafffbb3644ccc80c5da584e6311) C:\WINDOWS\system32\DRIVERS\WudfPf.sys
2011/01/11 13:38:37.0921 WudfRd (28b524262bce6de1f7ef9f510ba3985b) C:\WINDOWS\system32\DRIVERS\wudfrd.sys
2011/01/11 13:38:38.0281 \HardDisk2 - detected Rootkit.Win32.TDSS.tdl4 (0)
2011/01/11 13:38:38.0296 ================================================================================
2011/01/11 13:38:38.0296 Scan finished
2011/01/11 13:38:38.0296 ================================================================================
2011/01/11 13:38:38.0312 Detected object count: 1
2011/01/11 13:39:39.0390 \HardDisk2 - processing error
2011/01/11 13:39:53.0953 \HardDisk2 - restored
2011/01/11 13:39:53.0953 Rootkit.Win32.TDSS.tdl4(\HardDisk2) - User select action: Cure Restore
2011/01/11 13:40:00.0203 Deinitialize success

Stealth MBR rootkit/Mebroot/Sinowal/TDL4 detector 0.4.2 by Gmer, http://www.gmer.net
Windows 5.1.2600 Disk: WDC_WD25 rev.10.0 -> Harddisk0\DR0 -> \Device\Ide\IAAStorageDevice-0

device: opened successfully
user: MBR read successfully
kernel: MBR read successfully
user & kernel MBR OK

Edited by inm8num2, 11 January 2011 - 07:24 PM.

#6 boopme


    To Insanity and Beyond

  • Global Moderator
  • 72,740 posts
  • Gender:Male
  • Location:NJ USA
  • Local time:12:22 AM

Posted 11 January 2011 - 10:06 PM

Hi, good job that got rid of Aleuron.

Now I fairly certain this will check the MBR

Download MBRCheck.exe to your desktop
XP users ] double click on MBRCheck.exe to run it
Vista and Windows 7 users ] right click on MBRCheck.exe and select Run as Administrator
It will show a black screen with some data on it
Click on the black C:\ in the upper left hand corner of the black screen
Choose Edit ] Select All ] Press Enter to copy the data to your clip board
Press Enter again to close MBRCheck
Now open up notepad or wordpad and paste the data in (press Control+V)

Post the results in your reply

Edited by boopme, 11 January 2011 - 10:07 PM.

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

#7 inm8num2

  • Topic Starter

  • Members
  • 67 posts
  • Local time:08:22 PM

Posted 11 January 2011 - 10:49 PM

Hi there,

Thanks for all your help and fast responses. MBRcheck.exe results are below. Drive F is the one that had Alureon and other problems.

MBRCheck, version 1.2.3
© 2010, AD

Windows Version: Windows XP Professional
Windows Information: Service Pack 3 (build 2600)
Logical Drives Mask: 0x000007ac

\\.\C: --> \\.\PhysicalDrive0 at offset 0x00000000`02f10c00 (NTFS)
\\.\F: --> \\.\PhysicalDrive6 at offset 0x00000000`01f60800 (NTFS)

Size Device Name MBR Status
232 GB \\.\PhysicalDrive0 Windows XP MBR code detected
SHA1: DA38B874B7713D1B51CBC449F4EF809B0DEC644A
37 GB \\.\PhysicalDrive6 RE: Windows XP MBR code detected
SHA1: DA38B874B7713D1B51CBC449F4EF809B0DEC644A

Press ENTER to exit...

Edited by inm8num2, 11 January 2011 - 10:51 PM.

#8 boopme


    To Insanity and Beyond

  • Global Moderator
  • 72,740 posts
  • Gender:Male
  • Location:NJ USA
  • Local time:12:22 AM

Posted 11 January 2011 - 11:04 PM

You're welcome looks clean.

There is one piece of malware on your machine here
e:\system volume information\_restore{92e646dd-6671-4fbf-89fe-1f22c423604f}\RP1475\A0125511.exe (Trojan.Agent) -> Quarantined and deleted successfully

This is the XP correct ?
Now you should Create a New Restore Point to prevent possible reinfection from an old one. Some of the malware you picked up could have been backed up, renamed and saved in System Restore. Since this is a protected directory your tools cannot access to delete these files, they sometimes can reinfect your system if you accidentally use an old restore point. Setting a new restore point AFTER cleaning your system will help prevent this and enable your computer to "roll-back" to a clean working state.

The easiest and safest way to do this is:
  • Go to 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 and Windows 7 users can refer to these links: Create a New Restore Point in Vista or Windows 7 and Disk Cleanup in Vista.
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 inm8num2

  • Topic Starter

  • Members
  • 67 posts
  • Local time:08:22 PM

Posted 12 January 2011 - 02:41 AM

Thanks again for all your help. I have booted my PC successfully, though the boot time between the Dell splash screen and Windows XP loading screen is a bit longer than it used to be.

Other issues:

- Shut Down button from Start Menu seems to stall computer --> must Ctrl-Alt-Del to Task Manager to restart/shut down
- However, after Windows exits it becomes stuck at the blue "Windows is shutting down" screen --> I must press the computer's power button to shut it off.

The slow boot time still has me concerned a bit, but the PC again seems to be okay otherwise.


I am unable to run System Restore. I get the error, "System Restore is unable to protect your computer."

Edited by inm8num2, 12 January 2011 - 02:17 PM.

#10 boopme


    To Insanity and Beyond

  • Global Moderator
  • 72,740 posts
  • Gender:Male
  • Location:NJ USA
  • Local time:12:22 AM

Posted 12 January 2011 - 04:40 PM

I Would suggest you run SFC. If other issues persist creat an XP topic and they can help you better on these issues.

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.

You are welcome.
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

#11 inm8num2

  • Topic Starter

  • Members
  • 67 posts
  • Local time:08:22 PM

Posted 12 January 2011 - 06:59 PM

Thanks for the reply. I don't have an OS recovery disc, so I may have to find alternate means to repair possibly missing/affected system files.

I'm confident the virus has been removed, so I will create a separate thread in the XP forum!

#12 boopme


    To Insanity and Beyond

  • Global Moderator
  • 72,740 posts
  • Gender:Male
  • Location:NJ USA
  • Local time:12:22 AM

Posted 12 January 2011 - 07:08 PM

Now that your log is properly posted, 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 Malware Removal Team member, nor should you continue to ask for help elsewhere. Doing so can result in system changes which may not show it 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 Malware Removal 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 Malware Removal Team members are very 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 Malware Removal 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 HJT Team member is already assisting you and not open the thread to respond.

To avoid confusion, I am closing this topic.

Edited by boopme, 19 January 2011 - 10:06 AM.

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