Windows 10: DRIVER_VERIFIER_DMA_VIOLATION e6

Discus and support DRIVER_VERIFIER_DMA_VIOLATION e6 in Windows 10 BSOD Crashes and Debugging to solve the problem; 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... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by keith rapata, Sep 13, 2022.

  1. 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 installing windows multiple times. I have a new Processor, Motherboard, and Ram so not sure what the problem could be. Thank you!!

    :)
     
    keith rapata, Sep 13, 2022
    #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, Sep 13, 2022
    #2
  3. 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, Sep 13, 2022
    #3
  4. zbook Win User

    DRIVER_VERIFIER_DMA_VIOLATION e6

    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, Sep 13, 2022
    #4
Thema:

DRIVER_VERIFIER_DMA_VIOLATION e6

Loading...
  1. DRIVER_VERIFIER_DMA_VIOLATION e6 - Similar Threads - DRIVER_VERIFIER_DMA_VIOLATION

  2. Mini dump file with Blue screen DRIVER_Verifier_DMA_Violation

    in Windows 10 Gaming
    Mini dump file with Blue screen DRIVER_Verifier_DMA_Violation: Hello, I was hoping someone could help me figure out what is causing a blue screen with error DRIVER_VERIFIER_DMA_VIOLATION on a HP laptop. I've tested the RAM and motherboard and came back clear. Here is the dump file it makes:...
  3. Mini dump file with Blue screen DRIVER_Verifier_DMA_Violation

    in Windows 10 Software and Apps
    Mini dump file with Blue screen DRIVER_Verifier_DMA_Violation: Hello, I was hoping someone could help me figure out what is causing a blue screen with error DRIVER_VERIFIER_DMA_VIOLATION on a HP laptop. I've tested the RAM and motherboard and came back clear. Here is the dump file it makes:...
  4. Acer Spin 1 - error "DRIVER_VERIFIER_DMA_VIOLATION

    in Windows 10 Gaming
    Acer Spin 1 - error "DRIVER_VERIFIER_DMA_VIOLATION: Start up, says to enter single use code all good there, then takes me to a screen to create a PIN which then tells me "something went wrong" and to "skip for now" ... this takes me back to the sign in screen and the loop starts all over. I've tried everything. I can't seem to...
  5. Acer Spin 1 - error "DRIVER_VERIFIER_DMA_VIOLATION

    in Windows 10 Software and Apps
    Acer Spin 1 - error "DRIVER_VERIFIER_DMA_VIOLATION: Start up, says to enter single use code all good there, then takes me to a screen to create a PIN which then tells me "something went wrong" and to "skip for now" ... this takes me back to the sign in screen and the loop starts all over. I've tried everything. I can't seem to...
  6. Acer Spin 1 - error "DRIVER_VERIFIER_DMA_VIOLATION

    in Windows 10 Drivers and Hardware
    Acer Spin 1 - error "DRIVER_VERIFIER_DMA_VIOLATION: Start up, says to enter single use code all good there, then takes me to a screen to create a PIN which then tells me "something went wrong" and to "skip for now" ... this takes me back to the sign in screen and the loop starts all over. I've tried everything. I can't seem to...
  7. BSOD error message "DRIVER_VERIFIER_DMA_VIOLATION".

    in Windows 10 BSOD Crashes and Debugging
    BSOD error message "DRIVER_VERIFIER_DMA_VIOLATION".: My laptop shuts down quite frequently with a blue screen and error message "DRIVER_VERIFIER_DMA_VIOLATION". This happens not at start up, but at random times when the laptop in 'on'. Would be grateful for anyone's help in identifying the root cause of this. The minidump files...
  8. BSOD error message "DRIVER_VERIFIER_DMA_VIOLATION".

    in Windows 10 Gaming
    BSOD error message "DRIVER_VERIFIER_DMA_VIOLATION".: My laptop shuts down quite frequently with a blue screen and error message "DRIVER_VERIFIER_DMA_VIOLATION". This happens not at start up, but at random times when the laptop in 'on'. Would be grateful for anyone's help in identifying the root cause of this. The minidump files...
  9. BSOD error message "DRIVER_VERIFIER_DMA_VIOLATION".

    in Windows 10 Software and Apps
    BSOD error message "DRIVER_VERIFIER_DMA_VIOLATION".: My laptop shuts down quite frequently with a blue screen and error message "DRIVER_VERIFIER_DMA_VIOLATION". This happens not at start up, but at random times when the laptop in 'on'. Would be grateful for anyone's help in identifying the root cause of this. The minidump files...
  10. HP ProBook 450 G9 - DRIVER_VERIFIER_DMA_VIOLATION e6

    in Windows 10 Gaming
    HP ProBook 450 G9 - DRIVER_VERIFIER_DMA_VIOLATION e6: We're currently running into an issue with our HP 450 G9 i5 12th Gen laptops Win10 22H2 where they are receiving the BSOD and on reboot are met with a DMA Protection message. This seems to be a growing issue for this model however there has been no solution to the problem....