Windows Default Lock Screen Stopped Working

[MadDemon64]

Usually when I wake up my computer it shows the standard lock screen, but occasionally it does not. Today when it did not I saw the following in my reliability history and event viewer:

Description
Faulting Application Path: C:\Windows\SystemApps\Microsoft.LockApp_cw5n1h2txyewy\LockApp.exe

Problem signature
Problem Event Name: MoAppCrash
Package Full Name: Microsoft.LockApp_10.0.10586.0_neutral__cw5n1h2txyewy
Application Name: praid:WindowsDefaultLockScreen
Application Version: 0.0.0.0
Application Timestamp: 5632d5a5
Fault Module Name: StackHash12_7ba
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: 887a0004
Exception Offset: 0
OS Version: 10.0.10586.2.0.0.768.101
Locale ID: 1033

Extra information about the problem
Bucket ID: 7fc814908c631ddbf76b124c0e5394d5 (133315673519)
___________________________________
Activation of app Microsoft.LockApp_cw5n1h2txyewy!WindowsDefaultLockScreen failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.
_____________________________________
Faulting application name: LockApp.exe, version: 0.0.0.0, time stamp: 0x5632d5a5
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.10586.212, time stamp: 0x56fa191c
Exception code: 0xc000027b
Fault offset: 0x0000000000517ae4
Faulting process id: 0x35f8
Faulting application start time: 0x01d1a9421940e0f8
Faulting application path: C:\Windows\SystemApps\Microsoft.LockApp_cw5n1h2txyewy\LockApp.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: 705c3c85-1f14-4f16-ba5e-605756fc9d66
Faulting package full name: Microsoft.LockApp_10.0.10586.0_neutral__cw5n1h2txyewy
Faulting package-relative application ID: WindowsDefaultLockScreen

Anyone know what this means and how to potentially fix it?

 

[scout_03]

did you try to reset it http://windows.microsoft.com/en-us/windows-10/getstarted-lock-screen also it would not be a bad idea to check you hdd with the maker software in case files are on bad sector .

 

[MadDemon64]

did you try to reset it http://windows.microsoft.com/en-us/windows-10/getstarted-lock-screen also it would not be a bad idea to check you hdd with the maker software in case files are on bad sector .

What is the maker software?

 

[scout_03]

mane and model of your hdd i link to it

 

[wpgwpg]

Try opening an administrator command prompt and issuing this command: sfc /scannow . That will scan for and attempt to correct any corrupt system files. It will run 10 - 20 min.

Good luck.

 

[MadDemon64]

I ran both the sfc from the command prompt and the check disk from c drive properties and found nothing.

 

[MadDemon64]

I was looking at the operation logs and found this error code:

ErrorCode -2147023170

Does it mean anything?

 

[MadDemon64]

New update:
I googled "remote procedure call failed" and came across a thread that talked about a similar problem coming from using the Photos app for the photo viewer default app. It said that the remote procedure call error could be fixed by switching to windows photo viewer. Is this correct?

 

[scout_03]

the error code lead to this https://www.google.ca/search?q=Error+Code+-2147023170&biw=1920&bih=969&source=lnms&sa=X&ved=0ahUKEwimwM6s4c3MAhWLFT4KHb8ICBoQ_AUIBigA&dpr=1 i never try it so could not tell .

 

[MadDemon64]

the error code lead to this https://www.google.ca/search?q=Error+Code+-2147023170&biw=1920&bih=969&source=lnms&sa=X&ved=0ahUKEwimwM6s4c3MAhWLFT4KHb8ICBoQ_AUIBigA&dpr=1 i never try it so could not tell .

I have no idea how to read that page.

 

[scout_03]

that is related to your error http://answers.microsoft.com/en-us/windows/forum/windows_10-windows_store/windows-store-crashes-with-exception-code/11cc9422-165f-4cf7-9525-2153d7e54de9 for this code Exception code: 0xc000027b so i would recheck all windows files .

 

[MadDemon64]

that is related to your error http://answers.microsoft.com/en-us/windows/forum/windows_10-windows_store/windows-store-crashes-with-exception-code/11cc9422-165f-4cf7-9525-2153d7e54de9 for this code Exception code: 0xc000027b so i would recheck all windows files .

Well I managed to check my files and nothing showed up as corrupt or anything, but I did change my picture viewer and that seemed to do the trick.
*Edit* Nevermind it's back to screwing up again.

 

[scout_03]

did you try the repair files for the os but i would check the hdd it could have bad sector .

 

[MadDemon64]

did you try the repair files for the os but i would check the hdd it could have bad sector .

I used sfc /scannow. It found nothing.
I used Dism /scanhealth and /checkhealth. It found nothing.
I used chkdsk /r. It found no bad sectors.

Maybe it won't happen now hopefully.

 

[scout_03]

try the files repair it could be a bad files and system read it or not .

 

[MadDemon64]

try the files repair it could be a bad files and system read it or not .

SFC and/or DISM are not the files repair? Then what is?

 

[scout_03]

dism is a image only so why you dont try with the os dvd to do the repair image could have a error in .

 

[MadDemon64]

dism is a image only so why you dont try with the os dvd to do the repair image could have a error in .

Because I upgraded to Windows 10 and the os dvd is for 8.1.

 

[scout_03]

then i dont see anything else i could do wait and see if someone else have a solution .