Hi again
Much of what follows is based on your Event Viewer error logs (thank you for providing them: no worries about having to compress/decompress them).
Intel Rapid Storage
I think we'll likely want to remove the Intel Rapid Storage drivers again. They are causing all sorts of trouble in your error logs. Your error logs were seriously large, considering the short span they covered (late August till now). Three different categories of errors were caused by the Intel Rapid Storage drivers: a Service Control Manager error, an Application error (crash event), and a .NET Runtime error related to "IAStorDataMgrSvc.exeFramework". These errors repeat over and over and over. Far too many.
ASMedia Controller Driver
I like the idea of sticking with a controller driver from ASMedia - whichever one yields the best results is OK. (It seems to be mostly the USB 3.1 drivers which get the worst press). And the generic storAHCI driver was generating a lot of warnings ("reset to device RaidPort2") while the ASMedia was gone.
Critical Errors
For that late August to present event period, your computer "rebooted unexpectedly" at least twenty times. A few of these were related to fatal "bugchecks". You can change a few settings to allow your system to display the error message when these errors occur (rather than automatically restarting) & to save a "mini dump" (which can be analyzed to try a determine the cause of the crash). If you have had system freezes that caused you to "hard reboot" (by holding down the power button for four to ten seconds and power off) - let us know. At the end of this post, I'll paste in the instructions for making those settings changes.
AI Suite related errors
A component named "Asus com service" seems to be having trouble loading. Now, if it is part of the Asus AI Suite, I imagine you might want to simply completely uninstall the AI Suite -- since it's a often-cited source of trouble.
Norton 360 & Nvidia Stream service errors
Norton & Nvidia were top suspects in your hard pagefault count charts. They are also producing a fair amount of errors in your logs. Both of them have had modules crashing regularly. For Nvidia, the errors point to the "NvStreamNetworkService.exe", the network streaming component of the optional "GeForce Experience" modules. Earlier in this thread, I think I posted a link to a few articles on how to manage the custom installs for the latest Nvidia drivers - you can clean out the old, and install the new - while being able to pick and choose which, if any, of the optional "extras" are needed or desired. For Norton, I still think trying things with Norton uninstalled is something to consider: your subscription is still good for the same period of time ... you can always reinstall if it turns out Norton isn't causing some of the trouble. Whether or not you uninstall Norton (at least for testing) -- Norton still needs to be either "repair reinstalled" or removed and reinstalled: it's causing errors in the background. And it's not good when modules of your antivirus crash. Can't hurt to boot the computer with a "Rescue CD" to provide a "second opinion" antimalware scan.
Windows Fast Startup
Your error logs have several entries "Windows failed fast startup with error status 0xC00000D4" ... now, these could well be related to the times when your system restarted after a crash (since "fast startup" relies on a partial hibernation to work, and Windows doesn't have time to hibernate when it crashes suddenly). If these entries continue even after the bugchecks and reboots are fixed, let us know - it might be worth investigating.
____________________________________
I promised to attach instructions for the "Automatic Restart" settings change, and the "Save as Mini-dump" setting for fatal errors. Here they are:
How to save "Minidumps" after Blue Screen Errors & Turn Off Automatic Restart after a System Crash
1) Right-click the Windows 10 Start Menu icon
2) Select System
3) Select Advanced Settings
4) In the Advanced tab, in the Startup and Recovery section, select Settings
5) In the System Failure section, make sure there is a checkmark in the option box "Write an event to the system log"
6) In the System Failure section, remove the checkmark from the option box "Automatically restart" (this will allow you to see the actual error screen - and be able to immediately see the error message without having to look through the logs)
7) In the System Failure section, in the drop-down menu for "Write debugging information", select the item "Small memory dump (256 KB)" ... you should see the "Small Dump Directory" location automatically display the default %SystemRoot%\Minidump [%SystemRoot% stands for the directory containing the Windows folder.... on many systems, that is C:\Windows].
8) Click OK to save and exit the settings window.
If you continue to get fatal errors (also called Blue Screen errors), you can try investigating possible causes by using a simple and free dump-analysis program, such as WhoCrashed by Resplendence Software (the same software house that produces Latency Monitor). Should serious Blue screen errors continue for any length of time, we'll refer you to the BSOD forum here at SysNative - where the techs have training with in-depth analysis and advanced tools for such errors.
Sorry for the extended length of this post ... there was a lot of material to cover. Might be easier to print this out, and just try things one small step at a time.
