J
Joseph_CB
Guest
I've been getting a lot of bsod's, so I thought maybe reinstalling windows might fix it, but it didn't. As it got worse, my games started crashing, saying that some of its files are corrupt. I've ran the memory diagnostic tool from windows since I can't use memtest86, and it showed up as having no errors. I downloaded WhoCrashed and this is what showed up.
System Information (local)
Computer name: DESKTOP-SM70JNN
Windows version: Windows 10, 10.0, version 2004, build: 19041
Windows dir: C:\Windows
Hardware: MS-7A38, Micro-Star International Co., Ltd., B450M PRO-VDH MAX (MS-7A38)
CPU: AuthenticAMD AMD Ryzen 3 3200G with Radeon Vega Graphics 8664, level: 23
4 logical processors, active mask: 15
RAM: 17125634048 bytes (15.9GB)
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 Fri 19/02/2021 10:18:33 am your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021921-6500-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFEA0000170CE0, 0x800000000000, 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 Thu 18/02/2021 6:53:06 pm your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021821-7343-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFBE00001A6CE0, 0x200000000000, 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 Wed 17/02/2021 7:12:37 pm your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021721-7515-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFED800032BCA0, 0x200000000000, 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 Tue 16/02/2021 7:15:01 pm your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021621-6484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x32A671)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80121B2A671, 0xFFFFFD052BCE6868, 0xFFFFFD052BCE60A0)
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 Mon 15/02/2021 8:06:09 pm your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021521-8578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0xBE (0xFFFFAE400B67DBA8, 0x8A00000000200121, 0xFFFF8704DAA96DD0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Mon 15/02/2021 6:55:34 pm 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+0x6364E)
Bugcheck code: 0x1A (0x41792, 0xFFFF8680CE49FC20, 0xC00000000000, 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).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\LiveKernelReports\PoW32kWatchdog-20210215-1630.dmp
Conclusion
7 crash dumps have been found and analyzed. Only 6 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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.
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.
Continue reading...
System Information (local)
Computer name: DESKTOP-SM70JNN
Windows version: Windows 10, 10.0, version 2004, build: 19041
Windows dir: C:\Windows
Hardware: MS-7A38, Micro-Star International Co., Ltd., B450M PRO-VDH MAX (MS-7A38)
CPU: AuthenticAMD AMD Ryzen 3 3200G with Radeon Vega Graphics 8664, level: 23
4 logical processors, active mask: 15
RAM: 17125634048 bytes (15.9GB)
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 Fri 19/02/2021 10:18:33 am your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021921-6500-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFEA0000170CE0, 0x800000000000, 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 Thu 18/02/2021 6:53:06 pm your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021821-7343-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFBE00001A6CE0, 0x200000000000, 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 Wed 17/02/2021 7:12:37 pm your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021721-7515-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFED800032BCA0, 0x200000000000, 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 Tue 16/02/2021 7:15:01 pm your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021621-6484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x32A671)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80121B2A671, 0xFFFFFD052BCE6868, 0xFFFFFD052BCE60A0)
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 Mon 15/02/2021 8:06:09 pm your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021521-8578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0xBE (0xFFFFAE400B67DBA8, 0x8A00000000200121, 0xFFFF8704DAA96DD0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Mon 15/02/2021 6:55:34 pm 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+0x6364E)
Bugcheck code: 0x1A (0x41792, 0xFFFF8680CE49FC20, 0xC00000000000, 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).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\LiveKernelReports\PoW32kWatchdog-20210215-1630.dmp
Conclusion
7 crash dumps have been found and analyzed. Only 6 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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.
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.
Continue reading...