It's a corrected error so no need to worry.

 

On other forums they said that is caused by hardware problem.

 

Not per se, WHEA merely means the system detected a hardware related issue. This can be drivers and hardware. But, since WHEA's aren't exactly telling what caused the error, it can be quite difficult to pinpoint the cause.

And no, because you see the CPU in a WHEA event does NOT mean it is the cause. The CPU is the one that notifies the system of the WHEA and thus is pretty much always involved.

My suggestions:
- Remove any overclocking
- Update chipset drivers
- Update BIOS if any is available
- Run driver verifier if above didn't help
http://www.techsupportforum.com/for...rums/f299/driver-verifier-windows-10-8-1-8-7-and-vista-bsod-related-473665.html

 

A spam of:
WHEA Event ID 19 CPU-corrected hw error

And only one :
WHEA Event ID 47 memory-corrected hw error

This day i remember i finished installing Windows 10. And system was completely on idle overnight.

Errors was only in 21 january. From 22 january till today no errors in event viewer,i checking now all days.

And i dont know why this errors happened in this day?

Computer is:
8700K stock, MTE on, 4700mhz auto clock
Asus Z370 Pro Gaming
16GB DDR 3000MHZ ( XMP ON)
Gtx 1080 Ti Aorus
Corsair 750 Rmi
SSD Crucial 525GB
HDD TOSHIBA 500GB
Windows 10 clean install 1709 Creator Fall Update

All settings in UEFI are stock,defaulted . Only XMP profile is on.

 

 

It might not be required, but I'd turn off the XMP profile to see if it makes a difference since it's indicative of both CPU/Memory, I could be completely wrong about this, just a thought.

 

I tested IHC Memtest and no errors:[ with xmp. Etc all stable.

But just worried about that warnings from 21.01

 

Also looks like the event is early in the morning, any chance this is related to the Sleep state ? or if power options are set to reduce the CPU processor power management where it's trying to run in a reduced mode but the XMP is kicking it up to perform full speed ? thinking out loud...

You can try turning off sleep/hibernate options or change power options to a full performance mode to see if that helps.

And play around the sleep state options in the BIOS, these are just assumptions based on the timeline of the event.

@axe0 quick question, are these notifications/warnings, or is it an actual event that occurred below the OS level and the OS kind of worked around it ?

 

Hi.

I tried to update to Win 10 build.

KB4056892 ( 16299.192).

And it stopped throwing that errors after installing update on 22.01 :

https://support.microsoft.com/pl-pl/help/4056892/windows-10-update-kb4056892

KB4056892 ( 16299.192).

And next i update to newest
16299.214
KB4058258
and still no errors.

https://support.microsoft.com/en-us/help/4058258


But yes. I remember i had hibernate/sleep mode turning on during that time when it throws errors. Now i have to NEVER on setting. Maybe that was related?

 

Latter, if the OS can't work it out, it results in a 0x124.

 

Thanks axe0 ! So if it leads to a 0x124, would this be troubleshot similar to a BSOD ? or is this outside the scope of the OS ?

 

If it occurs frequently I would treat it as a BSOD, it's a sign that the system may eventually crash and with some luck it can be prevented.

 

Aah, thanks much for the insight !

 

Probably, I was just going with a logical deduction based on the time line of the event, do keep an eye and let us know if you notice any changes..

 

This day i remember i finished installing Windows 10 with 16299.15 build ( build before meltdown/spectre ). And system was completely on idle overnight.

Errors starts showing on IDLE in event logs in 3 a.m and finished at 3 at noon.

I remember that after windows 10 updated to build 16299.192 . + disabled hibernating errors stop showing. After that errors stops showing. After update 0 errors. Then i updated to 16299.214 newest and still 0 errors.


Can somebody tell me if my hardware is fine or not? It was throwing WHEA-ERRORS on build 16299.15

 

Your hardware is fine, I've recently seen more systems throwing WHEA errors, all using 8700k CPU on the same build.

 

So if somebody said that :"If this isn't related to Meltdown/Spectre you should run a scan with Memtest86. The Event ID 19 is usually related to your RAM."

So its my ram fault? But like i said it only happened on 16299.15 build.
On 16299.192 build and 16299.214 build fine , no errrors. This is last question.



ps:
I tested memtest86 and ihcmemtests and 0 errors.

 

I wonder how he gets that idea, I don't see how the RAM is in such a way related that it is an immediate possibility.

 

Ok finally. I tested all games and benchmarks on 16299.214 build no single WHEA-LOGGER. So that was propably issue with build ( 16299.15 ) or system not hardware?

 

Again, your hardware is fine.

 

You probably received a Windows Update that was subsequently removed or updated because it was rushed/bad.

As usual, there appears to be nothing wrong with your hardware and your decision to do a W10 reinstall wasn't very wise.

As previously stated in your earlier topics: stop looking for problems that don't exist, eh?

 

That *somebody* was probably an overclocker himself, he would *know* what he'd done that would be most likely to cause that issue for him.

Meanwhile, back in the real world:

You probably received a Windows Update that was subsequently removed or updated because it was rushed/bad.

 

Hey again. Currently i am writing from work. I am making surveys with peoples on pcs. But still i am worried and thinking . Listen.

Somebody said this to me:"WHEA errors usually caused by unstable overclocks."

So what you think? I have unstable overclock? So why on win10 build 16299.192 and 16299.214 i dont have anymore WHEA LOGGER?

 

Axe you said:"Your hardware is fine, I've recently seen more systems throwing WHEA errors, all using 8700k CPU on the same build."

Are you sure? Thanks . Last question.

 

If I wasn't sure I wouldn't have said it.
Here's another user that had similar issues
https://www.tenforums.com/bsod-crashes-debugging/103716-8700k-whea-errors-16299-15-build.html

 

On tenforums this is my topic Its my nick xxx123.
So you was thinking only about this?

Or maybe from your experience other user experienced this?

 

I had some other sites, but for unknown reasons I can't find them back.

Apparently you've been asking on many forums about this, search results that are actually related to this are topics created by you.

 

Just worried because on intel community site, some person said that i have faulty cpu , because error was found in cpu So thats why i create topic.