8700K stock WHEA errors event log. I am depressed.

[sew333]

Hi. Today i checked my event viewer and found some weird errors from 21.01.2018 :

 

A spam of:

WHEA Event ID 19 CPU-corrected hw error

 

And only one :

WHEA Event ID 47 memory-corrected hw error

 

 

Here are screen with one of them:

 

 

 

 

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.

 

Temps of cpu fine,temps of gpu fine. Never had any single BSOD. Memtest86 and ihcmemtest no errors. All benchmarks passing, no crashing in games

 

Only saw that error in event viewer which make think that is still with cpu or rams or mobo or psu?

 

Looking across internet i have found bad opinions about this. I am so depressed guys!:(

[Demon_]

Update the BIOS and the drivers for the motherboard chipset. Update all the hardware drivers, if updates are available from your manufacturer.

[Cibit]

Is it not the meltdown fix ?

[BitMaster]

afaik the ms patch has been removed... you may still update your Bios.

 

use stock clocks, bios default and test the machine with either or all : prime95, aida and IBTv2

 

UPDATE your drivers for mobo too !! This sounds like a Intel-ME bug to me, see if you can update Intel Management Extension, Update USB 3.x ASmedia, Update Intel Chipset from Intel site directly, get all Intel from Intel, not asus is my best advice, unless asus has a newer one than intel offers to end users, sometimes this is the case.

 

disconnect all unneeded devices: mobo-cpu ( + Intel VGA ) RAM SSD PSU = done

 

no DVD, no 2nd or 3rd drive, no USB other than what you need ( kb + mouse ), no USB hub(s),

take it ALL off to see if the CORE computer parts are malfunctioning.

 

If it still errors with this kit, take RAM out, only ONE module per time, try each slot if needed with each RAM. Sometimes a slot is defect, Cibit iirc had that few eeks ago.

 

The devil is hidden in the detail, work with a plan, with a minimum of devices and you will exclude all that works, the rest that remains, has the error. Thats how I do it for 20 years now.

Pure empiric method. one by one...etc..it does cost a lot of time, we all know this and nobody pays you but you have to return the defect part, and not the whole bunch, they wont accept that I guess. If you can gell them precisley how why and when an error occurs you have good chances for RMA and help.

[sew333]

This happened in day when i finished installing Windows 10.

 

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

 

I triied memtest86,ihcmemtet all benchmarks and no errors. No bsods,no freezing.

 

Any ideas why that happened? That was error related to hardware or ?

[BitMaster]

I only see WHEA if I overdo overclocking the RAM, than it usually picks WHEA or even worse.

 

If it ONLY occured once, keep it in mind but dont bother too much about it.

 

If it comes again every week or so, you need a new driver, when available.

 

It will be hard to pinpoint what causes it if the system is fully equipped.

 

Also, if it comes back fast, like 1-2 days, load Ubuntu for a day or 2, may even be from USB,

 

and see if that reboots itself or errors somehow. It should run nonstop without ay glitches.

 

If it still does it in Linux..well, happy bug hunting.

Edited February 2, 2018 by BitMaster

[sew333]

The wierd thing was that system was on idle even not in load. And Windows 10 was doing literally nothing.

[BitMaster]

I have had similar things too, it's new boards and unripe bios'....early adopters pay a price beyond the $.

 

Mine shutdown out of the blue, usually in idle, every 5-10 days, always same error. Mine went away after a few weeks and updates.

 

It might be,mine was also whea, but i cant say for sure. Usually, as said, my ram causes it when set to xmp. baaahhhh

[sew333]

Hmm ok. Weird thing. I cant reproduce that error. It started and finished one day.

MemtestsIHC and 86 not showing errors. And no have stability problems. Also i know what you saying. Maybe some hard to resolve form of instability or something? Its new computer.

[sew333]

I checked now events today. 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 (kompilacja systemu operacyjnego: 16299.192)

 

 

:)

[sew333]

Any ideas why on 16299.xx ( previous ) was throwing that errors? on 16299.192 stopped ( intel emergency fix )

[BitMaster]

no idea