N
Nick V28
Hello,
I have a Lenovo X1 Extreme Gen 2 having a BSOD almost every night. Running Win 10 Pro V2004 - Intel i9-9880H CPU + 32GB RAM.
Laptop is connected to Lenovo Thinkpad thunderbolt 3 gen 2 docking station.
Connected to LG 34 inch wide screen monitor.
All drivers/BIOS/NVidia are up to date.
BSOD viewer output:
==================================================
Dump File : 120820-12406-01.dmp
Crash Time : 12/7/2020 11:44:26 PM
Bug Check String : DRIVER_VERIFIER_DMA_VIOLATION
Bug Check Code : 0x000000e6
Parameter 1 : 00000000`00000026
Parameter 2 : ffffdb85`99f3c060
Parameter 3 : 00000000`00000060
Parameter 4 : 00000000`00000005
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f5210
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+3f5210
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\120820-12406-01.dmp
Processors Count : 16
Major Version : 15
Minor Version : 19041
Dump File Size : 1,081,812
Dump File Time : 12/8/2020 8:25:30 AM
==================================================
WinDBG output:
*******************************************************************************
* *
* 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: ffffdb8599f3c060, Device Object of faulting device.
Arg3: 0000000000000060, Faulting information (usually faulting physical address).
Arg4: 0000000000000005, Fault type (hardware specific).
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3390
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on NVADASZ2-LT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 22648
Key : Analysis.Memory.CommitPeak.Mb
Value: 93
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: ffffdb8599f3c060
BUGCHECK_P3: 60
BUGCHECK_P4: 5
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: explorer.exe
STACK_TEXT:
fffff801`62c9fea8 fffff801`5f0d9fe7 : 00000000`000000e6 00000000`00000026 ffffdb85`99f3c060 00000000`00000060 : nt!KeBugCheckEx
fffff801`62c9feb0 fffff801`5f0c5f0b : 00000000`00000000 00000000`00000000 fffff801`5f849cd0 fffff801`5f849cd0 : nt!IvtHandleInterrupt+0x1a7
fffff801`62c9ff10 fffff801`5ee2ecd5 : fffff801`5f8f3b00 ffffc509`fb807d20 fffff801`5f8f3bb0 fffff801`5ee2ecd5 : nt!HalpIommuInterruptRoutine+0x4b
fffff801`62c9ff40 fffff801`5eff6b8c : ffffc509`fb807d20 fffff801`5f8f3b00 00000000`00000000 fffff801`5eff6cba : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`62c9ff90 fffff801`5eff6f97 : 00000000`00000000 00000010`00000000 ffff838d`00000000 c69a8873`00000028 : nt!KiInterruptSubDispatchNoLock+0x11c
ffffc509`fb807ca0 ffff83c3`b810cc28 : fffff801`5f006bb5 ffffdb85`b3bdf080 00000000`00000000 ffffc50a`00000000 : nt!KiInterruptDispatchNoLock+0x37
ffffc509`fb807e38 fffff801`5f006bb5 : ffffdb85`b3bdf080 00000000`00000000 ffffc50a`00000000 ffffdb85`00000000 : win32k!NtGdiSelectBitmap
ffffc509`fb807e40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
SYMBOL_NAME: nt!IvtHandleInterrupt+1a7
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.630
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
Continue reading...
I have a Lenovo X1 Extreme Gen 2 having a BSOD almost every night. Running Win 10 Pro V2004 - Intel i9-9880H CPU + 32GB RAM.
Laptop is connected to Lenovo Thinkpad thunderbolt 3 gen 2 docking station.
Connected to LG 34 inch wide screen monitor.
All drivers/BIOS/NVidia are up to date.
BSOD viewer output:
==================================================
Dump File : 120820-12406-01.dmp
Crash Time : 12/7/2020 11:44:26 PM
Bug Check String : DRIVER_VERIFIER_DMA_VIOLATION
Bug Check Code : 0x000000e6
Parameter 1 : 00000000`00000026
Parameter 2 : ffffdb85`99f3c060
Parameter 3 : 00000000`00000060
Parameter 4 : 00000000`00000005
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f5210
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+3f5210
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\120820-12406-01.dmp
Processors Count : 16
Major Version : 15
Minor Version : 19041
Dump File Size : 1,081,812
Dump File Time : 12/8/2020 8:25:30 AM
==================================================
WinDBG output:
*******************************************************************************
* *
* 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: ffffdb8599f3c060, Device Object of faulting device.
Arg3: 0000000000000060, Faulting information (usually faulting physical address).
Arg4: 0000000000000005, Fault type (hardware specific).
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3390
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on NVADASZ2-LT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 22648
Key : Analysis.Memory.CommitPeak.Mb
Value: 93
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: ffffdb8599f3c060
BUGCHECK_P3: 60
BUGCHECK_P4: 5
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: explorer.exe
STACK_TEXT:
fffff801`62c9fea8 fffff801`5f0d9fe7 : 00000000`000000e6 00000000`00000026 ffffdb85`99f3c060 00000000`00000060 : nt!KeBugCheckEx
fffff801`62c9feb0 fffff801`5f0c5f0b : 00000000`00000000 00000000`00000000 fffff801`5f849cd0 fffff801`5f849cd0 : nt!IvtHandleInterrupt+0x1a7
fffff801`62c9ff10 fffff801`5ee2ecd5 : fffff801`5f8f3b00 ffffc509`fb807d20 fffff801`5f8f3bb0 fffff801`5ee2ecd5 : nt!HalpIommuInterruptRoutine+0x4b
fffff801`62c9ff40 fffff801`5eff6b8c : ffffc509`fb807d20 fffff801`5f8f3b00 00000000`00000000 fffff801`5eff6cba : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`62c9ff90 fffff801`5eff6f97 : 00000000`00000000 00000010`00000000 ffff838d`00000000 c69a8873`00000028 : nt!KiInterruptSubDispatchNoLock+0x11c
ffffc509`fb807ca0 ffff83c3`b810cc28 : fffff801`5f006bb5 ffffdb85`b3bdf080 00000000`00000000 ffffc50a`00000000 : nt!KiInterruptDispatchNoLock+0x37
ffffc509`fb807e38 fffff801`5f006bb5 : ffffdb85`b3bdf080 00000000`00000000 ffffc50a`00000000 ffffdb85`00000000 : win32k!NtGdiSelectBitmap
ffffc509`fb807e40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
SYMBOL_NAME: nt!IvtHandleInterrupt+1a7
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.630
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
Continue reading...