Re: Lsass.exe problems - not Sasser Worm

hai, all

I have this problem too.

anyone know that's reason?



thanks
<c_koeber@xxxxxxxxxxxxx> wrote in message
news:1123034752.855033.117650@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Dear All,
> I am running windows 2003 Server Enterprise Edition (You can
> scroll to the bottom of this post to see my specs.) and recently
> Lsass.exe generates a runtime error. (The instruction at "0x742ea411"
> referenced memory at "0x0000000c". The memory could not be "read") This
> happens usually 2-5 minutes after system startup, but sometimes it
> never starts. The likelihood of it starting is greatly increased when I
> connect to system to the network (The network is connected to the
> Internet.)
> When I press ok, the system displays another popup, informing me
> that the system is shutting down in one minute with the status code of
> -1073741819 and the reason code of 0x50006. The system then does
> shutdown.
> I did not make any system changes before this happened so I
> immediately did a check with the hardware by visually inspecting the
> physical components of the system and running the MemTest and hard disk
> diagnostic utilities, but everything was working and in order. I then
> ran three separate anti-virus engines and ran the detect-and-removal
> tools from Microsoft for the common worms like Sasser, MyDoom, etc. but
> did not detect anything.
>
> My questions are:
>
> 1. Is there anything that I should do but I did not?
>
> 2. Anyone else experiencing these or similar symptoms?
>
> 3. And, of course, any remedies for fixing this problem?
>
> I thank everyone for their time and consideration in this matter!
>
> Sincerely,
>
> Christopher
>


.

Relevant Pages

  • Lsass.exe problems - not Sasser Worm
    ... I am running windows 2003 Server Enterprise Edition (You can ... scroll to the bottom of this post to see my specs.) ... connect to system to the network (The network is connected to the ... -1073741819 and the reason code of 0x50006. ...
    (microsoft.public.windows.server.general)
  • files and transfer wizard
    ... I am running 2 computers on a network both running windows xp pro sp2, ... says the file transfer has failed and doesn't give a reason. ...
    (microsoft.public.windowsxp.general)
  • Re: Lsass.exe problems - not Sasser Worm
    ... Unknown Device ... > I am running windows 2003 Server Enterprise Edition (You can ... > connect to system to the network (The network is connected to the ... > -1073741819 and the reason code of 0x50006. ...
    (microsoft.public.windows.server.general)
  • Re: Network Neighborhood
    ... > inability to browse by using Network Neighborhood in Windows 95 or Windows ... > communicated effectively with the other workgroup computers. ... > not have a common networking protocol, a common workgroup, and common user ... the computer that is running Windows ...
    (microsoft.public.win2000.networking)
  • Re: AT&T Tilt continues the tradition of crappy Windows Mobile phones; what phone can I buy ins
    ... reason), give the XDA-Devs cooked ROM's a try. ... the iPhone is ruled out because tethering my ... the network through my phone, EDGE-only is simply not an option. ... settings was invalid because of a corrupt ring tone, ...
    (microsoft.public.pocketpc)