Win 10 Computer Keeps Freezing Blue Screen Stop Error NMI Hardware Failure

Question

My new Win 10 Machine keeps freezing at Random Times telling me I have a NMI Hardware Failure.

How can I tell what component is failing? Could it be a Fire Wire card?

I'm also getting a DCOM ERROR 10016 at the same time

Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 10/21/2021 3:05:24 PM
Event ID: 1
Task Category: None
Level: Error
Keywords: WHEA Error Event Logs
User: LOCAL SERVICE
Computer: DESKTOP-V575QN4
Description:
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.
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>1</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2021-10-21T22:05:24.7588186Z" />
<EventRecordID>9095</EventRecordID>
<Correlation ActivityID="{258705c1-55d2-46c5-a2cb-4d394e7e7ca0}" />
<Execution ProcessID="4548" ThreadID="5260" />
<Channel>System</Channel>
<Computer>DESKTOP-V575QN4</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="Length">476</Data>
<Data Name="RawData">435045521002FFFFFFFF02000100000002000000DC01000014041600150A15140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FF89AD5BE6B7C942814ACF2485D6E98A7CD7D51B95C6D70100000000000000000000000000000000000000000000000010010000C00000000003000000000000ADCC7698B447DB4BB65E16F193C4F3DB00000000000000000000000000000000030000000000000000000000000000000000000000000000D00100000C0000000003000001000000E75412E7B9C14049AB76909703A4320F000000000000000000000000000000000100000000000000000000000000000000000000000000004301000000000000000200000000000055060A000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C000000000000000000000000000000000000000000000000000000000000000000000000000000A80000000000000000000000</Data>
</EventData>
</Event>

Answer 1

Hello SongQuester,

The WHEA-Logger errors are in many different varieties: CPU caused, unstable RAM, some specific RAM modules can cause some issues with Ryzen processors, GPU drivers...

My recommendation is to check when you receive this error the next line:
<Execution ProcessID="xxxx" ThreadID="xxxx" />

This will give you the information about the process that is calling the hardware for a better understanding of what is causing the issue. Please not that Process and Thread IDs will change every time you reboot your machine, so you will need to check after you receive a new error, and without rebooting.

My recommendation would be also to ensure that your Windows has been updated to latest version (21H1) and other updates have been also installed, check also in the section for optional and driver updates. Last, check with your hardware manufacturer websites for updated BIOS, Chipset, CPU, GPU, etc...

---

--If the reply is helpful, please Upvote and Accept as answer--

Answer 2

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive:

https://www.windowsq.com/t/bsod-posting-instructions.17/
https://www.windowsq.com/resources/v2-log-collector.8/
https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.