System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-35D1PBG
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\Windows
Hardware: Z370 AORUS Gaming 5, Gigabyte Technology Co., Ltd., Z370 AORUS Gaming 5-CF
CPU: GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 17122979840 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sun 08/07/2018 16:46:08 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070818-8000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198430)
Bugcheck code: 0x34 (0x51352, 0xFFFFCA8CC898F2F8, 0xFFFFCA8CC898EB40, 0xFFFFF8013D25D7AE)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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 08/07/2018 16:46:08 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x4422)
Bugcheck code: 0x34 (0x51352, 0xFFFFCA8CC898F2F8, 0xFFFFCA8CC898EB40, 0xFFFFF8013D25D7AE)
Error: CACHE_MANAGER
Bug check description: This indicates that a problem occurred in the file system's cache manager.
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 08/07/2018 16:36:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070818-7343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3A950)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80015450950, 0xFFFF87818E737748, 0xFFFF87818E736F90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 08/07/2018 16:24:51 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070818-7296-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFCD3FFAF49448, 0x400000000000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 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: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT



On Sun 08/07/2018 16:13:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070818-10031-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF805A461A755)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF805A461A755, 0xFFFF9007A1847448, 0xFFFF9007A1846C90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Sun 08/07/2018 16:10:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070818-7296-02.dmp
This was probably caused by the following module: storport.sys (0xFFFFF805C5F56D93)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF805C5F56D93, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 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:

hardware.sys

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.