I am currently conducting a system scan with the antivirus tool you asked me to use, but I doubt that that will find anything.
Here is a small number of errors and warnings that I have found.
I checked the Application Log first, but then I checked the system log and added a few of the errors and warnings that I found in there as well.
xXx
Application Errors:
The program backgroundTaskHost.exe version 6.3.9600.16384 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: c80
Start Time: 01cf075506166ec3
Termination Time: 4294967295
Application Path: C:\WINDOWS\system32\backgroundTaskHost.exe
Report Id: fa58b2b0-7348-11e3-bf3f-089e01967e33
Faulting package full name: Facebook.Facebook_1.2.0.12_x64__8xx8rvfyw5nnt
Faulting package-relative application ID: App
xXx
A problem prevented Customer Experience Improvement Program data from being sent to Microsoft, (Error 80070005).
xXx
Faulting application name: atieclxx.exe, version: 6.14.11.1143, time stamp: 0x51ad48db
Faulting module name: atieclxx.exe, version: 6.14.11.1143, time stamp: 0x51ad48db
Exception code: 0xc0000005
Fault offset: 0x000000000002ea19
Faulting process id: 0x1840
Faulting application start time: 0x01cf05ef076e7bd6
Faulting application path: C:\WINDOWS\system32\atieclxx.exe
Faulting module path: C:\WINDOWS\system32\atieclxx.exe
Report Id: 45949ff2-71e2-11e3-bf3f-089e01967e33
Faulting package full name:
Faulting package-relative application ID:
xXx
The program Facebook.exe version 0.0.0.1 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: c20
Start Time: 01cf049a96d56899
Termination Time: 4294967295
Application Path: C:\Program Files\WindowsApps\Facebook.Facebook_1.2.0.12_x64__8xx8rvfyw5nnt\Facebook.exe
Report Id: e0c71972-708d-11e3-bf3d-089e01967e33
Faulting package full name: Facebook.Facebook_1.2.0.12_x64__8xx8rvfyw5nnt
Faulting package-relative application ID: App
xXx
Activation of app Facebook.Facebook_8xx8rvfyw5nnt!App failed with error: The app didn't start in the required time. See the Microsoft-Windows-TWinUI/Operational log for additional information.
xXx
Activation of app Facebook.Facebook_8xx8rvfyw5nnt!App failed with error: The app didn't start in the required time. See the Microsoft-Windows-TWinUI/Operational log for additional information.
System Errors:
Warning: A multi-touch device reported inconsistent contact information.
xXx
Warning: The driver \Driver\WudfRd failed to load for the device SWD\SensorsAndLocationEnum\LPSensorSWDevice.
xXx
I have 8 of these errors within 2 seconds of each other: A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 40.
Error: The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
xXx
This is a warning I had after my computer JUST froze: The driver \Driver\WudfRd failed to load for the device SWD\SensorsAndLocationEnum\LPSensorSWDevice.
xXx
Error: The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
xXx
I always see this after having had to restart my laptop: Error: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.