not the sasser worm again

[Carleton]

This is my original post and Kelly's reply. I have
performed her recommended fix, but the fix tool she
instructed me to use (Symantec) still finds no sasser
infection and the problem persists . . . anything else is
much appreciated.

I have a new laptop. Within two weeks, I have begun
receiving a msg at startup "Instruction at 0x20608668
referenced memory at 0x744004490. Memory could not
be 'read'." Then the NT Authority gives me the Lsass.exe
error resulting in a reboot. Occurs 75% of the bootups.
Sounds like Sasser, but all my Microsoft updates are
current (always), antivirus is up to speed - and i've
checked for Sasser infiltration with the MS tool, Sophos,
NOD32, TrendMicro, and Symantec . . . no incidence of
Sasser. I cleared my system restore to make sure that it
wasn't in archive. I've run out of ideas. Help?

Hi,

Run the cleaner once more from line 321 (right hand side
http://www.kellys-korner-xp.com/xp_tweaks.htm

--
All the Best,
Kelly

Microsoft-MVP Windows® XP
2004 Windows MVP "Winny" Award

Troubleshooting Windows XP
http://www.kellys-korner-xp.com

Taskbar Repair Tool Plus!
http://www.kellys-korner-xp.com/taskbarplus!.htm


news:[email protected]...

 

[Haggis]

This is my original post and Kelly's reply. I have
performed her recommended fix, but the fix tool she
instructed me to use (Symantec) still finds no sasser
infection and the problem persists . . . anything else is
much appreciated.

I have a new laptop. Within two weeks, I have begun
receiving a msg at startup "Instruction at 0x20608668
referenced memory at 0x744004490. Memory could not
be 'read'." Then the NT Authority gives me the Lsass.exe
error resulting in a reboot. Occurs 75% of the bootups.
Sounds like Sasser, but all my Microsoft updates are
current (always), antivirus is up to speed - and i've
checked for Sasser infiltration with the MS tool, Sophos,
NOD32, TrendMicro, and Symantec . . . no incidence of
Sasser. I cleared my system restore to make sure that it
wasn't in archive. I've run out of ideas. Help?

-----and make sure you disable system restore and you are in safe
mode-------

Hi,

Run the cleaner once more from line 321 (right hand side
http://www.kellys-korner-xp.com/xp_tweaks.htm




news:[email protected]...

 

[GTS]

Does this happen if you boot into safe mode?

--

This is my original post and Kelly's reply. I have
performed her recommended fix, but the fix tool she
instructed me to use (Symantec) still finds no sasser
infection and the problem persists . . . anything else is
much appreciated.

I have a new laptop. Within two weeks, I have begun
receiving a msg at startup "Instruction at 0x20608668
referenced memory at 0x744004490. Memory could not
be 'read'." Then the NT Authority gives me the Lsass.exe
error resulting in a reboot. Occurs 75% of the bootups.
Sounds like Sasser, but all my Microsoft updates are
current (always), antivirus is up to speed - and i've
checked for Sasser infiltration with the MS tool, Sophos,
NOD32, TrendMicro, and Symantec . . . no incidence of
Sasser. I cleared my system restore to make sure that it
wasn't in archive. I've run out of ideas. Help?

Hi,

Run the cleaner once more from line 321 (right hand side
http://www.kellys-korner-xp.com/xp_tweaks.htm




news:[email protected]...

 

[MGGP]

Why don't you try Stinger, download here:
http://vil.nai.com/vil/stinger/

Also see this:
http://www.microsoft.com/security/incident/sasser.asp

Good Luck !