[SOLVED] Graphics issues after moving PC ?

Status
Not open for further replies.
May 27, 2024
3
0
20
Hi everyone,

I recently moved to a new house and have encountered several graphics-related problems with my PC, which I hope to get help with. I suspect that this is GPU damage, but I really hope it doesn't... I tried to be really gentle with my PC.

Here are the issues that I noticed so far:


1. Game Lag: One of my games, which used to run smoothly, is now experiencing significant lag. The strange part is that I have tested two games: Hell Divers 2 (a really intensive game) and Noita (a light pixel 2D game). Only "Noita" shows me slow-mo.

2. Web Browser Text Rendering: Text in my web browser is displayed incorrectly, or some letters are not shown. Maybe not only in Browser, but I haven't noticed it other places. Here are some examples: link to imgure with screens that i captured while tried to write this post

3. OBS Black Screen: OBS shows a black screen when trying to capture my monitor's signal, even though all settings are correct. (at least it worked for many times before)

My Setup:
  • CPU: AMD Ryzen 7 7800X3D 4.2 GHz 8-Core Processor
  • Motherboard: Gigabyte B650M AORUS ELITE AX Micro ATX AM5 Motherboard
  • Memory: G.Skill Trident Z5 Neo RGB 32 GB (2 x 16 GB) DDR5-6000 CL30 Memory
  • GPU: MSI SUPRIM LIQUID X GeForce RTX 4090 24 GB Video Card
  • OS: Windows 11 Home 23H2, build 22631.3593
What I've Tried So Far:

1. Updated GPU Drivers: Downloaded and installed the latest drivers from the Geforce Experience app

2. Checked Physical Connections: I ensured the GPU was seated correctly and all cables were securely connected.

3. System Updates: Ensured the operating system is up to date.


Here is logs from Even Viewer that i found might be helpful:

System LOG.txt:
Markdown (GitHub flavored):
Level    Date and Time    Source    Event ID    Task Category
Error    5/27/2024 6:53:49 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Error    5/27/2024 6:46:06 PM    BTHUSB    17    None    The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.
Error    5/27/2024 6:46:05 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Critical    5/27/2024 6:45:56 PM    Microsoft-Windows-Kernel-Power    41    (63)    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Error    5/27/2024 6:45:53 PM    stornvme    11    None    The driver detected a controller error on \Device\RaidPort1.
Error    5/27/2024 6:46:02 PM    EventLog    6008    None    The previous system shutdown at 6:17:23 PM on ‎5/‎26/‎2024 was unexpected.
Error    5/27/2024 6:45:52 PM    Microsoft-Windows-Kernel-Boot    29    None    Windows failed fast startup with error status 0xC00000D4.
Error    5/26/2024 6:00:01 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Error    5/26/2024 4:58:06 PM    Tcpip    4207    None    The IPv6 TCP/IP interface with index 19 failed to bind to its provider.
Error    5/26/2024 4:57:28 PM    BTHUSB    17    None    The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.
Error    5/26/2024 4:57:26 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Critical    5/26/2024 4:57:17 PM    Microsoft-Windows-Kernel-Power    41    (63)    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Error    5/26/2024 4:57:16 PM    stornvme    11    None    The driver detected a controller error on \Device\RaidPort1.
Error    5/26/2024 4:57:23 PM    EventLog    6008    None    The previous system shutdown at 4:49:57 PM on ‎5/‎26/‎2024 was unexpected.
Error    5/26/2024 4:57:15 PM    Microsoft-Windows-Kernel-Boot    29    None    Windows failed fast startup with error status 0xC00000D4.
Error    5/26/2024 4:50:03 PM    BTHUSB    17    None    The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.
Error    5/26/2024 4:49:58 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Error    5/26/2024 4:49:51 PM    stornvme    11    None    The driver detected a controller error on \Device\RaidPort1.
Error    5/26/2024 4:49:29 PM    Service Control Manager    7034    None    The nordsec-threatprotection-service service terminated unexpectedly.  It has done this 1 time(s).
Error    5/26/2024 4:49:27 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 4:49:26 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 4:49:26 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 4:49:26 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 4:49:26 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 4:49:26 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 4:49:26 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 4:49:26 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 4:22:00 PM    stornvme    11    None    The driver detected a controller error on \Device\RaidPort1.
Error    5/26/2024 4:06:41 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 4:06:41 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 4:06:41 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 4:06:41 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 4:06:41 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 4:06:41 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 4:06:41 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 4:06:41 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 4:06:40 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
Error    5/26/2024 4:00:27 PM    BTHUSB    17    None    The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.
Error    5/26/2024 4:00:26 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Error    5/26/2024 4:00:15 PM    stornvme    11    None    The driver detected a controller error on \Device\RaidPort1.
Error    5/26/2024 3:59:55 PM    Service Control Manager    7034    None    The nordsec-threatprotection-service service terminated unexpectedly.  It has done this 1 time(s).
Error    5/26/2024 3:59:52 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 3:59:52 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 3:59:52 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 3:59:52 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 3:59:52 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 3:59:52 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 3:59:52 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 3:59:52 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 3:01:34 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Error    5/26/2024 2:55:34 PM    stornvme    11    None    The driver detected a controller error on \Device\RaidPort1.
Error    5/26/2024 2:41:09 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 2:41:09 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 2:41:09 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 2:41:09 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 2:41:09 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 2:41:09 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 2:41:09 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/26/2024 2:41:09 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/25/2024 6:44:10 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Error    5/25/2024 6:39:28 PM    Service Control Manager    7000    None    "The Steam Client Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion."
Error    5/25/2024 6:39:28 PM    Service Control Manager    7009    None    A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect.
Error    5/25/2024 6:38:10 PM    stornvme    11    None    The driver detected a controller error on \Device\RaidPort1.
Error    5/25/2024 12:32:23 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout.
Error    5/25/2024 12:32:22 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/25/2024 12:32:22 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/25/2024 12:32:22 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/25/2024 12:32:22 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/25/2024 12:32:22 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/25/2024 12:32:22 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/25/2024 12:32:22 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/25/2024 12:32:22 AM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/24/2024 8:10:38 PM    Microsoft-Windows-DistributedCOM    10005    None    "DCOM got error ""87"" attempting to start the service GamingServices with arguments ""Unavailable"" in order to run the server:
{D529741A-1BF1-4D1E-9976-35089622E758}"
Error    5/24/2024 8:10:38 PM    Microsoft-Windows-DistributedCOM    10005    None    "DCOM got error ""87"" attempting to start the service GamingServices with arguments ""Unavailable"" in order to run the server:
{3E8C9ABE-9226-4609-BF5B-60288A391DEE}"
Error    5/24/2024 8:10:38 PM    Microsoft-Windows-DistributedCOM    10005    None    "DCOM got error ""87"" attempting to start the service GamingServices with arguments ""Unavailable"" in order to run the server:
{D529741A-1BF1-4D1E-9976-35089622E758}"
Error    5/24/2024 8:10:38 PM    Microsoft-Windows-DistributedCOM    10005    None    "DCOM got error ""87"" attempting to start the service GamingServices with arguments ""Unavailable"" in order to run the server:
{3E8C9ABE-9226-4609-BF5B-60288A391DEE}"
Error    5/24/2024 8:05:55 PM    Microsoft-Windows-WindowsUpdateClient    20    Windows Update Agent    Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience.
Error    5/24/2024 8:05:53 PM    Microsoft-Windows-WindowsUpdateClient    20    Windows Update Agent    Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.
Error    5/24/2024 6:00:01 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Error    5/24/2024 5:45:43 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Error    5/24/2024 5:39:43 PM    stornvme    11    None    The driver detected a controller error on \Device\RaidPort1.
Error    5/23/2024 11:53:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/23/2024 11:53:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/23/2024 11:53:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/23/2024 11:53:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/23/2024 11:53:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/23/2024 11:53:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/23/2024 11:53:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/23/2024 11:53:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/23/2024 6:56:07 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Error    5/23/2024 6:50:07 PM    stornvme    11    None    The driver detected a controller error on \Device\RaidPort1.
Error    5/22/2024 8:53:28 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout.
Error    5/22/2024 8:53:28 PM    Microsoft-Windows-DistributedCOM    10010    None    The server microsoft.windowscommunicationsapps_16005.14326.21888.0_x64__8wekyb3d8bbwe!microsoft.windowslive.calendar.AppXwkn9j84yh1kvnt49k5r8h6y1ecsv09hs.mca did not register with DCOM within the required timeout.
Error    5/22/2024 8:53:28 PM    Microsoft-Windows-DistributedCOM    10010    None    The server 5319275A.WhatsAppDesktop_2.2419.11.0_x64__cv1g1gvanyjgm!App.AppXagyrmpyx1bhhy2gjpvcnfecxpg298mss.mca did not register with DCOM within the required timeout.
Error    5/22/2024 8:53:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/22/2024 8:53:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/22/2024 8:53:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/22/2024 8:53:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/22/2024 8:53:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/22/2024 8:53:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/22/2024 8:53:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/22/2024 8:53:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/22/2024 6:31:21 PM    Service Control Manager    7000    None    "The Steam Client Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion."
Error    5/22/2024 6:31:21 PM    Service Control Manager    7009    None    A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect.
Error    5/22/2024 6:30:25 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Error    5/22/2024 5:30:04 PM    stornvme    11    None    The driver detected a controller error on \Device\RaidPort1.
Error    5/21/2024 11:04:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/21/2024 11:04:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/21/2024 11:04:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/21/2024 11:04:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/21/2024 11:04:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/21/2024 11:04:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/21/2024 11:04:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/21/2024 11:04:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/21/2024 6:17:13 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Error    5/21/2024 6:11:33 PM    BTHUSB    17    None    The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.
Error    5/21/2024 6:11:31 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Critical    5/21/2024 6:11:22 PM    Microsoft-Windows-Kernel-Power    41    (63)    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Error    5/21/2024 6:11:21 PM    stornvme    11    None    The driver detected a controller error on \Device\RaidPort1.
Error    5/21/2024 6:11:29 PM    EventLog    6008    None    The previous system shutdown at 10:36:07 PM on ‎5/‎20/‎2024 was unexpected.
Error    5/21/2024 6:11:20 PM    Microsoft-Windows-Kernel-Boot    29    None    Windows failed fast startup with error status 0xC00000D4.
Error    5/20/2024 10:17:25 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/20/2024 10:15:14 PM    BTHUSB    17    None    The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.
Error    5/20/2024 10:15:13 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Error    5/20/2024 10:15:03 PM    stornvme    11    None    The driver detected a controller error on \Device\RaidPort1.

Log Security.txt :
Markdown (GitHub flavored):
Level    Date and Time    Source    Event ID    Task Category
Error    5/27/2024 6:46:02 PM    Microsoft-Windows-Eventlog    1101    Event processing    Audit events have been dropped by the transport.  0
Error    5/26/2024 4:57:23 PM    Microsoft-Windows-Eventlog    1101    Event processing    Audit events have been dropped by the transport.  0
Error    5/21/2024 6:11:29 PM    Microsoft-Windows-Eventlog    1101    Event processing    Audit events have been dropped by the transport.  0
Error    5/20/2024 10:36:07 PM    Microsoft-Windows-Eventlog    1101    Event processing    Audit events have been dropped by the transport.  0

Log Application.txt:

Markdown (GitHub flavored):
Level    Date and Time    Source    Event ID    Task Category
Error    5/27/2024 6:46:22 PM    Application Error    1000    Application Crashing Events    "Faulting application name: cpudump.exe, version: 1.0.0.1, time stamp: 0x57cd3da5
Faulting module name: MFCCPU.dll, version: 24.1.5.2, time stamp: 0x6597cd4f
Exception code: 0xc0000005
Fault offset: 0x00004200
Faulting process id: 0x0x4584
Faulting application start time: 0x0x1DAB05DC99B6590
Faulting application path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\cpudump.exe
Faulting module path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\MFCCPU.dll
Report Id: 339d2d5c-06b7-48d1-837f-c1afb3d33f2c
Faulting package full name:
Faulting package-relative application ID: "
Warning    5/26/2024 5:48:23 PM    Microsoft-Windows-Perflib    1008    None    "The Open procedure for service ""WmiApRpl"" in DLL ""C:\Windows\system32\wbem\wmiaprpl.dll"" failed with error code The device is not ready.. Performance data for this service will not be available."
Error    5/26/2024 4:57:40 PM    Application Error    1000    Application Crashing Events    "Faulting application name: cpudump.exe, version: 1.0.0.1, time stamp: 0x57cd3da5
Faulting module name: MFCCPU.dll, version: 24.1.5.2, time stamp: 0x6597cd4f
Exception code: 0xc0000005
Fault offset: 0x00004200
Faulting process id: 0x0x4198
Faulting application start time: 0x0x1DAAF8570277688
Faulting application path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\cpudump.exe
Faulting module path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\MFCCPU.dll
Report Id: 27e89fa3-e392-4c2f-9dc8-e335c01bc4da
Faulting package full name:
Faulting package-relative application ID: "
Error    5/26/2024 4:50:15 PM    Application Error    1000    Application Crashing Events    "Faulting application name: cpudump.exe, version: 1.0.0.1, time stamp: 0x57cd3da5
Faulting module name: MFCCPU.dll, version: 24.1.5.2, time stamp: 0x6597cd4f
Exception code: 0xc0000005
Fault offset: 0x00004200
Faulting process id: 0x0x4750
Faulting application start time: 0x0x1DAAF8466DA8819
Faulting application path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\cpudump.exe
Faulting module path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\MFCCPU.dll
Report Id: c54710a1-d625-4bcc-8474-5d0abcfe91e5
Faulting package full name:
Faulting package-relative application ID: "
Error    5/26/2024 4:49:29 PM    VSS    8193    None    "Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.  hr = 0x8007045b, A system shutdown is in progress.
. "
Error    5/26/2024 4:49:29 PM    VSS    13    None    "Volume Shadow Copy Service information: The COM Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress.
] "
Error    5/26/2024 4:49:29 PM    VSS    8193    None    "Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.  hr = 0x8007045b, A system shutdown is in progress.
. "
Error    5/26/2024 4:49:29 PM    VSS    13    None    "Volume Shadow Copy Service information: The COM Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress.
] "
Error    5/26/2024 4:00:41 PM    Application Error    1000    Application Crashing Events    "Faulting application name: cpudump.exe, version: 1.0.0.1, time stamp: 0x57cd3da5
Faulting module name: MFCCPU.dll, version: 24.1.5.2, time stamp: 0x6597cd4f
Exception code: 0xc0000005
Fault offset: 0x00004200
Faulting process id: 0x0x49C4
Faulting application start time: 0x0x1DAAF7D79C0E6AB
Faulting application path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\cpudump.exe
Faulting module path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\MFCCPU.dll
Report Id: dcac26d8-d933-4b3a-943f-095e02ba62ed
Faulting package full name:
Faulting package-relative application ID: "
Error    5/26/2024 3:59:56 PM    Application Error    1000    Application Crashing Events    "Faulting application name: nordvpn-service.exe, version: 1.1.0.34, time stamp: 0x65112d57
Faulting module name: KERNELBASE.dll, version: 10.0.22621.3527, time stamp: 0x83efbeab
Exception code: 0xe0434352
Fault offset: 0x000000000006543c
Faulting process id: 0x0x1244
Faulting application start time: 0x0x1DAABA1EC17C839
Faulting application path: C:\Program Files\NordVPN\nordvpn-service.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: df595a75-0bea-4c81-bbc2-c84b246572bc
Faulting package full name:
Faulting package-relative application ID: "
Warning    5/26/2024 3:15:08 PM    Microsoft-Windows-Perflib    1008    None    "The Open procedure for service ""WmiApRpl"" in DLL ""C:\Windows\system32\wbem\wmiaprpl.dll"" failed with error code The device is not ready.. Performance data for this service will not be available."
Error    5/21/2024 6:27:59 PM    Application Error    1000    Application Crashing Events    "Faulting application name: cpudump.exe, version: 1.0.0.1, time stamp: 0x57cd3da5
Faulting module name: MFCCPU.dll, version: 24.1.5.2, time stamp: 0x6597cd4f
Exception code: 0xc0000005
Fault offset: 0x00004200
Faulting process id: 0x0x3984
Faulting application start time: 0x0x1DAABA439CF92ED
Faulting application path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\cpudump.exe
Faulting module path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\MFCCPU.dll
Report Id: f71eef08-faed-4874-9c06-05f9475ba2c3
Faulting package full name:
Faulting package-relative application ID: "
Error    5/21/2024 6:12:30 PM    amd3dvcacheSvc    1    None    "The description for Event ID 1 from source amd3dvcacheSvc cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

amd3dvcacheSvc
CreateHelperUserProcess - WTSQueryUserToken Failed failed with 1008

The message resource is present but the message was not found in the message table
"
Error    5/20/2024 10:15:29 PM    Application Error    1000    Application Crashing Events    "Faulting application name: cpudump.exe, version: 1.0.0.1, time stamp: 0x57cd3da5
Faulting module name: MFCCPU.dll, version: 24.1.5.2, time stamp: 0x6597cd4f
Exception code: 0xc0000005
Fault offset: 0x00004200
Faulting process id: 0x0x3DD8
Faulting application start time: 0x0x1DAAAFAD7AA03CE
Faulting application path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\cpudump.exe
Faulting module path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\MFCCPU.dll
Report Id: 63e47f1d-3467-4eca-92ec-73f6c2bd5984
Faulting package full name:
Faulting package-relative application ID: "



Has anyone experienced similar issues or has any suggestions on what else I can try to fix these problems? I really need someone's help.






Thanks in advance for your help!


ps:that was really paintful to write this post and see how your pc dies..
 
Thanks for the excellent advice. Here is what I have done so far:

1. As advised on another forum, I checked all connections in my PC and re-installed GPU.
2. Then I did some command as @Ralston18 suggested

Here is my cmd history:

Rich (BB code):
Microsoft Windows [Version 10.0.22631.3593]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\System32>DISM /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.3593

No component store corruption detected.
The operation completed successfully.

C:\Windows\System32>DISM /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.3593

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\Windows\System32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.3593

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\System32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\System32>findstr /c:"[SR]" C:\Windows\Logs\CBS\CBS.log > C:\Users\bebag\Desktop\SFC_Repair_Log.txt

C:\Windows\System32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\System32>chkdsk /f /r
The type of the file system is NTFS.
I cannot lock the current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) y

This volume will be checked the next time the system restarts.

C:\Windows\System32>


After the system restarted, I checked filtered CBS.log but didn't find anything interesting there.

Summary of ChatGPT that helped me in this process:
  1. DISM /Online /Cleanup-Image /CheckHealth: Verified that there is no immediate component store corruption.
  2. DISM /Online /Cleanup-Image /ScanHealth: Found that the component store was repairable.
  3. DISM /Online /Cleanup-Image /RestoreHealth: Successfully repaired the component store.
  4. sfc /scannow (First Run): Found and successfully repaired corrupt files.
  5. Extracting SFC Details: Created a log file with the details of the SFC repairs.
  6. sfc /scannow (Second Run): Did not find any integrity violations, indicating that the previous issues have been successfully resolved.

I also did a memory diagnostic with the help of this guide:
run-memory-diagnostics-windows


I am happy to say that my main issues has been solved by these steps
(probably even somewhere in the middle of it, but I continued to be sure)


However, it still has some warnings and errors. And I want to fix them before closing this Question.

Logs filter for the last 12 hours that included only Critical, Warnings and Errors:

Security.log:
Code:
Level    Date and Time    Source    Event ID    Task Category
Error    5/28/2024 8:04:51 PM    Microsoft-Windows-Eventlog    1101    Event processing    Audit events have been dropped by the transport.  0
Error    5/28/2024 7:59:34 PM    Microsoft-Windows-Eventlog    1101    Event processing    Audit events have been dropped by the transport.  0

System.log
Code:
Level    Date and Time    Source    Event ID    Task Category
Warning    5/28/2024 9:57:14 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 to the user win\bebag SID (S-1-5-21-1969507849-2187711627-3854667153-1001) from address LocalHost (Using LRPC) running in the application container MicrosoftWindows.Client.WebExperience_524.13200.10.0_x64__cw5n1h2txyewy SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
Warning    5/28/2024 9:36:27 PM    Microsoft-Windows-FilterManager    11    None    "File System Filter 'mshield' (Version 10.0, ‎2022‎-‎06‎-‎22T07:39:08.000000000Z) does not support bypass IO.
Supported features: 0x7."
Warning    5/28/2024 9:36:27 PM    Microsoft-Windows-FilterManager    11    None    "File System Filter 'mshield' (Version 10.0, ‎2022‎-‎06‎-‎22T07:39:08.000000000Z) does not support bypass IO.
Supported features: 0x7."
Warning    5/28/2024 9:35:43 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 to the user win\bebag SID (S-1-5-21-1969507849-2187711627-3854667153-1001) 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."
Warning    5/28/2024 9:35:39 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 to the user win\bebag SID (S-1-5-21-1969507849-2187711627-3854667153-1001) 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."
Warning    5/28/2024 9:31:22 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscDataProtection
 and APPID
Unavailable
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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."
Error    5/28/2024 9:29:25 PM    BTHUSB    17    None    The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.
Warning    5/28/2024 9:29:25 PM    BTHUSB    3    None    A command sent to the adapter has timed out. The adapter did not respond.
Warning    5/28/2024 9:29:21 PM    BTHUSB    3    None    A command sent to the adapter has timed out. The adapter did not respond.
Error    5/28/2024 9:29:21 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Warning    5/28/2024 9:29:19 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: msv1_0"
Warning    5/28/2024 9:29:19 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: sfapm"
Warning    5/28/2024 9:29:19 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: schannel"
Warning    5/28/2024 9:29:19 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: wdigest"
Warning    5/28/2024 9:29:19 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: cloudap"
Warning    5/28/2024 9:29:19 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: pku2u"
Warning    5/28/2024 9:29:19 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: tspkg"
Warning    5/28/2024 9:29:19 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: msv1_0"
Warning    5/28/2024 9:29:19 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: kerberos"
Warning    5/28/2024 9:29:19 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: negoexts"
Error    5/28/2024 9:29:13 PM    stornvme    11    None    The driver detected a controller error on \Device\RaidPort1.
Error    5/28/2024 8:35:42 PM    Service Control Manager    7034    None    The nordsec-threatprotection-service service terminated unexpectedly.  It has done this 1 time(s).
Error    5/28/2024 8:35:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/28/2024 8:35:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/28/2024 8:35:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/28/2024 8:35:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/28/2024 8:35:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/28/2024 8:35:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/28/2024 8:35:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/28/2024 8:35:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/28/2024 8:35:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/28/2024 8:35:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/28/2024 8:35:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/28/2024 8:35:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/28/2024 8:35:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/28/2024 8:35:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/28/2024 8:35:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Error    5/28/2024 8:35:39 PM    Microsoft-Windows-DistributedCOM    10010    None    The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
Warning    5/28/2024 8:06:52 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscDataProtection
 and APPID
Unavailable
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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."
Warning    5/28/2024 8:06:52 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.SecurityAppBroker
 and APPID
Unavailable
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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."
Warning    5/28/2024 8:06:52 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscBrokerManager
 and APPID
Unavailable
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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."
Warning    5/28/2024 8:06:11 PM    Microsoft-Windows-FilterManager    11    None    "File System Filter 'mshield' (Version 10.0, ‎2022‎-‎06‎-‎22T07:39:08.000000000Z) does not support bypass IO.
Supported features: 0x7."
Warning    5/28/2024 8:06:11 PM    Microsoft-Windows-FilterManager    11    None    "File System Filter 'mshield' (Version 10.0, ‎2022‎-‎06‎-‎22T07:39:08.000000000Z) does not support bypass IO.
Supported features: 0x7."
Error    5/28/2024 8:05:47 PM    NetBT    4311    None    "Initialization failed because the driver device could not be created. Use the string ""000000000100320000000000D71000C011010000250200C001000000000000000000000000000000"" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the  Globally Unique Interface Identifier (GUID) if NetBT was unable to  map from GUID to MAC address. If neither the MAC address nor the GUID were  available, the string represents a cluster device name. "
Error    5/28/2024 8:05:47 PM    NetBT    4311    None    "Initialization failed because the driver device could not be created. Use the string ""000000000100320000000000D71000C013010000250200C000000000000000000000000000000000"" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the  Globally Unique Interface Identifier (GUID) if NetBT was unable to  map from GUID to MAC address. If neither the MAC address nor the GUID were  available, the string represents a cluster device name. "
Warning    5/28/2024 8:05:33 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 to the user win\bebag SID (S-1-5-21-1969507849-2187711627-3854667153-1001) 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."
Warning    5/28/2024 8:05:30 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 to the user win\bebag SID (S-1-5-21-1969507849-2187711627-3854667153-1001) 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."
Error    5/28/2024 8:04:56 PM    BTHUSB    17    None    The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.
Warning    5/28/2024 8:04:56 PM    BTHUSB    3    None    A command sent to the adapter has timed out. The adapter did not respond.
Error    5/28/2024 8:04:52 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Warning    5/28/2024 8:04:52 PM    BTHUSB    3    None    A command sent to the adapter has timed out. The adapter did not respond.
Warning    5/28/2024 8:04:50 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: msv1_0"
Warning    5/28/2024 8:04:50 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: sfapm"
Warning    5/28/2024 8:04:50 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: schannel"
Warning    5/28/2024 8:04:50 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: wdigest"
Warning    5/28/2024 8:04:50 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: cloudap"
Warning    5/28/2024 8:04:50 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: pku2u"
Warning    5/28/2024 8:04:50 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: tspkg"
Warning    5/28/2024 8:04:50 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: msv1_0"
Warning    5/28/2024 8:04:50 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: kerberos"
Warning    5/28/2024 8:04:50 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: negoexts"
Critical    5/28/2024 8:04:45 PM    Microsoft-Windows-Kernel-Power    41    (63)    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Error    5/28/2024 8:04:44 PM    stornvme    11    None    The driver detected a controller error on \Device\RaidPort1.
Error    5/28/2024 8:04:51 PM    EventLog    6008    None    The previous system shutdown at 7:59:34 PM on ‎5/‎28/‎2024 was unexpected.
Warning    5/28/2024 8:01:35 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscBrokerManager
 and APPID
Unavailable
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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."
Warning    5/28/2024 8:01:35 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscDataProtection
 and APPID
Unavailable
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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."
Warning    5/28/2024 8:01:35 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.SecurityAppBroker
 and APPID
Unavailable
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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."
Warning    5/28/2024 8:00:45 PM    Microsoft-Windows-FilterManager    11    None    "File System Filter 'mshield' (Version 10.0, ‎2022‎-‎06‎-‎22T07:39:08.000000000Z) does not support bypass IO.
Supported features: 0x7."
Warning    5/28/2024 8:00:45 PM    Microsoft-Windows-FilterManager    11    None    "File System Filter 'mshield' (Version 10.0, ‎2022‎-‎06‎-‎22T07:39:08.000000000Z) does not support bypass IO.
Supported features: 0x7."
Error    5/28/2024 7:59:40 PM    BTHUSB    17    None    The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.
Warning    5/28/2024 7:59:40 PM    BTHUSB    3    None    A command sent to the adapter has timed out. The adapter did not respond.
Error    5/28/2024 7:59:36 PM    Microsoft-Windows-TPM-WMI    1796    None    The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see [url=https://go.microsoft.com/fwlink/?linkid=2169931]https://go.microsoft.com/fwlink/?linkid=2169931[/url]
Warning    5/28/2024 7:59:36 PM    BTHUSB    3    None    A command sent to the adapter has timed out. The adapter did not respond.
Warning    5/28/2024 7:59:35 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{7022A3B3-D004-4F52-AF11-E9E987FEE25F}
 and APPID
{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}
 to the user win\bebag SID (S-1-5-21-1969507849-2187711627-3854667153-1001) 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."
Warning    5/28/2024 7:59:35 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{7022A3B3-D004-4F52-AF11-E9E987FEE25F}
 and APPID
{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}
 to the user win\bebag SID (S-1-5-21-1969507849-2187711627-3854667153-1001) 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."
Warning    5/28/2024 7:59:35 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{7022A3B3-D004-4F52-AF11-E9E987FEE25F}
 and APPID
{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}
 to the user win\bebag SID (S-1-5-21-1969507849-2187711627-3854667153-1001) 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."
Warning    5/28/2024 7:59:35 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{7022A3B3-D004-4F52-AF11-E9E987FEE25F}
 and APPID
{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}
 to the user win\bebag SID (S-1-5-21-1969507849-2187711627-3854667153-1001) 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."
Warning    5/28/2024 7:59:35 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{7022A3B3-D004-4F52-AF11-E9E987FEE25F}
 and APPID
{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}
 to the user win\bebag SID (S-1-5-21-1969507849-2187711627-3854667153-1001) 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."
Warning    5/28/2024 7:59:35 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{7022A3B3-D004-4F52-AF11-E9E987FEE25F}
 and APPID
{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}
 to the user win\bebag SID (S-1-5-21-1969507849-2187711627-3854667153-1001) 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."
Warning    5/28/2024 7:59:34 PM    Microsoft-Windows-DistributedCOM    10016    None    "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{21B896BF-008D-4D01-A27B-26061B960DD7}
 and APPID
{03E09F3B-DCE4-44FE-A9CF-82D050827E1C}
 to the user win\bebag SID (S-1-5-21-1969507849-2187711627-3854667153-1001) 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."
Warning    5/28/2024 7:59:33 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: msv1_0"
Warning    5/28/2024 7:59:33 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: sfapm"
Warning    5/28/2024 7:59:33 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: schannel"
Warning    5/28/2024 7:59:33 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: wdigest"
Warning    5/28/2024 7:59:33 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: cloudap"
Warning    5/28/2024 7:59:33 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: pku2u"
Warning    5/28/2024 7:59:33 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: tspkg"
Warning    5/28/2024 7:59:33 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: msv1_0"
Warning    5/28/2024 7:59:33 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: kerberos"
Warning    5/28/2024 7:59:33 PM    LsaSrv    6155    None    "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: negoexts"
Critical    5/28/2024 7:59:29 PM    Microsoft-Windows-Kernel-Power    41    (63)    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Error    5/28/2024 7:59:27 PM    stornvme    11    None    The driver detected a controller error on \Device\RaidPort1.
Error    5/28/2024 7:59:34 PM    EventLog    6008    None    The previous system shutdown at 8:06:02 PM on ‎5/‎27/‎2024 was unexpected.
Error    5/28/2024 7:59:26 PM    Microsoft-Windows-Kernel-Boot    29    None    Windows failed fast startup with error status 0xC00000D4.

Setup.log (This one is strange for me and I think it was made somewhere in the middle of reboot and now everything is fine, but not sure):
Code:
Level    Date and Time    Source    Event ID    Task Category
Warning    5/28/2024 8:17:37 PM    Microsoft-Windows-Servicing    1015    None    2 of 8 instances of system store corruption have been repaired. Unrepaired corruptions may lead to failures in future system servicing.
Warning    5/28/2024 8:09:48 PM    Microsoft-Windows-Servicing    1015    None    0 of 8 instances of system store corruption have been repaired. Unrepaired corruptions may lead to failures in future system servicing.

Application.log:
Code:
Level    Date and Time    Source    Event ID    Task Category
Error    5/28/2024 9:35:25 PM    Application Error    1000    Application Crashing Events    "Faulting application name: cpudump.exe, version: 1.0.0.1, time stamp: 0x57cd3da5
Faulting module name: MFCCPU.dll, version: 24.1.5.2, time stamp: 0x6597cd4f
Exception code: 0xc0000005
Fault offset: 0x00004200
Faulting process id: 0x0x37A8
Faulting application start time: 0x0x1DAB13E919B5A2A
Faulting application path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\cpudump.exe
Faulting module path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\MFCCPU.dll
Report Id: cce0c4d0-8183-4bb2-bf8d-4c21eebe3fa1
Faulting package full name:
Faulting package-relative application ID: "
Error    5/28/2024 9:30:20 PM    amd3dvcacheSvc    1    None    "The description for Event ID 1 from source amd3dvcacheSvc cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

amd3dvcacheSvc
CreateHelperUserProcess - WTSQueryUserToken Failed failed with 1008

The message resource is present but the message was not found in the message table
"
Error    5/28/2024 8:05:14 PM    Application Error    1000    Application Crashing Events    "Faulting application name: cpudump.exe, version: 1.0.0.1, time stamp: 0x57cd3da5
Faulting module name: MFCCPU.dll, version: 24.1.5.2, time stamp: 0x6597cd4f
Exception code: 0xc0000005
Fault offset: 0x00004200
Faulting process id: 0x0x2994
Faulting application start time: 0x0x1DAB131F8E384EF
Faulting application path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\cpudump.exe
Faulting module path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\MFCCPU.dll
Report Id: 708ca110-7747-4d68-84f2-96b70371c6c5
Faulting package full name:
Faulting package-relative application ID: "
Error    5/28/2024 7:59:52 PM    Application Error    1000    Application Crashing Events    "Faulting application name: cpudump.exe, version: 1.0.0.1, time stamp: 0x57cd3da5
Faulting module name: MFCCPU.dll, version: 24.1.5.2, time stamp: 0x6597cd4f
Exception code: 0xc0000005
Fault offset: 0x00004200
Faulting process id: 0x0x2698
Faulting application start time: 0x0x1DAB131387D58E7
Faulting application path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\cpudump.exe
Faulting module path: C:\Program Files (x86)\Gigabyte\EasyTuneEngineService\MFCCPU.dll
Report Id: 83e965e1-7d3a-4747-8710-df442c312ebb
Faulting package full name:
Faulting package-relative application ID: "




I know that is a lot of text, so to help myself and others to help me, I used ChatGPT4o to analyze them. Here is the output of GPT:
Here are the main problems identified from your logs, summarized without duplication:

1. **Audit Events Dropped**:
- Error: Audit events have been dropped by the transport.

2. **System Store Corruption**:
- Warning: Multiple instances of system store corruption have been detected and not all have been repaired, which may lead to future system failures.

3. **Application Crashing (cpudump.exe)**:
- Error: The cpudump.exe application has crashed multiple times due to a fault in the MFCCPU.dll module.

4. **amd3dvcacheSvc Service Issue**:
- Error: amd3dvcacheSvc service failed with WTSQueryUserToken error.

5. **DistributedCOM Permission Issues**:
- Warning: Multiple COM Server applications are lacking appropriate Local Activation and Launch permissions.

6. **Bluetooth Adapter Failures**:
- Error: The local Bluetooth adapter has failed and the driver has been unloaded.

7. **Secure Boot Update Failure**:
- Error: Secure Boot update failed due to Secure Boot not being enabled on the machine.

8. **Credential Guard Issues**:
- Warning: LSA packages are not signed as expected, potentially causing unexpected behavior with Credential Guard.

9. **Unexpected System Reboots**:
- Critical: The system has experienced unexpected reboots without clean shutdowns.

10. **Driver Errors (stornvme and RaidPort1)**:
- Error: The driver detected a controller error on \Device\RaidPort1.

11. **Service Termination (nordsec-threatprotection-service)**:
- Error: The nordsec-threatprotection-service service terminated unexpectedly.

12. **NetBT Initialization Failure**:
- Error: Initialization failed for a NetBT driver device due to MAC address or GUID mapping issues.

13. **Kernel Boot Error**:
- Error: Windows failed fast startup with error status 0xC00000D4.

These issues need to be addressed to ensure system stability and security.

I will try to solve them, and kindly asking the Community of this forum to help me with advices.
 
Last edited:
Look in Reliability History/Monitor for any current error codes, warnings, and informational events.

Clear all of the Event Viewer logs and check every so often for new errors.

Basis being that there will always be errors but Windows will handle most of them without issues.

The objective being to find graphics related errors or other errors that disrupt system performance and/or operation.
 
Look in Reliability History/Monitor for any current error codes, warnings, and informational events.

Clear all of the Event Viewer logs and check every so often for new errors.

Basis being that there will always be errors but Windows will handle most of them without issues.

The objective being to find graphics related errors or other errors that disrupt system performance and/or operation.
Ok. Then i am closing the question. Thanks for help ! <3
 
Status
Not open for further replies.