WHEA error is it my GPU or CPU?

[Rstolpe]

Hi,
I have been getting ONE WHEA error and I'm pulling my hair regarding it.

My computer was almost idling I was talking in Skype for 1 hour and was in the other side of the room, When I then ended the call at the computer it did freeze for about 5 sec and then it start working agin - no BSOD or simuler.

Anyway I did see in HWiNFO64 that I did get a WHEA error.

This was the error:

 

Here is some more from the details:
 

Spoiler

Log Name:      System
Source:        Microsoft-Windows-WHEA-Logger
Date:          2020-09-22 14:51:39
Event ID:      19
Task Category: None
Level:         Warning
Keywords:     
User:          LOCAL SERVICE
Computer:      DESKTOP-96J2OR5
Description:
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Unknown Error Source
Error Type: Internal parity error
Processor APIC ID: 14

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>19</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2020-09-22T12:51:39.1820354Z" />
    <EventRecordID>5265</EventRecordID>
    <Correlation ActivityID="{e1870fab-ecab-41cd-9838-0e8c78ea0f03}" />
    <Execution ProcessID="4468" ThreadID="10436" />
    <Channel>System</Channel>
    <Computer>DESKTOP-96J2OR5</Computer>
    <Security UserID="S-1-5-19" />
  </System>
  <EventData>
    <Data Name="ErrorSource">0</Data>
    <Data Name="ApicId">14</Data>
    <Data Name="MCABank">0</Data>
    <Data Name="MciStat">0x9000004000010005</Data>
    <Data Name="MciAddr">0x0</Data>
    <Data Name="MciMisc">0x0</Data>
    <Data Name="ErrorType">12</Data>
    <Data Name="TransactionType">256</Data>
    <Data Name="Participation">256</Data>
    <Data Name="RequestType">256</Data>
    <Data Name="MemorIO">256</Data>
    <Data Name="MemHierarchyLvl">256</Data>
    <Data Name="Timeout">256</Data>
    <Data Name="OperationType">256</Data>
    <Data Name="Channel">256</Data>
    <Data Name="Length">872</Data>
    <Data Name="RawData">435045521002FFFFFFFF030002000000020000006803000026330C00160914140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B248949139377F4BA8F1E0062805C2A361BFE5EDB590D60100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000400000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000058020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000200000000000000000000000000000000000000000000005701000000000000000208000000000055060A000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000E00000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000E0000000000000055060A000008200EFFFBFA7FFFFBEBBF00000000000000000000000000000000000000000000000000000000000000000200000001000000A420581CDF90D6010E0000000000000000000000000000000000000000000000050001004000009000000000000000000000000000000000000000000E0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
  </EventData>
</Event>

 

As you can see it state CPU but also the Error Source is unknown according to it.

So I started to TS everything just too be sure, I did re-install Windows - I did check BIOS so MSI did not overclock the CPU, I did find something and that was that the P1 was for 4025w (overclockede) so I did change it to 125w that's Intel Default.

I did run memtest64 4-passes over night no issues with the RAM, I did also run OCCT samll and big data for 2 hours each no issue, Did try Prime95 blended for 3 hours no issues there either.

 

Then I did remember that sometimes my display was flickering so I did check in Event Viewer again and I did find this:

 

So after some googling it says that it indicate that my GPU is broken I did contact Palit and they told me to replace it. Was talking to the store and I'll send it in and get a 2080 Super as replacement for only 100 Euro extra.

 

Anyway this thing are getting me paranoid but it has not happened again, no more WHEA errors - should I just call it the day or should I contact Intel or something? OR is it possible that this was caused from the GPU? As the error source was unknown maybe it was from the GPU? The GPU are sending data to the CPU right?

 

My setup:
MSI meg z490 ace

i9 10900k

64GB DDR4 3200MHz

2070 Super (will soon get replace with 2080 Super)

[Jurrunio]

Imo it's just buggy windows. As an OS it has a ton of stuff running in the background, sometimes one of these things could crash. If it's not something critical the system will often just keep on running as usual. No need to replace anything.

[Rstolpe]

5 minutes ago, Jurrunio said:

Imo it's just buggy windows. As an OS it has a ton of stuff running in the background, sometimes one of these things could crash. If it's not something critical the system will often just keep on running as usual. No need to replace anything.

Ok, but Palit told me to RMA the 2070 Super due to the log from the GPU - and well that's OK for me I get the 2080 Super and maybe my display are stopping to flicker.

So the WHEA error is just to ignore and keep going?

[Mark Kaine]

this is either some Nvidia driver issue or an actual GPU issue.

 

I get thousands of those but only after booting up, it stops after a few minutes.

I definitely think it's not ideal but it's not a real issue either.

 

Never found out what's causing it,and unfortunately I don't think I still have warranty for my GPU either. At least pc works 99% of the time - I do get some mysterious bsods or crashes occasionally though (didn't happen in a long time tho actually)

[Rstolpe]

12 minutes ago, Mark Kaine said:

this is either some Nvidia driver issue or an actual GPU issue.

 

I get thousands of those but only after booting up, it stops after a few minutes.

I definitely think it's not ideal but it's not a real issue either.

 

Never found out what's causing it,and unfortunately I don't think I still have warranty for my GPU either. At least pc works 99% of the time - I do get some mysterious bsods or crashes occasionally though (didn't happen in a long time tho actually)

I have been reading up on the GPU errors and you can underclock your GPU people are writing that it fixes the issue. Or replacing the card with one that are 100% OK.

 

What I'm worried about is the WHEA error that stated CPU.

[Jurrunio]

51 minutes ago, Rstolpe said:

Ok, but Palit told me to RMA the 2070 Super due to the log from the GPU - and well that's OK for me I get the 2080 Super and maybe my display are stopping to flicker.

So the WHEA error is just to ignore and keep going?

I will just ignore it

[Rstolpe]

I did get this replay from Intel now regarding the WHEA - I did contact them before I did write here in the forum.

 

"

The WHEA error seems to be an indication that a parity error was detected, likely in data arriving from memory. It could be in the processor cores, processor uncore or in graphics subsystem. This was a single-bit error, which is recoverable (can be reconstituted). If it had been a multi-bit error, it would have been more catastrophic.

 

Neither of these other reports had anything to do with this WHEA error. They occurred days apart from the WHEA error.

 

Should you be concerned? Yes. Is it the processor's fault? Likely. If it reoccurs, I would RMA the processor.

"

 

Reoccurs is that if it happens again right? English is not my main speaking.

But I'm wondering also regarding: "The WHEA error seems to be an indication that a parity error was detected, likely in data arriving from memory"

Does he mean that it can be the RAM? So basically the issue can be in my RAM if I do understand him right? Or do he mean the SSD?