Well from your DDS log, I saw this:
Warning: possible TDL3 rootkit infection !TDSSKiller is the tool we use to take of this infection.
Bootkit Removal Tool is a tool that will also work but for some reason it wouldn't work on your system.
--------------------------
TDSSKiller found and cured the rootkit:
14:33:14.0515 3136 Detected object count: 1
14:33:14.0515 3136 Actual detected object count: 1
14:33:24.0015 3136 \Device\Harddisk0\DR0 ( Rootkit.Boot.Pihar.b ) - will be cured on reboot
14:33:24.0015 3136 \Device\Harddisk0\DR0 - ok
14:33:24.0015 3136 \Device\Harddisk0\DR0 ( Rootkit.Boot.Pihar.b ) - User select action: Cure
14:33:44.0640 3876 Deinitialize success
We ran
TDSSKiller again and it confirms the rootkit is gone.
------------------------------
I had you run
RogueKiller to check for any other infections and also check the master boot record (MBR)
It turned up clean (OK) except for the host file: (which was corrupt)
-----------------------------
+++++ PhysicalDrive0: SAMSUNG HD160JJ/P +++++
--- User ---
[MBR] 54f27e3eb12aa828010f072d5d43f642
[BSP] 11d467b9f31927f29d49c85858b51038 : Windows XP MBR Code
Partition table:
0 - [ACTIVE] NTFS (0x07) [VISIBLE] Offset (sectors): 63 | Size: 159989 Mo
User = LL1 ... OK!
User = LL2 ... OK!
Finished : << RKreport[1].txt >>
RKreport[1].txt
---------------------------
I had you run
RogueKiller again to restore the host file back to what it's supposed to be.
¤¤¤ Resetted HOSTS: ¤¤¤
127.0.0.1 localhost
--------------------
So now we'll see how it is.
MrC