Have you encountered a bug with error messages and numerous LSA warnings?
Have you encountered a bug with error messages and numerous LSA warnings?
I need some technical assistance. I can't visit Microsoft because their customer support doesn't understand what they're doing. They follow a procedure, mostly reading notes that the person claims they actually do. I'm puzzled about these errors and warnings and don't know how to fix them.
I frequently encounter LSA (LsaSrv) warnings—specifically BugCheck, Error 1001, and a Wininit warning with ID 15. Additionally, while I was away, the screen saver started swirling but when I returned, three of them froze, preventing my screen from connecting. I noticed the A0 on the motherboard is functional, but after turning it off and on again, it changed to 64 and then performed some action.
This issue has occurred repeatedly when the screen saver was active, even though it shouldn't have caused such problems. I've already sent the 4070 TUF to ASUS for inspection. They provided a new one, which works now, but it continues to behave oddly. When I contacted Microsoft about it, they couldn't resolve the matter. In India, people are unclear about what's happening, and they keep pointing fingers at the graphics card as the problem, even though the GPU is fine. It happened with my 3060 as well.
I've uninstalled NVIDIA drivers multiple times using DDU, but it didn't solve the issue. When everything froze, the PC restarted itself. I own a 65" LG QNED 85 monitor with built-in monitors and used it as a TV. An HDMI cable connected to the Sceptre 200Hz wide screen and a Wacom Cintiq 22HD. When it froze, I turned on the monitor and then the Sceptre—at that moment, the big screen was in standby while the Sceptre displayed the frozen image.
I've reinstalled drivers numerous times, but the problem persisted. NVIDIA also claimed responsibility for the issue, citing DDR4 RAM and the GPU, suggesting I send it to ASUS. They provided a replacement GPU, but it didn't fix the problem. I uninstalled it again and still faced the same issues. NVIDIA insisted the problem was with the motherboard, but they seemed uncertain about the cause.
I also experienced driver errors (DistributedCOM event ID 10016). Windows 11 might be involved, though I'm not certain. I receive an error from volmgr (event ID 162, source Eventlog, event ID 6008) and a critical kernel power event (ID 41). Articles suggested it could be related to the power supply unit, but this PSU is brand new—just a year old, Corsair 1200i. I'm unsure where to start or how to proceed without risking further damage by sending my PC to a support group for $300.
My main concern is the freezing during screen saver sessions after sitting for an hour or more. Microsoft asked me to recreate the issue, but I couldn't. I've dealt with similar problems since Windows 98, and I'm seeking clear guidance on resolving these warnings and errors.
Update your post with complete hardware details and operating system information.
PSU: make, model, wattage.
Disk drive(s): make, model, capacity, current usage?
= = = =
This has occurred repeatedly when a screen saver was active.
Begin by turning off the screen saver.
Download all necessary drivers directly from the manufacturer’s official site. Install and adjust as needed.
Avoid third-party tools or installers.
Check Reliability History/Monitor for better insights; the timeline view is more intuitive than Event Viewer, and patterns may become clear.
Run built-in Windows Troubleshooters—they might resolve the issue.
Also execute "sfc /scannow" and "dism".
References:
https://www.lifewire.com/how-to-use-sfc-...es-2626161
https://www.windowscentral.com/how-use-d...s-10-image
I turned off the screen saver while the computer was idle when I left to shower; the screens were off. Upon returning, the desktop froze. It came back on when I powered it up using the LG 65" QNED 85 class i monitor. After turning it off and back on, it would wake up again. There was no suspend mode or hibernate function, and the screen saver remained disabled. Nvidia mistakenly identified me as the GPU, which was already acknowledged. I verified with a reliable monitor that there were two errors and three previous errors.
Troubleshoot in Settings shows no graphics-related issues, everything appears normal. The screen saver is off but still freezes occasionally; it resolves when I power on and off the screen, though sometimes it doesn’t. All drivers were downloaded and installed. The sfc /scannow command found no integrity problems, and Dism reported no corruption in component storage.
The setup and power configuration for all 12 HDDs remain unclear—do they connect directly to the host PC or include external units with separate supplies? The 1200 Watt PSU appears to be quite recent, likely supporting past heavy gaming sessions, video editing tasks, or even bit mining activities.
There are no LsaSvr-related error codes detected. Is there an instance of Lsasrv.exe running on the system? For a detailed inspection, use Process Explorer (available from Microsoft) via the provided link.
6 external drives and 6 internal ones. So far in Process Explorer I see a System Idle Process at CPU 99.8 -99%. I checked my HDMI fiber optic cable and found a kink, but didn’t notice it. The 1200W PSU is only a year and a half old compared to another one that’s been working since 2006 and still is! That one is on a different PC. This one is brand new. Heavy gaming when streaming, video editing when editing, no bit mining.
I’ve been experiencing this issue:
- The application-specific permission settings don’t allow Local Activation for the COM Server app with the given CLSID and APPID.
- There’s also a warning about security permissions related to an event ID 263 and multiple DistributedCOM warnings.
- I tried contacting Microsoft, but they seem unsure of how to proceed and rely on their notes without much expertise. One support representative mentioned escalating to Level 3, but they never called back.
- Customer service reps are mostly from India, Philippines, or Nigeria, and sometimes they’re rude when dealing with issues. This place is my last resort.
Reduce components as much as possible to a minimal setup for testing.
Aim for a simple baseline to check if errors persist.
Gradually reintroduce parts one by one, giving time and at least one restart between each addition.
Keep repeating this until everything functions correctly without issues.
It seems the build has hit a critical point where performance drops unexpectedly.
Expect to repeat troubleshooting steps multiple times—learning curves are likely involved.
Take care, stay methodical, and track as many measurable parameters as you can during testing.
Monitor actual usage and percentage values, noting which resources consume the most.
It’s possible everything works fine with configuration X, but fails at X+1.
Identify X and X+1 for further analysis.
I understand the assistance, though the outcome didn't resolve my issue. I discovered a workaround but encountered a Command Prompt problem. The link provided matches what I needed, yet when executing the command, I received an error stating the file wasn't found. The system reported: "The call to GetNameSecurityInfo () failed."