@nvmsocool  I would re-enable driver verifier if that hasn't fixed the problem, but my guess would be that this is a driver issue that might still exist even in the current release of the offending driver.  I suspect it will be either the GPU driver or the Oculus Link driver that is responsible for converting rendered video to USB data for transmission to the Quest, since the Quest does not use DisplayPort Alt Mode for video -- or possibly an issue that only arises with the specific combination of running Oculus Link on systems with the GPU you have.  I can't think of any obvious troubleshooting steps you've missed, so you might just have to keep an eye out for updates, unfortunately.

Check this out:

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xe6--driver-verifier-dma-violation

computing ntoskrnl.exe (short for Windows NT operating system kernel executable), also known as kernel image, provides the kernel and executive layers of the Microsoft Windows NT kernel space, and is responsible for various system services such as hardware abstraction, process and memory management, thus making it a fundamental part of the system. It contains the cachemanager, the executive, the kernel, the security reference monitor, the memory manager, and the scheduler (Dispatcher).

Oh yeah, I have been there a couple times. I get parameter 1 easy enough, its 26 which  means an "IOMMU detected DMA violation" type error. It is being called by ntoskrnl.exe, which is a windows base program so the error is likely caused by another application calling ntoskrnl.exe. 

I believe my Oculus Quest 2 fried my R4 because it won't turn on no more it just shorts out also my Oculus Quest 2 just keeps loading forever tried resetting it just loads a chip