It is extremely unlikely that the CVI compiler is causing this issue. If there were issues in using this driver with CVI versus another compiler, they would show up at compilation, not execution. Things like if they were using data types available in the other compilers but not in CVI, or C++ code, etc. You could use a different compiler, but you would probably see the same behavior. We support compilation of our code in other environments and have external libraries and headers you can use, but I can't see it helping your problem.
Best Regards,
Chris Matthews
National Instruments