Windows 10 BSOD Driver DMA violation driver verifier

[FurkanAlbayrak]

My zenbook S13 throws up a BSOD upon every bootup. A DMA violation driver verifier.


The device is almost 10 months old and is up to date on all drivers. I cant figure out why it has started doing this.

I ran a Windbg preview on one of the minidumps produced during the failed bootup.


Can someone please help












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

[COLOR=rgba(30, 30, 30, 1)]Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\041921-7546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`0a800000 PsLoadedModuleList = 0xfffff807`0b42a3d0
Debug session time: Mon Apr 19 18:23:38.613 2021 (UTC + 1:00)
System Uptime: 0 days 3:55:05.344
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....................
For analysis of this file, run [/COLOR][COLOR=rgba(0, 0, 255, 1)]!analyze -v
[/COLOR][COLOR=rgba(30, 30, 30, 1)]nt!KeBugCheckEx:
fffff807`0abf5e40 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff807`11283eb0=00000000000000e6
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: 00000000004189fa, Faulting information (usually faulting physical address).
Arg4: 0000000000000006, Fault type (hardware specific).

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3999

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 23183

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

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

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

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

BUGCHECK_P3: 4189fa

BUGCHECK_P4: 6

BLACKBOXBSD: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxbsd[/COLOR][COLOR=rgba(30, 30, 30, 1)])


BLACKBOXNTFS: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxntfs[/COLOR][COLOR=rgba(30, 30, 30, 1)])


BLACKBOXPNP: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxpnp[/COLOR][COLOR=rgba(30, 30, 30, 1)])


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: csrss.exe

TRAP_FRAME: ffffbb046fe79c28 -- [/COLOR][COLOR=rgba(0, 0, 255, 1)](.trap 0xffffbb046fe79c28)
[/COLOR][COLOR=rgba(30, 30, 30, 1)]Unable to read trap frame at ffffbb04`6fe79c28

STACK_TEXT:
fffff807`11283ea8 fffff807`0acdad37 : 00000000`000000e6 00000000`00000026 00000000`00000000 00000000`004189fa : nt!KeBugCheckEx
fffff807`11283eb0 fffff807`0acc6c5b : 00000000`00000000 00000000`00000000 fffff807`0b449d70 fffff807`0b449d70 : nt!IvtHandleInterrupt+0x1a7
fffff807`11283f10 fffff807`0ab27f55 : fffff807`0b4f3c00 fffff807`1127c890 fffff807`0b4f3cb0 fffff807`11283fc0 : nt!HalpIommuInterruptRoutine+0x4b
fffff807`11283f40 fffff807`0abf77bc : fffff807`1127c890 fffff807`0b4f3c00 ffffbb04`6fe79c78 fffff807`0abf78ea : nt!KiCallInterruptServiceRoutine+0xa5
fffff807`11283f90 fffff807`0abf7bc7 : 636e6546`64657465 43327830`20444965 636e6546`20323245 48676e69`52444965 : nt!KiInterruptSubDispatchNoLock+0x11c
fffff807`1127c810 fffff807`0fa8449b : ffffbb04`6fe79c02 fffff807`1127c9e0 ffffbb04`6fe79c28 ffffbb04`6fe79c20 : nt!KiInterruptDispatchNoLock+0x37
fffff807`1127c9a0 fffff807`0fa84295 : ffffbb04`6fe79c20 ffffbb04`6fe79c01 00000000`00000084 ffffbb04`6fe79c00 : ACPI!ACPIEcServiceIoLoop+0x187
fffff807`1127ca20 fffff807`0fa8360f : 00000000`00000002 ffffbb04`6fe79c20 fffff807`1127ced0 fffff807`0fa56725 : ACPI!ACPIEcServiceDevice+0x95
fffff807`1127ca50 fffff807`0fa8331c : 00000000`0000000a 00000000`0000000a 00000000`00000000 00000000`00000000 : ACPI!AcpiEcCommonDpcHandler+0x4b
fffff807`1127ca80 fffff807`0fa7332b : fffff807`08471180 00000000`00000000 00000000`00000000 fffff807`1aeafe10 : ACPI!ACPIEcGpeServiceRoutine+0xc
fffff807`1127cab0 fffff807`0aa0781e : fffff807`08474240 fffff807`1127cee0 fffff807`08471180 fffff807`00000002 : ACPI!ACPIInterruptDispatchEventDpc+0x1d52b
fffff807`1127cbb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e


SYMBOL_NAME: nt!IvtHandleInterrupt+1a7

MODULE_NAME: [/COLOR][COLOR=rgba(0, 0, 255, 1)]nt

[/COLOR][COLOR=rgba(30, 30, 30, 1)]IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.928

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
---------[/COLOR]

Continue reading...