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.

Hello bpat74 and welcome to TenForums

If you check the posting instructions at the top of the page you will see that we require a set of logfiles so that we can explore the reasons for your crashes. Please provide these they will automatically include the dump files so you do not need to send them separately.

We analyse the files by hand and do not reply on programs like Who Crashed - these are unreliable and can only solve the simplest of crashes which involve obviously faulty drivers.

Already, from the info you have provided we can see that hardware failure is likely to be involved.

Hello philc43 and thank you very much for your reply! I am so sorry but i haven't seen the posting instructions. So, used the Log Collector and i have uploaded the results. Here is the link:
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Thank you again!

The crash dumps reveal memory address problems such as possible one-bit corruption.

It is possible your memory is slightly overclocked. I'm guessing it has always been set like this but please confirm if you have tweaked the clock speed up to 2667Mhz from the recommended 2400MHz. If so I would reduce it to 2400MHz.

Please also test the memory with memtest86. This program will run for 4 passes and perform several tests. Please let it complete the 4 passes and then set it going for another 4 passes to thoroughly test the RAM. If you get any errors you can stop the test because it will indicate that the RAM is faulty and needs replacing.

Hello and thank you again. No, i haven't touched the RAM clock speed, i guess it was initially set at this clock speed. Can i run Windows Memory Diagnostic alternatively? So, you think it is a hardware issue and something related to faulty driver or software issue?
Thank you.

Windows Memory Diagnostic is not so useful as a thorough test of the RAM, there are times I have seen this test pass and Memtest86 fail. Until I see the data on the RAM tests I am keeping an open mind on the cause.

I 've never used memtest86 , is it 100% safe? I imagine it stresses RAM to the limit, so is there a risk not being able to boot to windows after the test finishes?

The memtest86 test has been run by many many people on this site and other BSOD sites too. I have not come across a single instance of a system failing as a result of running the test.

Ok thank you very much!

Hello again, it was about 10 or more days that i did not have any BSOD but the problem returned... I have BSOD almost every day now.. So, i ran Windows Memory Diagnostic Tool and the result is: "The Windows Memory Diagnostic tested the computer's memory and detected hardware errors. To identify and repair these problems, contact the computer manufacturer".
I share here the event viewer logs with the link below. It's not clear what kind of problem RAM has. Do i have to run memtest86 as you mentioned above or there is nothing more memtest86 can show? If it is necessary, i 'll run memtest and post the results here. Do you think that i have to replace my RAM? Thank you very much for your help.

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