I ran sfc, chkdsk, and memory verifier and I got nothing. When I ran driver verifier, I got xsplitvcam, so I got rid of that. However, I'm still crashing and I'm clueless at this point.

I have an Inspiron 5482 2 in 1 and I have checked on windows update and dell update that my drivers are updated.

Any help would be greatly appreciated.

WinDbg: https://pastebin.com/cQWU9jUd

Whocrashed log:

On Wed 14-Apr-21 12:46:39 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041421-12453-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF80536FF3204)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80536FF3204, 0x0, 0x8)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Wed 14-Apr-21 12:46:39 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (0xFFFFF80536FF3204)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80536FF3204, 0x0, 0x8)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Mon 12-Apr-21 14:53:57 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041221-11093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5DB0)
Bugcheck code: 0x139 (0x0, 0x0, 0x0, 0xFFFFF8055F38D210)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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-Apr-21 09:11:05 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041221-11140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5DB0)
Bugcheck code: 0x139 (0x3, 0xFFFFF38A59557490, 0xFFFFF38A595573E8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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-Apr-21 08:00:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\LiveKernelReports\NDIS-20210412-0800.dmp
This was probably caused by the following module: ndis.sys (ndis!NdisReleaseNicActive+0xB1D)
Bugcheck code: 0x15E (0x25, 0x23, 0xFFFFC001E935D9F8, 0xE070101)
Error: BUGCODE_NDIS_DRIVER_LIVE_DUMP
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network Driver Interface Specification (NDIS)
Bug check description: NDIS has captured a live kernel dump. NDIS does not generate a bug check in this situation.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 11-Apr-21 10:50:02 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041121-9265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5DB0)
Bugcheck code: 0x50 (0xFFFFF088403A00D8, 0x0, 0xFFFFF8011B5F9711, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 10-Apr-21 10:00:24 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041021-9609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5DB0)
Bugcheck code: 0xF7 (0xF6C0F69FD849, 0xF6C0F69FD859, 0xFFFF093F096027A6, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
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 driver has overrun a stack-based buffer.
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.