Topic: HDSPe causes BSOD Driver Verifier DMA Violation with Thunderbolt 3
Update: fixed in driver version 4.36 (HDSPe) and 2.16 (HDSPe FX), 12/09/2020, for TB3 expansion chassis - registry mod no longer necessary. For systems with TB3 to TB2 conversion read on.
This is information from this thread:
Using a newer computer with a second or later generation Thunderbolt 3 implementation, a TB3 to TB2 adapter (Startech or Apple) and a Sonnet Echo TB2 to ExpressCard adapter, or any TB2 to PCIe chassis, Windows throws a Blue Screen Of Death with Driver Verifier DMA Violation warning.
This issue seems not present on first generation Thunderbolt 3 implementations (the Thunderbolt Control Center is also different, and the Apple adapter won't work with that hardware).
Remedy (special thanks to forum user glittle):
It seems the BSOD caused by some strange interaction (because this issue has nothing to do with DMA) of the DMA Verifier process can be disabled via a registry entry.
is set to 0x00000002(2) by default. This has to be changed to 0x00000000(0).
There is advice to change a second entry as well:
which might not be necessary (at least it wasn't on our test systems), but as it could only improve reliability there is no reason not to change it as well.
Be careful with registry modifications as these can destroy your Windows installation easily! If you feel unsure let someone do it who knows this stuff!