Issue with the system while using ASTER

[NickSayfer]

Hello everyone,

I’m facing a rather tricky issue and would appreciate any help.

The task: I need to run 4–5 instances of the same game on a single PC.

What I’ve done so far:

Created 4 virtual desktops.

Set up virtual monitors on each desktop.

Installed Parsec on each desktop to connect to them from the same PC.

Everything seemed to work at first.

The problem:

I couldn’t get more than 2 game instances to run simultaneously without crashes.

When attempting to launch the 3rd instance, the system started exhibiting strange behavior:

File Explorer would not open or would restart unexpectedly;

Parsec would fail to connect to the desktop or crash;

Other software started behaving erratically.

Error logs from Windows Event Viewer:

Application crash log:

Faulting application name: Moonlight.exe, version: 6.1.0.0, timestamp: 0x66e8f103
Faulting module name: nvoglv64.dll, version: 32.0.15.9174, timestamp: 0x6953da3b
Exception code: 0xc0000005
Fault offset: 0x0000000000c2b848
Faulting process ID: 0x9390
Application start time: 0x1DC88C0552C261A
Faulting application path: C:\Program Files\Moonlight Game Streaming\Moonlight.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7840b4313191ae17\nvoglv64.dll
Report ID: 62237992-ea32-447d-9daf-b349f1e91184
Faulting package full name:
App-related fault package ID:
Event ID: 1000
NVIDIA OpenGL driver error:

The NVIDIA OpenGL driver failed to initialize a connection with the GPU. This may be due to insufficient memory, exhausted system resources, or too many graphics applications running simultaneously. The application will not display correctly.
(pid=37)
Event ID: 2

COM server error:

The application-specific parameters do not grant Local Activation permission for the COM server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
for user NT AUTHORITY\LOCAL SERVICE with security ID (S-1-5-19) and address LocalHost (using LRPC), running in an application container with security ID (unavailable).

Troubleshooting steps I’ve tried:

Suspecting monitor conflicts, I installed 4 different virtual monitor solutions with separate drivers (resulting in 4 distinct drivers being detected).

Initially, 3 game sessions launched successfully without errors.

However, when I added a 4th desktop and attempted to launch another instance, the same issues reappeared:

Moonlight (I switched from Parsec) would crash upon connection;

The same error logs were generated.

It’s unclear whether the system simply can’t handle more than 3 sessions, or if the initial success with 3 instances was coincidental (previous attempts also had mixed results).

I’ve been troubleshooting this for days without finding a solution. Any insights or suggestions would be greatly appreciated!

My system specs:

CPU: Ryzen 7500F

GPU: RTX 5070

RAM: 32 GB

OS: Windows 11

[Cuposer63]

Any idea?

[Robertkager]

Seeing these issues after installing a new driver, huh? I had similar crashes and connection problems with Parsec after updating my Nvidia drivers once. A clean driver install using DDU (Display Driver Uninstaller) fixed it for me. Have you tried that? It's a bit tedious, but worth a shot.

[approvalafter]

It really sounds like you’re hitting a GPU resource limit rather than a desktop or monitor issue. The nvoglv64.dll crash and the NVIDIA OpenGL “failed to initialize a connection with the GPU” error usually show up when VRAM or driver contexts are exhausted, especially with multiple hardware-accelerated sessions running at once. Even though your RTX 5070 is powerful, consumer NVIDIA drivers aren’t designed to handle many concurrent 3D/OpenGL contexts like that, particularly through Parsec/Moonlight plus virtual displays.

[Eileste]

are there any recommended settings for the NVIDIA GPU or the virtual desktop environment that might help prevent crashes?

[foodreply]

You’re hitting GPU/resource limits—your RTX 5070 can’t handle that many concurrent OpenGL/game instances, which is why the NVIDIA driver fails and apps crash. Virtual desktops and monitors don’t isolate GPU resources, so all instances still compete for the same VRAM and driver context. Your best options are lowering graphics/VRAM usage, limiting instances to 2–3, or using true virtualization with GPU partitioning/passthrough instead of desktop duplication.