Cannot Find PXIe-1090 in MAX

[DGray3DS]

I have a PXIe-1090 rack. I can see the instruments in MAX, but not the chassis. I have run through all the database articles on this subject to no avail. I have tried this on two computers, a Dell Precision 7670 workstation laptop, and a Lenovo T14 Thinkpad laptop. The Thunderbolt Control Center on both shows the device as connected and correctly identifies it. Both the System and MXI lights on the front of the 1090 are lit green. I went through the entire set of actions in Cannot See PXIe Chassis When Using Thunderbolt, including reinstalling all software, all to no avail.

Here is a screenshot of MAX showing the hardware and software in question.

Any ideas where to go from here? I feel like I am missing something pretty basic.

[santo_13]

Nevertheless, since your PXIe-4353 and PXIe-6341 show up on NI MAX, I don't see any added value in getting the 1090 chassis show up

[DGray3DS]

They show up in MAX, but are unusable. Their channels do not show up in LabVIEW and no info shows up for them in MAX. I have seen this issue before in MXI bus expanders, and resetting the MAX configuration data usually cured it. Not this time.

Operating system for all this is fully patched and up-to-date Windows 10. I will query my IT department to see if they have restrictions on the Thunderbolt bus.

[DGray3DS]

IT department has confirmed that they do not have any policies in place to restrict the Thunderbolt ports, and our AV solution does not restrict it, either. Another thread indicated that there is a Windows 10 Thunderbolt bug, which should be cured by going to Windows 11, which could cause this issue. I am now on Windows 11 and still have the issue. When I have time, I will work through the entire list of solutions I linked earlier to see if the result is different on Win 11. In the meantime, if anyone has any ideas, please let me know.

[DGray3DS · Accepted solution]

Finally found it. One of my IT folks noticed that the devices were listed as locked in Device Manager with weird Device status.

Searching for this error led to the following NI page. This led me to the correct BIOS item to turn off restrictions to DMA from the Thunderbolt port. The setting was hiding under the virtualization settings. The Dell BIOS does not have a Vtd entry, but it does have settings for DMA access under the virtualization settings. The original article I mentioned above did mention such a BIOS setting, but did not include enough information for me to find it.

[ZCEE]

Thank you for creating this post and for taking the time to post the solution! I had the exact same issue and have been messing around with different drivers, settings, operating systems, and computers for days. I even went into the UEFI to look at the thunderbolt settings with no success.

Thanks to you, I also found the DMA settings buried in the Virtualization section of the UEFI and now everything works fine.

[dcamp]

I can confirm that a very similar issue exists with a NI PXIe-4468 installed in a NI PXIe-1090 on a Lenovo P5 workstation running Windows 11 10.0.22631. In this case, the NI PXIe-1090 is detected and seems to work correctly.  The NI PXIe-4468 shows up but any attempt to use it results in errors saying that it is not present or not working.

Disabling VT-D in the Lenovo P5 bios seems to allow us to use the PXIe-1090 / PXIe-4468 but doing so exposes the system to potential security threats.  A real solution would be great.

Driver Verifier DMA Violation Blue Screen With MXIe or Thunderbolt Modules

https://learn.microsoft.com/en-us/windows/security/hardware-security/kernel-dma-protection-for-thund...

https://learn.microsoft.com/en-us/windows-hardware/drivers/pci/enabling-dma-remapping-for-device-dri...

https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-dmaguard#dmaguard-devicee...

https://learn.microsoft.com/en-us/windows-hardware/drivers/pci/dsd-for-pcie-root-ports#identifying-e...