Unsolved
This post is more than 5 years old
2 Posts
0
1429
July 22nd, 2020 17:00
17 R4, incompatible with Oculus Quest?
I have been getting a DRIVER_VERIFIER_DMA_VIOLATION BSOD when playing rift games after a short time. My temps are low, fans working, and all other 2D games work just fine. This seems to be an issue others have as well: https://answers.microsoft.com/en-us/windows/forum/all/driververifierdmaviolation-when-using-oculus-rift/21359277-c282-4181-9125-bf7df55cd3cb and https://www.sysnative.com/forums/threads/bsod-driver_verifier_dma_violation-0xe6.26990/ and https://www.reddit.com/r/oculus/comments/cl9a2e/oculus_rift_problem_on_windows_10/
I have tried disabling the driver verifier, updating all of my drivers, updating windows, running the hardware troubleshooter, disabling my antivirus, running SFC, running DISM, uninstalling Oculus, and uninstalling the application, but to no avail. I have also ran some BSOD diagnostics on the dump file but I wasn't able to spot anything obvious enough for a noob.
No other computers seem to have this error with Oculus, so it is something with the laptop, does anyone know what could be the cause?
jphughan
11 Legend
•
14K Posts
•
79.9K Points
0
July 22nd, 2020 18:00
@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.
A51-06
7 Practitioner
•
3.1K Posts
•
13.7K Points
0
July 22nd, 2020 19:00
Check this out:
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xe6--driver-verifier-dma-violation
A51-06
7 Practitioner
•
3.1K Posts
•
13.7K Points
0
July 22nd, 2020 20:00
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).
nvmsocool
2 Posts
0
July 22nd, 2020 20:00
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.
Rick carp
2 Posts
0
May 27th, 2021 12:00
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