不間斷藍屏,DRIVER_VERIFIER_DMA_VIOLATION (e6)
匿名
Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\021922-10312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff802`45000000 PsLoadedModuleList = 0xfffff802`45c2a2d0
Debug session time: Sat Feb 19 12:40:59.534 2022 (UTC + 8:00)
System Uptime: 0 days 13:14:30.806
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`453f73b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff802`4b091eb0=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: 00000000403eaf8e, Faulting information (usually faulting physical address).
Arg4: 0000000000000004, Fault type (hardware specific).
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1624
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 6869
Key : Analysis.Init.CPU.mSec
Value: 374
Key : Analysis.Init.Elapsed.mSec
Value: 42779
Key : Analysis.Memory.CommitPeak.Mb
Value: 93
FILE_IN_CAB: 021922-10312-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: e6
BUGCHECK_P1: 26
BUGCHECK_P2: 0
BUGCHECK_P3: 403eaf8e
BUGCHECK_P4: 4
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: ffffae8717157040 -- (.trap 0xffffae8717157040)
Unable to read trap frame at ffffae87`17157040
STACK_TEXT:
fffff802`4b091ea8 fffff802`454db3f7 : 00000000`000000e6 00000000`00000026 00000000`00000000 00000000`403eaf8e : nt!KeBugCheckEx
fffff802`4b091eb0 fffff802`454c6ffb : 00000000`00000000 00000000`00000000 fffff802`45c49d30 fffff802`45c49d30 : nt!IvtHandleInterrupt+0x1a7
fffff802`4b091f10 fffff802`452de205 : fffff802`45cf3bc0 fffff802`4b082a90 fffff802`45cf3c70 00000000`00000000 : nt!HalpIommuInterruptRoutine+0x4b
fffff802`4b091f40 fffff802`453f8d2c : fffff802`4b082a90 fffff802`45cf3bc0 00000000`00000304 fffff802`453fe0a0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`4b091f90 fffff802`453f9137 : fffff802`4b082b30 00000000`00000001 00000000`00040046 fffff802`45217138 : nt!KiInterruptSubDispatchNoLock+0x11c
fffff802`4b082a10 fffff802`453faeda : 00000000`00000000 fffff802`45d27a00 ffffae87`17157040 00000000`00000304 : nt!KiInterruptDispatchNoLock+0x37
fffff802`4b082ba0 00000000`00000000 : fffff802`4b083000 fffff802`4b07c000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
SYMBOL_NAME: nt!IvtHandleInterrupt+1a7
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.1526
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1a7
FAILURE_BUCKET_ID: 0xE6_nt!IvtHandleInterrupt
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {2cafa897-b47c-7b20-cee6-b1b68f30ec38}
Followup: MachineOwner
---------
Windows for home | Windows 10 | 裝置和驅動程式
鎖定的問題。 此問題已從 Microsoft 支援服務社群移轉。 您可以對其是否有幫助進行投票,但無法對問題新增註解或回覆,或進行追蹤。