[SOLVED] Random BSOD, and WHE id 19 error on event log

fidham98

Honorable
Dec 25, 2015
10
0
10,510
0
Hi there i just recently upgraded my pc from i5 7500 to i7 10700f and since then i got a numerous amount bsod and it happens randomly.
Some time my pc running fine a day no BSOD what so ever and the other got a lot of bsod.
some stuff i already tried running Intel Processor Diagnostic found no error
running prime 95 test found no error too
testing ram kit using windows memory diagnostic found no error too
Im at lost
my full pc spec
i7 10700f
RTX 3070ti
16GB DDR4
EVGA GT 750W gold
here is the minidump
https://1drv.ms/u/s!Alo54hJtaQZkz00-qvo3_QJOnyYx?e=EDm2h4
 
Last edited:
OK i will try it, if i disable the intel turbo thingy and the whe gone is it mean i got a faulty cpu?
i read about others who have the same problem like me, it might be voltage on cpu core to low.
and others say the whe log can be ingnored if it doesn't cause crashes and blue screen.
So far since im reinstall a fresh copy of windows my pc did not have a single BSOD .
only got a couple of whe log on the event viewer.
when I first looked at the error it looked like it was reported by source = microsoft and the error was correctable but it ended being converted to fatal error and a bug check was called.
you can run the intel cpu diagnostics and see if it reports some problem but it is not likely. I think it is just going to be some voltage needs to be set in some range.
so that your cpu does not have cache problems.

cpu's have massive amounts of code (logic) there are hundreds of bugs and everyone get the bugs. Some are so minor they are never fixed for the entire series of that CPU. others are fixed as new steps (versions) of the same cpu are released. The cpus are released then rounds of microcode updates are released to the motherboard vendors to work around bugs in the cpu. Then the motherboard vendor updates the bios (if they still support the board)
this process takes 6 to 9 months. many users do not install the bios updates and get bugchecks, windows error reporting sends the error info to microsoft and microsoft looks at the memory dump. Microsoft finds bugs and reports them to vendors and might also update the cpu dll that they load for each vendor. this CPU dll attempts to patch the microcode to work around certain bugs in the cpu.

my best guess would be that your issue is going to be related to some cpu voltage setting slightly out of range for what it should be (for your motherboard) rather than a actual bug in the CPU. But I do not know for sure.
I have had many people using amd CPUs just replace the cpu and all the problems went away. Only one time this happened with a intel cpu and it had failed the intel cpu diagnostics.
The Intel® Processor Diagnostic Tool Overview, Download, and...
I think this is a more basic functions test but you can run it.
 
Last edited:
Hi there i just recently upgraded my pc from i5 7500 to i7 10700f and since then i got a numerous amount bsod and it happens randomly.
Some time my pc running fine a day no BSOD what so ever and the other got a lot of bsod. here is the minidump
some stuff i already tried running Intel Processor Diagnostic found no error
running prime 95 test found no error too
testing ram kit using windows memory diagnostic found no error too
Im at lost
my full pc spec
i7 10700f
RTX 3070ti
16GB DDR4
EVGA GT 750W gold
here is the minidump
https://1drv.ms/u/s!Alo54hJtaQZkz00-qvo3_QJOnyYx?e=EDm2h4
That means you changed the mobo.
Did you reinstall windows or are you running off the old OS?
Proper bios and mobo drivers?
 

fidham98

Honorable
Dec 25, 2015
10
0
10,510
0
You might want to start with a fresh install of windows.
Then get all the proper drivers.
Test.
i have reinstall my windows and install all the driver so far haven't got a bsod but i still got WHE error id 19 on event logger like this
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Unknown Error Source
Error Type: Cache Hierarchy Error
Processor APIC ID: 7

The details view of this entry contains further information.

and here is the detail view
-System

-Provider
[ Name] Microsoft-Windows-WHEA-Logger
[ Guid] {c26c4f3c-3f66-4e99-8f8a-39405cfed220}

EventID19

Version0

Level3

Task0

Opcode0

Keywords0x8000000000000000

-TimeCreated
[ SystemTime] 2022-06-19T19:15:26.5476596Z

EventRecordID1035

-Correlation
[ ActivityID] {12abb783-a3bf-41c0-bf0c-7862fad5daf0}

-Execution
[ ProcessID] 3336
[ ThreadID] 12824

ChannelSystem

ComputerDESKTOP-PHP1BUP

-Security
[ UserID] S-1-5-19

-EventData

ErrorSource0

ApicId7

MCABank0

MciStat0x9400004000050150

MciAddr0x1f8037de08c6f

MciMisc0x0

ErrorType9

TransactionType0

Participation256

RequestType5

MemorIO256

MemHierarchyLvl0

Timeout256

OperationType256

Channel256

Length936

RawData435045521002FFFFFFFF03000200000002000000A8030000190F1300130616140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B248949139377F4BA8F1E0062805C2A3DA5E437DFF83D80100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000200000000000000000000000000000000000000000000007F01000000000000000201030000000055060A00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000070000000000000000000000000000000000000000000000000000000000000000000000000000000700000000000000070000000000000055060A0000081007BFFBFA7FFFFBEBBF0000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F001400000000006F8CE07D03F80100000000000000000000000000000000000000000000000000020000000100000039DE02EE1084D80107000000000000000000000000000000000000000000000050010500400000946F8CE07D03F80100000000000000000000000000070000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 

fidham98

Honorable
Dec 25, 2015
10
0
10,510
0
i have reinstall my windows and install all the driver so far haven't got a bsod but i still got WHE error id 19 on event logger like this
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Unknown Error Source
Error Type: Cache Hierarchy Error
Processor APIC ID: 7

The details view of this entry contains further information.

and here is the detail view
-System

-Provider
[ Name]Microsoft-Windows-WHEA-Logger
[ Guid]{c26c4f3c-3f66-4e99-8f8a-39405cfed220}

EventID19

Version0

Level3

Task0

Opcode0

Keywords0x8000000000000000

-TimeCreated
[ SystemTime]2022-06-19T19:15:26.5476596Z

EventRecordID1035

-Correlation
[ ActivityID]{12abb783-a3bf-41c0-bf0c-7862fad5daf0}

-Execution
[ ProcessID]3336
[ ThreadID]12824

ChannelSystem

ComputerDESKTOP-PHP1BUP

-Security
[ UserID]S-1-5-19

-EventData

ErrorSource0

ApicId7

MCABank0

MciStat0x9400004000050150

MciAddr0x1f8037de08c6f

MciMisc0x0

ErrorType9

TransactionType0

Participation256

RequestType5

MemorIO256

MemHierarchyLvl0

Timeout256

OperationType256

Channel256

Length936

RawData435045521002FFFFFFFF03000200000002000000A8030000190F1300130616140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B248949139377F4BA8F1E0062805C2A3DA5E437DFF83D80100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000200000000000000000000000000000000000000000000007F01000000000000000201030000000055060A00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000070000000000000000000000000000000000000000000000000000000000000000000000000000000700000000000000070000000000000055060A0000081007BFFBFA7FFFFBEBBF0000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F001400000000006F8CE07D03F80100000000000000000000000000000000000000000000000000020000000100000039DE02EE1084D80107000000000000000000000000000000000000000000000050010500400000946F8CE07D03F80100000000000000000000000000070000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Bump. Any suggestion what might cause this?
 
looks like bios version 2.30 has been removed from the vendor website.
the last released versions is 2.20 I would down grade the bios back to 2.20 version.

i would also remove the overclock driver
RTCore64.sys Thu Jun 18 04:55:42 2020
until you get the system stable. (overclock drivers get the blame for problems like this)
you can use microsoft autoruns64 to disable or remove the driver.
Autoruns for Windows - Windows Sysinternals | Microsoft Docs


since you found this in the log Cache Hierarchy Error
you might consider running prime95 to confirm your cpu is ok.
(you would also would want to reset the bios to defaults or make a change and change it back and save results,
you might want to turn off bios functions that change the speed of a CPU. (any turbo or speed step functions)

- make sure you apply microsoft windows updates so it updates the dll file that knows about the various bugs in your cpu and applies the CPU microcode patch if your BIOS has not been patched.


ASRock > B560M Pro4

Error : Unknown (Proc 0 Bank 0)
Status : 0x0000000000000000

2: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.3, DMIVersion 0, Size=3240]
BiosMajorRelease = 5
BiosMinorRelease = 19
BiosVendor = American Megatrends International, LLC.
BiosVersion = P2.30
BiosReleaseDate = 10/05/2021
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = B560M Pro4
SystemFamily = To Be Filled By O.E.M.
SystemVersion = To Be Filled By O.E.M.
SystemSKU = To Be Filled By O.E.M.
BaseBoardManufacturer = ASRock
BaseBoardProduct = B560M Pro4
BaseBoardVersion =
2: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 2904
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 165 Stepping 5
ProcessorNameString = REG_SZ Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz
Update Status = REG_DWORD 2
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD e200000000
2: kd> !sysinfo cpumicrocode
Initial Microcode Version: 000000e2:00000000
Cached Microcode Version: 000000e2:00000000
Processor Family: 06
Processor Model: a5
Processor Stepping: 05
 
Last edited:

fidham98

Honorable
Dec 25, 2015
10
0
10,510
0
looks like bios version 2.30 has been removed from the vendor website.
the last released versions is 2.20 I would down grade the bios back to 2.20 version.

i would also remove the overclock driver
RTCore64.sys Thu Jun 18 04:55:42 2020
until you get the system stable. (overclock drivers get the blame for problems like this)
you can use microsoft autoruns64 to disable or remove the driver.
Autoruns for Windows - Windows Sysinternals | Microsoft Docs


since you found this in the log Cache Hierarchy Error
you might consider running prime95 to confirm your cpu is ok.
(you would also would want to reset the bios to defaults or make a change and change it back and save results,
you might want to turn off bios functions that change the speed of a CPU. (any turbo or speed step functions)

- make sure you apply microsoft windows updates so it updates the dll file that knows about the various bugs in your cpu and applies the CPU microcode patch if your BIOS has not been patched.


ASRock > B560M Pro4

Error : Unknown (Proc 0 Bank 0)
Status : 0x0000000000000000

2: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.3, DMIVersion 0, Size=3240]
BiosMajorRelease = 5
BiosMinorRelease = 19
BiosVendor = American Megatrends International, LLC.
BiosVersion = P2.30
BiosReleaseDate = 10/05/2021
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = B560M Pro4
SystemFamily = To Be Filled By O.E.M.
SystemVersion = To Be Filled By O.E.M.
SystemSKU = To Be Filled By O.E.M.
BaseBoardManufacturer = ASRock
BaseBoardProduct = B560M Pro4
BaseBoardVersion =
2: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 2904
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 165 Stepping 5
ProcessorNameString = REG_SZ Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz
Update Status = REG_DWORD 2
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD e200000000
2: kd> !sysinfo cpumicrocode
Initial Microcode Version: 000000e2:00000000
Cached Microcode Version: 000000e2:00000000
Processor Family: 06
Processor Model: a5
Processor Stepping: 05
i already run prime 95 2 times and found no error , bios setting was all at default too, and about the bios version there is a 2.30 version in this link bios.

how do i apply microcode patch on the bios?
can mixed ram kit trigger this issue?sorry if im asking too much im new to this
 
Last edited:
i already run prime 95 2 times and found no error , bios setting was all at default too, and about the bios version there is a 2.30 version in this link bios.

how do i apply microcode patch on the bios?
can mixed ram kit trigger this issue?sorry if im asking too much im new to this
yes, i see the bios update. I think I made a typo when I looked it up before, looked at the wrong model.
microsoft installs a bios update when you do the windows update. I gets loaded at boot time in case you don't get a patch from the motherboard vendor.
you can get some errors from a mixed ram kit but you should not get this error. generally this error would be for cache ram inside the cpu.
there are various levels of cache that feed to the cpu cores. between each level of cache there is a bus that transfers the data, this is done by setting a voltage on the cpu package pins. The voltage is then converted to a frequency so level of the cache runs as the same speed as the connection. if the voltage is off then the data on the bus gets corrupted as it goes through the levels of the cache.
you might consider going into bios and turn off functions that change the cpu speeds in hopes to prevent this problem. IE turn off things like intel turbo, or intel speed step and run at a single speed and see if it helps.

normally, these voltages are tweaked over time and tuned for each motherboard by the motherboard vendor.
it is hard to debug this error since there are about 100 known bugs in the actual cpu and how it reports its hardware error codes.
(at least intel documents them and publishes the errata list for each cpu. AMD hides theirs)
 
Reactions: fidham98

fidham98

Honorable
Dec 25, 2015
10
0
10,510
0
yes, i see the bios update. I think I made a typo when I looked it up before, looked at the wrong model.
microsoft installs a bios update when you do the windows update. I gets loaded at boot time in case you don't get a patch from the motherboard vendor.
you can get some errors from a mixed ram kit but you should not get this error. generally this error would be for cache ram inside the cpu.
there are various levels of cache that feed to the cpu cores. between each level of cache there is a bus that transfers the data, this is done by setting a voltage on the cpu package pins. The voltage is then converted to a frequency so level of the cache runs as the same speed as the connection. if the voltage is off then the data on the bus gets corrupted as it goes through the levels of the cache.
you might consider going into bios and turn off functions that change the cpu speeds in hopes to prevent this problem. IE turn off things like intel turbo, or intel speed step and run at a single speed and see if it helps.

normally, these voltages are tweaked over time and tuned for each motherboard by the motherboard vendor.
it is hard to debug this error since there are about 100 known bugs in the actual cpu and how it reports its hardware error codes.
(at least intel documents them and publishes the errata list for each cpu. AMD hides theirs)
OK i will try it, if i disable the intel turbo thingy and the whe gone is it mean i got a faulty cpu?
i read about others who have the same problem like me, it might be voltage on cpu core to low.
and others say the whe log can be ingnored if it doesn't cause crashes and blue screen.
So far since im reinstall a fresh copy of windows my pc did not have a single BSOD .
only got a couple of whe log on the event viewer.
 
OK i will try it, if i disable the intel turbo thingy and the whe gone is it mean i got a faulty cpu?
i read about others who have the same problem like me, it might be voltage on cpu core to low.
and others say the whe log can be ingnored if it doesn't cause crashes and blue screen.
So far since im reinstall a fresh copy of windows my pc did not have a single BSOD .
only got a couple of whe log on the event viewer.
when I first looked at the error it looked like it was reported by source = microsoft and the error was correctable but it ended being converted to fatal error and a bug check was called.
you can run the intel cpu diagnostics and see if it reports some problem but it is not likely. I think it is just going to be some voltage needs to be set in some range.
so that your cpu does not have cache problems.

cpu's have massive amounts of code (logic) there are hundreds of bugs and everyone get the bugs. Some are so minor they are never fixed for the entire series of that CPU. others are fixed as new steps (versions) of the same cpu are released. The cpus are released then rounds of microcode updates are released to the motherboard vendors to work around bugs in the cpu. Then the motherboard vendor updates the bios (if they still support the board)
this process takes 6 to 9 months. many users do not install the bios updates and get bugchecks, windows error reporting sends the error info to microsoft and microsoft looks at the memory dump. Microsoft finds bugs and reports them to vendors and might also update the cpu dll that they load for each vendor. this CPU dll attempts to patch the microcode to work around certain bugs in the cpu.

my best guess would be that your issue is going to be related to some cpu voltage setting slightly out of range for what it should be (for your motherboard) rather than a actual bug in the CPU. But I do not know for sure.
I have had many people using amd CPUs just replace the cpu and all the problems went away. Only one time this happened with a intel cpu and it had failed the intel cpu diagnostics.
The Intel® Processor Diagnostic Tool Overview, Download, and...
I think this is a more basic functions test but you can run it.
 
Last edited:

fidham98

Honorable
Dec 25, 2015
10
0
10,510
0
when I first looked at the error it looked like it was reported by source = microsoft and the error was correctable but it ended being converted to fatal error and a bug check was called.
you can run the intel cpu diagnostics and see if it reports some problem but it is not likely. I think it is just going to be some voltage needs to be set in some range.
so that your cpu does not have cache problems.

cpu's have massive amounts of code (logic) there are hundreds of bugs and everyone get the bugs. Some are so minor they are never fixed for the entire series of that CPU. others are fixed as new steps (versions) of the same cpu are released. The cpus are released then rounds of microcode updates are released to the motherboard vendors to work around bugs in the cpu. Then the motherboard vendor updates the bios (if they still support the board)
this process takes 6 to 9 months. many users do not install the bios updates and get bugchecks, windows error reporting sends the error info to microsoft and microsoft looks at the memory dump. Microsoft finds bugs and reports them to vendors and might also update the cpu dll that they load for each vendor. this CPU dll attempts to patch the microcode to work around certain bugs in the cpu.

my best guess would be that your issue is going to be related to some cpu voltage setting slightly out of range for what it should be (for your motherboard) rather than a actual bug in the CPU. But I do not know for sure.
I have had many people using amd CPUs just replace the cpu and all the problems went away. Only one time this happened with a intel cpu and it had failed the intel cpu diagnostics.
The Intel® Processor Diagnostic Tool Overview, Download, and...
I think this is a more basic functions test but you can run it.
Yeah i already run that and its shows no error so i think i will just ignore it for now , my pc seems stable for now didnt have any crash nor bsod
 

ASK THE COMMUNITY

TRENDING THREADS