not the sasser worm

C

Carleton

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?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

not the sasser worm again 3
lsass.exe terminates with code 1073741819 1
What would cause an lsass.exe termination even before the login window is displayed? 1
the instruction at " " referenced memory at " ". The memory could not be read. 3
Compass Rule Manger 2
Services.exe issue 5
ERROR: the instruction at/the memory could not be read/written 1
Windows - Application Error - The memory could not be read! 1

Top