Lsass exe terminated unexpectedly with status code 128

The process wininit. The system will now shut down and restart. Attachments: Up to 10 attachments including images can be used with a maximum of 3. After researching, I found two threads mentioned the similar issue and contained possible solutions.

But both of them were for Windows Server or R2. Steps: 1. Viewing current policy settings: a. At the Ntdsutil. You want to connect to the server that you are currently working with. Remove From My Forums. Answered by:. Archived Forums. Windows Server General Forum. Sign in to vote. This server is fully locked down, and has updated virus protection. There are no viruses or malware of any kind. What can I look at to see what caused the lsass to terminate?

Not an IT pro? Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Was looking everywhere for help. I used it numerous times to clean up my registry. I started in safe mode went to regseeker and had it put in an old backup registry. Restarted and so far everything is good.

I fixed it by using the msconfig utility from an XP Professional machine. I followed MSFTs fix to the letter and no success. Boot into safe mode and turn off all. With the MSConfig utility you can kill everything at startup the Win. Add things back in one by one until you find the error again.

The popup appear AFTER the login windows… 2 pc are infected on the company network … try the 2 kb and that didnt fix the problem. I applied security update and the problem went away. The problem hit me the morning of Aug 15, , so I assume the problem was Zotob worm that was reported in the media, e. The various fixes referenced above did not work for me; it was the security update that did the trick.

Since the worm causes reboot when I tried to access the network, I unplugged the network cable and restarted my machine. I then downloaded the patch on another machine and copied it over using flash memory.

After installing it on the infected machine I reattached the network cable and everything is fine. This problem hit us too at August 15th at two different machines using Win SP4. The problem occurs only when connected to the Internet dial-up or ethernet.

As far as I can see for now, update did the trick! I started having the same problem yesterday with the difference that my computer shuts down only if I run the Start Active directory Wizard. I am running Windows Advanced Server. I have tried all of the fixes above with the exception of installing Windows in another directory and etc… and none have worked for me.

But it did not solve the problem. Then realised when i did not do a dial-up to Internet, the message did not appear. So tried dialing up to the Internet, and sure enough, the message pops up almost immediately. Initially suspected it was the Internet Explorer program that is causing the problem, so launch Internet Explorer without dialing up, but message never appears. This leads me to believe the dial-up connection instance is causing the problem. In the end, set up another instance of the dial-up connection and delete the old one, and thankfully, the message did not appear again.

Get a real operating system. FYI: linux is free. Linux is NOT really free to enterprises, but more expensive. Compare with Linux, Windows Server has lower total cost of ownership, easy to manage and administer, easier to hire IT people for Windows, etc.

Sounds just like the talking points from Redmond. Funny how you can get the results you want when you pay for the study. At least not if you have a clue about what you are doing. This whole TCO thing is completely bogus. Oh, and by the way, I have been administering both Windows and Linux platforms for about 15 years now. Hi all, I have managed to solve the problem.

I spent forever looking through forums applying patches, doing scans etc but the problem still remained! I am using XP SP2. In the end I copied lsass. I then used a pre-installed environment disk to access the windows file system and overwrit the originals. It worked! I am aware that most people wont have a PE disk so try this….. It was fine until I updated. This only happens when I try to install new devices. Any ideas?