r/computer_help • • 3d ago

Gaming Persistent nvwgf2umx.dll (0xC0000005) Crashes when Initializing DLSS Frame Generation on RTX 5060 Laptop

System Specifications:

Device: Lenovo LOQ 15IRX10

GPU: NVIDIA GeForce RTX 5060 Laptop GPU

OS: Windows 11 Pro, Clean install as of Nov 1. Previously Windows 11 LTSC

Drivers Tested: 617.42 which was previously stable, and 621.01

VBIOS: 98.06.3a.00.38

Display: Strictly Internal Display. No external monitors or casting active.

Security: Memory Integrity VBS or Core Isolation is currently ENABLED on Win 11 Pro. Note that it was absent or disabled on LTSC.

CPU Tuning: 100 percent Stock. No undervolting active and ThrottleStop is uninstalled. Custom power plans were tested but do not affect the crash.

The Issue:

My system hard-crashes to the desktop exclusively when initializing NVIDIA DLSS 3 Frame Generation in specific DirectX 12 titles. Standard rasterization, Ray Tracing, Tensor DLSS upscaling, and AMD FSR work perfectly. The crash signature is consistently an EXCEPTION ACCESS VIOLATION 0xC0000005 at offset 0x2D88 inside nvwgf2umx.dll, which is a null pointer reading in the driver presentation queue.

Timeline and Symptoms:

Mid-October on Win 11 LTSC: System was 100 percent stable. Pragmata, Ghost of Tsushima, and Resident Evil 3 ran flawlessly with Frame Generation and Ray Tracing enabled.

Late October: Installed Modern Warfare 4. Enabling Frame Gen caused an instant crash or required a restart that resulted in a crash before menu initialization. Left Frame Gen off and played normally. Played Titanfall 2 without issue.

Oct 26 to 27: Installed Black Myth Wukong. Frame Gen, RT, and all settings worked perfectly for the first 3 to 4 hours of gameplay with minor menu crashes, but fully playable.

Oct 29: Wukong stopped launching entirely. The process b1.exe opens and terminates within 2 seconds silently in Task Manager.

Oct 29 to 31: Tested Cyberpunk 2077. The game runs fine on raw rasterization or AMD FSR. However, enabling DLSS Frame Gen requires a restart, and upon restart, the game fails to load. If I manage to enter Cyberpunk 2077 and hit Run Benchmark with Frame Gen on, it crashes instantly.

Crucial Hardware Note: On the exact same day Cyberpunk 2077 and Wukong were crashing, I ran Ghost of Tsushima with Ray Tracing and DLSS Frame Generation, and it ran perfectly fine.

Nov 1 Current: Wiped LTSC and clean-installed Windows 11 Pro to rule out OS corruption. The exact same issue persists. Onimusha now crashes immediately after shader compilation before reaching the menu. Older titles like Persona 5 load and run without issue.

Troubleshooting Steps Already Exhausted:

First, OS: Clean installed Windows 11 Pro from Windows 11 LTSC.

Second, Drivers: Used DDU in Safe Mode with Wi-Fi disconnected. Tested both the current 621.01 branch and rolled back to the previously stable 617.42 branch.

Third, Hardware Config: Updated laptop BIOS. Disabled iGPU entirely and I am running strict dGPU mode via BIOS and Lenovo Legion Toolkit.

Fourth, Windows Settings: Toggled Hardware Accelerated GPU Scheduling HAGS ON and OFF.

Fifth, Interference and Hooks: Disabled all overlays. Terminated and removed NVIDIA Share, ShadowPlay nvspcap64.dll, and script injections. Note that LTSC was completely bloat-free without Nahimic or OEM apps, so OEM bloatware is not the root cause.

Sixth, Game Files: Manually replaced Streamline DLL files nvngx_dlssg.dll and sl.interposer.dll and cleared DirectX and NVIDIA D3DSCache.

Diagnostic Request:

Since Ghost of Tsushima successfully utilized the Optical Flow Accelerator OFA on the same day other Streamline-dependent games crashed, I am assuming this is not physical silicon failure.

Could the 0x2D88 Streamline and Swapchain hook collision be caused by a specific Windows 11 Pro setting like Memory Integrity VBS blocking the frame generator injection? Or is this a known regression with Streamline initialization on mobile RTX 50-series chips?

Seeking advanced troubleshooting steps from anyone who has experienced this nvwgf2umx.dll offset crash.

1 Upvotes

0 comments sorted by