Windows 10: Frequent BSOD - WhoCrashed Pointing to hardware.sys primarily

I've been having pretty much daily and sometimes multiple times per day BSOD. Using WhoCrashed to analyze the crash dumps I get a report, but not much help in the way of what might actually be the issue. It seems to be pointing to RAM I think, but in all honesty I've thought NVMe and drivers at various points as well. I'm just going to list the dumps below, I really appreciate any input advice on this one, it's resulting in a few corrupt save files and I would love to get it fixed:


[COLOR=rgba17, 17, 17, 1]On Thu 4/1/2021 3:33:24 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\040121-6156-01.dmp
This was probably caused by the following module: [COLOR=rgba17, 17, 17, 1]hardware.sys[/COLOR] hardware
Bugcheck code: 0x1A 0x41792, 0xFFFFF43FFD7CEF88, 0x4000000000000, 0x0
Error: [COLOR=rgba17, 17, 17, 1]MEMORY_MANAGEMENT[/COLOR]
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: [COLOR=rgba17, 17, 17, 1]hardware.sys MEMORY_MANAGEMENT[/COLOR]

[/COLOR]

[COLOR=rgba17, 17, 17, 1]On Thu 4/1/2021 3:33:24 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: [COLOR=rgba17, 17, 17, 1]hardware.sys[/COLOR] hardware
Bugcheck code: 0x1A 0x41792, 0xFFFFF43FFD7CEF88, 0x4000000000000, 0x0
Error: [COLOR=rgba17, 17, 17, 1]MEMORY_MANAGEMENT[/COLOR]
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: [COLOR=rgba17, 17, 17, 1]hardware.sys MEMORY_MANAGEMENT[/COLOR]

[/COLOR]

[COLOR=rgba17, 17, 17, 1]On Thu 4/1/2021 11:24:08 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\040121-6375-01.dmp
This was probably caused by the following module: [COLOR=rgba17, 17, 17, 1]ntoskrnl.exe[/COLOR] nt+0x3F5C50
Bugcheck code: 0x1000007E 0xFFFFFFFFC0000005, 0xFFFFF80456A00EEF, 0xFFFFE2024231DD98, 0xFFFFE2024231D5D0
Error: [COLOR=rgba17, 17, 17, 1]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/COLOR]
file path: C:\Windows\system32\ntoskrnl.exe
product: [COLOR=rgba17, 17, 17, 1]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba17, 17, 17, 1]Microsoft Corporation[/COLOR]
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.

[/COLOR]

[COLOR=rgba17, 17, 17, 1]On Tue 3/30/2021 2:57:35 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\033021-6250-01.dmp
This was probably caused by the following module: [COLOR=rgba17, 17, 17, 1]hardware.sys[/COLOR] hardware
Bugcheck code: 0x1A 0x41792, 0xFFFFB6BFFD80CE88, 0x4000000000000, 0x0
Error: [COLOR=rgba17, 17, 17, 1]MEMORY_MANAGEMENT[/COLOR]
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: [COLOR=rgba17, 17, 17, 1]hardware.sys MEMORY_MANAGEMENT[/COLOR]

[/COLOR]

[COLOR=rgba17, 17, 17, 1]On Fri 3/26/2021 2:42:21 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\032621-8640-01.dmp
This was probably caused by the following module: [COLOR=rgba17, 17, 17, 1]ntoskrnl.exe[/COLOR] nt+0x3F5C50
Bugcheck code: 0x154 0xFFFF8C0F915B0000, 0xFFFFDE0CBA891830, 0x1, 0x0
Error: [COLOR=rgba17, 17, 17, 1]UNEXPECTED_STORE_EXCEPTION[/COLOR]
file path: C:\Windows\system32\ntoskrnl.exe
product: [COLOR=rgba17, 17, 17, 1]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba17, 17, 17, 1]Microsoft Corporation[/COLOR]
description: NT Kernel & System
Bug check description: This indicates that the store component caught an unexpected exception.
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.

[/COLOR]

[COLOR=rgba17, 17, 17, 1]On Thu 3/18/2021 5:05:56 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031821-6421-01.dmp
This was probably caused by the following module: [COLOR=rgba17, 17, 17, 1]ntoskrnl.exe[/COLOR] nt+0x3F5C50
Bugcheck code: 0x1A 0x41202, 0xFFFF863FFAF523C8, 0xFFFBFFFF00000420, 0xFFFF9B034E6B8B00
Error: [COLOR=rgba17, 17, 17, 1]MEMORY_MANAGEMENT[/COLOR]
file path: C:\Windows\system32\ntoskrnl.exe
product: [COLOR=rgba17, 17, 17, 1]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba17, 17, 17, 1]Microsoft Corporation[/COLOR]
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
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. [/COLOR]

:)

 

QCAMAIN1.SYS CAUSING BSOD

This was probably caused by the following module:
qcamain1.sys (Qcamain10x64+0x108678)

Bugcheck code: 0x1D3 (0x333, 0x0, 0x0, 0x0)

Error: CUSTOM_ERROR

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: qcamain1.sys .

Google query: qcamain1.sys CUSTOM_ERROR

Using WhoCrashed I found this thread: QCAMAIN1.SYS CAUSING BSOD (Code 37 Error) however without
solution, locked.

I did get BSOD almost everytime I moved the laptop.

This worked for me:

unscrew wifi module, push a little into the socket. Screw in. DONE

 

Frequent BSODs - L1C63x64.sys


Hi bobjbain,

Welcome to the 10forums.

Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Alcohol120% and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window.


Please check Qualcomm or Atheros for driver updates.
The Qualcomm Atheros network driver is old and needs updating
Code:

Code:

1: kd> lmvm L1C63x64 start             end                 module name fffff801`baca0000 fffff801`bacc2000   L1C63x64 T (no symbols)                Loaded symbol image file: L1C63x64.sys     Image path: \SystemRoot\System32\drivers\L1C63x64.sys     Image name: L1C63x64.sys     Timestamp:        Mon Apr 01 05:15:17 2013 (5158FBC5)     CheckSum:         000245C4     ImageSize:        00022000     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update links for drivers:
AMD - amd_xata and amd_sata
Check iTunes for software updates - GEARAspiWDM
Realtek - RtNdPt60
VMware software or VMWare site - vmwvusb, hcmon
Motherboard manufacturer - stwrt64 (audio)
Citrix

Old drivers
Code:

Code:

PxHlpa64	fffff801`b78f0000	fffff801`b78fb380	Fri Feb 02 22:24:22 2007 (45c3ac06)	0001320c		PxHlpa64.sys RtNdPt60	fffff801`b9550000	fffff801`b955c000	Mon Jul 20 04:27:32 2009 (4a63d614)	0000ceac		RtNdPt60.sys vmwvusb	fffff801`bae70000	fffff801`bae7f000	Sat Jul 24 04:30:08 2010 (4c4a5030)	0000ea69		vmwvusb.sys GEARAspiWDM	fffff801`bad70000	fffff801`bad76c00	Thu May 03 21:56:17 2012 (4fa2e2e1)	00008963		GEARAspiWDM.sys amd_sata	fffff801`b7770000	fffff801`b778d000	Fri Nov 30 10:00:42 2012 (50b875ba)	0001959b		amd_sata.sys amd_xata	fffff801`b7810000	fffff801`b781a000	Fri Nov 30 10:00:46 2012 (50b875be)	00010bf8		amd_xata.sys L1C63x64	fffff801`baca0000	fffff801`bacc2000	Mon Apr 01 05:15:17 2013 (5158fbc5)	000245c4	None	L1C63x64.sys hcmon	fffff801`b8ee0000	fffff801`b8ef1000	Tue Aug 06 03:10:44 2013 (52004d14)	00016f0e		hcmon.sys stwrt64	fffff801`bb000000	fffff801`bb08c000	Fri Aug 16 12:26:26 2013 (520dfe52)	0008bd1c		stwrt64.sys dnelwf64	fffff801`b8970000	fffff801`b8995000	Thu Oct 03 05:45:14 2013 (524ce84a)	00021cb3		dnelwf64.sys

AMD Overdrive driver, known for causing BSOD's.
Recommended to remove the software and driver.
Code:

Code:

AODDriver2 c:\program files\ati technologies\ati.ace\fuel\amd64\aoddriver2.sys

 

dxgmms2.sys BSOD

Hello,

A while back, my computer lost power while it was installing windows updates. Since then, I've had BSODs every couple days, with various errors pointing to a driver error. These were annoying, but manageable. I tried a few basic troubleshooting steps, like
using a removal tool for my graphics card drivers and reinstalling, but I didn't do much else.

The last couple days, the BSOD rate has ramped up, and I started seeing "dxgmms2.sys" get listed in the BSODs, which is relatively new.

I followed the instructions
here.

And here are my dmp files resulting from that:
https://1drv.ms/u/s!Au4wk9mJt6sJgcFgkEXA4rOFod4-cg?e=wIzEMq

Thanks.