F5F Stay Refreshed Hardware Desktop WHEA LOGGER initiating random restarts

WHEA LOGGER initiating random restarts

WHEA LOGGER initiating random restarts

J
JohannesTJ
Junior Member
7
01-19-2016, 01:30 AM
#1
Hello everyone, I recently upgraded my system with a new motherboard (ASUS PRIME B450M-A), processor (Ryzen 5 3500X), and modern components. Inside, the old graphics card (AMD Radeon R9 390) is still present. I installed new RAM—two 8GB DDR4 KINGSTON FURY modules at 3200MHz—and upgraded the power supply to a quiet system model with 9,700W capacity. The SSD is a 240GB Kingston and an 1TB HDD.

When trying to run WARZONE, the PC keeps resetting during gameplay. I checked forums and found many users reporting issues with the Ryzen 5 and ASUS board. A recent BIOS update (version 3211) helped for some, but it didn’t resolve the problem for me. In the Event Viewer, there’s a warning about a hardware error (WHEA-Logger ID:18). Someone mentioned it might be related to the processor or cache issues. Any tips would be greatly appreciated! Thanks.
J
JohannesTJ
01-19-2016, 01:30 AM #1

Hello everyone, I recently upgraded my system with a new motherboard (ASUS PRIME B450M-A), processor (Ryzen 5 3500X), and modern components. Inside, the old graphics card (AMD Radeon R9 390) is still present. I installed new RAM—two 8GB DDR4 KINGSTON FURY modules at 3200MHz—and upgraded the power supply to a quiet system model with 9,700W capacity. The SSD is a 240GB Kingston and an 1TB HDD.

When trying to run WARZONE, the PC keeps resetting during gameplay. I checked forums and found many users reporting issues with the Ryzen 5 and ASUS board. A recent BIOS update (version 3211) helped for some, but it didn’t resolve the problem for me. In the Event Viewer, there’s a warning about a hardware error (WHEA-Logger ID:18). Someone mentioned it might be related to the processor or cache issues. Any tips would be greatly appreciated! Thanks.

I
iTzPandaNuss
Member
144
01-19-2016, 02:45 AM
#2
As discussed in our PM chat, sharing a complete crash dump could help someone understand what happened.
I
iTzPandaNuss
01-19-2016, 02:45 AM #2

As discussed in our PM chat, sharing a complete crash dump could help someone understand what happened.

O
Orangespider2
Junior Member
7
01-19-2016, 03:40 AM
#3
I understand those crash reports.
O
Orangespider2
01-19-2016, 03:40 AM #3

I understand those crash reports.

C
cmyoungblood13
Junior Member
5
01-23-2016, 10:16 PM
#4
I receive the files you mentioned.
C
cmyoungblood13
01-23-2016, 10:16 PM #4

I receive the files you mentioned.

F
173
01-24-2016, 05:17 AM
#5
We only require the mini summaries. The greater the quantity or value, the clearer the pattern will be.
F
firebuckler123
01-24-2016, 05:17 AM #5

We only require the mini summaries. The greater the quantity or value, the clearer the pattern will be.

T
Titow29
Member
154
01-25-2016, 07:02 PM
#6
The system detected a serious issue with its configuration. It suggests the hive loaded by the OS loader might be damaged. This is rare because the loader verifies hives for corruption. It may also point to missing or altered critical registry entries—possibly due to someone misusing regedt32. Restarting from LastKnownGood could resolve it, but persistent registry changes may require a full reinstall or using an Emergency Repair Disk.
T
Titow29
01-25-2016, 07:02 PM #6

The system detected a serious issue with its configuration. It suggests the hive loaded by the OS loader might be damaged. This is rare because the loader verifies hives for corruption. It may also point to missing or altered critical registry entries—possibly due to someone misusing regedt32. Restarting from LastKnownGood could resolve it, but persistent registry changes may require a full reinstall or using an Emergency Repair Disk.