|
Junior Member
Join Date: Nov 2005
Posts: 5
|
Well, here's an interesting followup to this VERY PERPLEXING problem:
After posting above, I decided to review what's been said about this on the net. It seems the only definitive isolation of this lsass problem was once with a server problem and a corruption of the paging space entry in the registry.
I looked at my own paging space specifications and they seemed ok, but decided to see if this problem was paging space related. I changed my specs from custom space specification to allowing the system to choose a paging space. I then rebooted.
Upon reboot, I got the lsass.exe error again, but decided that it might take TWO BOOTS to implement the paging space change so just went ahead and let it reboot again. AMAZINGLY, windows came up!
Unfortunately, it came up WITHOUT NETWORKING. I checked devices and saw my Intel network card was indicated as being in error. Soooooo.. I uninstalled the Intel driver and rebooted. I got the prompt saying there was a problem last time and would I like a normal reboot. I took normal reboot.
The reboot (after removing the network driver) got the lsass.exe error again. As before, I ignored it and tried again.
Up came windows!!!! It took a bit for windows to recognize the Intel card and load the driver, but once it did, I had my networking back again. I'm typing this before trying as yet another two or three reboots to see what happens. Then I'll power off reboot and see if that's different.
This is VERY ODD. I still don't have a clue what is failing but rebuilding the paging file and reloading the network driver both somehow caused the repair.
Any insight?
|