BSODs of various types, mostly citing ntoskrnl.exe

I've been experiencing BSODs for a while now. I've been trying to troubleshoot but I'm at my wit's end at this point. I have used two different SSDs, and both wind up experiencing this issue. I have force-installed all the newest drivers I can find. I did a Windows system reset, and it still wound up giving me a BSOD later that day.

I ran the Memory Test diagnostic through 24 passes, and my memory came up clean through all of them. I'm just not sure what the problem is at this point. All of my requested info from this site's infodump is contained on my Google Drive.

Most of my BSODs cite the ntoskrnl.exe as the source of fault, although recently it has also cited ndis.sys. The stated BSOD string has included: System Service Exception, KMode Exception Not Handled, and Page Fault in Nonpaged Area.

I really appreciate any assistance at this point!

Laptop: Asus UX410
Intel Core i7-8550u 1.8 GHz
Windows 10 Home 19044.1889
RAM: 16 gb (2x8) DDR4
SSD (OS) + HDD

Update Intel Wi-Fi driver - Intel(R) Dual Band Wireless-AC 8265

I tried updating at the English version of Intel's site, but when I go to install it, even running as an administrator, it doesn't change the driver version when I check it. I tried uninstalling the device and manually installing the driver again, but then it went back to an even earlier version of the driver, dated to January of this year compared to the one I currently have installed from March of this year (22.130.0.5).

- - - Updated - - -

I've had two more BSODs thus far today. I've added them to my Google Drive folder. Running Driver Verifier now to hopefully figure out the issue. Despite the fact that the MemTest came back clean, I've also ordered a new RAM chip to replace the non-soldered RAM, just in case that's the problem.

I had another BSOD last night - there was no bug check string. I added the Minidump and full MEMORY.dmp to the Google Drive folder I previously linked.

After uninstalling the RealTek imaging device for a plug-in webcam and then running another round of sfc /scannow and DISM fixes, this finally appears to be fixed.