LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Compatibility issue with AMD

Hi,

I recently have a problem of compatibilities between Labview and AMD graphic cards.

The latest one occurred with an AMD Ryzen 5 7520 using Labview 2025 Runtime, Vision dev module runtime 2025, VAS 2025, DAQMx and Visa 2025. 

The problem can display differently. Sometimes it freezes my executable (done with Labview) after a random time. Sometimes it can be seen when I open NIMax and the window freezes and/or some values in the system resources shows as loading without changing.

I solve the issue by reinstalling the AMD drivers and erasing the previous ones. Did someone have the same issue and found the origin or a different way to solve it?

0 Kudos
Message 1 of 4
(137 Views)

Are you sure you have a problem between compatibility of LabVIEW and the graphics card (GPU)?

 

The model number you provided - AMD Ryzen 5 7520 - corresponds to a CPU (processor), not a graphics card.

 

"Sometimes it freezes my executable (done with Labview) after a random time. Sometimes it can be seen when I open NIMax and the window freezes and/or some values in the system resources shows as loading without changing." - I have not experienced this behaviour before. Are you sure this is caused by the CPU and/or GPU? Seems unlikely to me.

 

NI MAX can take a long time to load, and can sometimes be unresponsive. This can happen on any CPU.

0 Kudos
Message 2 of 4
(73 Views)

@Petru_Tarabuta wrote:

Are you sure you have a problem between compatibility of LabVIEW and the graphics card (GPU)?

 

The model number you provided - AMD Ryzen 5 7520 - corresponds to a CPU (processor), not a graphics card.


I could not find any information about a 7520, just a 7520U. This chip has an embedded GPU, i.e. Radeon 610M graphics.

 

If reinstalling the drives solves a problem, just means that there was some system corruption. The entire question is very unclear, for example I don't even know what kind of procedure would be to "I solve the issue by reinstalling the AMD drivers and erasing the previous ones.". This seems like the wrong order of steps.

0 Kudos
Message 3 of 4
(33 Views)

Hi,

Thank you for your fast answer. 

I am unsure effectively if it is CPU or GPU. The main thing I know is that removing and putting back the latest AMD drivers (of course in that order !) works. I did not have this issue with Intel drivers so far.

I would have guess also that there could be some corruption but I buy the laptop already loaded with Microsoft and it happened on different AMD engines I have. 

I wanted to share in case someone had the same issue and if the community had similar experience

 

0 Kudos
Message 4 of 4
(1 View)