lsass is a core Windows service that is responsible for authentication and related user management. If it is corrupt then the system will crash. It is heavily used and would most likely crash your system pretty quickly if corrupted. It is unlikely that your application is actually causing it an issue. Does it crash if you right click some random process (like notepad) and use Run As to run as a different user?
The error code indicates an access violation which means a memory issue. lsass does have integration points so it is possible a third-party component has hooked into Windows security and is ultimately failing. If you have any third party "login" apps installed then remove them.
If this is the only place you're seeing problems then it could be a corrupt file which leads me to believe you may have a bad drive. But I would expect more errors. You could try running the sfc
tool to have it check the system files and repair them if needed. If your drive is old then you might want to chkdsk it as well.
Another cause could be bad memory but this tends to cause sporadic crashes throughout the system. Running a memory test would check this pretty fast though.
Yet another possibility is that you simply need to ensure your system is updated with the latest patches. Barring that then malicious software can try to circumvent the process for whatever reasons so it never hurts to do a malicious software scan.
If nothing seems to work then it might be necessary to repair the OS. It really doesn't seem like a corrupt lsass process to me but this would be a last resort to recover the system.