NoMachine 4.5.0 client ‘access violation’

[steffen]

Hello,

I installed the free version of NoMachine onto a Windows 7 (64 bit, German) pc and I defined a connection to the NX server. I ‘m able to start the session and can login to the NX server successfully. After that I need to choose my desktop environment. Shortly after I clicked on either GNOME or KDE the program windows disappears. I logged in to the mentioned pc as a different user and after that I installed  5.2.21, always same result. See attachments please. It works fine on a different pc using the same settings and the same credentials.

Any ideas?

[Britgirl]

Hi, it would be better if we could see the logs from your connecting client version 5.2.21. You say that you also reproduced it after installing 5.2.21 on your connecting client, so we will investigate the bug on the latest version.

Since you’ve installed the free version of NoMachine that means we will need server and client logs from that client machine as they will include the nxtrace.log. Note: we are not asking for the logs from the machine that you are connecting to.
https://www.nomachine.com/DT07M00098

Please send them to forum[at]nomachine[dot]com making sure you include reference to this topic.

[Britgirl]

The client logs were missing it seems. Please send those from the 5.2.21 version. The .nx directory, and to be exact the R-* directories from there is what we will be looking for.

https://www.nomachine.com/DT07M00098#7

[steffen]

Hello,

I sent an email again some minutes ago. Didn’t you received my last email to forum[at]nomachine[dot]com? It was sent on 23.05.2017. This information would be very helpful.

Thanks Steffen

[Britgirl]

Yes, we did receive it. But that time you didn’t attach the .nx directory, your second email had it attached. Anyway, they don’t show anything that would tell us what is happening other than we can see that something is crashing when libraries are being loaded. We can pass you a debug version (for 5.2.21, not for an earlier version) if you are interested in installing it and extracting the logs – they’ll give us additional details.

[steffen]

Hello

Yes, I’m interested. It would be helpful to get it to work. Just let me know what I have to do.

[Britgirl]

We use Microsoft’s DXVA and DirectX 9 APIs for hardware decoding acceleration on Windows platforms. The problem you’re having is that this function from DX9 returns to us invalid values of frame stride. Without the correct value we can’t process frame and therefore this crash happens. You can switch to software decoding by setting key “Enable hardware accelerated decoding” in player.cfg to “disabled” – in this case by default you’ll be using VP8 decoding, unless you follow steps in article https://www.nomachine.com/AR10K00696 or buy AVC Pack to enable H264 software decoding. Other possibility would be to update graphics drivers and DirectX. Also make sure you don’t have any custom DirectX libraries in your system in default paths that could be loaded instead of original ones.

[Author]

Posts