BSOD on restart loop

[VAData]

Since this morning I have been experiencing BSOD after BSOD after BSOD. System gets bsod then restarts, loads windows then gets bsod again and again.
I managed to boot in recovery mode and ran whocrashed, which yielded the following results:
System Information (local)

Computer name: DESKTOP-FNR8PRL
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., PRIME X370-PRO
CPU: AuthenticAMD AMD Ryzen 7 1700X Eight-Core Processor AMD586, level: 23
16 logical processors, active mask: 65535
RAM: 34284154880 bytes total



Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 30.04.2017 12:29:46 your computer crashed
crash dump file: C:\WINDOWS\Minidump\043017-7906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x19 (0x20, 0xFFFFCD07F29D0000, 0xFFFFCD07F29D0EA0, 0x5EA0200)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 30.04.2017 12:29:46 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x81EAE)
Bugcheck code: 0x19 (0x20, 0xFFFFCD07F29D0000, 0xFFFFCD07F29D0EA0, 0x5EA0200)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys .
Google query: nvlddmkm.sys BAD_POOL_HEADER



On Sun 30.04.2017 10:14:00 your computer crashed
crash dump file: C:\WINDOWS\Minidump\043017-7515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1A (0x61941, 0x1C619A00FF0, 0xD, 0xFFFFA9008B505B00)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 30.04.2017 10:10:57 your computer crashed
crash dump file: C:\WINDOWS\Minidump\043017-10203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1A (0x41201, 0xFFFF8681D01C0400, 0x35372E3734342033, 0xFFFF8C8E4DE7C130)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Do you have idea what might be the problem?
I tried sfc scannow, nothing was found.

 

[johnbl]

-I would make sure you have the latest BIOS update to support your new CPU
and make sure you install all of latest motherboard drivers from your motherboard vendor.

last bios update was 2017/04/10 to fix cpu microcode for the new cpu
https://www.asus.com/us/Motherboards/PRIME-X370-PRO/HelpDesk_Download/

if you still get the problems after you update, you have to change the memory dump type to kernel, then run verifier to force the system to bugcheck when a driver writes outside of its memory area.
guessing the update motherboard audio driver will fix several of the bugchecks, and the updated BIOS would fix 2 of them.

if you get a new bugcheck after this, put the memory dump on a server, share it for public access and post a link.