F5F Stay Refreshed Hardware Desktop The WHEA error could point to your GPU or CPU depending on the issue.

The WHEA error could point to your GPU or CPU depending on the issue.

The WHEA error could point to your GPU or CPU depending on the issue.

H
hakan10
Member
54
09-26-2020, 05:25 AM
#1
Hey, I've encountered a single WHEA warning. My machine was almost idle while chatting on Skype for an hour across the room. When I ended the call, it froze for about five seconds before resuming normal operation—no BSOD or simulation. HWiNFO64 showed a WHEA error with these details:

- Log Name: System
- Source: Microsoft-Windows-WHEA-Logger
- Date: 2020-09-22 14:51:39
- Event ID: 19
- Level: Warning
- Keywords: User: LOCAL SERVICE, Computer: DESKTOP-96J2OR5

The summary says a corrected hardware issue occurred. The error type was an internal parity fault on the processor. Further info is available in the event record (ID 5265).

I double-checked everything—reinstalled Windows, verified BIOS, confirmed no CPU overclocking, ran memory tests, OS checks, and even used OCCT and Prime95. All passed.

The details also mention a P1 setting of 4025W, which I changed to the default 125W. My display flickered briefly, but that didn’t trigger any warnings.

I’m still a bit worried, but it seems resolved. Should I just let it go or reach out to Intel for confirmation? Also, could this have come from the GPU? My setup includes an MSI MEG Z490 with an i9-10900K and 64GB DDR4 RAM.
H
hakan10
09-26-2020, 05:25 AM #1

Hey, I've encountered a single WHEA warning. My machine was almost idle while chatting on Skype for an hour across the room. When I ended the call, it froze for about five seconds before resuming normal operation—no BSOD or simulation. HWiNFO64 showed a WHEA error with these details:

- Log Name: System
- Source: Microsoft-Windows-WHEA-Logger
- Date: 2020-09-22 14:51:39
- Event ID: 19
- Level: Warning
- Keywords: User: LOCAL SERVICE, Computer: DESKTOP-96J2OR5

The summary says a corrected hardware issue occurred. The error type was an internal parity fault on the processor. Further info is available in the event record (ID 5265).

I double-checked everything—reinstalled Windows, verified BIOS, confirmed no CPU overclocking, ran memory tests, OS checks, and even used OCCT and Prime95. All passed.

The details also mention a P1 setting of 4025W, which I changed to the default 125W. My display flickered briefly, but that didn’t trigger any warnings.

I’m still a bit worried, but it seems resolved. Should I just let it go or reach out to Intel for confirmation? Also, could this have come from the GPU? My setup includes an MSI MEG Z490 with an i9-10900K and 64GB DDR4 RAM.

_
_DeathTrap_
Member
212
10-01-2020, 03:55 PM
#2
It seems like the interface is quite unstable. The operating system runs many background processes, which can cause occasional crashes. Unless it's a major issue, the system usually continues functioning normally. No replacement is necessary at this time.
_
_DeathTrap_
10-01-2020, 03:55 PM #2

It seems like the interface is quite unstable. The operating system runs many background processes, which can cause occasional crashes. Unless it's a major issue, the system usually continues functioning normally. No replacement is necessary at this time.

G
GrimAuxilitrix
Junior Member
16
10-02-2020, 04:52 AM
#3
Palit recommended returning the 2070 Super because of the GPU log, which is fine since I already have the 2080 Super and my screen might be flickering. The WHEA warning can be ignored and you should proceed.
G
GrimAuxilitrix
10-02-2020, 04:52 AM #3

Palit recommended returning the 2070 Super because of the GPU log, which is fine since I already have the 2080 Super and my screen might be flickering. The WHEA warning can be ignored and you should proceed.

L
LuigiTNT11
Junior Member
2
10-02-2020, 06:20 AM
#4
It seems like the problem might be related to the Nvidia driver or the GPU itself. I encounter thousands of these issues, but they only appear after the system starts up and stop after a few minutes. It’s not a perfect situation, but it isn’t a genuine issue either. I haven’t identified the cause, and unfortunately, my warranty for the GPU is likely expired as well. At least the PC functions properly about 99% of the time—though I still experience occasional strange beeps or crashes now and then (they haven’t happened much recently).
L
LuigiTNT11
10-02-2020, 06:20 AM #4

It seems like the problem might be related to the Nvidia driver or the GPU itself. I encounter thousands of these issues, but they only appear after the system starts up and stop after a few minutes. It’s not a perfect situation, but it isn’t a genuine issue either. I haven’t identified the cause, and unfortunately, my warranty for the GPU is likely expired as well. At least the PC functions properly about 99% of the time—though I still experience occasional strange beeps or crashes now and then (they haven’t happened much recently).

K
kervinc
Posting Freak
804
10-02-2020, 07:15 AM
#5
I've been looking into GPU issues and some users suggest downclocking to resolve problems. They also mention switching to a fully functional card. My main concern is the WHEA warning indicating CPU-related errors.
K
kervinc
10-02-2020, 07:15 AM #5

I've been looking into GPU issues and some users suggest downclocking to resolve problems. They also mention switching to a fully functional card. My main concern is the WHEA warning indicating CPU-related errors.

N
navotj
Junior Member
7
10-07-2020, 06:30 AM
#6
I'll just skip it.
N
navotj
10-07-2020, 06:30 AM #6

I'll just skip it.

P
Papyrule
Senior Member
560
10-08-2020, 01:13 PM
#7
I received this replay from Intel about the WHEA issue. I reached out before posting here. The error suggests a parity mistake was found, probably in memory data—could come from the CPU core, processor uncore, or graphics part. It was a single-bit problem and could be fixed. A multi-bit error would have been more serious. This wasn’t related to other reports that happened later. You should be concerned. The fault likely lies with the processor. If it happens again, I’d consider returning it for repair.
P
Papyrule
10-08-2020, 01:13 PM #7

I received this replay from Intel about the WHEA issue. I reached out before posting here. The error suggests a parity mistake was found, probably in memory data—could come from the CPU core, processor uncore, or graphics part. It was a single-bit problem and could be fixed. A multi-bit error would have been more serious. This wasn’t related to other reports that happened later. You should be concerned. The fault likely lies with the processor. If it happens again, I’d consider returning it for repair.