Hỏi / Đáp Vấn đề về đồ họa sau khi di chuyển PC?

[stNIKOLAS]

Xin chào mọi người,
Tôi mới chuyển đến nhà mới và gặp phải một số vấn đề liên quan đến đồ họa với PC của mình, tôi hy vọng sẽ nhận được sự trợ giúp. Tôi nghi ngờ rằng đây là hỏng GPU, nhưng tôi thực sự hy vọng là không... Tôi đã cố gắng thực sự nhẹ nhàng với PC của mình.

Sau đây là các vấn đề mà tôi nhận thấy cho đến nay:


1. Độ trễ của trò chơi: Một trong những trò chơi của tôi, vốn chạy mượt mà, giờ đây lại bị trễ đáng kể. Điều kỳ lạ là tôi đã thử nghiệm hai trò chơi: Hell Divers 2 (một trò chơi thực sự chuyên sâu) và Noita (một trò chơi 2D pixel nhẹ). Chỉ có "Noita" cho tôi thấy chuyển động chậm.
2. Kết xuất văn bản trên trình duyệt web: Văn bản trong trình duyệt web của tôi được hiển thị không chính xác hoặc một số chữ cái không được hiển thị. Có thể không chỉ trong Trình duyệt, nhưng tôi chưa nhận thấy điều đó ở những nơi khác. Sau đây là một số ví dụ: liên kết đến imgure có màn hình mà tôi đã chụp khi cố gắng viết bài đăng này
3. Màn hình đen OBS: OBS hiển thị màn hình đen khi cố gắng thu tín hiệu từ màn hình của tôi, mặc dù tất cả các cài đặt đều chính xác. (ít nhất là nó đã hoạt động trong nhiều lần trước đây)
Thiết lập của tôi:

• CPU:

• Bộ xử lý AMD Ryzen 7 7800X3D 4,2 GHz 8 nhân
• Bo mạch chủ: Bo mạch chủ Gigabyte B650M AORUS ELITE AX Micro ATX AM5
• Bộ nhớ: Bộ nhớ G.Skill Trident Z5 Neo RGB 32 GB (2 x 16 GB) DDR5-6000 CL30
• GPU: Card màn hình MSI SUPRIM LIQUID X GeForce RTX 4090 24 GB
• Hệ điều hành: Windows 11 Trang chủ 23H2, bản dựng 22631.3593

Những gì tôi đã thử cho đến nay:

1. Trình điều khiển GPU được cập nhật: Tải xuống và cài đặt trình điều khiển mới nhất từ ứng dụng Geforce Experience

2. Kiểm tra kết nối vật lý: Tôi đảm bảo GPU được lắp đúng cách và tất cả các dây cáp được kết nối an toàn.

3. Cập nhật hệ thống: Đảm bảo hệ điều hành được cập nhật.


Sau đây là nhật ký từ Even Viewer mà tôi thấy có thể hữu ích:

System LOG.txt:

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.

Nhật ký Security.txt:

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

Nhật ký Application.txt:

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: "

Có ai gặp phải vấn đề tương tự không hoặc có gợi ý nào về những gì khác tôi có thể thử để khắc phục những vấn đề này không? Tôi thực sự cần sự giúp đỡ của ai đó.






Cảm ơn trước vì sự giúp đỡ của bạn!


ps: thật sự rất buồn khi viết bài đăng này và xem máy tính của bạn chết như thế nào..

 

[Ralston18]

Có thể tệp bị hỏng hoặc lỗi....

Thử chạy "dism" và "sfc /scannow".

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/cach-sach-scan-sua-windows-2626161

 

[stNIKOLAS]

Có thể tệp bị hỏng hoặc lỗi....

Thử chạy "dism" và "sfc /scannow".

https://www.windowscentral.com/cách-sử-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161Cảm ơn vì lời khuyên tuyệt vời. Đây là những gì tôi đã làm cho đến nay:

1. Theo lời khuyên trên một diễn đàn khác, tôi đã kiểm tra tất cả các kết nối trong PC của mình và cài đặt lại GPU.
2. Sau đó, tôi thực hiện một số lệnh như @Ralston18 gợi ý

Đây là lịch sử cmd của tôi:

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>

Sau khi hệ thống khởi động lại, tôi đã kiểm tra CBS.log đã lọc nhưng không tìm thấy bất kỳ thông tin thú vị nào ở đó.

Tóm tắt về ChatGPT đã giúp tôi trong quá trình này:

1. DISM /Online /Cleanup-Image /CheckHealth

1. : Đã xác minh rằng không có lỗi hỏng kho lưu trữ thành phần ngay lập tức.
2. DISM /Online /Cleanup-Image /ScanHealth: Đã tìm thấy kho lưu trữ thành phần có thể sửa chữa được.
3. DISM /Online /Cleanup-Image /RestoreHealth: Đã sửa chữa thành công kho lưu trữ thành phần.
4. sfc /scannow (Lần chạy đầu tiên): Đã tìm thấy và sửa chữa thành công các tệp bị hỏng.
5. Trích xuất chi tiết SFC: Đã tạo tệp nhật ký có thông tin chi tiết về các lần sửa chữa SFC.
6. sfc /scannow (Lần chạy thứ hai): Không tìm thấy bất kỳ vi phạm tính toàn vẹn nào, cho thấy các sự cố trước đó đã được giải quyết thành công.

Tôi cũng đã thực hiện chẩn đoán bộ nhớ với sự trợ giúp của hướng dẫn này:

Cách chạy Chẩn đoán bộ nhớ trên Windows 10 & 11​

Nếu hệ thống của bạn bị sập, chạy chậm hoặc là một phần của quá trình bảo trì thường xuyên, việc chạy chẩn đoán bộ nhớ để tìm ra sự cố sẽ hữu ích.

windowsloop.comrun-memory-diagnostics-windows


Tôi vui mừng thông báo rằng các vấn đề chính của tôi đã được giải quyết bằng các bước này
(thậm chí có thể ở đâu đó ở giữa, nhưng tôi vẫn chắc chắn)

Tuy nhiên, vẫn có một số cảnh báo và lỗi. Và tôi muốn sửa chúng trước khi đóng Câu hỏi này.

Bộ lọc nhật ký trong 12 giờ qua chỉ bao gồm các mục Quan trọng, Cảnh báo và Lỗi:

Security.log:

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

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 (Tôi thấy lạ vì tệp này được tạo ra ở đâu đó giữa quá trình khởi động lại và bây giờ mọi thứ đều ổn, nhưng không chắc chắn):

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:

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: "

Tôi biết rằng đó là rất nhiều văn bản, vì vậy để giúp bản thân và những người khác giúp tôi, tôi đã sử dụng ChatGPT4o để phân tích chúng. Đây là đầu ra của GPT:

Sau đây là những vấn đề chính được xác định từ nhật ký của bạn, được tóm tắt mà không trùng lặp:

1. **Sự kiện kiểm toán đã bị loại bỏ**:
- Lỗi: Sự kiện kiểm toán đã bị loại bỏ bởi quá trình vận chuyển.

2. **Hỏng kho lưu trữ hệ thống**:
- Cảnh báo: Nhiều trường hợp hỏng kho lưu trữ hệ thống đã được phát hiện và không phải tất cả đều được sửa chữa, điều này có thể dẫn đến lỗi hệ thống trong tương lai.

3. **Ứng dụng bị sập (cpudump.exe)**:
- Lỗi: Ứng dụng cpudump.exe đã bị sập nhiều lần do lỗi trong mô-đun MFCCPU.dll.

4. **Sự cố dịch vụ amd3dvcacheSvc**:
- Lỗi: dịch vụ amd3dvcacheSvc không thành công với lỗi WTSQueryUserToken.

5. **Sự cố quyền COM phân tán**:
- Cảnh báo: Nhiều ứng dụng Máy chủ COM không có quyền Kích hoạt cục bộ và Khởi chạy phù hợp.

6. **Lỗi bộ điều hợp Bluetooth**:
- Lỗi: Bộ điều hợp Bluetooth cục bộ đã thành công và trình điều khiển đã bị hủy tải.

7. **Lỗi cập nhật khởi động an toàn**:
- Lỗi: Cập nhật khởi động an toàn không thành công do Khởi động an toàn không được bật trên máy.

8. **Sự cố bảo vệ thông tin xác thực**:
- Cảnh báo: Các gói LSA không được ký như mong đợi, có khả năng gây ra hành vi không mong muốn với Credential Guard.

9. **Khởi động lại hệ thống bất ngờ**:
- Nghiêm trọng: Hệ thống đã gặp phải tình trạng khởi động lại bất ngờ mà không tắt máy sạch.

10. **Lỗi trình điều khiển (stornvme và RaidPort1)**:
- Lỗi: Trình điều khiển phát hiện lỗi bộ điều khiển trên \Device\RaidPort1.

11. **Chấm dứt dịch vụ (nordsec-threatprotection-service)**:
- Lỗi: Dịch vụ nordsec-threatprotection-service chấm dứt đột ngột.

12. **Lỗi khởi tạo NetBT**:
- Lỗi: Khởi tạo không thành công cho thiết bị trình điều khiển NetBT do sự cố ánh xạ địa chỉ MAC hoặc GUID.

13. **Lỗi khởi động hạt nhân**:
- Lỗi: Windows không khởi động nhanh được với trạng thái lỗi 0xC00000D4.

Những sự cố này cần được giải quyết để đảm bảo tính ổn định và bảo mật của hệ thống.

Tôi sẽ cố gắng giải quyết chúng và vui lòng yêu cầu Cộng đồng của diễn đàn này giúp tôi bằng lời khuyên.

 

[Ralston18]

Xem trong Lịch sử/Giám sát độ tin cậy để biết bất kỳ mã lỗi, cảnh báo và sự kiện thông tin hiện tại nào.

Xóa tất cả nhật ký của Trình xem sự kiện và kiểm tra thường xuyên để tìm lỗi mới.

Cơ sở là sẽ luôn có lỗi nhưng Windows sẽ xử lý hầu hết các lỗi đó mà không có vấn đề gì.

Mục tiêu là tìm lỗi liên quan đến đồ họa hoặc các lỗi khác làm gián đoạn hiệu suất và/hoặc hoạt động của hệ thống.

 

[stNIKOLAS]

Xem trong Lịch sử/Màn hình Độ tin cậy để biết bất kỳ mã lỗi, cảnh báo và sự kiện thông tin hiện tại nào.

Xóa tất cả nhật ký Trình xem sự kiện và kiểm tra thường xuyên để tìm lỗi mới.

Cơ sở là sẽ luôn có lỗi nhưng Windows sẽ xử lý hầu hết các lỗi mà không có vấn đề gì.

Mục tiêu là tìm lỗi liên quan đến đồ họa hoặc các lỗi khác làm gián đoạn hiệu suất và/hoặc hoạt động của hệ thống.

Được rồi. Vậy thì tôi sẽ đóng câu hỏi. Cảm ơn vì đã giúp đỡ! <3