Hilfe!! 8700K WHEA-LOGGER

sew333

Banned
Thread Starter
Mitglied seit
17.07.2017
Beiträge
102
Hi. My question is i dont know why i get WHEA-LOGGER in day 21.01.2018. My system was currently idling when i remember. Windows 10 Fall Creator Update build was 16299.15

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:

image.jpg

My pc:

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.

Any clues why on 16299.15 i get hardware corrected errors when on newest builds not?

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 no errors. All benchmarks passing, no crashing in games

Only saw that warnings in event viewer from 21.01 using Win 10 build 16299.15 which make think that is something with voltages or software? 16299.192 and 16299.214 builds no WHEA-LOGGERS.

Maybe somebody tested 8700K on 16299.15 build?



English only please ! :)
 
Wenn Du diese Anzeige nicht sehen willst, registriere Dich und/oder logge Dich ein.
Wenn du nur englisch kannst, wärst du doch sicher viel besser in einem englischsprachigen Forum aufgehoben, meinst du nicht... klingst irgendwie logisch.
 
Ein Beispiel, Prime95 kann laufen ohne Fehler, trotzdem kann es eine hohe Anzahl von WHEA Fehlern geben.
 
Build 16299.15:

image.jpg



Win 10 16299.192 and 16299.214 builds no WHEA-LOGGERS.
 
If you wanna get help in "only english pls", then join an english community...

Btw there should be communities in your native language.

reddit may help you
Google too
 
Nein. Melden geht neuerdings über Tapatalk eben nicht mehr.

Gesendet von meinem G8341 mit Tapatalk

Falls es kein update Problem ist, könntest du Tapatalk deinstallieren und neu installieren, könnte helfen ...

Könnte auch schon helfen den Cache Speicher von deinem Handy zu löchen, was natürlich auch noch sein kann ist, dass das Problem beim HWLUXX Board liegt, könnte man denen mal einen Hinweis geben ..
 
Zuletzt bearbeitet:
I was getting WHEA-LOGGER 19 in build 16299.15 ( build before meltdown/spectre ) ,its from October 2017 build. Processor and mobo i bought in december 2017.

On build 16299.192 ( 3 january 2018 ) and build 16299.214 ( 31 january 2018 ) no WHEA-LOGGER 19 errors, its fine

so rma cpu ?
 
but the problem is, taht you will not receive on rma any proper cpu by Intel at the moment, would suggest to change your cpu platform ...
 
Holzmann...
Er schreibt, dass der Fehler mit der 16299.214 behoben ist bzw. nicht mehr auftritt und Du rätst zum Plattformwechsel?!
 
Stimmt hatte ich nicht gesehen ...
 
i had 390.65 drivers (
GeForce 390.65 WHQL (with security fixes for Meltdown and Spectre )

On old system 16299.15 ( before meltdown spectre ) hmm ?

Maybe thats why it was throwing WHEA?
 
Hi. My question is i dont know why i get WHEA-LOGGER in day 21.01.2018. My system was currently idling when i remember. Windows 10 Fall Creator Update build was 16299.15

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

And only one : WHEA Event ID 47 memory-corrected hw error
...
All settings in UEFI are stock,defaulted . Only XMP profile is on.

Any clues why on 16299.15 i get hardware corrected errors when on newest builds not?

English only please ! :)
A corrected Error means that the ECC found a Data Error in processing, but it was corrected, so it will have no effect to your PC System.
If the error is uncorrected then you would get System freeze and BSOD.

If you don´t use ECC RAM, then the ID47 is created in Error or the Cache System of the CPU correct it and overwrite the specific Memory adress.

All CPUs using ECC for the Cache System. ;)
 
Zuletzt bearbeitet:
So problem its hardware issue cpu or ram?
If the corrected error gone with another Windows build it should be Software related.
Maybe it is a debug mode from windows which is not disabled in build 16299.15.
 
Ok i formatted disk installed again clean install Windows 10 build 16299.15 without update. And still no WHEA-LOGGER 19.
So they had happened once. Anyway is this reason to worry?
 
Hey all. WHEA-LOGGER 19 back after 3 months. I saw 1 entry yesterday ,look:

image.jpg


image.jpg



Nothing get crashed. Just entry on event log. Pc was idling,only steam on background running.
Should I be worry or not?

Windows 10 the newest build of Fall Creator Update.
 
Ok i formatted disk installed again clean install Windows 10 build 16299.15 without update. And still no WHEA-LOGGER 19.
So they had happened once. Anyway is this reason to worry?
Microsoft Windows 10 Pro 10.0.16299.309 (64-bit)
No, your Error Correction Code is still valid! ;)
 
This single one WHEA-LOGGER 19 yesterday happened on build 16299.309 . So what now? Should i ignore or just change something in UEFI?
 
I was checking event logs on 25.10.2018 and had spam of WHEA-LOGGER 19 entries.
They happened when system was idling from 23.10 - 25.10 , so nothing happening in system only spam. Is this reason to worry? My actually Windows 10 is 1803.

I had them too on 21.01 january but they dissapeared after 21.01 january.
Windows 10 1709 build 16299.15 it was.

Like i said.
But now they appeared again after few months ,from 23.10 october -25.10 october and dissapeared again. I must say that i was little surprised that i saw them again after few months especially on idle .
Windows 10 1803 actually.

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


A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Cache Hierarchy Error

( screens on top of the topic )





Dont have any crashing,no freezing,no bsods,scores are fine etc.

So question. ANyway is this reason to worry or skip it if they stop it again?
Maybe something with voltage or something ( reading reddit ) but they appeared when system was idling ( not gaming ) and i was away from pc. All drivers installed.
Thanks
 
Hardwareluxx setzt keine externen Werbe- und Tracking-Cookies ein. Auf unserer Webseite finden Sie nur noch Cookies nach berechtigtem Interesse (Art. 6 Abs. 1 Satz 1 lit. f DSGVO) oder eigene funktionelle Cookies. Durch die Nutzung unserer Webseite erklären Sie sich damit einverstanden, dass wir diese Cookies setzen. Mehr Informationen und Möglichkeiten zur Einstellung unserer Cookies finden Sie in unserer Datenschutzerklärung.


Zurück
Oben Unten refresh