Windows 10: Constantly BSOD:MEMORY MANAGEMENT& SYSTEM_THREAD_EXCEPTION not handled

I constantly have BSOD on my hp laptop and its getting worse (1 BSOD every day). I did not make any changes in the hardware and the problem persists. Here is the analysis from whoCrashed:

System Information (local)
________________________________________

Computer name: LAPTOP-OK443G7O
Windows version: Windows 10, 10.0, version 2004, build: 19041
Windows dir: C:\WINDOWS
Hardware: HP Pavilion Laptop 15-cs2xxx, HP, 84C1
CPU: GenuineIntel Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz 8664, level: 6
8 logical processors, active mask: 255
RAM: 17061695488 bytes (15,9GB)

________________________________________
Crash Dump Analysis
________________________________________

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Thu 18/03/2021 13:27:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031821-11250-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFF580E7A54930, 0x10000, 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/03/2021 09:52:59 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031721-13625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C50)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8051CA60057, 0xFFFFB802C26E7118, 0xFFFFB802C26E6950)
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.

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

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

Here are the links for the .dpm files:

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.


Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Thank you for your help.

:)

 

BSOD- memory management

Upon checking the dump file, the issue is being caused by ntoskrnl.exe. Ntoskrnl.exe is the one responsible for memory management that is why you're having the Memory Management error. We suggest that you follow the steps found in the link that we provided
in our last reply to resolve the issue. Please take note that if you're overclocking your processor or video card, kindly reset their settings to default.

Let us know the outcome after performing the provided steps.

 

IRQ memory BSODS, device manager, memory range?

The only time I've seen that type of BSOD for myself is when I fried the PCI-e slots on my Striker 2 board... There wasn't anything that I could do, try and rma and go on.. I would suggest the steps that MilkyWay has said.. But, if you really don't know much about Bios's... I wouldn't play with Irq's... That can mess up everything on your board. USB, ethernet, ram, chip... But, that's just me on playing with irq's... To much of a hassle IMHO..

 

Memory management BSOD

I just built a new PC from the ground up. I’ve been getting a BSOD memory managment error constantly. I’ve run sfc scannow, the windows memory check program, i’ve made sure ALL drivers are current. Through all of this i have noticed that this BSOD is happening
when I am downloading. Happened while I was creating a windows10 ISO with the windows download tool, it happened while I was running windows update, and it happened while I was downloading one of my PC games. I can’t figire the problem out for the life of
me.