Windows 10: Windows BSODs; Chrome, Firefox, Discord, and Slack crash frequently

I have reformatted and reinstalled Windows 10 with synced configurations turned off; used the memory scan utility; used the disk scan utility; checked my hardware and cleaned it; re-seated my RAM sticks, reset BIOS, and the problem continues with no answers. I get a BSOD every couple hours, a couple times a day. It's been happening for a couple months.

I have crash dump reports: https://drive.google.com/file/d/1QdEaKM8lDH5JXPSewW2yAk_2hvD3PME4/view?usp=sharing

Please help me determine whether this is hardware-related or not :-


Dump summary from WhoCrashed:

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

On Mon 12/7/2020 4:34:22 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120720-5468-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0x21 0xFFFFA30A21513300, 0x2, 0xFFFFFFFFFFFFFFFF, 0xFFFFFFFFFFFA2F0B
Error: QUOTA_UNDERFLOW
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 quota charges have been mishandled by returning more quota to a particular block than was previously charged.
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 12/7/2020 4:34:22 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+0x5F3A9
Bugcheck code: 0x21 0xFFFFA30A21513300, 0x2, 0xFFFFFFFFFFFFFFFF, 0xFFFFFFFFFFFA2F0B
Error: QUOTA_UNDERFLOW
Bug check description: This indicates that quota charges have been mishandled by returning more quota to a particular block than was previously charged.
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 12/6/2020 5:51:21 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120620-5296-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0x1000007E 0xFFFFFFFFC0000005, 0xFFFFF8026BCA0F41, 0xFFFFB609699AECF8, 0xFFFFE2008ABFC920
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 12/6/2020 12:46:14 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120620-4781-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0x3B 0xC0000005, 0xFFFFF80038146B12, 0xFFFF818CDEE96720, 0x0
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 12/6/2020 7:13:40 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120620-4968-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0xC2 0xD, 0xFFFFA480DB0C1711, 0x6D4E6F, 0xF8BD15562F806B71
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 Sat 12/5/2020 8:36:51 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120520-4828-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0xEF 0xFFFFA70D86555080, 0x0, 0x0, 0x0
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


-semicomatose

:)