C
Cybot
Windows 10 Pro 1909 (OS Build 18363.535)
MSI GE73 Raider RGB 8RE
since about the December cumulative update for windows 10, when I turn on my system, or wake the system, the login screen is acting like I am running windows on a 15 year old machine, not one less than a year old. the cursor severely lags, any sound that plays (i.e. the logon sound) is broken up, like the system is under heavy load, and trying to enter any keyboard input (pin code or password) is severely delayed. once I login to windows, the issue disappears. windows becomes responsive and the input lag disappears. looking at the event viewer the problem seems to lay with the lock screen app (which surprised me. I would have thought the locking mechanism of windows would have been built into the system, not relying on an app). I am seeing some strange messages that give no real info on what went wrong with the app. had anyone else encountered this issue? is there a way to solve it? or do we have to wait for M$ to fix what they broke?
error messages seen in event viewer:
Fault bucket 2218673995797537995, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0
Problem signature:
P1: Microsoft.LockApp_10.0.18362.449_neutral__cw5n1h2txyewy
P2: praid:WindowsDefaultLockScreen
P3: 0.0.0.0
P4: 00000000
P5: StackHash_0000
P6: 0.0.0.0
P7: 00000000
P8: 00000000
P9: PCH_84
P10:
Attached files:
\\?\C:\Users\Cybot\AppData\Local\Temp\WERB00E.tmp.WERDataCollectionStatus.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB36A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB9D4.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAAC.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC490.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.LockAp_196ccb5fca52dd6d6a1038fc51d341a75da856_6df23506_0b05746a-9635-4d12-ac52-1d09d6cf15c4
Analysis symbol:
Rechecking for solution: 0
Report Id: d9240c33-70c7-4c28-a905-70c3b8a1dc6c
Report Status: 268566528
Hashed bucket: c9207e59cf82a3c1aeca503e7fe8a4cb
Cab Guid: 0
Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x00000000
Fault offset: 0x0000000000000000
Faulting process id: 0x39b0
Faulting application start time: 0x01d5b38674e30b7d
Faulting application path: bad_module_info
Faulting module path: unknown
Report Id: d9240c33-70c7-4c28-a905-70c3b8a1dc6c
Faulting package full name: Microsoft.LockApp_10.0.18362.449_neutral__cw5n1h2txyewy
Faulting package-relative application ID: WindowsDefaultLockScreen
I have run chkdsk on all my disks (C:, D:, and E
I ran both the standard 'chkdsk x:' command as well as the 'chkdsk /scan /perf x:' command
i have run sfc /scannow
I have also run DISM /online /cleanup-image /checkhealth
no issues were found
as an extra step due to the windows feature involved, I also ran a scan with MBAM premium and ESET Smart Security Premium.
No threats were found.
I also ran MRT which reported no threats found
Continue reading...
MSI GE73 Raider RGB 8RE
since about the December cumulative update for windows 10, when I turn on my system, or wake the system, the login screen is acting like I am running windows on a 15 year old machine, not one less than a year old. the cursor severely lags, any sound that plays (i.e. the logon sound) is broken up, like the system is under heavy load, and trying to enter any keyboard input (pin code or password) is severely delayed. once I login to windows, the issue disappears. windows becomes responsive and the input lag disappears. looking at the event viewer the problem seems to lay with the lock screen app (which surprised me. I would have thought the locking mechanism of windows would have been built into the system, not relying on an app). I am seeing some strange messages that give no real info on what went wrong with the app. had anyone else encountered this issue? is there a way to solve it? or do we have to wait for M$ to fix what they broke?
error messages seen in event viewer:
Fault bucket 2218673995797537995, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0
Problem signature:
P1: Microsoft.LockApp_10.0.18362.449_neutral__cw5n1h2txyewy
P2: praid:WindowsDefaultLockScreen
P3: 0.0.0.0
P4: 00000000
P5: StackHash_0000
P6: 0.0.0.0
P7: 00000000
P8: 00000000
P9: PCH_84
P10:
Attached files:
\\?\C:\Users\Cybot\AppData\Local\Temp\WERB00E.tmp.WERDataCollectionStatus.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB36A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB9D4.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAAC.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC490.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.LockAp_196ccb5fca52dd6d6a1038fc51d341a75da856_6df23506_0b05746a-9635-4d12-ac52-1d09d6cf15c4
Analysis symbol:
Rechecking for solution: 0
Report Id: d9240c33-70c7-4c28-a905-70c3b8a1dc6c
Report Status: 268566528
Hashed bucket: c9207e59cf82a3c1aeca503e7fe8a4cb
Cab Guid: 0
Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x00000000
Fault offset: 0x0000000000000000
Faulting process id: 0x39b0
Faulting application start time: 0x01d5b38674e30b7d
Faulting application path: bad_module_info
Faulting module path: unknown
Report Id: d9240c33-70c7-4c28-a905-70c3b8a1dc6c
Faulting package full name: Microsoft.LockApp_10.0.18362.449_neutral__cw5n1h2txyewy
Faulting package-relative application ID: WindowsDefaultLockScreen
I have run chkdsk on all my disks (C:, D:, and E
I ran both the standard 'chkdsk x:' command as well as the 'chkdsk /scan /perf x:' command
i have run sfc /scannow
I have also run DISM /online /cleanup-image /checkhealth
no issues were found
as an extra step due to the windows feature involved, I also ran a scan with MBAM premium and ESET Smart Security Premium.
No threats were found.
I also ran MRT which reported no threats found
Continue reading...