Late last year (sometime a little before Christmas) I got this error:
lsass.exe - System Error "Security Accounts Manager initialization failed because of the following error: The handle is invalid. Error Status: 0xc0000008. Please click OK to shutdown the system and reboot into Safe Mode, check the event log for more detailed information."
Seeing how restarting the system in Safe Mode resulted in the same, I searched for a solution. I failed at that and settled for using the system recovery disks that were provided with the laptop (HP Pavilion ze5170 I think.)
Well, everything worked fine until last night when I shut it down. I woke up to find the same error. Crossing my fingers, I used the recovery disks again and updated Windows after it was reinstalled. When I restarted my computer, I got this very same error.
So, any solutions? Or should I desperately recover my system for a third time and attempt to manually fix whatever file corruption is causing this?
Edit: The only significant change to the system that I can think of was that it happened after the second restart after downloading and installing a windows patch (after the installation, the prompt asks for a restart. After that restart, when the system was restarted the error appears.) This may just be something that does not involve this, but any other information helps, I guess.
lsass.exe - System Error "Security Accounts Manager initialization failed because of the following error: The handle is invalid. Error Status: 0xc0000008. Please click OK to shutdown the system and reboot into Safe Mode, check the event log for more detailed information."
Seeing how restarting the system in Safe Mode resulted in the same, I searched for a solution. I failed at that and settled for using the system recovery disks that were provided with the laptop (HP Pavilion ze5170 I think.)
Well, everything worked fine until last night when I shut it down. I woke up to find the same error. Crossing my fingers, I used the recovery disks again and updated Windows after it was reinstalled. When I restarted my computer, I got this very same error.
So, any solutions? Or should I desperately recover my system for a third time and attempt to manually fix whatever file corruption is causing this?
Edit: The only significant change to the system that I can think of was that it happened after the second restart after downloading and installing a windows patch (after the installation, the prompt asks for a restart. After that restart, when the system was restarted the error appears.) This may just be something that does not involve this, but any other information helps, I guess.