whea errors, why and what to do?

[squallypo]

hello guys, my brother recently noticed that he has his pc rebooting out of nowhere with no BSOD.

and it just happend that i came to check his event viewer and it has some WHEA errors some with id 18

these are his specs:

bios F11d

ryzen 5600x (stock settings)

cooler master cpu cooler hyper 212 black edition

aorus elite b550m motherboard

xpg spectrix d50 2x8 set to 3200mhz on bios.

kingston 480 ssd

seagate 1tb HDD

rx 570 gigabyte gaming 4gb

xpg pylon 750w bronze psu

 

things ive done so far:

ran sfc/ scannow with no errors.

ran memtest86 with no errors.

updated the latest chipset from amd website for the b550m

[Windows7ge]

In what manor does it reboot? A orderly reboot or a sudden black screen followed by the BIOS splash-screen?

[squallypo]

7 hours ago, Windows7ge said:

In what manor does it reboot? A orderly reboot or a sudden black screen followed by the BIOS splash-screen?

sudden black screen followed by bios splash screen.

[Windows7ge]

Any O.C. on any of the components? XMP/DOCP even?

[squallypo]

35 minutes ago, Windows7ge said:

Any O.C. on any of the components? XMP/DOCP even?

Just xmp profile on the rams, other than that no oc on the processor and the gpu, and as I said I already run s memtest86 with no errors as you can see.

[Windows7ge]

28 minutes ago, squallypo said:

Just xmp profile on the rams, other than that no oc on the processor and the gpu, and as I said I already run s memtest86 with no errors as you can see.

This is true but did you run it more than once? O.C.'s are never guaranteed and enabling XMP is technically overclocking. It might be stable 99% of the time but that other 1% is when the system crashes/reboots. I would try disabling it for a few days and seeing if it helps the situation.

[squallypo]

6 minutes ago, Windows7ge said:

This is true but did you run it more than once? O.C.'s are never guaranteed and enabling XMP is technically overclocking. It might be stable 99% of the time but that other 1% is when the system crashes/reboots. I would try disabling it for a few days and seeing if it helps the situation.

just ran it once, the whole test was almost an hour, ill do it again today just to see if it still goes okay.

 

[squallypo]

and still no errors while doing memtest86 for second time

[Murteira]

I noticed a similar error in my setup, same source (WHEA-Logger) but different ID (19).  As described below (sorry, Brazilian Portuguese)

Quote

 

Erro de hardware corrigido.

 

Relatado pelo componente: Núcleo do Processador
Origem do Erro: Unknown Error Source
Tipo de Erro: Bus/Interconnect Error
ID APIC do Processador: 0

 

 

Some facts about my issue:

• The message above differs from yours because it states a hardware error was detected but was also corrected.
• Windows was logging this event 2 to 3 times per second on my system event log.
• Besides some Nvidia driver crashes (and recovery) while using Hyper-V console window, my gamming was mostly unaffected.
• Disabling D.O.C.P in BIOS solved my problem.

 

My system:

• AMD Ryzen 5 5600X
• Asus TUF Gaming X570-PLUS/BR motherboard
• Crucial Ballistix Sport LT, RGB, 32GB (2x16), 3600MHz, DDR4, CL16 - BL2K16G36C16U4RL
• EVGA Nvidia 2080GTX Black

Since you filtered the log in your screenshots to only show errors, I guess maybe you have some of these Event 19 ones too (they are categorized as warnings) with some sporadically fatal Events 18 in the mix.

I really hope you get rid of it too by disabling D.O.C.P in the BIOS, so we rule out any Processor malfunction and RMA woes out of the question.  Next step is trying less agressive memory timmings/voltage manually in the BIOS.  I will let you guys know, but I will probably leave it as it is now for a couple days just to be sure.

 

Edit: typos

[m9x3mos]

I had a very similar problem on my z390 9900k system. Turned out the bios battery was starting to fail. Put a new one in, cleared the cmos, setup again and was working perfectly again. I would try that before going to rma things as a last ditch effort. And as mentioned, see if it goes away without docp being enabled on the ram. As with xmp on was the only time I had problems.