Question Windows 10 crash with DRIVER_VERIFIER_DMA_VIOLATION

[GGent]

Hello, everybody. Have an issue with windows crash. Time to time it is crash with DRIVER_VERIFIER_DMA_VIOLATION
Can not find a correct reason for it.
Can you help me please to find a root cause for it?
I have learned that is a driver problem but which one?
DMP file is attached.
https://drive.google.com/file/d/1lewuPgsM0R1RoLF6p2uuj_XsbcU_c7MH/view?usp=sharing

Thank you in advance!

UPD: Memory have checked already and no problems found.

 

[ubuysa]

This bugcheck can only happen when you have Driver Verifier enabled, so why do you have Driver Verifier enabled? And with which settings?

Driver Verifier is a troubleshooting tool for detecting misbehaving drivers, is is NOT normal to have it enabled unless you are troubleshooting.

The dump you uploaded is inconclusive I'm afraid. It was caused by Driver Verifier because IOMMU detected a driver misusing DMA. However, the device node address, which identifies the device, is not available in the dump, so I can't tell you from this dump what caused the failure from this dump alone.

Unless you are troubleshooting some issue you should disable Driver Verifier by entering the command verifier /reset.

 

[johnbl]

looks like you did not turn on the verifier flags, just one of your drivers is getting flagged by verifier automatic checks.

I would remove any of this special drivers/hardware that you are not using. if you are using all of it, I would go into bios and disable any hardware device that you do not need. If you need everything, I would go into bios and make any change and change it back and save the configuration. This should rebuild the database of hardware settings that the bios has assigned and sends to windows.
I would also go into windows control panel, device manager. find the menu item to show hidden devices, check it to show them, then go and delete every greyed out entry shown in the list.

i would also start cmd.exe as an admin and run
dism.exe /online /cleanup-image /restorehealth
(this should fix your modified windows files, but it might break the program that modified the files)
(I assume the modifications are from the hardware copy protection software) (aladdin Knowledge Systems) (out of business?)


-----------
modified windows core files.

the only verifier flag set was
[X] (0x00000000) Automatic Checks

I think the problem is going to be with the special usb rs232 recording software or in the Siemans usb drivers.

old driver installed:
C:\Windows\system32\drivers\WinCCRtKbdFilter.sys Tue Aug 21 03:36:02 2012
vuhub.sys Wed Dec 9 01:58:48 2015
plcsimlwf.sys Wed Apr 6 05:42:37 2022 (driver for simulation of programmable logic arrays)
npf.sys Thu Feb 28 17:31:24 2013 (old driver to capture network traffic)
hardlock.sys Thu Jun 21 18:45:47 2018 (Aladdin Knowledge Systems )
fusbhub.sys Wed Dec 9 01:58:14 2015
eusbstub.sys Wed Dec 9 01:57:52 2015
ortkbdrtmwdf.sys Fri Dec 9 00:17:50 2016
CProCtrl.5.0.0.10008.sys Tue Jan 19 16:46:41 2021
aksdf.sys Thu Nov 17 08:28:28 2016
aksfridge.sys Tue Aug 27 02:18:23 2019

============

machine info:
BiosVendor = HP
BiosVersion = U85 Ver. 01.14.00
BiosReleaseDate = 01/14/2025
SystemManufacturer = HP
SystemProductName = HP ProBook 450 15.6 inch G9 Notebook PC
SystemFamily = 103C_5336AN HP ProBook
SystemVersion = SBKPF,SBKPFV2
SystemSKU = 5Y3T8EA#ABB
BaseBoardManufacturer = HP
BaseBoardProduct = 8AA1
BaseBoardVersion = KBC Version 21.71.00
0: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 2496
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 154 Stepping 4
ProcessorNameString = REG_SZ 12th Gen Intel(R) Core(TM) i5-1235U
Update Status = REG_DWORD 2
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD 43600000000

 

[johnbl]

note: if you change the memory dump type to kernel and provide memory.dmp file I can read name of the device that caused the problem.

you might be able to see a device in device manager that is having problems and remove the device and let windows plug and play reinstall it to get it to work correctly.

after you figure out the device, you might be able to run the verifier.exe and tell windows to exclude the driver from automatic testing.
note: running (not sure of the version)
Intel(R) Innovation Platform Framework (IPF)