Windows 10: Bluescreen Error/Crash - DRIVER_VERIFIER_DMA_VIOLATION e6

Discus and support Bluescreen Error/Crash - DRIVER_VERIFIER_DMA_VIOLATION e6 in Windows 10 BSOD Crashes and Debugging to solve the problem; I have been having a few bluescreen crashes lately. Could some help me troubleshoot this crash. 0: kd> !analyze -v... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Rijo varghese, Feb 16, 2021.

  1. Bluescreen Error/Crash - DRIVER_VERIFIER_DMA_VIOLATION e6


    I have been having a few bluescreen crashes lately. Could some help me troubleshoot this crash.



    0: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    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: 0000000000000080, Faulting information usually faulting physical address.

    Arg4: 0000000000000005, Fault type hardware specific.



    Debugging Details:

    ------------------



    *** WARNING: Unable to verify timestamp for win32k.sys



    KEY_VALUES_STRING: 1





    PROCESSES_ANALYSIS: 1



    SERVICE_ANALYSIS: 1



    STACKHASH_ANALYSIS: 1



    TIMELINE_ANALYSIS: 1





    DUMP_CLASS: 1



    DUMP_QUALIFIER: 400



    BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202



    SYSTEM_MANUFACTURER: Dell Inc.



    SYSTEM_PRODUCT_NAME: Precision 5540



    SYSTEM_SKU: 0906



    BIOS_VENDOR: Dell Inc.



    BIOS_VERSION: 1.7.0



    BIOS_DATE: 05/11/2020



    BASEBOARD_MANUFACTURER: Dell Inc.



    BASEBOARD_PRODUCT: 03G9D9



    BASEBOARD_VERSION: A00



    DUMP_TYPE: 2



    BUGCHECK_P1: 26



    BUGCHECK_P2: 0



    BUGCHECK_P3: 80



    BUGCHECK_P4: 5



    CPU_COUNT: c



    CPU_MHZ: a20



    CPU_VENDOR: GenuineIntel



    CPU_FAMILY: 6



    CPU_MODEL: 9e



    CPU_STEPPING: d



    CPU_MICROCODE: 6,9e,d,0 F,M,S,R SIG: CA'00000000 cache CA'00000000 init



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



    BUGCHECK_STR: 0xE6



    PROCESS_NAME: System



    CURRENT_IRQL: c



    ANALYSIS_SESSION_HOST: W1971116



    ANALYSIS_SESSION_TIME: 02-16-2021 10:23:01.0323



    ANALYSIS_VERSION: 10.0.18362.1 amd64fre



    LAST_CONTROL_TRANSFER: from fffff8073c59dc14 to fffff8073c7c3b20



    STACK_TEXT:

    fffff807`4148bea8 fffff807`3c59dc14 : 00000000`000000e6 00000000`00000026 00000000`00000000 00000000`00000080 : nt!KeBugCheckEx

    fffff807`4148beb0 fffff807`3c598c9c : fffff807`3c5c8d80 fffff807`3c5c8d80 fffff807`3c5cc200 00000000`00000001 : hal!IvtHandleInterrupt+0x1d4

    fffff807`4148bf10 fffff807`3c6fdaa5 : fffff807`3c5cc200 fffff807`4147ca50 fffff807`3c5cc2b0 00000000`00000008 : hal!HalpIommuInterruptRoutine+0x4c

    fffff807`4148bf40 fffff807`3c7c547c : fffff807`4147ca50 fffff807`3c5cc200 00000000`0000084c fffff807`3c5cc200 : nt!KiCallInterruptServiceRoutine+0xa5

    fffff807`4148bf90 fffff807`3c7c5887 : ffffa403`b39f3000 00000000`00000002 fffff807`4147cb00 00000000`00000001 : nt!KiInterruptSubDispatchNoLock+0x11c

    fffff807`4147c9d0 fffff807`3c7c761a : 00000000`00000000 fffff807`38205180 ffffa403`b14c6380 00000000`0000084c : nt!KiInterruptDispatchNoLock+0x37

    fffff807`4147cb60 00000000`00000000 : fffff807`4147d000 fffff807`41476000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x4a





    THREAD_SHA1_HASH_MOD_FUNC: 0cfc1e867edaaf1fd57f2eadb5ab73d7c233a354



    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 0bca2be4d8d511d04b4debcff20a9ba4fcc5a960



    THREAD_SHA1_HASH_MOD: 782650af79f96574cdba6be2f36ad0d2d7924552



    FOLLOWUP_IP:

    nt!KiCallInterruptServiceRoutine+a5

    fffff807`3c6fdaa5 0fb6e8 movzx ebp,al



    FAULT_INSTR_CODE: 45e8b60f



    SYMBOL_STACK_INDEX: 3



    SYMBOL_NAME: nt!KiCallInterruptServiceRoutine+a5



    FOLLOWUP_NAME: MachineOwner



    MODULE_NAME: nt



    IMAGE_NAME: ntkrnlmp.exe



    DEBUG_FLR_IMAGE_TIMESTAMP: 0



    IMAGE_VERSION: 10.0.18362.1316



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: a5



    FAILURE_BUCKET_ID: 0xE6_nt!KiCallInterruptServiceRoutine



    BUCKET_ID: 0xE6_nt!KiCallInterruptServiceRoutine



    PRIMARY_PROBLEM_CLASS: 0xE6_nt!KiCallInterruptServiceRoutine



    TARGET_TIME: 2021-01-29T18:15:14.000Z



    OSBUILD: 18362



    OSSERVICEPACK: 1316



    SERVICEPACK_NUMBER: 0



    OS_REVISION: 0



    SUITE_MASK: 272



    PRODUCT_TYPE: 1



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS



    OS_LOCALE:



    USER_LCID: 0



    OSBUILD_TIMESTAMP: unknown_date



    BUILDDATESTAMP_STR: 190318-1202



    BUILDLAB_STR: 19h1_release



    BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202



    ANALYSIS_SESSION_ELAPSED_TIME: 224a



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:0xe6_nt!kicallinterruptserviceroutine



    FAILURE_ID_HASH: {2b0e63ba-aae0-93ee-5379-fdfd15c60138}



    Followup: MachineOwner

    ---------

    :)
     
    Rijo varghese, Feb 16, 2021
    #1
  2. phelanka7 Win User

    BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6)

    I have been getting this error (BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6)) typically while playing video games but have seen it occur simply idling. The thing that I find strange is that I don't even have the Driver Verifier turned on. I have done the "verifier /reset" command which was one of the first things I tried to do to fix it after Googling the error. I have tried a number of things to try and fix this. A non-exhaustive list includes:

    • Reinstalling GPU drivers using DDR (Display Driver Remover)
    • Meticulously updating every single driver for every device
    • Clean out the registry using CCleaner
    • Flashing BIOS
    • Ran Memtest86 (RAM stress test)
    • Ran Prime95 (cpu stress test)
    • chkdsk

    I'm far from computer illiterate but this has me completely stumped. So I come to you, the experts, hat in hand. Please help me. You're my only hope.
     
    phelanka7, Feb 16, 2021
    #2
  3. zbook Win User
    BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6)

    The memory dump again displayed corruption:

    Wed Dec 5 21:18:09.857 2018 (UTC - 6:00)

    Code:

    If there are more corrupt dump files it may be useful to tray an in place upgrade repair as a trial and error step.
    Repair Install Windows 10 with an In-place Upgrade | Tutorials

    The next two crashes will be debugged and if the corruption persists then plan an in place upgrade repair.

    The operating system on the computer is: Version 10.0.17134 Build 17134

    The repair can be performed with a same version iso upgrading to 1809 or with an 1803 iso.

    This is the iso for 1809:
    Download Windows 10
    Download Windows 10 ISO File | Tutorials


    These are options for older iso:
    Windows Download - #1 Windows ISO Download Source
    Microsoft Windows and Office ISO Download Tool
    TechBench by WZT (v4.1.1)
     
    zbook, Feb 16, 2021
    #3
  4. Bluescreen Error/Crash - DRIVER_VERIFIER_DMA_VIOLATION e6

    DRIVER_VERIFIER_DMA_VIOLATION

    A. Analysis Results

    File Name: 080119-11437-01.dmp

    DRIVER_VERIFIER_DMA_VIOLATION (e6)

    IMAGE_NAME: ntkrnlmp.exe

    *** WARNING: Unable to verify timestamp for aswSnx.sys

    File Name: 081319-9890-01.dmp

    DRIVER_VERIFIER_DMA_VIOLATION (e6)

    IMAGE_NAME: ntkrnlmp.exe

    *** WARNING: Unable to verify timestamp for aswbidsdriver.sys

    *** WARNING: Unable to verify timestamp for aswSP.sys

    *** WARNING: Unable to verify timestamp for aswSnx.sys

    File Name: 081319-11156-01.dmp

    DRIVER_VERIFIER_DMA_VIOLATION (e6)

    IMAGE_NAME: ntkrnlmp.exe

    File Name: 081419-10734-01.dmp

    DRIVER_VERIFIER_DMA_VIOLATION (e6)

    IMAGE_NAME: ntkrnlmp.exe

    *** WARNING: Unable to verify timestamp for aswbidsdriver.sys

    File Name: 081419-11937-01.dmp

    DRIVER_VERIFIER_DMA_VIOLATION (e6)

    IMAGE_NAME: ntkrnlmp.exe

    B. Third Party Drivers

    All of below are AVAST

    aswSnx.sys

    aswbidsdriver.sys

    aswSP.sys

    C. Recommendations

    1. Create a system restore point first so that if something wrong happens you can revert.

    Type restore point in Cortana Search > Create a Restore point > Check whether against your drive, Protection is ON or not. If not ON, click Configure button below to Make it ON > Now press Create to create a restore point

    2. Update your AVAST to latest. If BSOD doesn't stop, get rid of AVAST.
     
    Vijay_Verma, Feb 16, 2021
    #4
Thema:

Bluescreen Error/Crash - DRIVER_VERIFIER_DMA_VIOLATION e6

Loading...
  1. Bluescreen Error/Crash - DRIVER_VERIFIER_DMA_VIOLATION e6 - Similar Threads - Bluescreen Error Crash

  2. DRIVER_VERIFIER_DMA_VIOLATION e6

    in Windows 10 Gaming
    DRIVER_VERIFIER_DMA_VIOLATION e6: Hello, I have gotten this BSOD a couple times now while playing a game. Its not all the time and seems to be random. Any help would be greatly appreciated because i cannot seem to figure out what is causing this issue and its starting to frustrate me. I have tried clean...
  3. DRIVER_VERIFIER_DMA_VIOLATION e6

    in Windows 10 Software and Apps
    DRIVER_VERIFIER_DMA_VIOLATION e6: Hello, I have gotten this BSOD a couple times now while playing a game. Its not all the time and seems to be random. Any help would be greatly appreciated because i cannot seem to figure out what is causing this issue and its starting to frustrate me. I have tried clean...
  4. DRIVER_VERIFIER_DMA_VIOLATION e6

    in Windows 10 BSOD Crashes and Debugging
    DRIVER_VERIFIER_DMA_VIOLATION e6: Hello, I have gotten this BSOD a couple times now while playing a game. Its not all the time and seems to be random. Any help would be greatly appreciated because i cannot seem to figure out what is causing this issue and its starting to frustrate me. I have tried clean...
  5. DRIVER_VERIFIER_DMA_VIOLATION e6

    in Windows 10 Gaming
    DRIVER_VERIFIER_DMA_VIOLATION e6: Hello Guys,maybe somebody can help me, i am receiving an Bluescreen very often.I have uploaded the Minidumps which was stored in the Minidump Folder I tried to analyze the dumps with windbg but the only process which crash is follow ntkrnlmp.exe.Maybe anybody can check this...
  6. DRIVER_VERIFIER_DMA_VIOLATION e6

    in Windows 10 Software and Apps
    DRIVER_VERIFIER_DMA_VIOLATION e6: Hello Guys,maybe somebody can help me, i am receiving an Bluescreen very often.I have uploaded the Minidumps which was stored in the Minidump Folder I tried to analyze the dumps with windbg but the only process which crash is follow ntkrnlmp.exe.Maybe anybody can check this...
  7. DRIVER_VERIFIER_DMA_VIOLATION e6

    in Windows 10 BSOD Crashes and Debugging
    DRIVER_VERIFIER_DMA_VIOLATION e6: Hello Guys,maybe somebody can help me, i am receiving an Bluescreen very often.I have uploaded the Minidumps which was stored in the Minidump Folder I tried to analyze the dumps with windbg but the only process which crash is follow ntkrnlmp.exe.Maybe anybody can check this...
  8. Blue Screen - DRIVER_VERIFIER_DMA_VIOLATION e6

    in Windows 10 Software and Apps
    Blue Screen - DRIVER_VERIFIER_DMA_VIOLATION e6: Hey, I recently rebuilt my PC and a few days ago my USB devices microphone, keyboard, mouse started turning off and back on again on their own this only happens a few times a day and sometimes I need to restart my PC for the device to work again. I am also getting on average...
  9. BSOD - DRIVER_VERIFIER_DMA_VIOLATION e6

    in Windows 10 BSOD Crashes and Debugging
    BSOD - DRIVER_VERIFIER_DMA_VIOLATION e6: Hello One of our Lenovo P53 Notebooks threw this bluescreen today, out of nowhere the user was typing in notepad. It is not reproducable. Driver verifier is disabled. I have a minidmup and a memorydump, please tell me what's needed. I tried analyzing them using WinDBG...
  10. BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6)

    in Windows 10 BSOD Crashes and Debugging
    BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6): I have been getting this error (BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6)) typically while playing video games but have seen it occur simply idling. The thing that I find strange is that I don't even have the Driver Verifier turned on. I have done the "verifier /reset" command...