Viewer Fails to Launch on Secondary Display (Not Responding)

[Kris Spade]

Hey all,

I have 2 monitors, and an nVidia GTX 1080 Ti.  Several days ago, any time a Second Life viewer (TPV or official) launches on the second monitor, it just shows up white, with (Not Responding) in the window title.  Looking at the update history, it seems that the only Windows updates around that time were Windows Defender antivirus signature updates, and security updates.  At the time this started to occur, I was running a fully updated Windows 10 1909.  I tried everything I could think of to get it working, various clean installs, video driver rollback, etc.  What is interesting is that I ran into a few other people who have only started having the issue around this time.  I know in the past, nVidia cards had this issue for "some" people, but it seems recently it hit a whole lot of people who were never experiencing this in the past.  I never had an issue with this since I've owned this computer for over a year now.

Considering I couldn't seem to fix the issue, I dared to take the plunge and update to Windows 10 2004, hoping maybe this would fix it since one of the things they worked on was enhanced multi-display support.  Unfortunately this did not correct the issue, and thankfully, did not cause any additional issue.  Both monitors are using display ports, so I decided to try and have the secondary monitor use HDMI instead; this did not fix the issue so I reverted it back to the display port.  I tried to switch from the nVidia Game Ready Driver, to the nVidia Studio Driver, but this did not fix the issue either.  I am hoping anybody out here might have some insight, has run into this, and was able to find a fix.  I am also wondering if there is anybody out there on a Windows 10 desktop machine (with latest updates) with more than one monitor, and an nVidia card that, that is having no trouble launching a Second Life viewer from the secondary or tertiary display?

I have no problems with the viewer if I launch it from the primary display, and drag it over to the secondary display, but if I close the viewer on the secondary display, it will want to pop up there again next time, and freeze.

I have made some comments on the JIRA, but not everybody looks there, so I was hoping maybe somebody had some exposure to this who is reading the forums.  For anybody interested, the JIRA on this issue is here:  https://jira.secondlife.com/browse/BUG-227725

Any insight or guidance on this issue is highly appreciated.  Thank you!

[Kyrie Deka]

11 hours ago, Kris Spade said:

and an nVidia GTX 1080 Ti

Thanks for sharing, now watching the JIRA.  I have a 1080 so this caught my attention, but Jira Environment shows 1070? And courageous, that jumping to Win10 2004!

EDIT: Related to a different Jira, I disable my Intel and enable only the 1080, and all runs stellar - grateful for that!   Unknown if it helps, but in my case with the Intel disabled, left monitor as primary, and only the 1080 enabled - my FS viewer launches seemingly fine on the monitor I "closed" it prior on, either left primary, or right.

Edited June 18, 2020 by Kyrie Deka

[Rachel1206]

13 hours ago, Kris Spade said:

...  I am hoping anybody out here might have some insight, has run into this, and was able to find a fix.  I am also wondering if there is anybody out there on a Windows 10 desktop machine (with latest updates) with more than one monitor, and an nVidia card that, that is having no trouble launching a Second Life viewer from the secondary or tertiary display?

I have no problems with the viewer if I launch it from the primary display, and drag it over to the secondary display, but if I close the viewer on the secondary display, it will want to pop up there again next time, and freeze.

I have made some comments on the JIRA, but not everybody looks there, so I was hoping maybe somebody had some exposure to this who is reading the forums.  For anybody interested, the JIRA on this issue is here:  https://jira.secondlife.com/browse/BUG-227725

Any insight or guidance on this issue is highly appreciated.  Thank you!

FYI. I am running with two monitors extended and using GForce 1060 6GB, and Windows 10 2004, where Firestorm 6.3.9 (58205) May 27 2020 01:20:51 (64bit) (Firestorm-Releasex64) with Havok support is running on monitor 2 on a Asus gaming laptop without problems.

Second monitor on display port, the monitor Asus 24'' 144 KHz.

You see my setup on attached picture.

Edited June 18, 2020 by Rachel1206

[Kris Spade]

On 6/18/2020 at 10:00 AM, Kyrie Deka said:

Thanks for sharing, now watching the JIRA.  I have a 1080 so this caught my attention, but Jira Environment shows 1070? And courageous, that jumping to Win10 2004!

EDIT: Related to a different Jira, I disable my Intel and enable only the 1080, and all runs stellar - grateful for that!   Unknown if it helps, but in my case with the Intel disabled, left monitor as primary, and only the 1080 enabled - my FS viewer launches seemingly fine on the monitor I "closed" it prior on, either left primary, or right.

The person who originally filed it was on a 1070 having the same issue, although I am on a 1080 Ti.

I did try disabling the Intel onboard GPU from Device Manager, but no change in status (I read that Jira also).  Did you happen to do it that way, or through the BIOS?

[Kris Spade]

On 6/18/2020 at 12:07 PM, Rachel1206 said:

FYI. I am running with two monitors extended and using GForce 1060 6GB, and Windows 10 2004, where Firestorm 6.3.9 (58205) May 27 2020 01:20:51 (64bit) (Firestorm-Releasex64) with Havok support is running on monitor 2 on a Asus gaming laptop without problems.

Second monitor on display port, the monitor Asus 24'' 144 KHz.

You see my setup on attached picture.

Nice!  Is the viewer launching from either of the monitors just fine? I can launch it from my primary (which is the monitor on my right) but if if I drag it to the left monitor, and relaunch it, it will attempt to launch on the left monitor and freeze with a white screen (Not Responding).

[Kyrie Deka]

6 hours ago, Kris Spade said:

I did try disabling the Intel onboard GPU from Device Manager, but no change in status (I read that Jira also).  Did you happen to do it that way, or through the BIOS?

I enable/disable through Device Manager only.  

[Kris Spade]

I just updated BUG-227725 on the Jira with my findings on how I got this fixed for myself today, in case anybody else runs into this in the future.

In my case, it was a piece of software called Nahimic, which is packaged with the Realtek HD Universal Audio driver.  If you manually close the NAHIMIC processes from Task Manager and open the viewer on the second monitor, it opens up just fine.

After discovering that terminating these processes solved the issue for me, I disabled the Nahimic service in Services and rebooted, and no longer have the issue. No software modification was required (I couldn't find an uninstaller for this specifically).