Windows 10: Ongoing daily BSOD - DRIVER_VERIFIER_DMA_VIOLATION - ntoskrnl.exe

Discus and support Ongoing daily BSOD - DRIVER_VERIFIER_DMA_VIOLATION - ntoskrnl.exe in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello, I have a Lenovo X1 Extreme Gen 2 having a BSOD almost every night. Running Win 10 Pro V2004 - Intel i9-9880H CPU + 32GB RAM. Laptop is... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Nick V28, Dec 8, 2020.

  1. NICK V28
    Nick V28 Win User

    Ongoing daily BSOD - DRIVER_VERIFIER_DMA_VIOLATION - ntoskrnl.exe


    Hello,


    I have a Lenovo X1 Extreme Gen 2 having a BSOD almost every night. Running Win 10 Pro V2004 - Intel i9-9880H CPU + 32GB RAM.

    Laptop is connected to Lenovo Thinkpad thunderbolt 3 gen 2 docking station.

    Connected to LG 34 inch wide screen monitor.


    All drivers/BIOS/NVidia are up to date.


    BSOD viewer output:

    ==================================================

    Dump File : 120820-12406-01.dmp

    Crash Time : 12/7/2020 11:44:26 PM

    Bug Check String : DRIVER_VERIFIER_DMA_VIOLATION

    Bug Check Code : 0x000000e6

    Parameter 1 : 00000000`00000026

    Parameter 2 : ffffdb85`99f3c060

    Parameter 3 : 00000000`00000060

    Parameter 4 : 00000000`00000005

    Caused By Driver : ntoskrnl.exe

    Caused By Address : ntoskrnl.exe+3f5210

    File Description :

    Product Name :

    Company :

    File Version :

    Processor : x64

    Crash Address : ntoskrnl.exe+3f5210

    Stack Address 1 :

    Stack Address 2 :

    Stack Address 3 :

    Computer Name :

    Full Path : C:\WINDOWS\Minidump\120820-12406-01.dmp

    Processors Count : 16

    Major Version : 15

    Minor Version : 19041

    Dump File Size : 1,081,812

    Dump File Time : 12/8/2020 8:25:30 AM

    ==================================================



    WinDBG output:

    ******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DRIVER_VERIFIER_DMA_VIOLATION e6An illegal DMA operation was attempted by a driver being verified.Arguments:Arg1: 0000000000000026, IOMMU detected DMA violation.Arg2: ffffdb8599f3c060, Device Object of faulting device.Arg3: 0000000000000060, Faulting information usually faulting physical address.Arg4: 0000000000000005, Fault type hardware specific.Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3390 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on NVADASZ2-LT Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 22648 Key : Analysis.Memory.CommitPeak.Mb Value: 93 Key : Analysis.System Value: CreateObject 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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: e6BUGCHECK_P1: 26BUGCHECK_P2: ffffdb8599f3c060BUGCHECK_P3: 60BUGCHECK_P4: 5CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: explorer.exeSTACK_TEXT: fffff801`62c9fea8 fffff801`5f0d9fe7 : 00000000`000000e6 00000000`00000026 ffffdb85`99f3c060 00000000`00000060 : nt!KeBugCheckExfffff801`62c9feb0 fffff801`5f0c5f0b : 00000000`00000000 00000000`00000000 fffff801`5f849cd0 fffff801`5f849cd0 : nt!IvtHandleInterrupt+0x1a7fffff801`62c9ff10 fffff801`5ee2ecd5 : fffff801`5f8f3b00 ffffc509`fb807d20 fffff801`5f8f3bb0 fffff801`5ee2ecd5 : nt!HalpIommuInterruptRoutine+0x4bfffff801`62c9ff40 fffff801`5eff6b8c : ffffc509`fb807d20 fffff801`5f8f3b00 00000000`00000000 fffff801`5eff6cba : nt!KiCallInterruptServiceRoutine+0xa5fffff801`62c9ff90 fffff801`5eff6f97 : 00000000`00000000 00000010`00000000 ffff838d`00000000 c69a8873`00000028 : nt!KiInterruptSubDispatchNoLock+0x11cffffc509`fb807ca0 ffff83c3`b810cc28 : fffff801`5f006bb5 ffffdb85`b3bdf080 00000000`00000000 ffffc50a`00000000 : nt!KiInterruptDispatchNoLock+0x37ffffc509`fb807e38 fffff801`5f006bb5 : ffffdb85`b3bdf080 00000000`00000000 ffffc50a`00000000 ffffdb85`00000000 : win32k!NtGdiSelectBitmapffffc509`fb807e40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25SYMBOL_NAME: nt!IvtHandleInterrupt+1a7MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.19041.630STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 1a7FAILURE_BUCKET_ID: 0xE6_nt!IvtHandleInterruptOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {2cafa897-b47c-7b20-cee6-b1b68f30ec38}Followup: MachineOwner

    :)
     
    Nick V28, Dec 8, 2020
    #1
  2. LEWISH95
    LewisH95 Win User

    Ntoskrnl BSOD

    • Update your Realtek audio driver.
    • Update your computer.
    • Disable overclocking settings.
    • Turn off BlueStacks/ another Android emulator.
    • Clean your registry.
    • Check your disk for errors.
    • Fix bad memory issues.
    • Remove faulty sticks of RAM.
    • I hope these methods help you!
    • Regards,
    • Lewis

      * Added by Moderator: Information from
      https://windowsreport.com/windows-8-bsod-ntoskrnl-exe/

      * Moderator note: Advice given on this page might or might not be safe and/or effective but there are programs usually classified as PUP's (Potentially Unwanted Programs) being pushed that should not be downloaded or installed.
     
    LewisH95, Dec 8, 2020
    #2
  3. MARITZACAPIRO
    MaritzaCapiro Win User
    BSOD ntoskrnl..exe+1b35e0

    Hi, KirbyBakken

    My name is Maritza and I am an Independent Advisor. I would be happy to help you today.

    Check this link, I hope it helps

    https://www.thewindowsclub.com/ntoskrnl-exe-hig...

    Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised
    on the site before you decide to download and install it.

    Let us know if these steps help you to resolve the issue.
     
    MaritzaCapiro, Dec 8, 2020
    #3
  4. ANGHERATH
    AngHerath Win User

    Ongoing daily BSOD - DRIVER_VERIFIER_DMA_VIOLATION - ntoskrnl.exe

    Constant BSOD. Stop code: Driver_Verifier_DMA_Violation

    I regret to inform you that the BSOD has occurred again with the stop code Driver_Verifier_DMA_Violation. Would you also need the dump for that too? It is in the same folder as the others.
     
    AngHerath, Dec 8, 2020
    #4
Thema:

Ongoing daily BSOD - DRIVER_VERIFIER_DMA_VIOLATION - ntoskrnl.exe

Loading...

  1. Ongoing daily BSOD - DRIVER_VERIFIER_DMA_VIOLATION - ntoskrnl.exe - Similar Threads - Ongoing daily BSOD

  2. BSOD - DRIVER_VERIFIER_DMA_VIOLATION

    in Windows 10 Gaming
    BSOD - DRIVER_VERIFIER_DMA_VIOLATION: So apparently I was trying to use Microsoft Defender Antivirus offline scanI downloaded a fake file exe from a plagarised google sponsored website a few days back and suspect that its causing all the problems, but im also not sure if i have the problems before thatWhen the...

  3. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: KUKutter_UKFirstly, I would like to say that I am posting this again because after having an instant reply from an 'Andrew', and posting my dmp files as requested on July 24th I haven't heard anything back since! I have responded a couple of times but nothing is happening to...

  4. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: Hi there, My new machine around 8 months old now runs perfectly most of the time. Uptime 3 - 6 weeks at a time. NO issues at all - I am a heavy PC user: Gaming, Audio Work and some 3D modelling, so my machine goes through its paces.Every now and then on boot, I get the error...

  5. Ongoing BSODs - DRIVER_VERIFIER_DMA_VIOLATION

    in Windows 10 BSOD Crashes and Debugging
    Ongoing BSODs - DRIVER_VERIFIER_DMA_VIOLATION: I need assistance with identifying the cause of BSODs which started March 30. PC passed all Memtest86 tests. Minidumps are at https://1drv.ms/u/s!Anxzpza18UMVkLgj-0ciYE_ElOS4og....

  6. 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...

  7. BSOD ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe: My computer has crashed a few times often when i play games. I bought more ram because i thought that it was the issue but it didn't help. It did work a few days but then the crashes came back. After that i fixed the BSOD´s by lowering the graphics and the resolution on the...

  8. BSOD DRIVER_VERIFIER_DMA_VIOLATION

    in Windows 10 BSOD Crashes and Debugging
    BSOD DRIVER_VERIFIER_DMA_VIOLATION: I am getting a BSOD on my system intermittently. There is no specific application that triggers it, but my system is consistently connected to a Dell TB16 Dock.Here is the minidump file ....

  9. BSOD ntoskrnl..exe+1b35e0

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe+1b35e0: Help. Getting 4-5 of these a day. Running latest Windows 10 Pro, Xibo signboard, Docker with Xibo server. Always the same 'Caused By Address'. Put in new memory, ran memory test, no errors, all drivers up to date. Change disk type to AHCA, made sure windows driver was...

  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...