Dell G7 7500 - DRIVER_VERIFIER_DMA_VIOLATION (e6)

Status
Not open for further replies.
G

gkp2011

Member
Joined
Sep 13, 2020
Posts
6
Dell G7 7500 - DRIVER_VERIFIER_DMA_VIOLATION (e6)

Getting random BSODs multiple times. Updates for all drivers have been done previously and has crashed tonight about 3 times.

· OS - Windows 10 2004
x64 (64-bit)?
Original OS OEM
System about 2 months



************* Path validation summary **************
Response Time (ms) Location
Error c:\mysymbols
Deferred cache*c:\symbolcache
Deferred SRV*c:\symbols*Symbol information
Symbol search path is: c:\mysymbols;cache*c:\symbolcache;SRV*c:\symbols*Symbol information
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`5d600000 PsLoadedModuleList = 0xfffff800`5e22a310
Debug session time: Sun Sep 13 00:24:34.451 2020 (UTC - 5:00)
System Uptime: 0 days 0:00:16.176
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols

Loading unloaded module list
.........
For analysis of this file, run !analyze -v
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: ffffb10d8c863060, Device Object of faulting device.
Arg3: 000000000000002f, Faulting information (usually faulting physical address).
Arg4: 0000000000000006, Fault type (hardware specific).

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 3

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on G7-RNFVO97

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 5

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: e6

BUGCHECK_P1: 26

BUGCHECK_P2: ffffb10d8c863060

BUGCHECK_P3: 2f

BUGCHECK_P4: 6

BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


PROCESS_NAME: System

STACK_TEXT:
fffff800`63e90ea8 fffff800`5dada6e7 : 00000000`000000e6 00000000`00000026 ffffb10d`8c863060 00000000`0000002f : nt!KeBugCheckEx
fffff800`63e90eb0 fffff800`5dac660b : 00000000`00000000 00000000`00000000 fffff800`5e249c30 fffff800`5e249c30 : nt!IvtHandleInterrupt+0x1a7
fffff800`63e90f10 fffff800`5d880795 : fffff800`5e2f3a80 fffff800`63e81a50 fffff800`5e2f3b30 fffff800`5d880795 : nt!HalpIommuInterruptRoutine+0x4b
fffff800`63e90f40 fffff800`5d9f581c : fffff800`63e81a50 fffff800`5e2f3a80 00000000`000001d2 fffff800`5d9fab90 : nt!KiCallInterruptServiceRoutine+0xa5
fffff800`63e90f90 fffff800`5d9f5c27 : fffff800`63e81af0 00000000`00000001 00000000`00040046 fffff800`5d907018 : nt!KiInterruptSubDispatchNoLock+0x11c
fffff800`63e819d0 fffff800`5d9f79ca : 00000000`00000000 00000000`00000000 fffff800`5e326600 00000000`000001d2 : nt!KiInterruptDispatchNoLock+0x37
fffff800`63e81b60 00000000`00000000 : fffff800`63e82000 fffff800`63e7b000 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
---------

0: kd> !devobj ffffb10d8c863060
Device object (ffffb10d8c863060) is for:
NTPNP_PCI0030 \Driver\pci DriverObject ffffb10d8a1036c0
Current Irp 00000000 RefCount 0 Type 00000022 Flags 00001040
SecurityDescriptor ffffc18b6073bba0 DevExt ffffb10d8c8631b0 DevObjExt ffffb10d8c8638d8 DevNode ffffb10d8c8d49a0
ExtensionFlags (0x00000800) DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffb10d8c8e5e20 \Driver\ACPI
Device queue is not busy.
0: kd> !devnode ffffb10d8c8d49a0
DevNode 0xffffb10d8c8d49a0 for PDO 0xffffb10d8c863060
Parent 0xffffb10d8c8549e0 Sibling 0000000000 Child 0xffffb10d8ccc3cb0
InstancePath is "PCI\VEN_8086&DEV_15E9&SUBSYS_09F31028&REV_06\24F704E110B3020000"
ServiceName is "USBXHCI"
State = DeviceNodeEnumeratePending (0x30c)
Previous State = DeviceNodeStarted (0x308)
StateHistory[10] = DeviceNodeStarted (0x308)
StateHistory[09] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[08] = DeviceNodeEnumeratePending (0x30c)
StateHistory[07] = DeviceNodeStarted (0x308)
StateHistory[06] = DeviceNodeStartPostWork (0x307)
StateHistory[05] = DeviceNodeStartCompletion (0x306)
StateHistory[04] = DeviceNodeStartPending (0x305)
StateHistory[03] = DeviceNodeResourcesAssigned (0x304)
StateHistory[02] = DeviceNodeDriversAdded (0x303)
StateHistory[01] = DeviceNodeInitialized (0x302)
StateHistory[00] = DeviceNodeUninitialized (0x301)
StateHistory[19] = Unknown State (0x0)
StateHistory[18] = Unknown State (0x0)
StateHistory[17] = Unknown State (0x0)
StateHistory[16] = Unknown State (0x0)
StateHistory[15] = Unknown State (0x0)
StateHistory[14] = Unknown State (0x0)
StateHistory[13] = Unknown State (0x0)
StateHistory[12] = Unknown State (0x0)
StateHistory[11] = Unknown State (0x0)
Flags (0x6c0000b0) DNF_ENUMERATED, DNF_IDS_QUERIED,
DNF_BOOT_CONFIG_RESERVED, DNF_NO_LOWER_DEVICE_FILTERS,
DNF_NO_LOWER_CLASS_FILTERS, DNF_NO_UPPER_DEVICE_FILTERS,
DNF_NO_UPPER_CLASS_FILTERS
CapabilityFlags (0x00403e53) DeviceD1, DeviceD2,
Removable, UniqueID,
SurpriseRemovalOK, WakeFromD0,
WakeFromD1, WakeFromD2,
WakeFromD3
Unknown flags 0x00400000

Dump Coming soon
 
For share links please use: one drive, drop box, or google drive

The memory dump link was not opened.



There were 4 mini dumps debugged and all displayed bugcheck E6.

The logs also displayed bugcheck 14F.

There was 1 misbehaving hardware driver identified: nvlddmkm.sys








Windows 10 Business
19041




Please perform the following steps:

1) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
2) re-install the Nvidia GPU driver from the Dell or Nvidia website
3) On the Nvidia website make sure that you check the clean install box and if available install the physx driver.

Display Driver Uninstaller Download version 18.0.2.7 (or newer version if available)
Wagnardsoft

Display Driver Uninstaller: How to use - Windows 7 Help Forums
Display Driver Uninstaller: How to use - Windows 7 Help Forums

Download Drivers | NVIDIA
Download Drivers | NVIDIA

Support for Dell G7 15 7500 | Drivers & Downloads | Dell US
Challenge Page



The RAM is overclocked.

At the time the Sysnative log collector was ran RAM displayed: 3200

The Intel CPU, i7-10750H supports RAM speeds up to DDR4-2933.

Please return to stock.





Code: 
Name    NVIDIA GeForce RTX 2070 with Max-Q Design
PNP Device ID    PCI\VEN_10DE&DEV_1F14&SUBSYS_09F31028&REV_A1\4&28F60B1&0&0008
Adapter Type    GeForce RTX 2070 with Max-Q Design, NVIDIA compatible
Adapter Description    NVIDIA GeForce RTX 2070 with Max-Q Design
Adapter RAM    (1,048,576) bytes
Installed Drivers    C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvldumdx.dll
Driver Version    27.21.14.5206
INF File    oem176.inf (Section133 section)
Color Planes    Not Available
Color Table Entries    Not Available
Resolution    Not Available
Bits/Pixel    Not Available
Memory Address    0x82000000-0x82FFFFFF
Memory Address    0x70000000-0x7FFFFFFF
Memory Address    0x80000000-0x81FFFFFF
IRQ Channel    IRQ 4294967250
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVDMI.INF_AMD64_C494AEE3704C1CAD\NVLDDMKM.SYS (27.21.14.5206, 23.55 MB (24,694,504 bytes), 8/29/2020 3:15 PM)


Code: 
nvlddmkm.sys Wed Aug 12 15:15:17 2020 (5F3469F5)
 
Last edited:
The first thing to know is why you are using verifier.
If you set verifier on by mistake, just reset it with verifier /reset (launching It from an elevated command prompt, i.e. command prompt (admin)).
 
Bugcheck 0xE6 may show up even without Driver Verifier enabled
 
Re-uploaded dump via gdrive

MEMORY.7z

It's weird it shows ram overclocked, I haven't changed anything to oc, it currently configured as stock from store.
 
Lower the RAM clocks in the BIOS and see if you still have blue screens
 
So I checked in the Bios, theres no settings I could see to change the ram clocks

It looks like the pc came by default with 3200 DDR4

C:\WINDOWS\system32>wmic memorychip get devicelocator, speed
DeviceLocator Speed
DIMM A 3200
DIMM B 3200

C:\WINDOWS\system32>wmic memorychip get devicelocator, manufacturer, partnumber, serialnumber, capacity, speed, memorytype, formfactor
Capacity DeviceLocator FormFactor Manufacturer MemoryType PartNumber SerialNumber Speed
8589934592 DIMM A 12 802C00000000 0 8ATF1G64HZ-3G2J1 26F0F490 3200
8589934592 DIMM B 12 802C00000000 0 8ATF1G64HZ-3G2J1 26F0D8D5 3200

1600011480369.png


1600011510662.png

1600011525805.png
 
But hang on, the cpu will automatically clock it at it's supported speed anyway when you put in a faster ram. So that shouldn't be root of issue
 
Rich (BB code): 
0: kd> !devstack ffffb10d8c863060
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffffb10d8cc75dc0  \Driver\USBXHCI    ffffb10d8cc9cf30  USBFDO-2
  ffffb10d8c8e5e20  \Driver\ACPI       ffffb10d8c7f37f0  
> ffffb10d8c863060  \Driver\pci        ffffb10d8c8631b0  NTPNP_PCI0030
!DevNode ffffb10d8c8d49a0 :
  DeviceInst is "PCI\VEN_8086&DEV_15E9&SUBSYS_09F31028&REV_06\24F704E110B3020000"
  ServiceName is "USBXHCI"

Looking at the device stack, it appears to be related to your USB bus controller. One which is developed by Intel and other is developed by nVidia.



What devices do you have connected when the crashes occur? I assume that you have a gaming mouse attached?
 
Normally yes, corsair k95 keyboard, logitech g903

But yesterday's case, no usb attachments at all when kept crashing on me
 
Hmm, I'll need to have a look at the other dump files.

For the analysts in this thread, I think the fourth parameter might possibly correspond to the following enumeration:

Rich (BB code): 
0: kd> dt _FAULT_INFORMATION_ARM64_TYPE
nt!_FAULT_INFORMATION_ARM64_TYPE
   UnsupportedUpstreamTransaction = 0n0
   AddressSizeFault = 0n1
   TlbMatchConflict = 0n2
   ExternalFault = 0n3
   PermissionFault = 0n4
   AccessFlagFault = 0n5
   TranslationFault = 0n6
   MaxFaultType = 0n7
 
Maybe (or maybe not) I found something interesting:
Read More:

TbtBusDrv.sys is the driver for Thunderbolt(TM) Controller - 15E8.
It should be in c:\windows\system32\drivers\tbtbusdrv.sys
Version 1.41.0823.0000 (English)
Date January 26 2020 22:47:18
Size 2789320 bytes
It's a Kernel Driver and it's running.
Its "service name" is NHI.
Device ID: PCI\VEN_8086&DEV_15E8&SUBSYS_09F31028&REV_06\24F704E110B3020000
It seems already to be the latest version.

If you are not using the thunderbolt port (likely with a docking station), you can try to disable it (obviously, only after you got your precautions: system image or full backup, system restore point, backup of your important files) disabling the Thunderbolt(TM) Application Launcher from windows services and/or changing the driver start type and/or in device manager and/or in your BIOS options.

If you are using it, you can try to disable (with the same precautions of the thunderbolt port) IOMMU and the VT options in your BIOS (if you are not using virtual machines).
 
Last edited:
Status
Not open for further replies.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top