[axe0]

Again, your hardware is fine.

 

[satrow]

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?

 

[sew333]

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?

 

[satrow]

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.

 

[axe0]

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:

Emphasis added.

That this somebody experienced it, does not mean it is the same for you just because you get the same WHEA logs.

 

[sew333]

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.

 

[axe0]

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

 

[sew333]

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?

 

[axe0]

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.

 

[sew333]

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.

 

[satrow]

If the CPU was faulty, how did updating W10 fit it... ?

Your hardware's still fine, do something constructive with it

 

[K9BEG]

This is what happens when you try to find help from too many sources. You get confused.

 

[sew333]

Just cant understand. Errors start at 21.01.2018 3:00 at night and finished at 3 pm. After that 0 errors till today.

 

[sew333]

https://forums.anandtech.com/threads/whea-logger-and-ivy-a-warning-p.2308021/


"Saying you get no errors in those programs simply means your processor is stable when running the instructions requested by those programs. But other programs, like your OS, will request your CPU process computations using other instructions from the ISA.

Your CPU's ISA supports nearly 2000 instructions. No program in the public domain will stress test all of them. LinX and Prime95 test maybe 100 of them.

WHEA errors are errors that are happening for other instructions, it is basically your OS telling you the CPU is not stable, same as LinX telling you it isn't stable.

As far as why you should care...its called "silent data corruption" and you should care about that. "

 

[axe0]

Here's a technical guide about WHEA (0x124 crashes) that explains why the terminology of this guy you quote is incorrect.

TL;DR;
WHEA is an event reported by the CPU to catch hardware related problems, which doesn't mean the CPU is actually the reason of it.

 

[sew333]

Here is somebody with the same issue ( but nothing helped to him ) and he replaced cpu:

https://communities.intel.com/thread/110783

 

[axe0]

The CPU can also cause WHEA errors, but so can many other elements of a system...

I didn't mean to say that the CPU is not a possible cause, but that it should not be pointed at without troubleshooting other elements first.

I would ask you to stop looking into this, I and many others cannot explain why you experienced those logs in that specific build, please let it rest.

 

[tristar]

Once you start messing more with the system, you're probably going to drive it into more serious issues :S At this point, just keep an eye, but don't make major changes, you have a working machine and it's good to be proactive but at this time, go with the flow.

We're only a post away and you can see the speed with which you get responses, so in case anything changes, drop us a post and we'll get back.. Until then, grab a beer and chill out

 

[sew333]

Last thing. When this WHEA-LOGGER 19 warnings appear ,almost before warnings i get message generating itself in event viewer: UserPowerModeService reset policy scheme .

+ USB PENDRIVE was plugged in pc in this time .

Maybe that was somehow related?

 

[sew333]

i think not