• Happy holidays, folks! Thanks to each and every one of you for being part of the Tom's Hardware community!

Question PC freeze to PC reboot to bad errors? Please help

Toggle sidebar Toggle sidebar
W

wizard100

Nov 16, 2024
2
1
15
CPU - AMD Ryzen 5700x
GPU - EVGA 3090 ftw3
Motherboard - ROG Crosshair VIII Dark Hero X570
SSD - Samsung 980 Pro (pc stopped detecting, replaced with WD Black SN850X)
DDR4 RAM - G.Skill Trident Z neo 32gb 2x16 @ 3600mhz
PSU - EVGA Supernova 1600 G+ 1600w

Hey all. I built this PC around release of 3090. No issues or replacements until now. Drivers/windows updated, temps normal, cleaned, BIOS may of fell behind on updates until now. Initial issue was random frozen display. It was once every couple of days. Increased to daily, then only BIOS boot, then before BIOS boot. Full breakdown, inspection and reseat of entire PC, rewire all PSU cables. Deep clean. Tested all RAM, also used known good RAM (a1 only). Removed CMOS bat, reset CMOS Boot to BIOS. Updated BIOS with flash. SSD would fail tests or fail to be recognized was only item out of place on BIOS at this point. Replaced w/ new (unsure if old is actually bad). Able to install windows after 2-5 random freezes w/ new SSD installed. Updated all drivers, w/ random freezes during. Freezes went from frozen display to crash reboot to BIOS. Now, I can log, use PC as normal for 2-5 minutes, then crashes to reboot BIOS, rinse repeat couple of times for error log. I have no idea how to read them. I picked up on some scary bad words please help me.

Thanks!


Code: 
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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NetBT" />
    <EventID Qualifiers="49152">4311</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-16T04:41:13.0624341Z" />
    <EventRecordID>1558</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="312" />
    <Channel>System</Channel>
    <Computer>DESKTOP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Binary>000000000100320000000000D71000C011010000250200C001000000000000000000000000000000</Binary>
  </EventData>
</Event>





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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NetBT" />
    <EventID Qualifiers="49152">4311</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-16T04:41:13.0624341Z" />
    <EventRecordID>1558</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="312" />
    <Channel>System</Channel>
    <Computer>DESKTOP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Binary>000000000100320000000000D71000C011010000250200C001000000000000000000000000000000</Binary>
  </EventData>
</Event>





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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NetBT" />
    <EventID Qualifiers="49152">4311</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-16T04:43:18.2634864Z" />
    <EventRecordID>1648</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8520" />
    <Channel>System</Channel>
    <Computer>DESKTOP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Binary>000000000100320000000000D71000C011010000250200C001000000000000000000000000000000</Binary>
  </EventData>
</Event>





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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NetBT" />
    <EventID Qualifiers="49152">4311</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-16T04:43:18.2634864Z" />
    <EventRecordID>1648</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8520" />
    <Channel>System</Channel>
    <Computer>DESKTOP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Binary>000000000100320000000000D71000C011010000250200C001000000000000000000000000000000</Binary>
  </EventData>
</Event>





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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NetBT" />
    <EventID Qualifiers="49152">4311</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-16T04:43:18.2634864Z" />
    <EventRecordID>1647</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8572" />
    <Channel>System</Channel>
    <Computer>DESKTOP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Binary>000000000100320000000000D71000C013010000250200C000000000000000000000000000000000</Binary>
  </EventData>
</Event>





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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NetBT" />
    <EventID Qualifiers="49152">4311</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-16T04:43:18.2634864Z" />
    <EventRecordID>1647</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8572" />
    <Channel>System</Channel>
    <Computer>DESKTOP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Binary>000000000100320000000000D71000C013010000250200C000000000000000000000000000000000</Binary>
  </EventData>
</Event>





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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" />
    <EventID>18</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-16T04:43:10.0173254Z" />
    <EventRecordID>1637</EventRecordID>
    <Correlation ActivityID="{6b85e57d-028f-48be-9f89-1606f71813fd}" />
    <Execution ProcessID="4076" ThreadID="5592" />
    <Channel>System</Channel>
    <Computer>DESKTOP</Computer>
    <Security  />
  </System>
  <EventData>
    <Data Name="ErrorSource">3</Data>
    <Data Name="ApicId">22</Data>
    <Data Name="MCABank">5</Data>
    <Data Name="MciStat">0xbea0000000000108</Data>
    <Data Name="MciAddr">0x1fff80347c2a330</Data>
    <Data Name="MciMisc">0xd01a0ffe00000000</Data>
    <Data Name="ErrorType">9</Data>
    <Data Name="TransactionType">2</Data>
    <Data Name="Participation">256</Data>
    <Data Name="RequestType">0</Data>
    <Data Name="MemorIO">256</Data>
    <Data Name="MemHierarchyLvl">0</Data>
    <Data Name="Timeout">256</Data>
    <Data Name="OperationType">256</Data>
    <Data Name="Channel">256</Data>
    <Data Name="Length">936</Data>
    <Data Name="RawData">435045521002FFFFFFFF03000100000002000000A8030000032B0400100B18140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBA5FCB404E237DB0102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002010000000000100FA2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001600000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000001600000000000000100FA200000818160B32F87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F0002060000000030A3C24703F8FF01000000000000000000000000000000000000000000000000020000000200000036FC9905E237DB01120000000000000000000000000000000000000005000000080100000000A0BE30A3C24703F8FF0100000000FE0F1AD0000000001600000000000000B00005000000004D00000000F9010000230000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
  </EventData>
</Event>





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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" />
    <EventID>18</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-16T04:43:10.0173254Z" />
    <EventRecordID>1637</EventRecordID>
    <Correlation ActivityID="{6b85e57d-028f-48be-9f89-1606f71813fd}" />
    <Execution ProcessID="4076" ThreadID="5592" />
    <Channel>System</Channel>
    <Computer>DESKTOP</Computer>
    <Security  />
  </System>
  <EventData>
    <Data Name="ErrorSource">3</Data>
    <Data Name="ApicId">22</Data>
    <Data Name="MCABank">5</Data>
    <Data Name="MciStat">0xbea0000000000108</Data>
    <Data Name="MciAddr">0x1fff80347c2a330</Data>
    <Data Name="MciMisc">0xd01a0ffe00000000</Data>
    <Data Name="ErrorType">9</Data>
    <Data Name="TransactionType">2</Data>
    <Data Name="Participation">256</Data>
    <Data Name="RequestType">0</Data>
    <Data Name="MemorIO">256</Data>
    <Data Name="MemHierarchyLvl">0</Data>
    <Data Name="Timeout">256</Data>
    <Data Name="OperationType">256</Data>
    <Data Name="Channel">256</Data>
    <Data Name="Length">936</Data>
    <Data Name="RawData">435045521002FFFFFFFF03000100000002000000A8030000032B0400100B18140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBA5FCB404E237DB0102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002010000000000100FA2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001600000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000001600000000000000100FA200000818160B32F87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F0002060000000030A3C24703F8FF01000000000000000000000000000000000000000000000000020000000200000036FC9905E237DB01120000000000000000000000000000000000000005000000080100000000A0BE30A3C24703F8FF0100000000FE0F1AD0000000001600000000000000B00005000000004D00000000F9010000230000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
  </EventData>
</Event>





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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NetBT" />
    <EventID Qualifiers="49152">4311</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-16T04:41:13.0624341Z" />
    <EventRecordID>1558</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="312" />
    <Channel>System</Channel>
    <Computer>DESKTOP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Binary>000000000100320000000000D71000C011010000250200C001000000000000000000000000000000</Binary>
  </EventData>
</Event>





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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NetBT" />
    <EventID Qualifiers="49152">4311</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-16T04:41:13.0624341Z" />
    <EventRecordID>1558</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="312" />
    <Channel>System</Channel>
    <Computer>DESKTOP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Binary>000000000100320000000000D71000C011010000250200C001000000000000000000000000000000</Binary>
  </EventData>
</Event>





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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NetBT" />
    <EventID Qualifiers="49152">4311</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-16T04:46:44.3988864Z" />
    <EventRecordID>1739</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="680" />
    <Channel>System</Channel>
    <Computer>DESKTOP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Binary>000000000100320000000000D71000C011010000250200C001000000000000000000000000000000</Binary>
  </EventData>
</Event>   





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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NetBT" />
    <EventID Qualifiers="49152">4311</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-16T04:46:44.3988864Z" />
    <EventRecordID>1739</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="680" />
    <Channel>System</Channel>
    <Computer>DESKTOP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Binary>000000000100320000000000D71000C011010000250200C001000000000000000000000000000000</Binary>
  </EventData>
</Event>   





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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NetBT" />
    <EventID Qualifiers="49152">4311</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-16T04:46:44.3988864Z" />
    <EventRecordID>1738</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="680" />
    <Channel>System</Channel>
    <Computer>DESKTOP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Binary>000000000100320000000000D71000C013010000250200C000000000000000000000000000000000</Binary>
  </EventData>
</Event>   





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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NetBT" />
    <EventID Qualifiers="49152">4311</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-16T04:46:44.3988864Z" />
    <EventRecordID>1738</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="680" />
    <Channel>System</Channel>
    <Computer>DESKTOP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Binary>000000000100320000000000D71000C013010000250200C000000000000000000000000000000000</Binary>
  </EventData>
</Event>





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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" />
    <EventID>18</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-16T04:46:36.0962118Z" />
    <EventRecordID>1730</EventRecordID>
    <Correlation ActivityID="{dcdc780b-f563-4f6c-bbd8-d81160b8c836}" />
    <Execution ProcessID="5048" ThreadID="5544" />
    <Channel>System</Channel>
    <Computer>DESKTOP</Computer>
    <Security  />
  </System>
  <EventData>
    <Data Name="ErrorSource">3</Data>
    <Data Name="ApicId">0</Data>
    <Data Name="MCABank">27</Data>
    <Data Name="MciStat">0xbaa000000000080b</Data>
    <Data Name="MciAddr">0x0</Data>
    <Data Name="MciMisc">0xd01a0ffe00000000</Data>
    <Data Name="ErrorType">10</Data>
    <Data Name="TransactionType">256</Data>
    <Data Name="Participation">0</Data>
    <Data Name="RequestType">0</Data>
    <Data Name="MemorIO">2</Data>
    <Data Name="MemHierarchyLvl">3</Data>
    <Data Name="Timeout">0</Data>
    <Data Name="OperationType">256</Data>
    <Data Name="Channel">256</Data>
    <Data Name="Length">936</Data>
    <Data Name="RawData">435045521002FFFFFFFF03000100000002000000A80300001D2E0400100B18140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BB1A91937FE237DB0102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002040000030000100FA2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000000000000000000100FA200000818000B32F87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000B3F8F31CB1C5A249AA595EEF92FFA63C01000000000000009E07C0060400000000000000000000000000000000000000000000000000000000000000000000000200000002000000C9D67A80E237DB0100000000000000000000000000000000000000001B0000000B0800000000A0BA000000000000000000000000FE0F1AD00000000000000000000500002E0001000000005D000000007D000000270000000000000000000000000000000000000000000000000010000000000000001000000000000000100000000000000010003B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
  </EventData>
</Event>





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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" />
    <EventID>18</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-16T04:46:36.0962118Z" />
    <EventRecordID>1730</EventRecordID>
    <Correlation ActivityID="{dcdc780b-f563-4f6c-bbd8-d81160b8c836}" />
    <Execution ProcessID="5048" ThreadID="5544" />
    <Channel>System</Channel>
    <Computer>DESKTOP</Computer>
    <Security  />
  </System>
  <EventData>
    <Data Name="ErrorSource">3</Data>
    <Data Name="ApicId">0</Data>
    <Data Name="MCABank">27</Data>
    <Data Name="MciStat">0xbaa000000000080b</Data>
    <Data Name="MciAddr">0x0</Data>
    <Data Name="MciMisc">0xd01a0ffe00000000</Data>
    <Data Name="ErrorType">10</Data>
    <Data Name="TransactionType">256</Data>
    <Data Name="Participation">0</Data>
    <Data Name="RequestType">0</Data>
    <Data Name="MemorIO">2</Data>
    <Data Name="MemHierarchyLvl">3</Data>
    <Data Name="Timeout">0</Data>
    <Data Name="OperationType">256</Data>
    <Data Name="Channel">256</Data>
    <Data Name="Length">936</Data>
    <Data Name="RawData">435045521002FFFFFFFF03000100000002000000A80300001D2E0400100B18140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BB1A91937FE237DB0102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002040000030000100FA2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000000000000000000100FA200000818000B32F87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000B3F8F31CB1C5A249AA595EEF92FFA63C01000000000000009E07C0060400000000000000000000000000000000000000000000000000000000000000000000000200000002000000C9D67A80E237DB0100000000000000000000000000000000000000001B0000000B0800000000A0BA000000000000000000000000FE0F1AD00000000000000000000500002E0001000000005D000000007D000000270000000000000000000000000000000000000000000000000010000000000000001000000000000000100000000000000010003B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
  </EventData>
</Event>
 
Sounds like a nightmare from Hell itself. When the computer was running did you install the AMD Chipset drivers for your motherboard or are you using the Windows drivers? Also, are you using Windows 10 or Windows 11? From what I looked up on this issue the Windows drivers can cause problems for the motherboard. There are Professionals here who can help resolve the issues you are having now. All the best.
 
digitaldata77 said:
Sounds like a nightmare from Hell itself. When the computer was running did you install the AMD Chipset drivers for your motherboard or are you using the Windows drivers? Also, are you using Windows 10 or Windows 11? From what I looked up on this issue the Windows drivers can cause problems for the motherboard. There are Professionals here who can help resolve the issues you are having now. All the best.
Click to expand...
Windows 10 and interesting find on those drivers. I will definitely try the chipset drivers from AMD. Thank you for the help and I’ll let you know if I’m successful.
 
  • Like
Reactions: digitaldata77
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom