BSODs maybe caused by Trojans

Previous thread on BSODs: BSOD 0x0000000a, 0x000000c2, 0x00000019 and the most common 0x00000024

I removed F-secure and installed Security Essentials and MBAM. So far, Security Essentials scan finished and found two threats; TrojanDownloader:ASX/Wimad.AS and TrojanClicker:ASX/Wimad.CS.
MBAM found Trojan.MSIL.Injector, which was also removed.
Any suggestions, what should I do next or do I just wait if a BSOD appears again?

TDSSKILLER

download link TDSSKiller

Save to the Desktop

Right-click the program and select


When the TDSSKiller console opens, click on: Change Parameters
Under Additional Options, place a check in the box next to: Detect TDLFS File System

Click: OK


Press: Start Scan


If a suspicious object is detected, the default action is Skip, leave it as is, and click on: Continue
If malicious objects are found, they show in the Scan results.
Ensure Cure (the default) is selected, then click: Continue > Reboot now, to finish the cleaning process.
(Note: If Cure is not available, select Skip, >>Do not select: Delete<<)


When done, the tool outputs its log to the disk with the Windows Operating System, normally C:\


Logs have a name like:
C:\TDSSKiller.X.X.X_12.04.2013_15.31.43_log.txt


Please post the TDSSKiller log in your reply.

Once you're done with that run this

<==== Download Link


<==== Download Link

Click on one of the links above that goes with your Windows 7 bit versions

Save to the Desktop.

Close all windows and browsers

Right click on and choose

Press: SCAN

provide the RKreport.txt (Mode: Scan) in your reply.

When running TDSSKiller, I got a BSOD (see minidump attached & the TDSSKiller's log). Proceeded with a new scan, it went through without problems (the other log file).
Proceeding to RogueKillerX64 >

jaine said:

Previous thread on BSODs: BSOD 0x0000000a, 0x000000c2, 0x00000019 and the most common 0x00000024

I removed F-secure and installed Security Essentials and MBAM. So far, Security Essentials scan finished and found two threats; TrojanDownloader:ASX/Wimad.AS and TrojanClicker:ASX/Wimad.CS.
MBAM found Trojan.MSIL.Injector, which was also removed.
Any suggestions, what should I do next or do I just wait if a BSOD appears again?

That is why I still use Spybot S&D, though the teatimer function can slow down booting, it has a feature that you can use to 'immunize' and it works with the browser[s] you use to protect from within to keep downloaders and clickers out of your system before they implant themselves. After d/l'ing the weekly definition files and running a scan [time consuming though] you can see in the bottom left had corner
what malware it is seeking out and it does seem to have kept the two above out or they would have showed up on the results pane. (on my system that is)

jaine said:

When running TDSSKiller, I got a BSOD (see minidump attached & the TDSSKiller's log). Proceeded with a new scan, it went through without problems (the other log file).
Proceeding to RogueKillerX64 >

Unzip the folder and upload just the tdsskiller log please .

But then I can't upload the minidump here...
Anyways, attached it and the RogueKiller logs too.

Doesn't look like TDSSKILLER completed . Rerun the scan again with tdsskiller

The second log file is the one that completed, the first one was the one with the crash interrupting it.

Download

HitManPro

64-Bit Version OS HitmanPro_x64

32-Bit Version OS HitmanPro

Save to the Desktop

Right click on HitmanPro.exe and choose

When HitmanPro opens up click on Settings uncheck Scan for tracking cookies . Click on OK . Then click on the Next button

Click on No, I only want to perform a one-time scan to check this computer on the Setup page . Click Next once done .

Let it scan the PC once its done Click Next

Click Activate free license to start the free 30 days trial and remove all the malicious files from your computer then click Next

Copy and Paste the contents of the log . Locate in C:\ProgramData\Hitman Pro\Logs