Isaac sim 5.1.0 crash on windows

Important: Isaac Sim support

Isaac Sim version:

6.0.0
5.1.0
5.0.0
4.5.0
4.2.0
4.1.0
4.0.0
4.5.0
2023.1.1
2023.1.0-hotfix.1
Other (please specify):

Operating System

Ubuntu 24.04
Ubuntu 22.04
Ubuntu 20.04
Windows 11
Windows 10
Other (please specify):

GPU Information

  • Model: NVIDIA RTX A4000
  • Driver Version: 582.08

Topic Description

Isaac Sim 5.1.0 Crash & Performance Issues: Comparison of RTX 6000 (Workstation) and RTX A4000 (Laptop) during PX4/ZMQ Integration

Detailed Description

I am developing an object-tracking simulation involving Isaac Sim 5.1.0 (Windows) and PX4 Autopilot (WSL2) using the Pegasus Simulator extension. My goal is to test guidance algorithms across various scenarios.

Because the native ROS2 bridge resulted in unusable frame rates (0.4 FPS), I implemented a custom ZMQ (UDP/TCP) sender script in the Script Editor to stream RGB and Depth frames to WSL2. I am encountering different, critical stability issues on two separate hardware configurations.

System 1: System (RTX 6000 | Driver: 595.79)

  • Behavior: Initially, implementing ZMQ was successful, improving the frame rate from 0.4 FPS (ROS2) to 22 FPS (ZMQ).

  • The Issue: After a few days of operation, the application began crashing to the desktop (CTD) consistently.

  • Attempted Fixes: I have performed a clean re-installation of Isaac Sim and deleted the Omniverse cache, but the application continues to crash immediately or shortly after start.

System 2: System (RTX A4000 | Driver: 582.08)

  • Behavior: Frame rates are low, and stability is poor during the connection phase.

  • The Issue: The application crashes at two specific points:

    1. During the initial MAVLink connection to PX4.

    2. Intermittently while running the Python script in the Script Editor to send frames via ZMQ.

  • Goal: I need to identify the root cause of these crashes—whether it is a memory management issue with omni.replicator or a thread-safety conflict between the Pegasus extension and the ZMQ update loop or the silent update of OS. Because driver update was 3 months ago during that time the application is working perfectly fine after few day getting crashed.

Steps to Reproduce

  1. Launch Isaac Sim 5.1.0 with the Pegasus extension.
  2. Establish MAVLink communication with PX4 on WSL2.
  3. Run a Python script to attach RGB/Depth annotators and push data via ZMQ (PUSH socket).
  4. On RTX 6000: Application crashes after app ready.
  5. On RTX A4000: Application crashes during the MAVLink handshake or script execution.

Error Messages

(If applicable, copy and paste any error messages you received)

Screenshots or Videos

2026-04-16T06:07:51Z [602,573ms] [Warning] [carb.crashreporter-breakpad.plugin] [crash] telemetrySessionId = ‘8747484981225982595’
2026-04-16T06:07:51Z [602,575ms] [Warning] [carb.crashreporter-breakpad.plugin] [crash] terminatedByAbort = ‘0’
2026-04-16T06:07:51Z [602,577ms] [Warning] [carb.crashreporter-breakpad.plugin] [crash] totalRamBareMetalMB = ‘130777’
2026-04-16T06:07:51Z [602,579ms] [Warning] [carb.crashreporter-breakpad.plugin] [crash] totalRamLimitedMB = ‘130777’
2026-04-16T06:07:51Z [602,581ms] [Warning] [carb.crashreporter-breakpad.plugin] [crash] totalSwapBareMetalMB = ‘150233’
2026-04-16T06:07:51Z [602,583ms] [Warning] [carb.crashreporter-breakpad.plugin] [crash] totalSwapLimitedMB = ‘150233’
2026-04-16T06:07:51Z [602,584ms] [Warning] [carb.crashreporter-breakpad.plugin] [crash] userId = ‘default’
2026-04-16T06:07:51Z [602,587ms] [Warning] [carb.crashreporter-breakpad.plugin] [crash] workingDirectory = ‘E:\Mahesh Rao\isaac-sim-5.1.0’
2026-04-16T06:07:51Z [602,588ms] [Fatal] [carb.crashreporter-breakpad.plugin] [crash] Thread 32312 backtrace follows:
2026-04-16T06:07:51Z [602,590ms] [Fatal] [carb.crashreporter-breakpad.plugin] 000: gpu.foundation.plugin.dll!omni::activity::getInstance+0x12b7ee
2026-04-16T06:07:51Z [602,592ms] [Fatal] [carb.crashreporter-breakpad.plugin] 001: omni.kit.renderer.plugin.dll!carbOnPluginStartup+0x1cf5c
2026-04-16T06:07:51Z [602,594ms] [Fatal] [carb.crashreporter-breakpad.plugin] 002: omni.kit.renderer.plugin.dll!carbOnPluginStartup+0xea30
2026-04-16T06:07:51Z [602,596ms] [Fatal] [carb.crashreporter-breakpad.plugin] 003: omni.kit.renderer.plugin.dll!carbOnPluginStartup+0x10d46
2026-04-16T06:07:51Z [602,602ms] [Fatal] [carb.crashreporter-breakpad.plugin] 004: carb.eventdispatcher.plugin.dll!+0x11925
2026-04-16T06:07:51Z [602,607ms] [Fatal] [carb.crashreporter-breakpad.plugin] 005: omni.kit.loop-isaac.plugin.dll!+0x1ad8c
2026-04-16T06:07:51Z [602,612ms] [Fatal] [carb.crashreporter-breakpad.plugin] 006: omni.kit.app.plugin.dll!+0x222da
2026-04-16T06:07:51Z [602,614ms] [Fatal] [carb.crashreporter-breakpad.plugin] 007: omni.kit.app.plugin.dll!carbOnPluginQuickShutdown+0x71b5
2026-04-16T06:07:51Z [602,619ms] [Fatal] [carb.crashreporter-breakpad.plugin] 008: kit.exe!+0x66f0
2026-04-16T06:07:51Z [602,621ms] [Fatal] [carb.crashreporter-breakpad.plugin] 009: kit.exe!+0x6d0a
2026-04-16T06:07:51Z [602,623ms] [Fatal] [carb.crashreporter-breakpad.plugin] 010: kit.exe!+0x74d0
2026-04-16T06:07:51Z [602,625ms] [Fatal] [carb.crashreporter-breakpad.plugin] 011: KERNEL32.DLL!BaseThreadInitThunk+0x17
2026-04-16T06:07:51Z [602,627ms] [Fatal] [carb.crashreporter-breakpad.plugin] 012: ntdll.dll!RtlUserThreadStart+0x2c

Below are the screenshots of the issues.

System 1 (with gpu rtx 6000 and driver version: 595.79)

System 2 (with gpu A4000 and driver version: 582.08)

Hi @sunkesula.rao,

I investigated your crash report. Here’s what I found:

Primary Issue: GPU Driver 595.79 Is Not Validated

Your System 1’s driver 595.79 is from the R590 branch, which is not validated for Isaac Sim 5.1.0.

The Isaac Sim Requirements recommends 580.88.

The Omniverse Technical Requirements lists these as the validated Windows drivers for Ada/Ampere GPUs:

  • R570 branch: 573.42 (Workstation)
  • R580 branch: 581.42

Your crash backtrace (gpu.foundation.plugin!omni::activity::getInstance → omni.kit.renderer.plugin) is a renderer-level crash consistent with driver incompatibility.

You mentioned it “worked for a few days then started crashing” — this strongly suggests a silent Windows driver auto-update pushed your driver from a validated R580 version to the unvalidated 595.79.

Let us know if rolling back to recommended driver resolves the crashes!