WHEA LOGGER, random restarts

[netmail8]

Hello guys,

I bought a new motherboard (ASUS PRIME B450M-A) and a new processor (Ryzen 5 3500x), inside is the old graphics (AMD Radeon R9 390), NEW RAM (2 X KINGSTON FURY 8GB DDR4, 3200MHz), new POWER SUPPLY (be quiet system power 9 700W ), KINGSTON SSD 240gb, hdd 1tb.

I tried to install WARZONE but the PC is constantly resetting when it enters the game. I read a ton of forums, the mass of the team has a problem with the Ryzen 5 and ASUS motherboard, most of the BIOS update helped (it came out a few days ago, version 3211), but to me it didn't.

In the Event Viewer for the above displays WHEA- Logger Event ID:18, ID 19 A fatal hardware error has occurred. Reported by component: Processor core Error source: Machine Check Exception Error type: Cache Hierarchy Error Processor APIC ID: 1 

Bios has been updated .... Does anyone have any suggestions? Thank you

[Middcore]

Like I said in our PM conversation, if you can post a full crashdump, someone may be able to interpret it. 

[Radium_Angel]

I can interpret those crash dumps.

[netmail8]

27 minutes ago, Radium_Angel said:

I can interpret those crash dumps.

i upload 1 memory.dmp and one mini dump

https://drive.google.com/drive/folders/1hdHI7RkcLFJ1WO4pu7fqV5hm72MP7yoQ?usp=sharing

[Radium_Angel]

Just now, netmail8 said:

i upload 1 memory.dmp and one mini dump

https://drive.google.com/drive/folders/1hdHI7RkcLFJ1WO4pu7fqV5hm72MP7yoQ?usp=sharing

The mini dumps are all I need. The more you have (or get) the better we can determine a pattern.

 

[Radium_Angel]

3 minutes ago, netmail8 said:

i upload 1 memory.dmp and one mini dump

https://drive.google.com/drive/folders/1hdHI7RkcLFJ1WO4pu7fqV5hm72MP7yoQ?usp=sharing

Here are the results of the mini dump. Not something I'd seen before:

 

BAD_SYSTEM_CONFIG_INFO (74)
Can indicate that the SYSTEM hive loaded by the osloader/NTLDR
was corrupt.  This is unlikely, since the osloader will check
a hive to make sure it isn't corrupt after loading it.
It can also indicate that some critical registry keys and values
are not present.  (i.e. somebody used regedt32 to delete something
that they shouldn't have)  Booting from LastKnownGood may fix
the problem, but if someone is persistent enough in mucking with
the registry they will need to reinstall or use the Emergency
Repair Disk.
Arguments:
 

BUGCHECK_CODE:  74

BUGCHECK_P1: 2

BUGCHECK_P2: ffff860e2403ea20

BUGCHECK_P3: 2

BUGCHECK_P4: ffffffffc000014c

ERROR_CODE: (NTSTATUS) 0xc000014c - {The Registry Is Corrupt}  The structure of one of the files that contains Registry data is corrupt, or the image of the file in memory is corrupt, or the file could not be recovered because the alternate copy or log was absent or corrupt.

___

 

Your system OS is corrected beyond repair, or the hard drive the OS is stored on is going bad, corrupting the OS in the process.