Bluescreen Error - DRIVER_VERIFIER_DMA_VIOLATION (e6)

Anonymous
2022-10-05T22:44:55.387+00:00

Hello, everyone!

We have a HP ZBook 15u G6 that has bluescreened with the same DMA Violation error randomly, off and on for a couple years now. I've grabbed crash dumps and am hoping someone will be able to help me narrow down what the issue might be. Thanks in advance!

Troubleshooting steps I've already tried:
Update of all drivers, I've even tried drivers directly from the manufacturer's site.
Ran SFC and DSIM commands to clean up corrupt drivers.
Driver Verifier is turned off.
Complete reimage.

Please let me know if more information is required to assist.

DRIVER_VERIFIER_DMA_VIOLATION (e6)
An illegal DMA operation was attempted by a driver being verified.
Arguments:
Arg1: 0000000000000026, IOMMU detected DMA violation.
Arg2: ffffe384b91ae0a0, Device Object of faulting device.
Arg3: 0000000000000090, 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

Key  : Analysis.CPU.mSec  
Value: 2780  

Key  : Analysis.DebugAnalysisManager  
Value: Create  

Key  : Analysis.Elapsed.mSec  
Value: 18251  

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

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

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

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  

BUGCHECK_CODE: e6

BUGCHECK_P1: 26

BUGCHECK_P2: ffffe384b91ae0a0

BUGCHECK_P3: 90

BUGCHECK_P4: 5

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff8044dc80ea8 fffff8044a2db467 : 00000000000000e6 0000000000000026 ffffe384b91ae0a0 0000000000000090 : nt!KeBugCheckEx
fffff8044dc80eb0 fffff8044a2c72eb : 0000000000000000 0000000000000000 fffff8044aa49c10 fffff8044aa49c10 : nt!IvtHandleInterrupt+0x1a7
fffff8044dc80f10 fffff8044a008a45 : fffff8044aaf3b00 fffffb87c6e22400 fffff8044aaf3bb0 fffff8044a008a45 : nt!HalpIommuInterruptRoutine+0x4b
fffff8044dc80f40 fffff8044a1fa91c : fffffb87c6e22400 fffff8044aaf3b00 0000000000000000 fffff8044a1faa4a : nt!KiCallInterruptServiceRoutine+0xa5
fffff8044dc80f90 fffff8044a1fad27 : ffffe384ca2fa7b0 fffff8044a4ce915 ffffa19bb16822eb 0000000000000001 : nt!KiInterruptSubDispatchNoLock+0x11c
fffffb87c6e22380 fffff8044a140445 : fffffb87c6e226e8 fffff8044a17b6fa 0000000000000002 ffffe384c263f1b0 : nt!KiInterruptDispatchNoLock+0x37
fffffb87c6e22510 fffff8044a17b6fa : 0000000000000002 ffffe384c263f1b0 0000000000000002 0000000000000000 : nt!HalpPCIConfig+0xf5
fffffb87c6e22520 fffff8044c7aac79 : fffff8044c87ade2 fffffb87c6e226e8 000000000000f900 fffff8044a14eee9 : nt!HaliPciInterfaceWriteConfig+0x2a
fffffb87c6e22570 fffff8044c87b8a2 : 000000000000f900 fffff80400000002 0000001300000004 ffffe38400000002 : ACPI!AcpiWrapperWriteConfig+0x29
fffffb87c6e225c0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : pci!PciWriteDeviceConfig+0x2d2

SYMBOL_NAME: nt!IvtHandleInterrupt+1a7

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.2006

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1a7

FAILURE_BUCKET_ID: 0xE6_nt!IvtHandleInterrupt

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {2cafa897-b47c-7b20-cee6-b1b68f30ec38}

Followup: MachineOwner
---------

0: kd> !devobj ffffe384b91ae0a0
Device object (ffffe384b91ae0a0) is for:
Cannot read info offset from nt!ObpInfoMaskToOffset
\Driver\pci DriverObject ffffe384b6e2e740
Current Irp 00000000 RefCount 0 Type 00000022 Flags 00001040
SecurityDescriptor ffffd285cf9713a0 DevExt ffffe384b91ae1f0 DevObjExt ffffe384b91ae938 DevNode ffffe384b91ae9e0
ExtensionFlags (0x00000804) DOE_REMOVE_PENDING, DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffe384bc318780 Name paged out
Device queue is not busy.

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
36,441 questions
0 comments No comments
{count} vote

5 answers

Sort by: Most helpful
  1. Docs 15,151 Reputation points
    2022-10-07T02:09:26.497+00:00

    Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

    https://www.tenforums.com/bsod-crashes-debugging/

    https://www.elevenforum.com/t/bsod-posting-instructions.103/

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post there is /\ with a number: click = a helpful post
    .
    .
    .
    .
    .


  2. Docs 15,151 Reputation points
    2022-10-08T06:37:02.01+00:00

    Download and install HP UEFI hardware diagnostics version 8.7.1.0:

    https://ftp.hp.com/pub/softpaq/sp141501-142000/sp141572.exe

    Plan to run the HP UEFI hardware diagnostics overnight while sleeping.

    Power on the computer and repetitively click F2 or F10 > system > extensive > loop until error > check the results the next day > if it is has made two or more loops then > click esc > take pictures > post images or share links into this thread displaying the tests performed with results > run component tests as needed

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post there is /\ with a number: click = a helpful post
    .
    .
    .
    .
    .


  3. Docs 15,151 Reputation points
    2022-10-21T03:47:52.977+00:00

    1) Open administrative command prompt and copy and paste:

    msdt.exe -id WindowsUpdateDiagnostic
    msdt.exe -id DeviceDiagnostic
    sfc /scannow
    dism/online /cleanup-image /restorehealth

    For each Microsoft Windows troubleshooter click view detailed information > post share links into this thread

    For scannow, dism, and chkdsk post share links into this thread displaying the commands with results (type ctrl + a then ctrl + c then post into notepad or wordpad

    2) Make a new restore point:

    https://www.tenforums.com/tutorials/4571-create-system-restore-point-windows-10-a.html

    3) Read this link on Windows Driver Verifier (WDV):

    https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html

    4) Learn the methods to recover from using the tool by booting into safe mode and then running one or more of these commands:

    verifier /reset

    verifier /bootmode resetonbootfail

    5) Run the WDV tool with these settings:

    a) Test all non-Microsoft drivers
    b) Test no Microsoft drivers
    c) Start WDV with the three customized tests displayed in the Ten Forums link

    6) If there is no immediate BSOD then open administrative command prompt and type or copy and paste:

    verifier /querysettings

    Post a share link into this thread using one drive, drop box, or google drive

    7) For any BSOD post a new V2 log collector share link into the newest post

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post there is /\ with a number: click = a helpful post
    .
    .
    .
    .
    .


  4. Docs 15,151 Reputation points
    2022-10-28T02:35:02.023+00:00

    1) Make a new restore point:
    https://www.tenforums.com/tutorials/4571-create-system-restore-point-windows-10-a.html

    2) Restart WDV with these customized test settings:

    [ ] 0x00000001 Special pool.  
    [ ] 0x00000002 Force IRQL checking.  
    [ ] 0x00000008 Pool tracking.  
    [ ] 0x00000010 I/O verification.  
    [ ] 0x00000020 Deadlock detection.  
    [ ] 0x00000080 DMA checking.  
    [ ] 0x00000100 Security checks.  
    [ ] 0x00000800 Miscellaneous checks.  
    [ ] 0x00020000 DDI compliance checking.  
    [ ] 0x00080000 DDI compliance checking (additional).  
    [ ] 0x00000200 Force pending I/O requests.  
    [ ] 0x00000400 IRP logging.  
    

    If there is no immediate BSOD then open administrative command prompt and type or copy and paste: verifier /querysettings

    Post a share link into this thread using one drive, drop box, or google drive.

    For any new BSOD post a new V2 share link into the newest post.

    WDV can run in the background while the computer is used with the understanding that there could be an unexpected shutdown and restart.

    Plan to run WDV with additional customized test settings.

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post there is /\ with a number: click = a helpful post
    .
    .
    .
    .
    .

    0 comments No comments

  5. Docs 15,151 Reputation points
    2022-10-30T14:55:44.503+00:00

    Just checking if there's any progress or updates?

    0 comments No comments