Windows 10: 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 preview but could not get to the source of the bluescreen see bugcheck analysis at the bottom.

According to this website https://askbob.tech/why-am-i-getting-a-stop-e6/ the error means there is an I/O Violation which can occur even with driver verifier disabled.

OS is WIndows 10 2004, all the latest Windows Updates are installed. All drivers are at most 2 weeks old, the device is basically brand new hardware as well as OS install.

The Notebook is connected to a "Lenovo ThinkPad Thunderbolt 3 Dock Gen 2"

The BSOD cannot be reproduced, but I really need to know what caused it to prevent such a thing in the future.

Ran SFC and DISM and they finished without fixing any errors ,reporting all good.


Any help is greatly appreciated



*******************************************************************************
* *
* 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: ffffb98bc64790a0, Device Object of faulting device.
Arg3: 00000000000000a0, 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: 5671

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on myComputer

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 11105

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

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: e6

BUGCHECK_P1: 26

BUGCHECK_P2: ffffb98bc64790a0

BUGCHECK_P3: a0

BUGCHECK_P4: 5

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff807`4369eea8 fffff807`3eada6e7 : 00000000`000000e6 00000000`00000026 ffffb98b`c64790a0 00000000`000000a0 : nt!KeBugCheckEx
fffff807`4369eeb0 fffff807`3eac660b : 00000000`00000000 00000000`00000000 fffff807`3f249c30 fffff807`3f249c30 : nt!IvtHandleInterrupt+0x1a7
fffff807`4369ef10 fffff807`3e880795 : fffff807`3f2f3a80 fffff807`4368fa50 fffff807`3f2f3b30 fffff807`4369efc0 : nt!HalpIommuInterruptRoutine+0x4b
fffff807`4369ef40 fffff807`3e9f581c : fffff807`4368fa50 fffff807`3f2f3a80 00000000`000001bc fffff807`3e9fab90 : nt!KiCallInterruptServiceRoutine+0xa5
fffff807`4369ef90 fffff807`3e9f5c27 : fffff807`4368faf0 00000000`00000001 00000000`00040046 fffff807`3e907018 : nt!KiInterruptSubDispatchNoLock+0x11c
fffff807`4368f9d0 fffff807`3e9f79ca : 00000000`00000000 fffff807`3f326600 ffffb98b`c4c7f040 00000000`000001bc : nt!KiInterruptDispatchNoLock+0x37
fffff807`4368fb60 00000000`00000000 : fffff807`43690000 fffff807`43689000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


SYMBOL_NAME: nt!IvtHandleInterrupt+1a7

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.508

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

:)

 

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.

 

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.

 

DRIVER_VERIFIER_DMA_VIOLATION

HI,

I try your recommendation, I uninstall my avast from laptop also I update all drivers, firmware (from official site of dell), and Docks TB16 firmware and drivers because mostly it happen when it is connected with docks Dell Thunderbolt Dock (TB16). Now we
will see if everything is ok.

Best regards,

Meriton