Hi. . .
Sorry that Altap did not work.
Did you ever run Driver Verifier?
Please zip up the minidumps from your multiple crashes described in your last post and attach to your next post. If none - change system settings.
Also, zip up the full kernel (\windows\memory.dmp) and upload it to Dropbox. Really no one will want to take the time to download your 1.2 GB dump from post #1. And there are a few proficient in Windbg (much more than I) that may see this thread and run through the full kernel, but doubtful if they have to download 1.2 GB. Use the most recent version of the full kernel dump.
RE: Windbg commands - I was just curious why you used !devobj because it returns info on a device object from a memory address that you provide. I did not know if you were going somewhere with it or not.
RE: USBHXCI - these are your USB 3.0 drivers, I assume? USBHXCI.sys is a Microsoft driver and is therefore sacrosanct and I highly doubt is involved in these crashes. You could try updating your 3rd party USB 3.0 drivers. Look in Device Manager for their names.
I checked the onlune reference for bugcheck 0xe6 and they don't list an error code 0x26 either - Bug Check 0xE6 DRIVER_VERIFIER_DMA_VIOLATION - Windows drivers | Microsoft Docs
"DMA" I assume to be "Direct Memory Access", which would indicate that a driver violated DMA rules, but no driver is listed on the stack - just HAL and of course NT (Windows Kernel) -
[CODE]0: kd> kn
# Child-SP RetAddr Call Site
00 fffff800`13a6feb8 fffff800`11447707 nt!KeBugCheckEx
01 fffff800`13a6fec0 fffff800`11442f9c hal!IvtHandleInterrupt+0x1b7
02 fffff800`13a6ff10 fffff800`115c5315 hal!HalpIommuInterruptRoutine+0x4c
03 fffff800`13a6ff40 fffff800`116549fc nt!KiCallInterruptServiceRoutine+0xa5
04 fffff800`13a6ff90 fffff800`11654df7 nt!KiInterruptSubDispatchNoLock+0x11c
05 ffff8407`65577a00 00000000`00000000 nt!KiInterruptDispatchNoLock+0x37
[/CODE]
Have you tested RAM just to be sure?
Test RAM with memtest.org MemTest86+
Regards. . .
jcgriff2
