Any update on PR: 312330 ?

[smike]

Problem:  

BSOD caused by NI-DAQ mx drivers. 

See related: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000001Dt0aCAC&l=en-US 

This page declares a pull request in the works, but was also last updated back in february. 
Any news on this?
I'd much rather install a security update than whitelist any executable that happens to save itself into the NI 'Program Files' directories.

[Kyle97330]

The page calls out the problem as being with DAQmx versions 19.0-21.8.

This could mean that versions 22.x and beyond do not have this issue.  Have you tried one of them?  DAQmx can be up to 3 versions later than your LabVIEW install, so if you're trying to use LabVIEW 2019, DAQmx 2022 will still work with it.

It could also be that the problem exists on later versions and they just didn't update the affected versions part of the description on the KB page, though.

[smike]

Thanks, I'll fiddle with versions and try to get this working. I'll report back, for posterity, if I find a configuration that works well.

[Darren]

I checked on the status of that fix, and it appears to be present in NI-DAQmx 22.5 and later. I'll work on getting that KB updated.

[smike]

Running LabView 2022Q3 Patch 6 with NI-DAQmx 25.5.0f295.
Locks up every time, eventually BSOD: DPC_WATCHDOG_VIOLATION

Tried running through WinDbg but after the system crash the debug_dump is nowhere to be found (prompted for a location and I gave it Documents) - no new files there, hidden or otherwise.

Seems like it's writing to memory until the process is complete and then trying to save to file at the end, which defeats the purpose of debugging software, but I digress - that's Microsoft's problem not NI. 

Maybe someone can suggest a better debugging tool or some flags I can call the driver (nipxicms.exe) / LabView with to get a better picture of what's going on?
Please and thank you!

EDIT:
Just saw @Darren 's post. Thank you!
Please let me know if there is any information I can provide that would be helpful, since I am actually experiencing the issue.

[Darren]

I'm not a DAQmx expert, but I am seeing a number of bug reports that reference this BSOD error, but aren't specifically the issue described in that KB.

I suggest submitting a support request so one of our DAQ engineers can help you troubleshoot the issue.

[smike]

Thanks, I've passed these details on to my team member who has a request open already, as he has more direct interaction with the tools. 

I'll update with any helpful action steps they provide, to hopefully illuminate a path to success for anyone who runs into this later.