Hello, and welcome!
The first thing I notice, it's the first thing I look for TBH, is that you're using mismatched RAM. You have two sticks of Corsair Vengeance Pro 4GB DDR3 1866 MHZ (CMY8GX3M2A1866C9) and two sticks of Corsair Vengeance 4GB DDR3 1600 MHz (CMZ8GX3M2A1600C9). Not only are the clock speeds different but so are some of the timings. Mismatched RAM is a major cause of BSODs, crashes, and other problems. The first thing I'd suggest is that you remove one pair of RAM sticks and see whether it's stable on the other.
The other issue can be seen in the dumps, which are all identical. Also, they all fail with a 0x3B bugcheck code, not the 0x144 you mention in the title. All the dumps point strongly at the driver aswSP.sys, it appears in every call stack with an odd 'breakpoint reached' exception code...
Code:
FAILURE_BUCKET_ID: 0x3B_80000003_aswSP!unknown_function
This is a driver from the Avast! security product and the version you have installed is very old, dating from 2021...
Code:
2: kd> lmvm aswSP
Browse full module list
start end module name
fffff807`208e0000 fffff807`20969000 aswSP T (no symbols)
Loaded symbol image file: aswSP.sys
Image path: \SystemRoot\system32\drivers\aswSP.sys
Image name: aswSP.sys
Browse all global symbols functions data
Timestamp: Fri Sep 10 10:31:23 2021 (613B09CB)
CheckSum: 0008B428
ImageSize: 00089000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
I would suggest that you look for an update for the Avast! product if you really must use it. TBH all third-party anti-malware products cause BSODs at some time or another, and you really don't need them. Windows Defender and Windows Firewall are perfectly good enough - they are all I use.
I'm a big supporter of only changing one thing at a time, so I strongly suggest that you remove one pair of RAM sticks first and see whether that was causing the BSODs. Only once you know whether the mixed RAM was (or wasn't) the problem should you update (or remove) Avast!.
