Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

PCIe-6321 Hourly errors since recent windows update

Hi,

 

we are running multiple test stands with PCIe-6321 cards. Since roughly 3 weeks we are having issues with the used DASYLab programms having errors every hour after the system start.

Most likely this started with a recent Windows 10 update (probably Servicing Stack 10.0.19041.4769 or .4892). It seems impossible to remove those Servicing Stack Upgrades.

 

We have two affected systems that still run DASYLab 9 and one with 2016SP1. I installed DASYLab 2022.1(evaluation version) on the 2016 PC and also updated DAQmx to the latest version (2024 Q3.1), but it still shows the errors.

Dasylab9 Error.PNG

Dasylab22 Error.PNG

Changing DAQmx versions on the other PCs also didn't seem to make any difference. I tried upgrading to 2024 Q3.1 as well as downgrading to 15.0.1.

 

The problem does not occur when I use a USB-6210 as data source. Also one system with DASYLab13 (DAQmx15.0 / NI Max 15.3.0f0) doesn't show these errors.

 

Has anybody similar issues or any ideas what else to try?

 

Kind Regards

Michael

0 Kudos
Message 1 of 3
(191 Views)

Since it seems related to a recent Windows system update, I would guess that something the DAQmx 63xx device driver is trying to do got degraded somehow. With other cards the necessary interrupt load or DMA transfer bandwidth might be lower and not cause the problem. Also DAQmx 15 seems to have a somewhat different driver implementation, but most likely will cause serious trouble on very new hardware motherboards with advanced PCI chipsets.

 

As such NI will need to debug this and likely will have a patch available soon, but a few weeks for detecting the problem, assigning resources to fix it, build a new driver, test, verify and validate it, and then finally releasing a new driver is pretty short.

 

I would make sure to report this to make sure NI is aware of it and then you will likely have to await DAQmx 2024 Q4 or something similar.

Rolf Kalbermatter
My Blog
0 Kudos
Message 2 of 3
(145 Views)

Hi,

I think the problem is more related to the antivirus update than the windows update. I had a similar problem before and disabling the antivirus solved it.

Message 3 of 3
(110 Views)