Starlight Precise 2.6 spills into shared system memory and drops to 0 FPS on RTX 5080 16GB

Hello,

I am experiencing a repeatable performance problem with Starlight Precise 2.6. Other Topaz enhancement models work normally on the same system; this problem only occurs with Starlight Precise 2.6.

System specifications

  • GPU: NVIDIA GeForce RTX 5080, 16GB VRAM

  • CPU: Intel Core Ultra 7 270K Plus

  • RAM: 96GB DDR5

  • OS: Windows 11 25H2, build 26200

  • NVIDIA driver: 610.88

  • Topaz Video: 1.7.1

  • Two 4K displays

  • Intel integrated graphics also available

Test settings

  • Source: 9-second H.264 High Profile video

  • Resolution: 1280Ă—720

  • Frame rate: approximately 24 FPS

  • Starlight Precise 2.6

  • Sharpness/Softness level: 1

  • Output: 2560Ă—1440, 2Ă— upscale

  • No frame interpolation or additional enhancement models

  • The complete source file is exported; no In/Out trim is being used

What happens

At the beginning of the export, the RTX 5080 appears to work normally. GPU power consumption remains above 250W and processing progresses for approximately two or three minutes.

After that, performance suddenly collapses:

  • GPU power drops from over 250W to approximately 84W and never recovers.

  • Processing speed drops to 0.0 FPS.

  • The estimated remaining time increases to more than 21 hours for a nine-second video.

  • GPU temperature is only around 46°C, so this does not appear to be thermal throttling.

  • GPU clocks remain high, but GPU memory-controller utilization drops to approximately 3%.

  • Neuroserver begins using a very large amount of shared system memory.

During the stalled state, I measured approximately:

  • 10.8–11.1GB dedicated GPU memory used by neuroserver.exe

  • 14.6GB shared GPU/system memory

  • Approximately 23GB working-set RAM

  • Approximately 33GB private committed memory

The GPU may still be reported as highly utilized, but power consumption and actual processing throughput are extremely low. This looks like VRAM oversubscription followed by NVIDIA/Windows system-memory fallback and severe memory-transfer thrashing.

A shorter five-second clip has completed successfully before, but nine-second and longer clips repeatedly enter this stalled state. A 30-second 720p clip can produce an estimated processing time of more than one day.

Troubleshooting already performed

  • Completely reinstalled Topaz Video

  • Restarted Topaz Video and Windows between tests

  • Tested the Topaz maximum-memory preference at both 70% and 100%

  • Confirmed that no other GPU-heavy applications were running

  • Confirmed that temperatures, GPU clocks, PCIe link and power delivery were normal

  • Confirmed that other Topaz models work normally

Changing the maximum-memory preference did not appear to constrain Starlight Precise 2.6. In the logs, Neuroserver was still launched with:

--max-gpu-mem 16

This occurred even when the application preference was set to 70%.

Questions

  1. Is this a known memory leak or VRAM-oversubscription issue in Starlight Precise 2.6 or Neuroserver?

  2. Why does the application continue to pass --max-gpu-mem 16 when the maximum-memory preference is reduced?

  3. Is there a supported way to force a smaller temporal batch, tiled processing, or a lower effective GPU-memory budget such as 12GB?

  4. Is 16GB VRAM genuinely expected to process 720p → 1440p footage with Precise 2.6 without falling back to shared system memory?

  5. Are there any additional logs or diagnostic files I can provide to help reproduce this?

The official requirements recommend 16GB VRAM for Starlight Precise 2.6, so I would expect this 720p test to remain usable on an RTX 5080.

Thank you.

  1. There is no known vram leak at the moment. For 16gb gpu, the model will try to use the most. If there is other program occupying vram, there can be a conflict and forcing the slp to spill vram. We recommend to reduce gpu usages by other programs.
  2. There is a known issue where the ui set max-gpu-mem is not used by the model. We will fix it in the next release.
  3. Same as 2.
  4. It is expected to process such resolution without falling to shared system memory.
  5. At the moment we do not need any log files. Thanks for offering!

It honestly scares me to see this post because I’m planning on getting the same GPU specifically for Starlight Precise rendering. I’ve been seeing very similar behavior on my 7900 XTX after switching to Starlight Precise 2.6. I managed to get a few clips to work by splitting the footage into 1‑minute segments, but that workaround isn’t reliable. One of my 480p videos fails no matter what, while a 720p sample surprisingly worked once I segmented it.

The pattern is always the same: the first few minutes look normal, VRAM stays within budget (around 14GB), and then Starlight starts over‑allocating VRAM. Once it pushes past the limit, the export eventually fails.

I’ve gone back and forth between Topaz 1.6.1 and 1.7.0 several times, and I just can’t get Starlight 2.6 to behave predictably. I’ve reverted to Starlight 2.5 for now because it consistently stays within VRAM limits, and that seems to correlate with successful full exports.

EDIT/UPDATE: After bouncing back and forth between 1.6.1 and 1.7.0 trying to figure out what was going on with my system, I managed to get most of the footage to process by breaking the project into 1‑second segments. VRAM and system usage still max out, but this method lets the model finish clips that otherwise stall.

It’s possible my projects were failing for a different underlying reason, but I wanted to note that I’m also seeing VRAM consistently maxed out and the “Max GPU Memory” setting in the UI doesn’t seem to reduce VRAM usage when set lower.

@balazsnemeth.com @mcyyxsky1986 please try the new beta that was just released to see if this issue continues.

Topaz Video 1.7.1.2.beta

ALARM :police_car_light:

I’m seeing the same issue on my RTX 5080 16GB.

Please help. Not for me.

For the tiny kittens standing in the rain waiting for this render to finish.

My setup:

Windows 11

RTX 5080 16GB

Topaz Video 1.7.0

Test:

1920Ă—1080

24 FPS

Starlight Precise 2.6

Sharpness 1

no interpolation

only 5 seconds of footage

Result:

0.0 FPS

~7 hours remaining

The GPU basically gives up on life.

I’ve already requested access to the Video Beta group so I can test 1.7.1.2 beta.

If there’s any workaround in the meantime, I’d be very grateful.

The kittens would too.