Hỏi / Đáp PC bị đơ đến khi khởi động lại thì lỗi là sao? Xin hãy giúp đỡ

[wizard100]

CPU - AMD Ryzen 5700x
GPU - EVGA 3090 ftw3
Bo mạch chủ - ROG Crosshair VIII Dark Hero X570
SSD - Samsung 980 Pro (máy tính ngừng phát hiện, thay thế bằng WD Black SN850X)
RAM DDR4 - G.Skill Trident Z neo 32gb 2x16 @ 3600mhz
PSU - EVGA Supernova 1600 G+ 1600w

Xin chào tất cả. Tôi đã xây dựng chiếc PC này vào khoảng thời gian phát hành 3090. Không có vấn đề gì hoặc phải thay thế cho đến bây giờ. Trình điều khiển/cửa sổ đã được cập nhật, nhiệt độ bình thường, đã được dọn dẹp, BIOS có thể đã bị chậm cập nhật cho đến bây giờ. Sự cố ban đầu là màn hình bị treo ngẫu nhiên. Nó xảy ra sau mỗi vài ngày. Tăng lên hàng ngày, sau đó chỉ khởi động BIOS, sau đó là trước khi BIOS khởi động. Phân tích toàn bộ, kiểm tra và lắp lại toàn bộ PC, nối lại tất cả các dây cáp PSU. Vệ sinh sâu. Đã kiểm tra tất cả RAM, cũng sử dụng RAM tốt đã biết (chỉ a1). Đã tháo CMOS bat, đặt lại CMOS Boot thành BIOS. Đã cập nhật BIOS với flash. SSD không vượt qua được các bài kiểm tra hoặc không được nhận dạng là mục duy nhất không đúng vị trí trên BIOS tại thời điểm này. Đã thay thế bằng cái mới (không chắc chắn liệu cái cũ có thực sự bị hỏng không). Có thể cài đặt Windows sau 2-5 lần đóng băng ngẫu nhiên khi cài đặt SSD mới. Đã cập nhật tất cả các trình điều khiển, với các lần đóng băng ngẫu nhiên trong quá trình. Đóng băng đã chuyển từ màn hình bị đóng băng sang khởi động lại sự cố vào BIOS. Bây giờ, tôi có thể đăng nhập, sử dụng PC bình thường trong 2-5 phút, sau đó bị sập để khởi động lại BIOS, lặp lại vài lần để biết nhật ký lỗi. Tôi không biết cách đọc chúng. Tôi đã nhận ra một số từ tệ đáng sợ, vui lòng giúp tôi.

Cảm ơn!

Log Name: System
Source: NetBT
Date: 11/15/2024 8:41:13 PM
Event ID: 4311
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP
Description:
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.
Event Xml:
   4311 0 2 0 0 0x80000000000000  1558   System DESKTOP      000000000100320000000000D71000C011010000250200C001000000000000000000000000000000 

Log Name: System
Source: NetBT
Date: 11/15/2024 8:41:13 PM
Event ID: 4311
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP
Description:
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.
Event Xml:
   4311 0 2 0 0 0x80000000000000  1558   System DESKTOP      000000000100320000000000D71000C011010000250200C001000000000000000000000000000000 

Log Name: System
Source: NetBT
Date: 11/15/2024 8:43:18 PM
Event ID: 4311
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP
Description:
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.
Event Xml:
   4311 0 2 0 0 0x80000000000000  1648   System DESKTOP      000000000100320000000000D71000C011010000250200C001000000000000000000000000000000 

Log Name: System
Source: NetBT
Date: 11/15/2024 8:43:18 PM
Event ID: 4311
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP
Description:
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.
Event Xml:
   4311 0 2 0 0 0x80000000000000  1648   System DESKTOP      000000000100320000000000D71000C011010000250200C001000000000000000000000000000000 

Log Name: System
Source: NetBT
Date: 11/15/2024 8:43:18 PM
Event ID: 4311
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP
Description:
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.
Event Xml:
   4311 0 2 0 0 0x80000000000000  1647   System DESKTOP      000000000100320000000000D71000C013010000250200C000000000000000000000000000000000 

Log Name: System
Source: NetBT
Date: 11/15/2024 8:43:18 PM
Event ID: 4311
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP
Description:
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.
Event Xml:
   4311 0 2 0 0 0x80000000000000  1647   System DESKTOP      000000000100320000000000D71000C013010000250200C000000000000000000000000000000000 

Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 11/15/2024 8:43:10 PM
Event ID: 18
Task Category: None
Level: Error
Keywords:
User: LOCAL SERVICE
Computer: DESKTOP
Description:
A fatal hardware error has occurred.
Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 22
The details view of this entry contains further information.
Event Xml:
   18 0 2 0 0 0x8000000000000000  1637   System DESKTOP    3 22 5 0xbea0000000000108 0x1fff80347c2a330 0xd01a0ffe00000000 9 2 256 0 256 0 256 256 256 936 435045521002FFFFFFFF03000100000002000000A8030000032B0400100B18140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBA5FCB404E237DB0102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002010000000000100FA2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001600000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000001600000000000000100FA200000818160B32F87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F0002060000000030A3C24703F8FF01000000000000000000000000000000000000000000000000020000000200000036FC9905E237DB01120000000000000000000000000000000000000005000000080100000000A0BE30A3C24703F8FF0100000000FE0F1AD0000000001600000000000000B00005000000004D00000000F9010000230000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 

Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 11/15/2024 8:43:10 PM
Event ID: 18
Task Category: None
Level: Error
Keywords:
User: LOCAL SERVICE
Computer: DESKTOP
Description:
A fatal hardware error has occurred.
Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 22
The details view of this entry contains further information.
Event Xml:
   18 0 2 0 0 0x8000000000000000  1637   System DESKTOP    3 22 5 0xbea0000000000108 0x1fff80347c2a330 0xd01a0ffe00000000 9 2 256 0 256 0 256 256 256 936 435045521002FFFFFFFF03000100000002000000A8030000032B0400100B18140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBA5FCB404E237DB0102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002010000000000100FA2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001600000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000001600000000000000100FA200000818160B32F87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F0002060000000030A3C24703F8FF01000000000000000000000000000000000000000000000000020000000200000036FC9905E237DB01120000000000000000000000000000000000000005000000080100000000A0BE30A3C24703F8FF0100000000FE0F1AD0000000001600000000000000B00005000000004D00000000F9010000230000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 

Log Name: System
Source: NetBT
Date: 11/15/2024 8:41:13 PM
Event ID: 4311
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP
Description:
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.
Event Xml:
   4311 0 2 0 0 0x80000000000000  1558   System DESKTOP      000000000100320000000000D71000C011010000250200C001000000000000000000000000000000 

Log Name: System
Source: NetBT
Date: 11/15/2024 8:41:13 PM
Event ID: 4311
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP
Description:
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.
Event Xml:
   4311 0 2 0 0 0x80000000000000  1558   System DESKTOP      000000000100320000000000D71000C011010000250200C001000000000000000000000000000000 

Log Name: System
Source: NetBT
Date: 11/15/2024 8:46:44 PM
Event ID: 4311
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP
Description:
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.
Event Xml:
   4311 0 2 0 0 0x80000000000000  1739   System DESKTOP      000000000100320000000000D71000C011010000250200C001000000000000000000000000000000 

Log Name: System
Source: NetBT
Date: 11/15/2024 8:46:44 PM
Event ID: 4311
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP
Description:
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.
Event Xml:
   4311 0 2 0 0 0x80000000000000  1739   System DESKTOP      000000000100320000000000D71000C011010000250200C001000000000000000000000000000000 

Log Name: System
Source: NetBT
Date: 11/15/2024 8:46:44 PM
Event ID: 4311
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP
Description:
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.
Event Xml:
   4311 0 2 0 0 0x80000000000000  1738   System DESKTOP      000000000100320000000000D71000C013010000250200C000000000000000000000000000000000 

Log Name: System
Source: NetBT
Date: 11/15/2024 8:46:44 PM
Event ID: 4311
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP
Description:
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.
Event Xml:
   4311 0 2 0 0 0x80000000000000  1738   System DESKTOP      000000000100320000000000D71000C013010000250200C000000000000000000000000000000000 

Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 11/15/2024 8:46:36 PM
Event ID: 18
Task Category: None
Level: Error
Keywords:
User: LOCAL SERVICE
Computer: DESKTOP
Description:
A fatal hardware error has occurred.
Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Bus/Interconnect Error
Processor APIC ID: 0
The details view of this entry contains further information.
Event Xml:
   18 0 2 0 0 0x8000000000000000  1730   System DESKTOP    3 0 27 0xbaa000000000080b 0x0 0xd01a0ffe00000000 10 256 0 0 2 3 0 256 256 936 435045521002FFFFFFFF03000100000002000000A80300001D2E0400100B18140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BB1A91937FE237DB0102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002040000030000100FA2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000000000000000000100FA200000818000B32F87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000B3F8F31CB1C5A249AA595EEF92FFA63C01000000000000009E07C0060400000000000000000000000000000000000000000000000000000000000000000000000200000002000000C9D67A80E237DB0100000000000000000000000000000000000000001B0000000B0800000000A0BA000000000000000000000000FE0F1AD00000000000000000000500002E0001000000005D000000007D000000270000000000000000000000000000000000000000000000000010000000000000001000000000000000100000000000000010003B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 

Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 11/15/2024 8:46:36 PM
Event ID: 18
Task Category: None
Level: Error
Keywords:
User: LOCAL SERVICE
Computer: DESKTOP
Description:
A fatal hardware error has occurred.
Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Bus/Interconnect Error
Processor APIC ID: 0
The details view of this entry contains further information.
Event Xml:
   18 0 2 0 0 0x8000000000000000  1730   System DESKTOP    3 0 27 0xbaa000000000080b 0x0 0xd01a0ffe00000000 10 256 0 0 2 3 0 256 256 936 435045521002FFFFFFFF03000100000002000000A80300001D2E0400100B18140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BB1A91937FE237DB0102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002040000030000100FA2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000000000000000000100FA200000818000B32F87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000B3F8F31CB1C5A249AA595EEF92FFA63C01000000000000009E07C0060400000000000000000000000000000000000000000000000000000000000000000000000200000002000000C9D67A80E237DB0100000000000000000000000000000000000000001B0000000B0800000000A0BA000000000000000000000000FE0F1AD00000000000000000000500002E0001000000005D000000007D000000270000000000000000000000000000000000000000000000000010000000000000001000000000000000100000000000000010003B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

 

[digitaldata77]

Nghe như cơn ác mộng từ Địa ngục vậy. Khi máy tính đang chạy, bạn đã cài đặt trình điều khiển Chipset AMD cho bo mạch chủ của mình hay bạn đang sử dụng trình điều khiển Windows? Ngoài ra, bạn đang sử dụng Windows 10 hay Windows 11? Theo những gì tôi tìm hiểu về vấn đề này, trình điều khiển Windows có thể gây ra sự cố cho bo mạch chủ. Có những Chuyên gia ở đây có thể giúp giải quyết các sự cố mà bạn đang gặp phải. Chúc bạn mọi điều tốt lành.

 

[wizard100]

Nghe như cơn ác mộng từ Địa ngục. Khi máy tính đang chạy, bạn đã cài đặt trình điều khiển Chipset AMD cho bo mạch chủ của mình hay bạn đang sử dụng trình điều khiển Windows? Ngoài ra, bạn đang sử dụng Windows 10 hay Windows 11? Theo những gì tôi tìm hiểu về vấn đề này, trình điều khiển Windows có thể gây ra sự cố cho bo mạch chủ. Có những Chuyên gia ở đây có thể giúp giải quyết các sự cố mà bạn đang gặp phải. Chúc bạn mọi điều tốt lành.

Windows 10 và những phát hiện thú vị về các trình điều khiển đó. Tôi chắc chắn sẽ thử trình điều khiển chipset từ AMD. Cảm ơn sự giúp đỡ của bạn và tôi sẽ cho bạn biết nếu tôi thành công.