06-28-2024 10:39 AM
Steps to reproduce:
NB: The issue doesn't persist in Parallels Desktop 19.4.1 because Parallels did some tweaks but the issue might occur again and exists in other Parallels Desktop versions.
06-28-2024 11:24 AM
@mushakov wrote:
NB: The issue doesn't persist in Parallels Desktop 19.4.1 because Parallels did some tweaks but the issue might occur again and exists in other Parallels Desktop versions.
So, in a nutshell, this was a bug in parallels and NI would have very little control over that.
06-29-2024 09:57 AM
Parallels applied a workaround to fix the issue for its customers but the issue is that LabVIEW loads its x86 drivers prior to the Windows drivers that makes Windows BSOD.
06-29-2024 10:29 AM
@mushakov wrote:
Parallels applied a workaround to fix the issue for its customers but the issue is that LabVIEW loads its x86 drivers prior to the Windows drivers that makes Windows BSOD.
Whatever that means...
This does not seem to be a problem for windows running on hardware, so the issue is still with parallels and fortunately they were able to fix their bug.
It is a bug fix, not a workaround, IMHO. 😄
07-01-2024 04:47 AM - edited 07-01-2024 04:53 AM
Did you do a LabVIEW install or a full LabVIEW + NI-DAQmx, + NI-VISA + NI-climbim and NI-climbam and whatever else adding up to a 50GB install or something like that?
A LabVIEW IDE install only should NOT install anything that could ever BSOD your Windows installation. NI-DAQmx, NI-VISA and NI-this and NI-that installs kernel device drivers that are compiled for Intel x64 CPUs. Windows 11 ARM does not provide full CPU virtualization for x64 software. Especially the kernel environment can not properly handle x64 virtualization.