Hi,
Rather like this thread I've ben having intermittent problems with DRIVER_VERIFIER_DMA_VIOLATION BSODs, where the Bugcheck code is listed in WhoCrashed as follows:
0x26 doesn't appear on the Microsoft page here
Verifier is not running, and a comprehensive memory test revealed no errors.
I can't recreate the problem or even work out exactly what provokes it. I thought I'd narrowed it down to an external USB sound card because plugging that in would cause the BSOD. However, I have replaced it with a different one, that seems to employ different drivers according to device manager.
Specs:
Dell XPS 9570
CPU i9-8950HK
32Gb RAM
W10 Enterprise
Intel 630 and Nvidia GTX 1050Ti Graphics
Toshiba NVMe SSD (1TB)
RealTek Audio - unused but remains enabled
Dell TB16 Thunderbolt Dock
Just updated to W10 1809 today, but the crash occurred again since
WinDBG reveled a bit more info (below) however I am uncertain how to further narrow down the culprit, if it is indeed a flaky Driver:
---------
Minidump attached. Full dump (zipped) is too large for the forum.
Stuck
Rather like this thread I've ben having intermittent problems with DRIVER_VERIFIER_DMA_VIOLATION BSODs, where the Bugcheck code is listed in WhoCrashed as follows:
Code:
On Mon 18/02/2019 15:35:53 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021819-17312-01.dmp
This was probably caused by the following module: hal.dll (hal+0x3C6F7)
Bugcheck code: 0xE6 (0x26, 0xFFFFDE0A1209C570, 0x24, 0x6)
Error: DRIVER_VERIFIER_DMA_VIOLATION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
0x26 doesn't appear on the Microsoft page here
Verifier is not running, and a comprehensive memory test revealed no errors.
I can't recreate the problem or even work out exactly what provokes it. I thought I'd narrowed it down to an external USB sound card because plugging that in would cause the BSOD. However, I have replaced it with a different one, that seems to employ different drivers according to device manager.
Specs:
Dell XPS 9570
CPU i9-8950HK
32Gb RAM
W10 Enterprise
Intel 630 and Nvidia GTX 1050Ti Graphics
Toshiba NVMe SSD (1TB)
RealTek Audio - unused but remains enabled
Dell TB16 Thunderbolt Dock
Just updated to W10 1809 today, but the crash occurred again since
WinDBG reveled a bit more info (below) however I am uncertain how to further narrow down the culprit, if it is indeed a flaky Driver:
Code:
0: kd> !analyze -v
***
[LIST]
[*]*
[*]Bugcheck Analysis *
[*]*
[/LIST]
***
DRIVER_VERIFIER_DMA_VIOLATION (e6)
An illegal DMA operation was attempted by a driver being verified.
Arguments:
Arg1: 0000000000000026, IOMMU detected DMA violation.
Arg2: ffffde0a1209c570, Device Object of faulting device.
Arg3: 0000000000000024, Faulting information (usually faulting physical address).
Arg4: 0000000000000006, Fault type (hardware specific).
Debugging Details:
------------------
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434
SYSTEM_MANUFACTURER: Dell Inc.
SYSTEM_PRODUCT_NAME: XPS 15 9570
SYSTEM_SKU: 087C
BIOS_VENDOR: Dell Inc.
BIOS_VERSION: 1.5.0
BIOS_DATE: 09/03/2018
BASEBOARD_MANUFACTURER: Dell Inc.
BASEBOARD_PRODUCT: 07GHH0
BASEBOARD_VERSION: A00
DUMP_TYPE: 1
BUGCHECK_P1: 26
BUGCHECK_P2: ffffde0a1209c570
BUGCHECK_P3: 24
BUGCHECK_P4: 6
CPU_COUNT: c
CPU_MHZ: b58
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: a
CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: 96'00000000 (cache) 96'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0xE6
PROCESS_NAME: System
CURRENT_IRQL: c
ANALYSIS_SESSION_HOST: XPS
ANALYSIS_SESSION_TIME: 02-18-2019 16:02:58.0749
ANALYSIS_VERSION: 10.0.18317.1001 amd64fre
LAST_CONTROL_TRANSFER: from fffff80772ab76f7 to fffff807721be440
STACK_TEXT:
fffff807[ICODE]751f9eb8 fffff807[/ICODE]72ab76f7 : 00000000[ICODE]000000e6 00000000[/ICODE]00000026 ffffde0a[ICODE]1209c570 00000000[/ICODE]00000024 : nt!KeBugCheckEx
fffff807[ICODE]751f9ec0 fffff807[/ICODE]72ab2f8c : fffff807[ICODE]72ae0990 fffff807[/ICODE]72ae0990 fffff807[ICODE]72ae3900 00000000[/ICODE]00000001 : hal!IvtHandleInterrupt+0x1b7
fffff807[ICODE]751f9f10 fffff807[/ICODE]7204d8b5 : fffff807[ICODE]72ae38e0 fffff807[/ICODE]751eaa50 fffff807[ICODE]72ae3990 00000000[/ICODE]00000008 : hal!HalpIommuInterruptRoutine+0x4c
fffff807[ICODE]751f9f40 fffff807[/ICODE]721bfd0c : fffff807[ICODE]751eaa50 fffff807[/ICODE]72ae38e0 00000000[ICODE]0000034b fffff807[/ICODE]72ae38e0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff807[ICODE]751f9f90 fffff807[/ICODE]721c0107 : 00000000[ICODE]00000002 00000000[/ICODE]00000000 fffff807[ICODE]751eab00 00000000[/ICODE]00000001 : nt!KiInterruptSubDispatchNoLock+0x11c
fffff807[ICODE]751ea9d0 fffff807[/ICODE]721c1e32 : 00000000[ICODE]00000000 fffff807[/ICODE]70521180 00000000[ICODE]00000000 fffff807[/ICODE]7256a400 : nt!KiInterruptDispatchNoLock+0x37
fffff807[ICODE]751eab60 00000000[/ICODE]00000000 : fffff807[ICODE]751eb000 fffff807[/ICODE]751e4000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : nt!KiIdleLoop+0x32
THREAD_SHA1_HASH_MOD_FUNC: 0cfc1e867edaaf1fd57f2eadb5ab73d7c233a354
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 20ae85ae27421a84a25dc0b18d2368318e3b023a
THREAD_SHA1_HASH_MOD: 782650af79f96574cdba6be2f36ad0d2d7924552
FOLLOWUP_IP:
nt!KiCallInterruptServiceRoutine+a5
fffff807`7204d8b5 0fb6e8 movzx ebp,al
FAULT_INSTR_CODE: 45e8b60f
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiCallInterruptServiceRoutine+a5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: a5
FAILURE_BUCKET_ID: 0xE6_nt!KiCallInterruptServiceRoutine
BUCKET_ID: 0xE6_nt!KiCallInterruptServiceRoutine
PRIMARY_PROBLEM_CLASS: 0xE6_nt!KiCallInterruptServiceRoutine
TARGET_TIME: 2019-02-18T15:35:53.000Z
OSBUILD: 17763
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: unknown_date
BUILDDATESTAMP_STR: 180914-1434
BUILDLAB_STR: rs5_release
BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434
ANALYSIS_SESSION_ELAPSED_TIME: 1513
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xe6_nt!kicallinterruptserviceroutine
FAILURE_ID_HASH: {2b0e63ba-aae0-93ee-5379-fdfd15c60138}
Followup: MachineOwner
Minidump attached. Full dump (zipped) is too large for the forum.
Stuck
Attachments
Last edited by a moderator: