Is my memory faulty?

boostmeister

Reputable
Jul 27, 2015
10
0
4,510
I recently built a new computer, after playing games or even browsing the web my PC blue screens, or a chrome tab crashes. I ran WhoCrashed and I got this:

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

Computer name: DESKTOP-L16RF9H
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\Windows
Hardware: ASRock, B250M-HDV
CPU: GenuineIntel Intel(R) Pentium(R) CPU G4560 @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8556134400 bytes total




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

Crash dumps are enabled on your computer.

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

On Mon 7/2/2018 3:24:06 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070218-27781-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFF84BFFF31D148, 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 Mon 7/2/2018 3:24:06 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFF84BFFF31D148, 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 Mon 7/2/2018 3:22:00 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070218-26359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x558FF)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF806F83F4778, 0xFFFFF909166D85A8, 0xFFFFF909166D7DF0)
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 7/1/2018 11:48:40 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070118-26296-01.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR+0xA556)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8015252A9D9, 0xFFFFCF8C77067DD8, 0xFFFFCF8C77067620)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 7/1/2018 10:47:45 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070118-23750-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF804E5B6EFBE)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF804E5B6EFBE, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 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.

Does anyone know how I can fix this?