There seem to be a number of people with this issue, and I've tried to follow some of the other threads here to resolve.
When connected to the net I get a pair of iexplore.exe processes appearing and then popups randomly appear. When I'm not on the net there's no noticeable problem.
I've attached DDS and GMER logs, but also tried the eSage Bootkit Remover which believes I have a problem:
----------------
Bootkit Remover
© 2009 eSage Lab
www.esagelab.com
Program version: 1.1.0.0
OS Version: Microsoft Windows XP Professional Service Pack 3 (build 2600)
System volume is \\.\C:
\\.\C: -> \\.\PhysicalDrive0 at offset 0x00000000`00007e00
Boot sector MD5 is: 305658c5e95259df8541c6683a71d729
Size Device Name MBR Status
---------------------------------------------------
465 GB \\.\PhysicalDrive0 Unknown boot code
Unknown boot code has been found on some of your physical disks
--
Unfortunately a fix operation doesn't resolve this (using the creation of a .bat file I've seen on these forums). I still get this message and I'm wondering if perhaps I need to consider running the Recovery console and doing a fixmbr...
Thanks in advance for any suggestions.
DM
When connected to the net I get a pair of iexplore.exe processes appearing and then popups randomly appear. When I'm not on the net there's no noticeable problem.
I've attached DDS and GMER logs, but also tried the eSage Bootkit Remover which believes I have a problem:
----------------
Bootkit Remover
© 2009 eSage Lab
www.esagelab.com
Program version: 1.1.0.0
OS Version: Microsoft Windows XP Professional Service Pack 3 (build 2600)
System volume is \\.\C:
\\.\C: -> \\.\PhysicalDrive0 at offset 0x00000000`00007e00
Boot sector MD5 is: 305658c5e95259df8541c6683a71d729
Size Device Name MBR Status
---------------------------------------------------
465 GB \\.\PhysicalDrive0 Unknown boot code
Unknown boot code has been found on some of your physical disks
--
Unfortunately a fix operation doesn't resolve this (using the creation of a .bat file I've seen on these forums). I still get this message and I'm wondering if perhaps I need to consider running the Recovery console and doing a fixmbr...
Thanks in advance for any suggestions.
DM