Beta - Lsass.exe is back

just for your info.....

I run XP Pro with SP2 v.2096 and haven't had a single problem with the beta v of NOD32....all good infact......


Try turning off DCOM if your still on XP SP1....

I never leave it on as i just don't trust MS patches....if you don't need it why in the hell leave it running when its such a risk..

60 second shutdowns get my alarm bells ringing.....an exploit is not a virus....at first...

Maybe I'm paraniod?.

 

The error reports appears all over the internet. They always appears after a windowsupdate. I am quite shure that the new hotfixes are designed to work in SP2, and creates errors in SP1. They dont seem to appear in SP2, so i am quite shure about this.

 

Want to bet they don't appear in SP2?

 

Ehh.. NO ! But i am quite shure it is a M$ "thing". Btw, take a look at this http://support.microsoft.com/default.aspx?scid=kb;en-us;828133 . They say it will be solved in the next service pack. It is not identical, but the resemblance is quite clear (to me)

 

Well I'm on the new SP2, Lsass error messages had disappeared, though I was still receiving some of the other error messages every now and then.

Installed the new Beta 2.12 and Lsass.exe error messages are back with force, at least 2 a day, even my partner now knows how to stop the system from shutting down, and she's getting pretty quick at it as well

I might end up having to format this system, though I don’t really see why I should have to. The Lsass.exe error messages have appeared on a FRESH install of XP Pro. I do have another machine alongside this one with all the exact same software and no error messages, so it remains a mystery, other than it comes and goes according to various Beta’s installed…

Cheers

 

Did a fresh install w/SP2 slipstreamed... same problems. Granted I don't have 2.12, but it happens with 2.11.

Different issue. This is a NOD32 issue.

 

Thanks Taz, good to see you have kept your club membership

I had fairly well lost the error messages until the new Beta 2.12.

Cheers

 

ROFLMAO it is very elusive I know you are just itching to try and become a member, however we are a elite bunch

 

One again - where do I get this version 2.12

Ruben

 

Hi Tosbsas,
a newer component update will be issued shortly (within a couple of days).

 

OK - has been talked about so much here -)

Ruben

 

It is just being issued to those having specific problems, of which it appears a lot are fixed...

If you build it, they will come - problems and solutions

Cheers

 

These Lsass shutdown error messages have increased dramatically with this new Beta, now getting 3 to 4+ in an hour or two, several times I've seen them just after bootup, it appears and then locks the machine solid, I've never seen so many of them until this version

Cheers

 

No, only the one...

I've just downloaded a newer version of the Beta, hopefully this will be better, don't think it could be any worse

Cheers

 

I could do, not a problem at all, this however will not fix the issue, the problem is a Eset one, though very intermittent, they are able to stop / slow down / and increase the errors according to each Beta released, as has been found by others:

I have seen this on several FRESH installs now, comes back to Eset...

Cheers

 

Latest Beta 2.12 released 16th Aug, 14 hours on and the Lsass.exe error has gone walkabout, neither sight nor sound has been heard So far so good

Cheers

 

Hi Blackspear, any idea where one can dowload the 2.12 version??

thanks,
Martin

 

It has been given out to those still having specific problems...

Marcos has replied that it should be released to the public in about a week...

https://www.wilderssecurity.com/showthread.php?t=44113&page=2

Cheers

 

Actually he mentioned in the next 24-48 hours.

 

New post here: See number 33

https://www.wilderssecurity.com/showthread.php?t=44113&page=2

Cheers

 

24hrs on and still no sign of the elusive error, they may have fixed it

 

This post may be a bit off-topic because I don't have NOD32 installed. However, I've experienced the same problems with lsass.exe and other processes terminating with a read/write of un-readable/un-writeable memory.

I noticed this problem when trying to slipstream the XP SP2. More specifically, executing the command "WindowsXP-KB835935-SP2-ENU.exe -x" (I also get the same problems when running it without the "-x" switch) will extract the files, but also causes system instability. with several Application Failures. A reboot (by using the off switch) is then required:

1) svchost.exe - "The instruction at "0x77f44fff" referenced memory at "0x77f45000". The memory could not be "read".

2) lsass.exe - "The instruction at "0x77f44f5f" referenced memory at "0xffffffff". The memory could not be "written".

3) explorer.exe - "The instruction at "0x77f44fff" referenced memory at "0x77f45000". The memory could not be "read".

About halfway through the extraction process the mem usage for each active process is reduced to a minimum (ie. I can see this from Task Manager when the command is executed). I assume any other resources they are using (eg. DLL's etc) are also flushed out of memory. It seems that the above processes have trouble and crash when this happens.

I am running XP Home and have 256MB of RAM, with a 512MB paging file.

While obviously not a problem with NOD in my case, the symptoms seem to be the same hence my post. Might also help to fix any NOD problems that might be having with lsass.exe too.

Has anyone else experienced this when executing the XP Service Pack 2 network install file (ie. WindowsXP-KB835935-SP2-ENU.exe) ?