F5F Stay Refreshed Hardware Desktop What causes these mistakes and how should you handle them?

What causes these mistakes and how should you handle them?

What causes these mistakes and how should you handle them?

M
MineWorst
Junior Member
Find
22
02-20-2020, 05:46 PM
#1
hello everyone, my brother recently found his pc restarting unexpectedly without any BSOD. when i checked his event viewer, there were some WHEA errors, specifically ID 18. his specs are: 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. he also has a kingston 480 ssd seagate 1tb hdd rx 570 gigabyte, gaming 4gb, and pylon 750w bronze psu. so far i've done: ran sfc/scannow with no issues, memtest86 with no errors, and updated the latest chipset from amd's website for the b550m.
Reply
Reply
M
MineWorst
02-20-2020, 05:46 PM #1

hello everyone, my brother recently found his pc restarting unexpectedly without any BSOD. when i checked his event viewer, there were some WHEA errors, specifically ID 18. his specs are: 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. he also has a kingston 480 ssd seagate 1tb hdd rx 570 gigabyte, gaming 4gb, and pylon 750w bronze psu. so far i've done: ran sfc/scannow with no issues, memtest86 with no errors, and updated the latest chipset from amd's website for the b550m.

Reply
Reply
C
cursino_8
Member
Find
226
02-20-2020, 06:33 PM
#2
It reboots in an orderly manner or it shows a sudden black screen with the BIOS splash-screen.
Reply
Reply
C
cursino_8
02-20-2020, 06:33 PM #2

It reboots in an orderly manner or it shows a sudden black screen with the BIOS splash-screen.

Reply
Reply
O
OKNK
Member
Find
231
02-20-2020, 07:02 PM
#3
Screen goes dark instantly, then displays a bios splash.
Reply
Reply
O
OKNK
02-20-2020, 07:02 PM #3

Screen goes dark instantly, then displays a bios splash.

Reply
Reply
X
xSALTEDx
Junior Member
Find
6
03-06-2020, 10:56 PM
#4
No, there are no O.C. components present. XMP and DOCP were not included.
Reply
Reply
X
xSALTEDx
03-06-2020, 10:56 PM #4

No, there are no O.C. components present. XMP and DOCP were not included.

Reply
Reply
X
xPenguinx
Junior Member
Find
11
03-18-2020, 03:51 PM
#5
XMP settings applied to the RAM modules. Processor and GPU remain unmodified. I've confirmed stability with no issues from running MemTest86.
Reply
Reply
X
xPenguinx
03-18-2020, 03:51 PM #5

XMP settings applied to the RAM modules. Processor and GPU remain unmodified. I've confirmed stability with no issues from running MemTest86.

Reply
Reply
Z
Zodzon123
Junior Member
Find
16
03-24-2020, 03:05 AM
#6
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.
Reply
Reply
Z
Zodzon123
03-24-2020, 03:05 AM #6

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.

Reply
Reply
D
Dinomatt98
Junior Member
Find
17
03-29-2020, 09:45 AM
#7
I just completed it once; the entire test took nearly an hour. I’ll try running it again today to check if everything works fine.
Reply
Reply
D
Dinomatt98
03-29-2020, 09:45 AM #7

I just completed it once; the entire test took nearly an hour. I’ll try running it again today to check if everything works fine.

Reply
Reply
E
Emir_05
Member
Find
55
03-31-2020, 03:27 AM
#8
Continued testing without any issues during the second run of MemTest86
Reply
Reply
E
Emir_05
03-31-2020, 03:27 AM #8

Continued testing without any issues during the second run of MemTest86

Reply
Reply
A
Andromith
Junior Member
Find
2
03-31-2020, 08:38 AM
#9
Observei um erro semelhante em minha configuração, mesmo fonte (WHEA-Logger) mas ID diferente (19). Abaixo estão alguns detalhes do meu problema: A mensagem que você viu muda porque diz sobre um erro de hardware que foi corrigido. No Windows, esse evento estava sendo registrado 2 a 3 vezes por segundo no log do sistema. Além disso, houve alguns travamentos do driver Nvidia (e recuperação) enquanto usava a janela do Hyper-V, mas minha jogabilidade não foi muito afetada. Desativar o D.O.C.P no BIOS resolveu o problema.
Sistema: AMD Ryzen 5 5600X, placa Asus TUF Gaming X570-PLUS/BR, Crucial Ballistix Sport LT, RGB, 32GB (2x16), 3600MHz, DDR4, CL16 - BL2K16G36C16U4RL, EVGA Nvidia 2080GTX Black.
Como você filtrou os logs nas imagens para mostrar apenas erros, talvez tenha algumas entradas do evento 19 também (categorizadas como avisos) com alguns eventos 18 graves de forma aleatória. Espero que você consiga corrigir isso também desativando o D.O.C.P no BIOS, para eliminar qualquer falha do processador e problemas de devolução.
Passo seguinte será tentar configurações de memória mais suaves manualmente no BIOS. Vou informar, mas provavelmente deixarei como está por alguns dias para garantir.
Correção: algumas erros de digitação.
Reply
Reply
A
Andromith
03-31-2020, 08:38 AM #9

Observei um erro semelhante em minha configuração, mesmo fonte (WHEA-Logger) mas ID diferente (19). Abaixo estão alguns detalhes do meu problema: A mensagem que você viu muda porque diz sobre um erro de hardware que foi corrigido. No Windows, esse evento estava sendo registrado 2 a 3 vezes por segundo no log do sistema. Além disso, houve alguns travamentos do driver Nvidia (e recuperação) enquanto usava a janela do Hyper-V, mas minha jogabilidade não foi muito afetada. Desativar o D.O.C.P no BIOS resolveu o problema.
Sistema: AMD Ryzen 5 5600X, placa Asus TUF Gaming X570-PLUS/BR, Crucial Ballistix Sport LT, RGB, 32GB (2x16), 3600MHz, DDR4, CL16 - BL2K16G36C16U4RL, EVGA Nvidia 2080GTX Black.
Como você filtrou os logs nas imagens para mostrar apenas erros, talvez tenha algumas entradas do evento 19 também (categorizadas como avisos) com alguns eventos 18 graves de forma aleatória. Espero que você consiga corrigir isso também desativando o D.O.C.P no BIOS, para eliminar qualquer falha do processador e problemas de devolução.
Passo seguinte será tentar configurações de memória mais suaves manualmente no BIOS. Vou informar, mas provavelmente deixarei como está por alguns dias para garantir.
Correção: algumas erros de digitação.

Reply
Reply
B
badwill911
Junior Member
Find
28
04-02-2020, 04:01 AM
#10
I faced a comparable issue on my z390 9900k system. It turned out the BIOS battery was deteriorating. Replaced it, reset the CMOS, and everything functioned normally again. I’d consider this solution before resorting to RMA. As noted, check if the problem resolves without enabling docp in RAM. Similar issues arose with XMP settings.
Reply
Reply
B
badwill911
04-02-2020, 04:01 AM #10

I faced a comparable issue on my z390 9900k system. It turned out the BIOS battery was deteriorating. Replaced it, reset the CMOS, and everything functioned normally again. I’d consider this solution before resorting to RMA. As noted, check if the problem resolves without enabling docp in RAM. Similar issues arose with XMP settings.

Reply
Reply