SECURE_PCI_CONFIG_SPACE_ACCESS_VIOLATION - What failed: nipcibrd.sys

[jrinpotomac]

Trying to create a distributable program to be installed on a Windows 11 computer. Below is a full description of what I am trying to do.

On a Windows 10 computer with LabWindows/CVI 2020 f3, I am building a distributable for installation on a Windows 11 computer.

I copy the cvidistkit onto a USB flash drive.

On running the distributable on the Windows 11 computer, it reports that the program was installed and that a reboot is required to finish the installation/setup.

Rebooting causes a Blue Screen Error.
- Stop Code: SECURE_PCI_CONFIG_SPACE_ACCESS_VIOLATION
- What failed: nipcibrd.sys

The only NI device that will be attached to this Windows 11 computer is an USB-6210 device. It seems that during the build process on the Windows 10 computer, unneeded device drivers are being included.

The Windows 11 computer does not have any NI product software on the computer.

Please advise as to how I can create a distributable on the Windows 10 computer that will work on the Windows 11 computer given that the only NI device for this computer is a USB-6210.

Tech support has not been able to provide me an answer yet.

I have read the "NI Product Compatibility for Microsoft Windows 11" and have look at other documents and forum topics.

Thanks

[rolfk]

NI-DAQmx is NOT an unneeded device driver when you use an USB-6210 device. And NI-DAQmx has various kernel device drivers and one of them is nipcibrd.sys driver. Despite its name it is not only for PCI boards but handles also things related to the chipset in your PC which contains all kinds of PCI related technology, also for the internal bus that connects your USB ports to the CPU bus.

Your problem is most likely that you have a fairly new PC hardware with a new chipset that supports some advanced features that the Windows 11 chipset driver enables and the NI DAQmx driver stumbles over since it had no idea that such a feature can be present when the driver was developed and tested.

The best would actually be to remove the DAQmx installer from the Installer Build in LabWindows CVI and instead install a more recent DAQmx driver from the NI download on that Windows 11 computer. Depending if it is a Windows 11 compatibility problem or some very specific hardware support problem you may need at least DAQmx 2022 Q3 (for Windows 11 compatibility) or maybe even a newer one like DAQmx 2023 Q3 if it is a very new computer with some advanced CPU and chipset.

[MarcelK]

nipcibrd.sys is usually not needed for DAQmx. It's part of the "PXI platform services" that causes bluescreens all over the company here, fortunately it can be uninstalled without negative side effects (directly use the MSI in "C:\Users\All Users\National Instruments\MDF\ProductCache\NI-PCI Bridge Driver [xx.xx.xxxxx]" for that). Not sure how to not include it in your distribution, the dependencies in NI software have become quite bonkers.

[rolfk]

It may depend what sort of DAQmx hardware you use. With Ethernet and possibly USB based devices it may indeed not be needed. With PCI(e) or PXI(e) hardware it for sure would be used in some way. Similar might be true for other bus systems that use internally PCI protocol mechanisms (eg. USB3).

[jrinpotomac]

Thank you everyone for your input. The computer I am using is a Panasonic FZ55 model Mk3. Does anyone have experience with this computer in regard to the problem encountered. I have been able to copy a windows image backup to my C drive. I can now boot the computer. My program runs but does not see the USB-6210 device.

[jrinpotomac · Accepted solution]

Solved the problem. Used latest 2025 Q1 NiDaqmx with LW/CVI 2020 f3.