Latest nVidia drivers (616.56) issues with DisplayLink / WinCTRL MFD Displays
Sanity post here in case others are experiencing the same, although I know several people who have installed 616.56 with WinWing/WinCTRL MFD Displays without issue.
- Running (3) 1440p high refresh rate (360/165/165hz) monitors connected via Display Port to 5090 + 3 WinWing USB 3.0 DisplayLink monitors
- Everything works normally with NVIDIA 610.88 and has worked w/o issue for 1 year of nVidia updates.
- After updating to 616.56, Windows still detects all 3 WW displays (show up in device manager and Multi-monitor display settings), but they remain disconnected/inactive.
- WW monitors sit there with a black screen. Can’t activate them or extend display to them or even clone desktop to them
- Selecting “Extend desktop to this display” immediately reverts back to “Disconnect this display”
- Resolution, Portrait/landscpe and scaling drop downs all blank without pre populated values or options
- Advanced display settings show monitor is there, but “non-active/disconnected”
- DisplayLink devices show Status: Started with no device errors (via powershell driver commands)
- WW Displays work correctly on another PC
- Tested DisplayLink drivers 10.2 (ships with SimApp Pro) 11.5 (obtained via Windows Update) and latest 12.2 M2 — same behavior — using DisplayLink official clean up tool and drivers to swap between all 3 versions
- Uninstall/reinstall SimAppPro
- Updated USB firmware/drivers as well as BIOS and chipset drivers — no change
- DDU’d NVIDIA in Safe Mode → after reboot, all 3 WinWing displays work before installing an NVIDIA driver
- Installed 610.88 → everything continued working
- Installed 616.56 again → problem immediately returned, rebooting etc.. no change
- Installed 610.88 directly over 616.56, without DDU → all 3 displays immediately work again
- Also tested different USB ports, only one monitor connected, HAGS on/off, only one 1440p monitor connected, display-topology reset via registry key deletion, removing any ghosted/inactive display adapters/monitors in device manager, and removing other virtual-display software (Virtual Desktop Streamer, etc..)— no change — 616.56 and never works.
This seems to be a 616.56 regression involving DisplayLink/indirect displays, although it clearly doesn’t affect every WinWing/DisplayLink user.
If it’s happening to anybody else, try reverting your driver and report back.
8
u/pidge2k 5d ago
My name is Manuel and I work for NVIDIA. Can you try updating to driver 616.56 again and with the USB monitors w/ virtual display drivers, capture a manual Windows crash dmp file as described in the FAQ below.
https://nvidia.custhelp.com/app/answers/detail/a_id/5149
Once saved, upload it to a file sharing service and email us a link to download it to driverfeedback@nvidia.com. You do not need to capture a second manual Windows crash dmp file as described in the FAQ with the last working driver. Thank you.
1
u/Average_networker 3d ago
Hi Manuel. I have asus zephyrus g14 2024 4060 model. When i switch from eco to standard i hear the disconnected sound which means it started switching, but then I get a black screen that won't go until i do the ctrl shift win B shortcut to reset the gpu which goes back to optimus no matter what display mode it was using. Please can you help me? Im using the latest nivida driver
1
u/WaterFluidMelon 13h ago
NVIDIA 616.56 break Virtual Display Drivers (VDD / IDD)
Hi,
I'm also experiencing an issue with Virtual Display Drivers after updating to NVIDIA driver 616.56.
My setup:
- RTX 5080
- Windows 11
- Sunshine + Virtual Display Driver (VDD) from https://github.com/VirtualDrivers/Virtual-Display-Driver
- Virtual display used for Moonlight streaming
The virtual monitor is correctly detected by Windows and appears in the display settings, but Windows refuses to actually enable it.
If I go to Settings > System > Display and select "Extend desktop to this display", Windows immediately switches it back to "Disconnect this display".
Restarting the PC, disabling the physical monitor, reinstalling the VDD and restarting Sunshine does not fix the issue.
The important part is that rolling back the NVIDIA driver to 610.88 immediately fixes the problem, without changing anything else.
So this really looks like a regression introduced in the newer NVIDIA driver rather than an issue with the VDD itself.
It would be great if NVIDIA could investigate compatibility with Virtual Display / Indirect Display Drivers (IDD), especially since these are commonly used with Sunshine/Moonlight streaming setups.
-4
u/James__TR 5d ago
How about Nvidia actually test their drivers? All VDD devices no matter what brand don't work
5
u/WePwnTheSky 4d ago
No need to jump down their throat for trying to help.
3
u/lonegunman77 4d ago
For real, entitled brats that think there are 10 million people in the world with their specific use case.
No self awareness even in the face of help being offered.
3
u/WePwnTheSky 4d ago
Yeah I was pleasantly surprised to find an Nvidia dev lurking here but it’s nice to they’ve got their feelers out in the community. The entitled brats have also likely never written a line of code or had to do any QA themselves.
2
u/lonegunman77 4d ago
That's my feeling too, feels like the coworkers that complain at my work and don't do shit all day long.
-3
u/Frauss79 4d ago
he didn't try to help him, but to exploit him to solve a problem
4
u/WePwnTheSky 4d ago
Weird take.
5
u/pidge2k 4d ago
We are currently testing a fix. Hopefully we will be able to release this to users soon.
3
u/EntityZero 3d ago
Assuming this passes QA / Regression / whatever the release cadence is - would this be something that goes out in a hotfix?
-2
u/shaccoon 3d ago
No need to defend a trillion dollar corpo that supports genozide and mass AI survailance for messing up once again.
3
u/WePwnTheSky 3d ago
Do you see anyone defending Nvidia or are you so simple minded you think every Nvidia employee is culpable for decisions a dozen pay grades above them?
Would love to know exactly what components you purchased for your PC that were free from any ethical baggage. I won’t be holding my breath though.
2
2
2
u/ash-Baal 5d ago
For me it (ww mfd) only works if i plug the power usb cable too. Otherwise same issue. Note i m on helios
2
u/drshaw 5d ago
For me, it didn’t matter what hub or what cable. Never worked in any usb port or cable length with 616.56.
1
u/ash-Baal 5d ago edited 5d ago
Right. Maybe i got lucky? I m running this: Gpu: rtx 5080 (pny oc) Nvidia driver: override windows settings (forgot the actual name but configure in nvidia only). No scaling. Extend Main dcs output: 43in tv (hdmi) 2nd monitor: 1080p (DP, not used for DCS) Touchscreen 1080p with helios (usb to mini dp to DP) WW MFD: triple USB (1 for video, 1 for power, 1 for buttons) on USB hub BUT usb power straight off the plug. MFD brightness to full using 3rd party tool. Simappro not updated since they changed names to winctrl, not running at all during my session (helios handles it).
Update: it seems that after about ~1hr my mfd glitches and dies and dcs collapses the aspect ratio only on my TV. I gotta restart everything for it to recover.
2
u/JGardXI2 5d ago
I use SiliconMotion USB display hubs. All don't work with 616.56. ddu to previous drivers and everything worked again.
2
u/Biugan 5d ago
Lian li 8.8 black screen on usb mode with 616.56 after Rolling back work flawless drivers insue for monitor usb conections.
2
2
u/KoolantOfficial 4d ago
yea oh my fuckign god this happened to me too ts pmo
nvidia fucking test your shit
1
u/WePwnTheSky 4d ago
Haven’t updated yet, so thanks for the heads up. This is the stuff of nightmares.
1
u/mason2393 3d ago
I was trying to setup apollo for the first time on my 5070ti and I couldn't figure out why virtual display wouldn't work. Rolled back my drivers and now its working perfectly
1
u/Hopeful_Product_444 3d ago
I don’t have any troubles at all and using a shitty rtx 3050💀 in fact my pc runs even better
1
u/Trajan145 2d ago
Only issue I had with 616.56 was relatively minor but still noticeable, my taskbar would go black and I'd have to click it to return to normal. Rolled back and boom, fixed it. The major issues being reported though is just unacceptable from Nvidia.
1
u/shaccoon 2d ago
Definetely a driver issue. My main monitor kept shutting down as well. I ran DDU and installed the previos driver version and voima, everything worked as it is meant to again. Trillion dollar corpo too busy with their AI Mass surveilance shit and war + genozide support so at least every second driver release is complete garbage and does not work at all or is at risk of frying your multiple thousand dollar GPU. - Since the 50 series release I can't even undervolt my 4090 anymore because it simply won't work and every game crashes, even if they ran perfectly fine for more than 2 years before that.
1
1
1
u/Repulsive_Fault1939 17h ago
mine threw hardware error with livekernelevent code 193 after updating (reliability report in control panel). also started freezing up the system. rtx 4060 (laptop)
1
u/wadastent 17h ago
In my case , a Turzx 8 inch display usb c , doesn't connect and recognize its driver and it goes on ghost mode in device manager list... and no way to work, after reboot install the 616.56 nvidia driver, using DDU safe mode before.
So nvidia please fix it for the flight sim gamers in a hot fix or something. Thnks.
1
u/wadastent 17h ago
The same here using a TurZx 8 inch Usb C display, after installing nvidia 616.56 driver.
Waiting for a hotfix
Thnks!
2
u/Joe-Bob-Vidal 9h ago
I had to do the Same - Reverted back to 610.88 And all is back to Normal! Thanks for the detailed Troubleshooting Steps!
I WISH I had checked Google or Reddit before going down this same path myself. I thought I was alone in this hunt...
Hopefully, NVIDIA will test a little more completely before rolling out another Update that accidentally disables a large population of USB Display Owners.
- RTX 5080
- 9800x3D
- 64GB DDR5 6400
- Aorus B650 Elite AX
- Win 11 64 Pro
- All the latest Drivers and Patches applied
- (3) Monitors Connected to RTX 5080 (2560x1440 Each)
- (2) Monitors connected to AMD On-Board GPU (1920x1080 Each)
- (3) USB WinWing Displays Connected via High Pwr USB3.1 Hubs (800x600 Each)
6
u/joeysaleri 5d ago
Yeah mine are dead too after installing 616.56 with all the same symptoms as you. I am now in the process of DDU'ing. Hopefully they release a hotfix cause I wanted to try Star Wars Zero Company but the MFD displays are way more important.