D5 Render Crashing When Starting Render

Get Help
1

Hello,

I’m facing an issue with D5 Render where the software crashes as soon as I start rendering. This happens even when I open a completely empty file and try to render—there is no heavy model or scene in it.

The application closes immediately when I click render, making it impossible to use the software.

Could you please help me resolve this issue or guide me on what might be causing it?

2

Hi @design30

Thanks for reaching out. Could you please confirm which version of D5 you are using? Please update to the latest version, as many rendering-crash issues have been resolved in it. Once updated, restart D5, try rendering again, and let me know if the problem persists.

1 Like
3

Hi @ela , I’m having the same problem since i updated, everything was working fine since the 3.0.1 update today, please release a fix, not only when i click render it just crashes after 1 or 2 minutes.

4

Tengo dos días con el error al darle “render” se abre la carpeta para guardar y comenzar el renderizado pero en milésimas de segundo después se cierra automáticamente, me pasa exactamente lo mismo cuando quiero abrir un archivo se cierra el programa.

Necesito una solución lo antes posible, si alguien ya le paso ayúdeme

5

Hi! That happened to me a week ago, and here is how it went for me and how I solved!

From one day to the next, without changing anything on my side, D5 started closing itself during rendering with no error message at all. It would consistently die around 10–11% (sometimes later), and it didn’t matter if the file was brand new and empty or an older project — same result: it would reach that early “calculating” stage and then just vanish.

At first I assumed it was project-related, but the key detail was that it also happened in a completely empty scene, so it didn’t feel like “one bad file”. I had previously triggered a TDR crash a couple of days earlier while stress-testing Real Displacement, and after that I hadn’t rendered again until the day this started.

I checked the obvious things (updates, drivers, etc.) and Windows wasn’t giving me anything useful: Event Viewer / Reliability Monitor showed nothing relevant around the time of the shutdown (only generic Windows noise). Running D5 as admin also behaved strangely (projects missing in the launcher), but it didn’t explain the render crash either.

So the situation was basically: D5 closes during “Calculating” at ~10–11% with zero logs/errors, even on an empty scene, and Windows doesn’t clearly report a GPU reset or app crash.

I went through the usual checklist because it really looked like a silent crash:

  • Checked for updates (Windows / NVIDIA / D5): nothing had changed in the last few days.
  • Tried running D5 as Administrator: interesting side effect — the Launcher didn’t show any recent projects when run as admin, but it did when run normally. This ended up being a red herring (different user context / recent list), not the cause of the render crash.
  • Looked for Windows evidence: Event Viewer (System/Application) + Reliability Monitor. Nothing useful tied to the actual crash moment (no clear LiveKernelEvent / WHEA / Display 4101 around it).
  • TDR-related actions (because I’d hit a TDR earlier): verified TdrDelay / TdrDdiDelay were set (raised them to test), cleaned DirectX shader cache, reset D5 state/preferences — still crashing at the same early percentage.
  • Disabled HAGS (Hardware-accelerated GPU scheduling): the crash point shifted (from ~10–11% to ~25%), but it still shut down with no message. That was a strong hint it was graphics-stack/state related, not the project file itself.
  • Driver clean install: used DDU + installed NVIDIA Studio driver clean. Same behavior: still closing around ~25% with no meaningful Windows log entry.
  • Output path tests: local desktop vs server output folder — no difference.

At this point the key observation was: even a completely empty scene would crash, so this wasn’t about Cesium, assets, or one corrupted project file. It looked like a broken D5 install state / config / cache that Windows wasn’t reporting cleanly.

What finally fixed the “crash even in empty scene” problem was a full reinstall of D5 / Launcher with personal config removed:

  • Uninstalled D5 / D5 Launcher
  • During uninstall (using Revo in my case, but you can do it manually), I made sure to check “Remove personal configuration”
  • Reinstalled D5
  • After that, I opened a brand new empty scene and it rendered and saved correctly — no more early-percent shutdowns.

That confirmed the root cause of the first issue was corrupted / unstable app state (config/cache/launcher state) rather than GPU power or a specific project.

Hope it helps!