There are 2 files in minidump folder.. I used who crashed and I'll write what came up.. Also these files showed up in the Dump Files Tab
http://prntscr.com/kaq65b
System Information (local)
--------------------------------------------------------------------------------
Computer name: JOHN
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\WINDOWS
Hardware: AB350-Gaming 3, Gigabyte Technology Co., Ltd., AB350-Gaming 3-CF
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor AMD586, level: 23
12 logical processors, active mask: 4095
RAM: 8537964544 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Wed 25/07/2018 10:50:57 πμ your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072518-5828-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF80677AEFE1D)
Bugcheck code: 0xD1 (0x200000, 0x2, 0x1, 0xFFFFF80677AEFE1D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 398.36
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 398.36
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 (NVIDIA Windows Kernel Mode Driver, Version 398.36 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 25/07/2018 10:42:18 πμ your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072518-7656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198430)
Bugcheck code: 0xD1 (0xFFFFF80220917120, 0x2, 0x0, 0xFFFFF802208596BB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 398.36 , NVIDIA Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.