nipbcfk.sys causes BSOD on Win11 [GPIB-USB-HS+]

[rhbrown]

Hoping for any suggestions how to resolve:  recently issued with a new (Dell) laptop running Win11, and followed all NI instructions for installing latest software to support a single GPIB-USB-HS+ device (quite a procedure).  The device had worked fine for years under Win10.  The fresh install on new machine appeared to work fine, but after a reboot, BSOD indicating that nipbcfk.sys caused page error.  Every 3rd or 4th reboot seemed to succeed, but I then tried to uninstall all NI software to clear the issue - not a simple process when reboot fails.  Seems to be related to PCI bridge and newer processors.  I have no idea whether I need the full NI package and/or what part contains nipbcfk.sys (is this essential?) but I do need to get the device running again...

[MikeJohnson77]

I am struggling with the same issue.  Installed National Instruments software on 5 computers and all 5 are gong to BSOD constantly.

nipbcfk.sys is the issue.

I need the software so simply uninstalling is not a fix.   I will update if I can find a solution.  

[rolfk]

What software and versions did you install? The driver in question is part of some NI kernel driver framework and if you try to install older device drivers on newer hardware this is one of the possible problems. A newer version of that driver often solves that problem.

Did you try to install NI-488.2 version 2025Q1? https://www.ni.com/en/support/downloads/drivers/download.ni-488-2.html#559044

If your application uses NI-VISA instead did you install the latest version 2025Q1: https://www.ni.com/en/support/downloads/drivers/download.ni-visa.html#558610

Even if your application is an older application, coming with its own driver installers and claiming it needs that version, it's not likely that it will not work with the newest NI-488.2 and/or NI-VISA version.

[rhbrown]

FWIW, I did try installing NI-488.2 2024 Q3 (along with everything else needed) in Sep 2024, and thought this had solved everything - until the next BSOD came along.    

During a previous uninstallation process of NI Software 23.5, I noticed the "NI-PCI Bridge Driver 23.5 64-bit" as part 43 of 64 products being removed.  My guess is that nipbcfk.sys lives in there... 

Since NI allows you to grab earlier versions of NI-488.2 package, I tried a couple of these (going back as far as I could).  Nothing works.  I suspect the issue is not with NI-488.2 itself, but buried somewhere within the vast architecture you need to install around it.  This issue seems to have been known since at least Jan 2023, so if it wasn't fixed by 2024Q3, I'm not confident NI is committed to solving it, or even aware.  

[rolfk]

The problem might be also actually in the firmware drivers and/or firmware itself on your computer. Have you tried to update to the latest versions available from your computer manufacturer? It definitely would not be the first time that that fixes curious crashes.

The NI low level drivers make use of quite some advanced features that your PC hardware chipset provides. Firmware for PCs is quite often put together in a bit of a hurry, and while testing is quite extensive, it never tests every possible advanced feature. And most PC manufacturers do not use NI hardware drivers as part of their test framework, although they may use NI hardware to do the actual tests. 😁

[rhbrown]

Thanks Rolf - the NI product that I purchased several years ago and am trying to get working again is a USB to GPIB adaptor, so I guess the only related firmware on the computer side would be the USB driver(s).  It is a very new Dell machine and frankly I doubt this is the cause, but I hear you. 

Update from yesterday:  NI software bundle 25.0.0 installed (while docked), survived 3 reboots, but caused the usual page fault error (citing nipbcfk.sys as the cause) after I undocked the laptop and restarted.  After a few tries, I could get back into system but have uninstalled all NI s/w, once again. 

Part of me wonders if simply removing nipbcfk.sys after installation would solve the issue, but I assume it must be needed to run, and each experiment of download / installation / reboot cycling/ crash / uninstallation takes way too long.

[rolfk]

---

@rhbrown wrote:

Thanks Rolf - the NI product that I purchased several years ago and am trying to get working again is a USB to GPIB adaptor, so I guess the only related firmware on the computer side would be the USB driver(s).  It is a very new Dell machine and frankly I doubt this is the cause, but I hear you. 

---

I've used Dell computers since about 25 years and they come with regular firmware updates for BIOS as well as docking stations (since they are their own USB connected device). And yes those firmwares can have significant effect in stability of a system. I never had an NI driver misbehaving like this, but I also tend to get computers that are usually one generation behind the greatest and hottest, partly because they are more price effective for the power they provide, partly because the worst firmware bugs tend to have been fixed by then.

Dells docking station integration always has been a little finicky at times, I had computers that simply crashed when they were undocked while being active, despite Dell advertising that it should work. And sometimes a firmware update suddenly fixed such things.

So no, it's not just the USB drivers that may be the culprit, but it may be the actual chipset drivers or even the BIOS firmware, either from your computer or the docking station, although the docking station firmware probably less likely.