Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


C:\WINDOWS\system32\lsass.exe, failed with status code c0000005. The machine must now be restarted

  • Please log in to reply
1 reply to this topic

#1 roz17


  • Members
  • 16 posts
  • Local time:10:16 PM

Posted 17 November 2008 - 04:55 PM

Been getting these for awhile now... went through with Panda (great job, very thorough, HIGHLY recommended)... doesn't seem to be a virus.... up to date on all patches, updates.. re-did sp3 to make sure...

Also, lsdelete not found since the virii cleaning above.... that seems to be the autocheck interruptis before start of windows....

running mcafee 8.5.0i and Symantec Protection Agent 5.1 as requirements from work...

everything I find says this is a failed negotiation with a 2003 server, but it's an XP box.... HELP?

Event Type: Error
Event Source: Winlogon
Event Category: None
Event ID: 1015
Date: 11/16/2008
Time: 8:44:17 PM
User: N/A
Computer: UPSTAIRS
A critical system process, C:\WINDOWS\system32\lsass.exe, failed with status code c0000005. The machine must now be restarted.

BC AdBot (Login to Remove)


#2 hamluis



  • Moderator
  • 56,272 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:16 PM

Posted 17 November 2008 - 05:08 PM

I find the same references as you...the server reference fits if you are part of a domain when this happens (e.g., at work).

If it's a standalone XP box, forget what I said :thumbsup:.

I think I'd run sfc /scannow and chkdsk /r, just to try to do something that might be productive.

I think I'd also run Memtest, since those c0000005 errors can be memory-related.


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users