PXIe-8301 Thunderbolt blocked Code 55

[E36M3]

Hi,

My issue is exactly this: PXIe-8301 Error Code 55 in Windows Device Manager - NI.

Is there an update in the works for PXI platform services that will allow the PXIe-8301 to operate with kernel DMA protection enabled? 

I was able to briefly disable kernel DMA protection, verifying that I could then communicate properly to my PXIe-1085 and cards through my PXIe-8301. Unfortunately, I am not allowed to turn this protection off at the lab where I work. 

It seems that enabling kernel DMA protection shouldn't mean a thunderbolt peripheral won't work at all: Kernel DMA Protection - Windows Security | Microsoft Learn (see "User Experience"). I do not plug my laptop (Dell Precision 7540, windows 10 enterprise 10.0.19044, hardware abstraction layer 10.0.19041.2728) into the PXIe-8301 until after I am logged in to windows, yet still get code 55 in device manager and broken communication.

[santo_13]

---

@E36M3 wrote:

Hi,

My issue is exactly this: PXIe-8301 Error Code 55 in Windows Device Manager - NI.

Is there an update in the works for PXI platform services that will allow the PXIe-8301 to operate with kernel DMA protection enabled? 

I was able to briefly disable kernel DMA protection, verifying that I could then communicate properly to my PXIe-1085 and cards through my PXIe-8301. Unfortunately, I am not allowed to turn this protection off at the lab where I work. 

It seems that enabling kernel DMA protection shouldn't mean a thunderbolt peripheral won't work at all: Kernel DMA Protection - Windows Security | Microsoft Learn (see "User Experience"). I do not plug my laptop (Dell Precision 7540, windows 10 enterprise 10.0.19044, hardware abstraction layer 10.0.19041.2728) into the PXIe-8301 until after I am logged in to windows, yet still get code 55 in device manager and broken communication.

---

If the only way to get the 8301 to work is by disabling DMA protection, do you have a way to persuade IT to disable it?

[E36M3]

Hi Santhosh - I requested a policy exception but haven't heard back yet. I was wondering whether to hold out hope that the NI driver might be updated to behave as described in the Microsoft Learn article on Thunderbolt peripherals and kernel DMA protection. I'm not sure which would take longer, a new driver from NI, or an exception from our IT department 😉