This problem occurs with NoMachine client running on a Windows host with a non-Intel graphics card (e.g. NVIDIA or AMD card) and only under these conditions:

- with some odd-numbered resolutions like 1536x801,1857x1057
- hardware decoding enabled

As a temporary workaround, disable the use of the hardware decoding in the client. Since the client suddenly terminates as soon as displaying the session, it's not possible to disable it via UI.

To do it manually, edit the player.cfg file in the user's home/.nx/config directory.
On Windows the .nx folder is hidden. To find it, write %USERPROFILE%\.nx in the address bar or the file browser.

Change the player.cfg file from:

<option key="Enable hardware accelerated decoding" value="true" />

to:

<option key="Enable hardware accelerated decoding" value="false" />

Then, connect the NoMachine session.