Microsoft windows whea logger код события 19 - Доктор Windows

Remove From My Forums

Вопрос

Здравствуйте. В журнал каждую минуту валит ошибку:

Имя журнала:   System

Источник:      Microsoft-Windows-WHEA-Logger

Дата:          04.07.2018 23:01:59

Код события:   19

Категория задачи:Отсутствует

Уровень:       Предупреждение

Ключевые слова:

Пользователь:  LOCAL SERVICE

Компьютер:     DESKTOP-D3QGQVR

Описание:

Произошла устраненная аппаратная ошибка.

 

Сообщивший компонент: ядро процессора

Источник ошибки: Исправленная ошибка проверки компьютера

Тип ошибки: Ошибка иерархии кэша

ИД APIC процессора: 2

 

Дополнительные сведения содержатся в подробностях этой записи.

Xml события:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{C26C4F3C-3F66-4E99-8F8A-39405CFED220}" />

    <EventID>19</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000000000000000</Keywords>

    <TimeCreated SystemTime="2018-07-04T20:01:59.233241500Z" />

    <EventRecordID>6503</EventRecordID>

    <Correlation ActivityID="{A7A55E90-4CE7-4716-800D-B91923365C79}" />

    <Execution ProcessID="4048" ThreadID="6656" />

    <Channel>System</Channel>

    <Computer>DESKTOP-D3QGQVR</Computer>

    <Security UserID="S-1-5-19" />

  </System>

  <EventData>

    <Data Name="ErrorSource">1</Data>

    <Data Name="ApicId">2</Data>

    <Data Name="MCABank">3</Data>

    <Data Name="MciStat">0xcc4000c000100151</Data>

    <Data Name="MciAddr">0x46d370000</Data>

    <Data Name="MciMisc">0x406485</Data>

    <Data Name="ErrorType">9</Data>

    <Data Name="TransactionType">0</Data>

    <Data Name="Participation">256</Data>

    <Data Name="RequestType">5</Data>

    <Data Name="MemorIO">256</Data>

    <Data Name="MemHierarchyLvl">1</Data>

    <Data Name="Timeout">256</Data>

    <Data Name="OperationType">256</Data>

    <Data Name="Channel">256</Data>

    <Data Name="Length">928</Data>

    <Data Name="RawData">435045521002FFFFFFFF03000200000002000000A00300003A011400040712140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F89034E75D1AC213D40100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000098020000080100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000200000000000000000000000000000000000000000000007F010000000000000002010300010000EA0609000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000200000000000000EA06090000081002BFFBFA7FFFFBEBBF0000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F005420000000000000376D040000000000000000000000000000000000000000000000000000000200000001000000326A49DDD113D40101000000000000000000000000000000000000000300000051011000C00040CC0000376D0400000085644000000000000000000002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>

  </EventData>

</Event>

Система:

Motherboard: Z370 PC PRO (last bios version)

CPU: i5-8400

RAM: Kingston DDR4-2444

VGA: GeForce GTX 970

PSU: Chieftec 550W

OS: Windows 10 Pro 1803 (17134.112)

Подскажите пожалуйста как можно выявить виновника?

Источник

[SOLVED] WHEA-Logger Event 19 — A Corrected Hardware Error has Occurred.

Thread starter

elliot1396
Start date

Jan 17, 2021

Status: Not open for further replies.

Hello!

I’ve had two Power cycles this evening which logged as a Kernel Power Error. These happened within the space of an hour and were clean, cut outs and restarts without BSOD.

I’ve been having intermittent BSOD issues recently but re-seated the components in my PC on the 14/01/2021 and It seems to have solved the issue, or somewhat replaced it with the issue I am now having!

I’ve found these (three identical) Warnings in Event Viewer (System).

One dated to 15/01/2021
Two dated to 17/01/2021

WHEA-Logger Event 19:

«A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Unknown Error Source
Error Type: No Error
Processor APIC ID: 0

The details view of this entry contains further information.»

I’m writing this post as I’m unable to find any information regarding this.

The Details View is posted below:

[ Name]

Microsoft-Windows-WHEA-Logger

[ Guid]

{c26c4f3c-3f66-4e99-8f8a-39405cfed220}

Keywords

0x8000000000000000

[ SystemTime]

2021-01-17T22:09:48.1932654Z

[ ActivityID]

{f43627bf-3a62-4a70-ad90-f987342e3b34}

MciStat

0x98004000003e0000

MciMisc

0xd01a0ffe00000000

RawData

435045521002FFFFFFFF03000200000002000000680300002F091600110115140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B248949139377F4BA8F1E0062805C2A3ECDCA19019EDD60100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000400000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000058020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E80000000000000000000000000000000002000000000000000000000000000000000000000000000057010000000000000002000000000000100F87000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000100F8700000818000B32D87EFFFB8B1700000000000000000000000000000000000000000000000000000000000000000200000002000000997CAF771DEDD60100000000000000000000000000000000000000001900000000003E0000400098000000000000000000000000FE0F1AD0000000000000000000048303FF000100000000000000000079000000230000000000000000000000000000000000000000000000000010000000000000001000000000000000100000000000000010001B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

An Update on the Issue:

I managed to solve it! It was indeed the RAM, running on it’s XMP Profile which was causing the issue. Instead, I manually set the Clock and Voltage in BIOS and I haven’t had an issue since. I’ve given it a few days clearance before posting this so I could be sure of the result, plus plenty of stress tests to ensure stability.

Noted on DriverEasy. I just wanted to be sure I wasn’t missing anything.

Thanks to Vic 40 for his help.

Elliot

Vic 40

: Oct 22, 2013

: 20,849

: 983

: 87,190

: 3,047

What hardware in the pc?

Have latest drivers?
Latest windows updates?
Latest bios?

What hardware in the pc?

Have latest drivers?
Latest windows updates?
Latest bios?

Hiya,

All latest drivers, bios & windows update. I also perform regular virus checks, I also use my head and common sense as to what I download and don’t….!!

Ryzen 9 3900x
Aorus Ultra x570 motherboard
32gb Ram
1x 1TB m.2 (boot)
1x 512gb m.2 (storage)
GTX 1080 FE
EVGA 750w fully modular gold

No overclocks running asides from the RAM on its 3600mhz profile through bios.

Temperatures stable and monitored

Next check is to check voltage on 12v rail of PSU, haven’t got round to this yet.

Spotted someone on the internet mentioning that in ‘power settings’ setting your drive to ‘Never Sleep’ had helped them.

This error ONLY occurs when idle and after a length of time, roughly 20-30 mins, where a power cycle will occur. This doesn’t happen while the machine is in use. I can prove this because I’ve been using the machine for hours on end, for the event to occur whilst I’m away from the computer and it is idle.

No issues or anything weird any other time whilst using the pc. Which does lead me away from the idea this could be the psu but worth a check anyway.

PC built back in March and was as good as gold for several months. I can roughly link this error from when I gave my pc a service a few weeks ago, updated bios, chipset drivers, system drivers, reseated all the components and cleaned them. Fixed my original BSOD error (I also found I was running in ram slot 1/3 rather than 2/4).

Thanks !
Elliot

Vic 40

: Oct 22, 2013

: 20,849

: 983

: 87,190

: 3,047

What ram exactly? also 2x16gb or 4x8gb. From one kit?

What ram exactly? also 2x16gb or 4x8gb. From one kit?

Hi!

It’s 2x 3200mhz 16GB Corsair Vengeance LPX in slots 2 + 4 on the motherboard which is a x570 Gigabyte Aorus Ultra.

Elliot

Vic 40

: Oct 22, 2013

: 20,849

: 983

: 87,190

: 3,047

There is a new bios «F33a from 2‎021-01-22» have that one already?
Install latest AMD drivers for the chipset before updating if not,
AMD Drivers and Support for Radeon, Radeon Pro, FirePro, APU, CPU, Ryzen, desktops, laptops

Also look for latest LAN and sound drivers as well on the motherboard site. Can try for the Intel LAN chip this as well,
Intel® Driver & Support Assistant

See if WhoCrashed can say what driver might be an issue,
WhoCrashed 3.01- Free Downloads

Think you still have bsod issues since having bugcheck 0x00000019.

Maybe an usefull vid, would skip the «restore point»,

View: https://www.youtube.com/watch?v=GCzRXMROJAI

There is a new bios «F33a from 2‎021-01-22» have that one already?
Install latest AMD drivers for the chipset before updating if not,
AMD Drivers and Support for Radeon, Radeon Pro, FirePro, APU, CPU, Ryzen, desktops, laptops

Also look for latest LAN and sound drivers as well on the motherboard site. Can try for the Intel LAN chip this as well,
Intel® Driver & Support Assistant

See if WhoCrashed can say what driver might be an issue,
WhoCrashed 3.01- Free Downloads

Think you still have bsod issues since having bugcheck 0x00000019.

Maybe an usefull vid, would skip the «restore point»,

View: https://www.youtube.com/watch?v=GCzRXMROJAI

Thanks Vic for your extensive help!

Just an update on my progress:

I’m now running F33a Bios, AMD Drivers for the chipset are on the latest.
I’m on the latest Sound and LAN drivers. I updated every driver on the system I could possibly find using DriverEasy.

I’ve run ‘WhoCrashed’ and It says I have no valid crash dumps to show, despite them being enabled with a valid directory listed. I wonder if this is due to the hard system crashes as apposed to a BSOD which may not be logging these correctly?

I’ve followed the tutorial in the video you sent. Thank you for that.

In addition, I’ve removed the XMP Profile on my RAM from the bios (3200 XMP now running at 2133) which is a shame but this is a process of trial and error. I seem to be able to remember some kind of a link between the WHEA-logs / hard crashes occuring since enabling the XMP setting in bios. So far so good with no errors or hard-restarts (2-3 hours in).

I’ve read a few articles about issues with OC’d ram and Ryzen processors. I’m not sure how relatable this is seeing as (from what I remember) an overclock is considered from 3600 mhz +, I’m only getting to 3200 Max.

I did come accross this fairly interesting article. I wonder if you’d be able to cast your opinions on this and how it relates to my issue. In my opinion, this seems fairly close to what I’m seeing:

Hope you are well and safe!

Thanks again,
Elliot

So now — Fingers crossed for me!

Vic 40

: Oct 22, 2013

: 20,849

: 983

: 87,190

: 3,047

About that thread, you can try and see if it will help. Nothing more i can really say.

Don’t use «driver easy» or such tools to find drivers, just look at the makers site from where the hardware is.

An Update on the Issue:

Noted on DriverEasy. I just wanted to be sure I wasn’t missing anything.

Thanks to Vic 40 for his help.

Elliot

Status: Not open for further replies.

Thread starter	Similar threads	Forum	Replies	Date
C	Question Kernel-Power, Event ID 41, Task Category: (63)	Systems	13	Jan 28, 2023
	Question LiveKernel Event Errorcode 193	Systems	4	Jan 14, 2023
M	Question Random restarts — Event 41	Systems	2	Dec 30, 2022
	Question Random restarts with «Event ID 41» and «Task category 63» ?	Systems	2	Dec 17, 2022
M	Question New PC restarts on load — Event Viewer shows Kernel power 41 error ?	Systems	7	Dec 11, 2022
E	Question PC Crashing During 3D Apps — Event 41 Kernel Power	Systems	5	Dec 7, 2022
	Question WHEA Logger 18 crashes	Systems	17	Nov 11, 2022
M	Question Spontaneous Random Crashes — WHEA Logger Event 18, No Pattern	Systems	2	Apr 24, 2022
T	Question WHEA logger event 18 crashing pc	Systems	3	Mar 2, 2022
	[SOLVED] My pc faces random reboots while playing games. Error 41, whea logger 18 & error 6008 in event viewer.	Systems	5	Feb 8, 2022

Advertising
Cookies Policies
Privacy
Term & Conditions
Topics

Источник

добрый день ,недавно произошел краш в игре , решил посмотреть в журнале событий инфу , нашел там такое предупреждение

Произошла устраненная аппаратная ошибка.

Сообщивший компонент: ядро процессора
Источник ошибки: Corrected Machine Check
Тип ошибки: Translation Lookaside Buffer Error
ИД APIC процессора: 0

Дополнительные сведения содержатся в подробностях этой записи.

и так каждую минуту

судя по логам началось все с 7 октября , винду переустанавливал , дрова в порядке , железо новое (месяца полтора)

добавлю еще что в некоторых играх при двухканальном режиме оперативной памяти случаются краши , с 1 планкой проблем нет

оперативку проверял мемтестом86 по 1 плашке каждую и в двухканале — ошибок не найдено
ssd также в порядке , проц гонял по интеловской утилите intel diagnostic tool — все тесты прошел

конфигурация пк ; i5 9400f , gigabyte z390ud , crucial ballistix lt sport 3000mhz , 1050ti4gb

__________________
Помощь в написании контрольных, курсовых и дипломных работ, диссертаций здесь

Источник

Remove From My Forums

Question
I started receiving some BSODs over the past couple months (Stop code: IRQL_NOT_LESS_OR_EQUAL). Windows 10 64-bit, X1 Carbon 2nd Gen (Type 20A7, 20A8).

When I went into Event Viewer I’m noticing hundreds of WHEA-Logger Event ID 19 errors, to the tune of a few per minute.

A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 2

The details view of this entry contains further information.

I’ve done reserach on this and still haven’t foud a solution. Has Lenovo noticed this issue or is there some kind of update available? I’m updated via Windows Updates and LSB, and don’t know where else to check.

Источник

Remove From My Forums

Question
I started receiving some BSODs over the past couple months (Stop code: IRQL_NOT_LESS_OR_EQUAL). Windows 10 64-bit, X1 Carbon 2nd Gen (Type 20A7, 20A8).

When I went into Event Viewer I’m noticing hundreds of WHEA-Logger Event ID 19 errors, to the tune of a few per minute.

A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 2

The details view of this entry contains further information.

I’ve done reserach on this and still haven’t foud a solution. Has Lenovo noticed this issue or is there some kind of update available? I’m updated via Windows Updates and LSB, and don’t know where else to check.

Источник

Вопрос

[SOLVED] WHEA-Logger Event 19 — A Corrected Hardware Error has Occurred.

Question

Question