NX Clietn silent crash (6.0.5.41290)
CompletedHi,
I am encountering recurrent crash from NX client version 6.0.5.41290 on a fresh install on Windows 11.
The client crash (window dissapears from screen) without any warning, after random delay and random click. Sometimes it works for about 5 minutes, sometimes logner when mouse is never used. 9 cameras stream from local server are displayed in low resolution.
The log are set to DEBUG. The output is the following. I can't foind the real reason of the application crash. Can you help me to find it ?
2025-09-16 16:43:39.296 242c INFO nx::log::Logger(0x1c5afaf1710): Log file size: 10M, log volume size: 250M, time period: 0h, file: C:/Users/Lhyfe/AppData/Local/Network Optix/Network Optix HD Witness Client/log/client_log.log
2025-09-16 16:43:39.313 242c INFO START: ================================================================================
2025-09-16 16:43:39.314 242c INFO START: Network Optix HD Witness Client started, version: 6.0.5.41290, revision: c312148c5257
2025-09-16 16:43:39.314 242c INFO START: Binary path: C:/Program Files/Network Optix/Nx Witness/client/6.0.5.41290/HD Witness.exe
2025-09-16 16:43:39.314 242c INFO START: Log level: info
2025-09-16 16:43:39.314 242c INFO START: Log file size: 10M, log volume size: 250M, time period: 0h, file: C:/Users/Lhyfe/AppData/Local/Network Optix/Network Optix HD Witness Client/log/client_log.log
2025-09-16 16:43:39.314 242c INFO START: Mutex implementation: qt
2025-09-16 16:43:39.321 242c INFO nx::vms::utils::TranslationManager::Private(0x1c5afb98390): Loaded 28 translations from :/translations
2025-09-16 16:43:39.324 242c INFO nx::network::cloud::OutgoingTunnelPool(0x1c5b4aab4f8): Assigned own peer id: dc_45ba3ddf-0876-4748-95d6-1f1659f8552e_1820074169
2025-09-16 16:43:39.339 242c INFO nx::vms::common::AbstractCertificateVerifier(0x1c5afb6c9a0): Adding trusted certificate AmazonRootCA1.pem into the CA list
2025-09-16 16:43:39.353 242c INFO nx::vms::common::AbstractCertificateVerifier(0x1c5afb6c9a0): Adding trusted certificate AmazonRootCA2.pem into the CA list
2025-09-16 16:43:39.353 242c INFO nx::vms::common::AbstractCertificateVerifier(0x1c5afb6c9a0): Adding trusted certificate AmazonRootCA3.pem into the CA list
2025-09-16 16:43:39.353 242c INFO nx::vms::common::AbstractCertificateVerifier(0x1c5afb6c9a0): Adding trusted certificate AmazonRootCA4.pem into the CA list
2025-09-16 16:43:39.353 242c WARNING nx::vms::common::AbstractCertificateVerifier(0x1c5afb6c9a0): Ignore not self-signed built-in certificate isrg-root-x1-cross-signed.pem
2025-09-16 16:43:39.354 242c WARNING nx::vms::common::AbstractCertificateVerifier(0x1c5afb6c9a0): Ignore not self-signed built-in certificate isrg-root-x2-cross-signed.pem
2025-09-16 16:43:39.354 242c INFO nx::vms::common::AbstractCertificateVerifier(0x1c5afb6c9a0): Adding trusted certificate isrg-root-x2.pem into the CA list
2025-09-16 16:43:39.354 242c INFO nx::vms::common::AbstractCertificateVerifier(0x1c5afb6c9a0): Adding trusted certificate isrgrootx1.pem into the CA list
2025-09-16 16:43:39.354 242c INFO nx::vms::common::AbstractCertificateVerifier(0x1c5afb6c9a0): Adding trusted certificate SFSRootCAG2.pem into the CA list
2025-09-16 16:43:39.355 242c INFO nx::vms::client::desktop::ApplicationContext::Private(0x1c5afbb7190): Setting QML root to qrc:///qml/
2025-09-16 16:43:39.362 2ea0 ERROR nx::cloud::gateway::VmsGatewayProcess(0x1c5b4fdd550): Start after crash detected
2025-09-16 16:43:39.364 2ea0 INFO nx::network::ssl::Certificate: Certificate path is empty
2025-09-16 16:43:39.364 2ea0 INFO nx::network::ssl::Certificate: Unable to load valid SSL certificate from file ''. Generating a new one
2025-09-16 16:43:39.395 2ea0 INFO nx::network::ssl::Context(0x7ffa44ca2d40): Default certificate set to C=US, CN=Nx Witness, O=Network Optix
2025-09-16 16:43:39.395 2ea0 INFO nx::cloud::gateway::VmsGatewayProcess(0x1c5b4fdd550): Network Optix VMS Gateway has been started on { 127.0.0.1:58350 }
2025-09-16 16:43:39.396 242c WARNING QMessageLogContext(0x785b14eb80): Warning: Setting a new default format with a different version or profile after the global shared context is created may cause issues with context sharing.
2025-09-16 16:43:39.397 242c INFO nx::vms::client::desktop: IniConfig iniFilesDir: C:\Users\Lhyfe\AppData\Local\nx_ini\
2025-09-16 16:43:39.670 242c INFO QnGLCheckerInstrument: Version: 4.6.0 NVIDIA 572.16.
2025-09-16 16:43:39.670 242c INFO QnGLCheckerInstrument: Renderer: NVIDIA T600/PCIe/SSE2.
2025-09-16 16:43:39.670 242c INFO QnGLCheckerInstrument: Vendor: NVIDIA Corporation.
2025-09-16 16:43:39.859 242c INFO nx::vms::client::desktop::SelfUpdater(0x785b14f058): Applauncher is up to date
2025-09-16 16:43:39.860 242c INFO nx::vms::client::desktop::SelfUpdater(0x785b14f058): Minilauncher will not be updated.
2025-09-16 16:43:39.901 242c INFO nx::audio::AudioDevice(0x7ffa530b2ad0): Version: 1.1
2025-09-16 16:43:39.901 242c INFO nx::audio::AudioDevice(0x7ffa530b2ad0): Company: OpenAL Community
2025-09-16 16:43:39.901 242c INFO nx::audio::AudioDevice(0x7ffa530b2ad0): Device type: OpenAL Soft
2025-09-16 16:43:39.946 37b4 INFO nx::cloud::gateway::VmsGatewayProcess(0x1c5b4fdd550): Retrieved public address 130.93.161.25. This address will be used for cloud connect
2025-09-16 16:43:40.077 242c ERROR nx::vms::client::core::ColorTheme(0x1c5c406b4b0): Singleton is created more than once.
2025-09-16 16:43:40.752 242c INFO nx::vms::client::core::SvgImageProvider(0x1c5afb6b7c0): Requested an SVG image with default size: ":/skin/timeline_tooltip/arrow_right.svg"
2025-09-16 16:43:40.753 242c INFO nx::vms::client::core::SvgImageProvider(0x1c5afb6b7c0): Requested an SVG image with default size: ":/skin/timeline_tooltip/arrow_left.svg"
2025-09-16 16:43:42.963 242c WARNING QJson: Can't deserialize field `expanded` from value `0`
-
I had this issue on our computers too. It's something to do with OpenGL graphics. Force it back to DirectX. The article below will give you a batch file to run to switch the graphics. This must be done on a per user basis if multiple people sign into the computer and have separate windows accounts.
0 -
Crashes are best investigated through the crash dumps. However the solution Zack Sauve shared likely resolves the issue. Per version 6.1, we'll default to DirectX.
With kind regards.
0
Post is closed for comments.
Comments
2 comments