BSOD and USB device issues

Question

Hi, I've been having BSOD (on multiple occassions with the same error message "DRIVER_VERIFIER_DMA_VIOLATION". I have also been having issues with my USB devices (mouse, keyboard, headset and controller) where my usb devices will stop responding and when trying a different port windows gives a notification saying "the usb device has malfunctioned".

System specs :

Mouse: Razer Deathadder v2

Keyboard RITEK 202

OS Windows 10 Home 64-Bit (10.0, Build 19045)

Motherboard ASUS Prime B660-PLUS D4 LGA 1700(Intel 12th Gen) ATX Motherboard

GPU: AMD Radeon RX 6650 XT

CPU 12th Gen Intel(R) Core(TM) i5-12400F (12 CPUs) ~2.5GHz

Memory: 32gb DDR4

750 watt 80+ gold psu

I have ran the DMP files through WINDBG which gives the following output:

DRIVER_VERIFIER_DMA_VIOLATION (e6)
An illegal DMA operation was attempted by a driver being verified.
Arguments:
Arg1: 0000000000000026, IOMMU detected DMA violation.
Arg2: 0000000000000000, Device Object of faulting device.
Arg3: 00000000401c40cd, Faulting information (usually faulting physical address).
Arg4: 0000000000000004, Fault type (hardware specific).

Debugging Details:
------------------

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2764

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 5374

    Key  : Analysis.IO.Other.Mb
    Value: 4

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 5

    Key  : Analysis.Init.CPU.mSec
    Value: 1015

    Key  : Analysis.Init.Elapsed.mSec
    Value: 15457

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 106

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xe6

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0xe6

    Key  : Bugcheck.Code.Register
    Value: 0xe6

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  e6

BUGCHECK_P1: 26

BUGCHECK_P2: 0

BUGCHECK_P3: 401c40cd

BUGCHECK_P4: 4

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  audiodg.exe

STACK_TEXT:  
fffff802`24a80ea8 fffff802`204ddd77     : 00000000`000000e6 00000000`00000026 00000000`00000000 00000000`401c40cd : nt!KeBugCheckEx
fffff802`24a80eb0 fffff802`204c994b     : 00000000`00000000 00000000`00000000 fffff802`20c49bd0 fffff802`20c49bd0 : nt!IvtHandleInterrupt+0x1a7
fffff802`24a80f10 fffff802`20208a45     : fffff802`20cf3ac0 ffffef84`9d3e7100 fffff802`20cf3b70 fffff802`20208a45 : nt!HalpIommuInterruptRoutine+0x4b
fffff802`24a80f40 fffff802`203fb13c     : ffffef84`9d3e7100 fffff802`20cf3ac0 00000000`00000000 fffff802`203fb26a : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`24a80f90 fffff802`203fb677     : ffffcf0e`bcd494a0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLock+0x11c
ffffef84`9d3e7080 fffff802`39421bc1     : 00000000`00000003 ffffcf0e`cb4c8080 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x37
ffffef84`9d3e7210 fffff802`394c916a     : ffffcf0e`bcd494a0 02100050`20400a18 00000000`00000001 fffff802`202851ef : USBXHCI!Controller_UcxEvtGetCurrentFrameNumber+0x81
ffffef84`9d3e7250 fffff802`4fce306b     : ffffef84`9d3e7350 ffffcf0e`cbebe0c0 00000000`c0000200 ffffcf0e`cbebe050 : ucx01000!Usbd_BusQueryBusTime+0x7a
ffffef84`9d3e72a0 fffff802`4fce314c     : 00000000`00000000 ffffcf0e`cbebe050 00000000`00000000 fffff802`202851ef : usbaudio!USBHwGetCurrentFrame+0x33
ffffef84`9d3e72d0 fffff802`4fce33f4     : 00000000`00000000 ffffef84`9d3e7408 ffffef84`9d3e7390 00000000`00000000 : usbaudio!UsbHwFrameCountTimestamp+0x60
ffffef84`9d3e7350 fffff802`4fce3c63     : ffffcf0e`cbebe050 ffffef84`9d3e7430 ffffef84`9d3e7490 00000000`00000000 : usbaudio!USBHwGetClockRatio+0x1a0
ffffef84`9d3e73f0 fffff802`4fd060c5     : 00000000`00000000 00000000`c000000d 00000000`00000000 ffffcf0e`cb8ccf00 : usbaudio!USBType1RenderBytePosition+0xb3
ffffef84`9d3e7480 fffff802`3938a5ca     : ffffcf0e`c7495710 ffffcf0e`c9ec0b38 00000000`00000048 00000000`00000000 : usbaudio!PropertyGetAudioPositionEx+0x65
ffffef84`9d3e74d0 fffff802`39389f2f     : 00000000`00000028 00000000`00000008 00000000`c0000225 ffffcf0e`cb8cc6e0 : ks!KspPropertyHandler+0x3ca
ffffef84`9d3e7530 fffff802`39389ad8     : 00000000`c0000230 00000000`00000000 ffffcf0e`cb8cc6e0 00000000`00000fff : ks!KspHandleAutomationIoControl+0xbf
ffffef84`9d3e75b0 fffff802`3938d514     : ffffcf0e`cb8cc6e0 ffffef84`9d3e7608 00000000`00000000 ffffcf0e`cad5bbb0 : ks!CKsPin::DispatchDeviceIoControl+0xe8
ffffef84`9d3e7600 fffff802`4fd019e3     : ffffcf0e`cb8cc6e0 ffffcf0e`cad5bbb0 ffffcf0e`cb8ccf00 ffffcf0e`cfef1480 : ks!KsDispatchIrp+0x44
ffffef84`9d3e7630 fffff802`2022a6b5     : ffffcf0e`cb8cc6e0 ffffef84`9d3e7700 ffffcf0e`cb8ccf48 00000000`00000000 : usbaudio!UsbAudioIrpDispatcher+0x143
ffffef84`9d3e7670 fffff802`393e16bf     : ffffcf0e`cb8cc6e0 ffffef84`9d3e7700 ffffcf0e`cb8ccf48 ffffcf0e`cfef1480 : nt!IofCallDriver+0x55
ffffef84`9d3e76b0 fffff802`393e1023     : ffffcf0e`cb8cc6e0 00000000`00000000 cf0ec6ad`00000000 ffffcf0e`c7958cc0 : ksthunk!CKernelFilterDevice::DispatchIrp+0x23b
ffffef84`9d3e7710 fffff802`2022a6b5     : 00000000`0000001c 00000000`0000001c 00000000`00000001 00000000`00000800 : ksthunk!CKernelFilterDevice::DispatchIrpBridge+0x13
ffffef84`9d3e7740 fffff802`206194c8     : ffffcf0e`cb8cc6e0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55
ffffef84`9d3e7780 fffff802`206192c7     : 00000000`00000000 ffffef84`9d3e7ac0 00000000`00040000 ffffef84`9d3e7ac0 : nt!IopSynchronousServiceTail+0x1a8
ffffef84`9d3e7820 fffff802`20618646     : 00000000`00000001 00000000`0000062d 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xc67
ffffef84`9d3e7960 fffff802`2040caf5     : ffffcf0e`cb4c8080 00000039`f98ff828 ffffef84`9d3e79e8 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
ffffef84`9d3e79d0 00007ffa`a01cd1a4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000039`f98ff7f8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`a01cd1a4

SYMBOL_NAME:  nt!IvtHandleInterrupt+1a7

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1a7

FAILURE_BUCKET_ID:  0xE6_26_nt!IvtHandleInterrupt

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {11608481-d56e-58cc-4b64-17c92254d2f4}

Followup:     MachineOwner

I have also tried putting the DMP file through "WhoCrashed" which pointed me to this driver: USBXHCI.SYS
any help appreciated

Answer 1

No worries. To troubleshoot this issue, kindly try the steps below (Skip a step that you have already tried):

1-If you have enabled the driver verifier by any chance, kindly disable it.

If you don't, enable it and let the computer crash 3 times then disable it and share the newly created minidump file:

https://www.tenforums.com/tutorials/5470-enable...

2-Right click on Start > Expand Universal Serial Bus Controller > Right click on the USB Root Hub and click on Uninstall > Check the box 'Delete the driver software for this device' > Uninstall > Restart your computer and see if your computer would be stable or not.

Please do not hesitate to ask if you need further assistance.

Stay safe

____________________________________________________________

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

Answer 2

Hi Dyari,

No, apologies but it did not make any more dumpfiles in the directory.

Thanks

Answer 3

Hi LeviTian1,

I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

The minidump files did not name any driver only indicate ntkrnlmp.exe which is a Windows component that means something else drove the system to a fault or it could be a memory corruption that usually happens due to driver incompatibility.

Did your computer produce more minidump files for further analysis?

Answer 4

Hi Dyari,

thanks

Answer 5

Hi LeviTian1,

I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

Kindly check C:\Windows\Minidump and copy available minidump files to the desktop then share them via One Drive or Google Drive in order to be analyzed and indicate which file is causing the crash.

Regards,