I have a user connecting to XP SP3 from 8.1 that occassionally has the Node Process crash on the remote side, prohibiting him from connecting any further.
logs reveal:
Module: C:\Program Files\NoMachine\bin\nxnode.bin pid some-pid
Thread: some-thread exception 0xc0000024, 'Unknown'
In: C:\WINDOWS\system32\ntdll.dll at 0x7c9673be
#0 ntdll.dll(RtlRaiseStatus)
#1 ntdll.dll(RtlDeleteAce)
#2 ntdll.dll(RtlLeaveCriticalSection)
#3 libnx.dll(ZN2Io7disableEP8WaitableP5Timer)
#4 libnx.dll(ZN17DispatchTimerList14removeRunnableEP8RunnableP5Timer)
#5 libnxdi.dll(ZN24DisplayServerApplication8addAudioEv)
#6 libnxdiag.dll(NXDisplayServerAudio)
#7 libnxdiag.dll(nxagentHandleRegion)
#8 libnxdiag.dll(nxagentHandleRegion)
#9 libnxdimi.dll(ZN12MirrorPoller14grabberHandlerEiPPcS1_)
#10 libnxc.dll
#11 kernel32.dll(GetModuleFileNameA)
sometimes the traceback is:
#0 ntdll.dll(RtlRaiseStatus)
#1 ntdll.dll(RtlDeleteAce)
#2 ntdll.dll(RtlLeaveCriticalSection)
#3 libnx.dll(ZN7Monitor4loopEPv)
#4 kernel32.dll(GetModuleFileNameA)
I have other users that connect via OS X to various Windows machines or Windows to various Linux machines, but no others that have this same particular situation to compare.
Any help would be most appreciated.
P.S. the code tag automatically closes on whitespace. I’d consider that a bug.