C
cmsix
After removing four pieces of malware with an antispyware scanner a
machine will not finish login without a spontaneous reboot. It happens
just after the dialog that says "loading personal settings" goes away.
For a few seconds the desktop background image will be there and then
poof, it's back to black and soon enough we're posting again.
This happens no matter how I try to boot from the boot menu. Safe
Mode, Safe Mode with Command Prompt, Last known good, the whole
shootin' match. Thing is, if you don't try to login it will just keep
going and after a while the screen saver will start up.
I put the drive in another machine and found the spyware scanner's log
files. It removed four files. Two of them went with ccview stuff and
two were from the e2give family. I just can't see where they could
have caused all this trouble.
This is an HP pavilion with the hidden partitions instead of a CD. I
have been using a different XP Home CD to start the recovery console,
but I really don't know that much about it. I looked at ntbtlog.txt
figuring I might get lucky with something on the last driver or two,
but no dice.
Can anyone tell me when the event logs kickoff? I'm assuming that they
get started before login, but don't know it. If they do is it likely
they'll have useful information if I put the drive back into another
machine and try to look them over? Can I even do that?
I also have a question regarding the built in backup. I did a backup
when I had the drive in the other XP machine. Will it be any use if I
reinstall, or will the fact that it wasn't the boot drive on the
machine that made the backup make a difference?
Of course I thought I'd covered my... posterior by creating a restore
point before I did anything. I had no clue that things could go so
wrong over four files, two of them just BHOs.
Anyway, that's enough about my problems. If you have any hint about
something I could try next, don't be shy. I'm not afraid to surf
somewhere and do some reading if you have a good pointer in the right
direction.
Just to recap, it doesn't seem to be a bootup problem. Everything is
jake until an attempt to login is made.
cmsix
machine will not finish login without a spontaneous reboot. It happens
just after the dialog that says "loading personal settings" goes away.
For a few seconds the desktop background image will be there and then
poof, it's back to black and soon enough we're posting again.
This happens no matter how I try to boot from the boot menu. Safe
Mode, Safe Mode with Command Prompt, Last known good, the whole
shootin' match. Thing is, if you don't try to login it will just keep
going and after a while the screen saver will start up.
I put the drive in another machine and found the spyware scanner's log
files. It removed four files. Two of them went with ccview stuff and
two were from the e2give family. I just can't see where they could
have caused all this trouble.
This is an HP pavilion with the hidden partitions instead of a CD. I
have been using a different XP Home CD to start the recovery console,
but I really don't know that much about it. I looked at ntbtlog.txt
figuring I might get lucky with something on the last driver or two,
but no dice.
Can anyone tell me when the event logs kickoff? I'm assuming that they
get started before login, but don't know it. If they do is it likely
they'll have useful information if I put the drive back into another
machine and try to look them over? Can I even do that?
I also have a question regarding the built in backup. I did a backup
when I had the drive in the other XP machine. Will it be any use if I
reinstall, or will the fact that it wasn't the boot drive on the
machine that made the backup make a difference?
Of course I thought I'd covered my... posterior by creating a restore
point before I did anything. I had no clue that things could go so
wrong over four files, two of them just BHOs.
Anyway, that's enough about my problems. If you have any hint about
something I could try next, don't be shy. I'm not afraid to surf
somewhere and do some reading if you have a good pointer in the right
direction.
Just to recap, it doesn't seem to be a bootup problem. Everything is
jake until an attempt to login is made.
cmsix