I have been searching all over for an answer to this issue. All the records on this issue are from 2004. Obviously the issue is similar, but not the same.
I am running a fairly new Windows XP SP 2 laptop, fully patched.
The user suddenly started getting this lsass.exe application error:
Lsass.exe Application Error
The instruction at 0x757a1273 referenced memory at 0x0000001 . The memory could not be written.
Once you click OK you get the following message before the system reboots:
The system process c:\windows\system32\lsass.
The event viewer states:
Faulting application lsass.exe version 5.1.2600.2180, faulting module lsasrv.dll, version 5.1.2600.2976, fault address 0x000712373.
I checked under the registry for the usual suspects such as sasser.
In hotkey_local _machine\software\microsof
Name: UserFaultCheck
Type: REG_EXPAND_SZ
Data: %systemroot%\system32\dump
Another thing that happened was at boot up I got an LSA Shell (Export Version) uncounted a problem and needed to close.
Now I have run virus scanning and have found nothing. I also ran spyware problems. The system is patch patched beyond Sasser vulnerabilities. Im totally confused. I havent seen any Google entries past 2005 for this error.
HELP!!!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hi,
Use SuperAntiSpyware to chekc for infection:
www.superantispyware.com
Also, run an online virus scanner:
http://www.kaspersky.com/v
http://support.f-secure.co
http://housecall.trendmicr
http://www.bitdefender.com
Regards,
I can boot the system in safe mode without any failure. It happens after the initial login in normal mode. Connected or unconnected to the internet. I tried doing a system restore to the day before. The system booted fine but then five minutes later, got the same failure.
- I only had one lsass.exe in the system32 directory, no place else.
- The sytem is less than a month old and fully patched with SP2.
- It crashes at boot up every time. If I leave the error message up, the system seems to work fine. As soon as I close out the error message, the system gives me the warning and reboots itself.
- Ran Memtest - No errors
- Running sfc /scannow - No errors
I ran SuperAntiSpyware and http://www.kaspersky.com/v
I think one of the scans did the trick. Not sure WHAT happened but it seems to be working now. I rebooted after the memory test, and it amazingly didn't crash! Thank you!!! For whatever the answer was. :-)
Of course I could have reformatted and redid the computer in less time than it took to get the error to go away. ugh...
Business Accounts
Answer for Membership
by: Vyper28Posted on 2007-10-04 at 15:22:26ID: 20018391
First step i would suggest is heading here: http://www.memtest.org/ and downloading the memtest iso, burn it to a cd and boot from it. Run the test, lets rule out actual faulty RAM before we start trying to hunt down the application causing the problem.
Some quick stuff you can check: Search the computer for lsass.exe you should have 3 results C:\windows\system32\
C:\WINDOWS\ServicePackFile
C:\WINDOWS\SoftwareDistrib
If you have anymore check the file names careful, though as you say, your machine should be sasser proof if it's fully updated.
Have you done an msconfig? Maybe try disabling everything and rebooting, see if the problem persists?
Does it crash constantly in normal mode? If you can get it running stable for a decent amount of time, try running an sfc scan. You need a windows disk, put it in the drive, start-->run--> sfc /scannow
I suspect if the machine truly is patched up, the ram could actually be the issue.