[BUG-37795] Severe performance issues in all Second Life viewers after installing KB3176938 (Windows Version 1607 Build 14393.105). Problem continues with KB3189866, KB3193494 & KB3194496

[sl-service-account]

Steps To Reproduce

• Login to Second Life on a Windows 10 system that has KB3176938 installed.

• Take the viewer out of focus by task switching to a different program.

• Bring the viewer back into focus and observe viewer performance.

  Observed Behaviour

• On many Windows 10 systems since the KB3176938 update was installed, SL viewers are suffering from severe low performance (1-2 FPS) when the viewer is brought back into focus after task switching to another program.

• On some systems this problem is intermittent but on other systems it will reproduce after the viewer has lost focus for the first time in a session.

• Some users have also reported that since KB3176938 was installed, running more then one Second Life viewer instance causes very low FPS whereas before KB3176938 was installed, performance when dual logged was good.

• It appears this problem is affecting all OpenGL based programs, not just Second Life viewers.

Other programs known to be affected at this time include:

• Runescape.

  • https://www.reddit.com/r/runescape/comments/50o7pf/kb3176938_for_windows_update_is_causing_massive/
  • http://services.runescape.com/m=forum/forums.ws?415,416,704,65828403
  • http://services.runescape.com/m=forum/forums.ws?409,410,100,65828520 (new link)

• X-Plane & other flight simulators.

  • http://forum.aerosoft.com/index.php?/topic/114962-fps-frieren-ein-seit-windows-kb3176938-update/
  • http://www.avsim.com/topic/494304-windows-update-crushes-fps/
  • https://www.reddit.com/r/flightsim/comments/51l249/xplane_and_kb3176938/?st=isvaktt6&sh=4be4b134 (new link)
  • http://forums.x-pilot.com/forums/topic/11524-win-10-cumulative-update-kb3176938/ (new link)
  • http://forums.x-plane.org/index.php?/forums/topic/107236-frame-rate-reduction-when-opening-other-programs-in-background/ (new link)
  • http://answers.microsoft.com/en-us/windows/forum/windows_10-update/kb3176936-problem-with-gameplay-x-plane/c98f1bc4-61f4-4c73-bd47-e129953eb4c7?auth=1 (new link)
  • http://forums.pilotedge.net/viewtopic.php?t=6544&p=43711 (new link)

• Dungeons & Dragons online. http://ddo.mmmos.com/?p=view&uid=57cab1a664efe&title=after-windows-10-updates%2C-frame-rate-now-under3

• Firestorm viewer bug report http://jira.phoenixviewer.com/browse/FIRE-20034 Massive FPS drop after Viewer Window lose focus - caused by KB3176938

• Microsoft community forum post http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/severe-performance-issues-in-firestorm-viewer/3cb682b1-42f7-4ce0-932b-2535d58fb8d8?page=1

• Inara Pey's blog post https://modemworld.me/2016/09/06/windows-10-opengl-issue-affecting-some-second-life-users/

• I have linked several reports about this problem to this issue.

  Workaround

• Once performance has dropped due to this bug, you must relog the viewer to restore performance.

• The only known workaround at this time is to uninstall KB3176938 on affected systems. http://www.howtogeek.com/235474/how-to-roll-back-builds-and-uninstall-updates-on-windows-10/

  So far uninstalling KB3176938 has fixed everyone reporting this problem.

Attachments

• BUG-37795.JPG 2016-09-08 22:25:34
• log_de.cmd 2016-09-21 14:40:07

Original Jira Fields

| Field | Value | | ------------- | ------------- | | Issue | BUG-37795 | | Summary | Severe performance issues in all Second Life viewers after installing KB3176938 (Windows Version 1607 Build 14393.105). Problem continues with KB3189866, KB3193494 & KB3194496 | | Type | Bug | | Priority | Unset | | Status | Needs More Info | | Resolution | Unresolved | | Reporter | Whirly Fizzle (whirly.fizzle) | | Created at | 2016-09-06T17:27:11Z | | Updated at | 2019-07-10T15:50:10Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2016-09-06T13:04:26.250-0500', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Viewer', 'Target Viewer Version': 'viewer-development', 'What just happened?': 'Filling in...', 'What were you doing when it happened?': '...', 'What were you expecting to happen instead?': '...', } ```

[sl-service-account]

Ansariel Hiller commented at 2016-09-06T18:04:26Z

Since apparently the only way to report bugs for normal Windows users is to use the Feedback tool which then also shows reports of other users using the same language version as oneself and this being a rather cumbersome way without unknown outcome, it would probably be more effective if Linden Lab seeks contact with Microsoft and inform them of the apparent issue with the latest update so Microsoft can start working on a fix.

[sl-service-account]

ginormous.woodget commented at 2016-09-06T18:30:04Z

Another way to reproduce the severe drop in fps is to cam around the sim a lot (alt+ arrow keys or left mouse button held down) and hit escape a few times to return camera to behind your avie. Now notice the drop in fps and the difficulty in moving around. Fast fix is to relog (I have only used Firestorm), and the ultimate workaround is to uninstall KB31769318.

[sl-service-account]

Nicky Perian commented at 2016-09-06T18:39:15Z

Could someone with switchable graphics switch to on-board graphics, likely Intel, temporarily and see if the problem still occurs?

Has anyone with AMD graphics experienced the issue?

[sl-service-account]

Whirly Fizzle commented at 2016-09-06T18:43:43Z, updated at 2016-09-06T18:44:23Z

Firestorm has seen users with AMD graphics also affected by this bug.

Example:

Elen Porthos added a comment - 2 days ago

I had same problems but uninstalling update (KB3176938) solved the problem and all works great.

CPU: AMD A10-5800K APU with Radeon(tm) HD Graphics (3793.12 MHz) Memory: 16336 MB OS Version: Microsoft Windows 10 64-bit (Build 14393) Graphics Card Vendor: ATI Technologies Inc. Graphics Card: AMD Radeon HD 7700 Series

Windows Graphics Driver Version: 8.17.0010.1474 OpenGL Version: 4.2.13447 Compatibility Profile Context 16.300.2511.1003

[sl-service-account]

ObviousAltIsObvious commented at 2016-09-06T19:18:27Z, updated at 2016-09-08T05:29:51Z

@Nicky Perian: yes, at least I can repro this with AMD 7700-7900 cards. Same as some Nvidia users have reported, disabling VBO can partially mitigate but the slowdown is still there. (And yeah, in this case removing and hiding KB3176938 also does put everything back to normal.)

Adding sysinfo late; this is one machine it repro'd on but I've since backed out the broken MS update.

Second Life 4.1.1.318504 (Second Life Release)
Release Notes

CPU: AMD Phenom(tm) 8650 Triple-Core Processor (2310.5 MHz)
Memory: 4095 MB
OS Version: Microsoft Windows 8 64-bit  (Build 9200) compatibility mode. real ver: 10.0 (Build 10586)
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: AMD Radeon HD 7700 Series

Windows Graphics Driver Version: 8.17.0010.1474
OpenGL Version: 4.2.13447 Compatibility Profile Context 16.300.2511.1003

J2C Decoder Version: KDU v7.2
Audio Driver Version: FMOD Ex 4.44.31
LLCEFLib/CEF Version: 1.5.3-(CEF-WIN-3.2526.1347-32)
LibVLC Version: 2.2.4
Voice Server Version: Not Connected
September 07 2016 21:28:24

[sl-service-account]

Soft Linden commented at 2016-09-06T21:39:36Z

Per https://support.microsoft.com/en-us/help/12387/windows-10-update-history there is no indication that KB3176938 contains security fixes. This update is also held back by activating the Windows 10 option to opt out of experimental updates. It should be safe to opt out of this update until Microsoft issues a fix.

If you aren't yet having the problem you can avoid becoming the next victim. Open Windows settings, "Update & Security," "Windows Update," "Advanced options," and check "Defer upgrades" to only receive updates that are either widely tested or important for security reasons.

[sl-service-account]

Ansariel Hiller commented at 2016-09-06T21:50:24Z

Hi Soft!

Is Linden Lab planning to contact Microsoft about this issue so they are at least aware of it? It will have much more impact if Linden Lab reports it rather than a simple Windows 10 user.

[sl-service-account]

Soft Linden commented at 2016-09-06T21:56:20Z

I don't know if contact has already been made or if it's still coming up. That sits with a different team, but yes that's the plan.

[sl-service-account]

ginormous.woodget commented at 2016-09-06T22:42:06Z, updated at 2016-09-06T22:48:41Z

Unfortunately Windows 10 HOME users, like myself cannot Defer Upgrades .. Windows 10 Professional, Enterprise, and Education edition customers can choose to defer Windows updates." I can only choose to join the Windows Insider Program (which get Insider Preview Builds – Be one of the first to see future updates and improvements to Windows and provide feedback ) OR NOT join (that's me). KB3176938 made the RELEASE track , so all the MS WIPers failed to catch this bug. I had to uninstall the update PLUS run the Windows 10 Update Share/Hide (wushowhide.diagcab) tool and select KB3176938 by name to stop it from being Installed again.

[sl-service-account]

Ansariel Hiller commented at 2016-09-06T22:47:58Z

You can use the "Show or hide updates troubleshooter" tool for this: https://support.microsoft.com/en-us/kb/3073930

[sl-service-account]

ginormous.woodget commented at 2016-09-06T23:06:06Z

Just wondering how many non-tech savvy Windows 10 Home SL users are even aware of the BUG and what to do about it. I did everything (clean Firestorm install , updated graphic drivers etc. to no avail UNTIL I decided to check The Firestorm JIRA (thank you guys)and saw this issue near the top. It might be helpful to include an entry on the SL Grid status page https://community.secondlife.com/t5/Status-Grid/bg-p/status-blog AND somewhere on The Firestorm website. Spread the word, and hope that first time new SL users don't encounter the FPS slowdown and decide SL too laggy, "I'm out of here" and quit.

[sl-service-account]

ginormous.woodget commented at 2016-09-06T23:28:30Z, updated at 2016-09-07T00:34:52Z

Interesting that now the webpage for the Show or hide updates troubleshooter" tool gives an ERROR when trying to access it. Either the page is getting hammered OR MS has deliberately disabled it. Curious "An error occurred while processing your request. Reference #97.24d3fea5.1473204252.9ace571 " EDIT.. Error Fixed

[sl-service-account]

ginormous.woodget commented at 2016-09-06T23:46:20Z

Here is a direct link to the Windows Update Show/Hide troubleshooter tool

http://download.microsoft.com/download/F/2/2/F22D5FDB-59CD-4275-8C95-1BE17BF70B21/wushowhide.diagcab

[sl-service-account]

Trager Alter commented at 2016-09-07T01:02:56Z

I uninstalled KB3176938 and this problem is gone in Firestorm. I did not have this problem with the Linden Lab viewer and used it until i heard of this fix. Now back to FS.

[sl-service-account]

Grumpity Linden commented at 2016-09-07T21:46:50Z

Contact has been made. Microsoft is investigating.

[sl-service-account]

Nicky Perian commented at 2016-09-07T23:31:27Z

I have been watching this for several days on the FS Jira and here and have yet to see a repro from SL default viewer or FS 32bit viewer. Is this really "in all Second Life viewers"?

[sl-service-account]

Whirly Fizzle commented at 2016-09-08T00:20:59Z

@Nicky

I guess you must have not read all the posts then. People have confirmed the problem affects the LL viewer, Firestorm viewer, Black Dragon viewer and Singularity viewer, as well as other OpenGL based programs.

AmurtigressK. replied on Sepetember 3rd 2016 An update to my previous post:

LindenLabs' SL Viewer 4.0.7.318301 (32 bit) is also affected. It took about 20 minutes on my main machine until the framerate dropped to 5 fps irreversibly

CorruptOutcast Resident added a comment - 2 days ago - edited

I decided to try SLV and Singularity next. Both had the same issue for me but it didn't present itself right away. After textures loaded and everything started to look normal is when losing focus on the window caused it.

https://community.secondlife.com/t5/General-Second-Life-Tech/Framerate-Dropoff-and-Ping-Increase-After-a-Few-Minutes/m-p/3064015/highlight/true#M5101 Reported the problm on the LL viewer, Firestorm and Black Dragon viewer.

[sl-service-account]

Nicky Perian commented at 2016-09-08T00:47:01Z, updated at 2016-09-08T00:53:35Z

@Wirly An About SecondLife posted? Or About Firestorm showing 32 bit version posted?

AmurtigressK. replied on Sepetember 3rd 2016 An update to my previous post: LindenLabs' SL Viewer 4.0.7.318301 (32 bit) is also affected. It took about 20 minutes on my main machine until the framerate dropped to 5 fps irreversibly

How can 20 minutes viewer out of focus be considered a normal user operating pattern?

I agree with all the reports that it is a valid problem, especially for those involved. I just think it needs to be narrowed to the graphics processor in use. I'm thinking it may be effecting newer graphics card as apposed to older ones.

[sl-service-account]

StarlightShining commented at 2016-09-08T00:53:40Z

@ Nicky - where in Whirly's quotes does it say it was 20 mins out of focus? It said it took 20 mins for the fps drop to occur.. n ot that it was 20 mins out of focus

[sl-service-account]

Nicky Perian commented at 2016-09-08T01:11:47Z

If I understand the problem correctly and I have been wrong before; It is remove focus away from the viewer to another application and keep both app windows open and watch for the fps to drop abnormally to say 3-5 fps and then return focus to the viewer and the fps does not recover.

[sl-service-account]

Nicky Perian commented at 2016-09-08T01:43:56Z

One thing folks might want to try is Fixed Bit Anti-Idle HUD or an equal. I have used it before when wanting to keep the viewer up and not wind up in away status. My use is to have the task manager open and watch for memory leaks but it may be a way to not see this problem.

[sl-service-account]

ObviousAltIsObvious commented at 2016-09-08T01:50:11Z

To be clear, switching to another window isn't even always necessary to trigger this bug, it's just a convenient way to get a repro started.

[sl-service-account]

Ansariel Hiller commented at 2016-09-08T16:08:51Z

@NickyP: Your attempts trying to talk this into a Firestorm-only issue are quite amusing since it affects different OpenGL applications as well, no matter if an ATI or nvidia GPU is used.

[sl-service-account]

Nicky Perian commented at 2016-09-08T18:09:05Z

@Ansariel: I'm not that stupid. The evidence is overwhelming that it isn't a Firestorm only issue. The first thing in troubleshooting is to define the problem. I don't think a rollback is a move to define the problem. It's kinda like "clear the cache" defines a problem. My point is there has been no root cause analysis done and the rollback is only an element of that. If the hardware/driver configuration causes the problem then it stands to reason that every viewer with SL code base comprising 99 percent, would under that configuration likely trigger the same thing.

From the MS thread you opened. User v-4abrew reported;

I use the latest Firestorm Viewer 4.7.9 and had an issue at first until I cleared everything out and then ran ccleaner to clean all temp files (temp/%temp%/prefetch) out then re-logged with no issues aside from things not rezzing in correctly its more blurred out but I have the Alienware 17 R3 with specs below... CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (2591.98 MHz) Memory: 16252 MB OS Version: Microsoft Windows 10 64-bit (Build 14393).105 Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce GTX 970M/PCIe/SSE2 Samsung 950 Pro SSD 300MBPS+Boost for Internet and 20+ FPS with 30+ people on sim running on a 4K screen in 4K not 1080p.

Since it is the same system as mine I'll try it as I have AU in the today's update queue.

[sl-service-account]

Malic Tolsen commented at 2016-09-08T21:29:06Z

I left a comment about this on the Firestorm JIRA as well, but I was able to stop this issue when I disabled the windows store update service... my only problem was it re-enabled after every reboot, so I removed the store fully from my computer and have not had this FPS loss issue since.

[sl-service-account]

Nicky Perian commented at 2016-09-09T02:32:02Z

Report on my Windows 10 Anniversary Update and subsequent KB3176936 update. From above https://jira.secondlife.com/browse/BUG-37795?focusedCommentId=509901&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-509901 Very close in configuration to my system, Another Alienware user reported the problem and resolved it by removing the KB3176936 update.

Using the hint above about using CCleaner I did the following: Update to Windows 10 Anniversary Update. Used CCleaner and Registry Tool. Used Revo Unistaller to removed all installed viewers. Used CCleaner and Registry Tool again. Update to Windows 10 Version 1607 for x64-based Systems (KB3176936) Used CCleaner and Registry Tool again. Installed: Second Life 4.0.7.318301 (Second Life Release) Release Notes

You are at 131.0, 135.8, 23.1 in Mesh Sandbox 1 located at sim10006.aditi.lindenlab.com (216.82.48.76:13008) SLURL: secondlife://Aditi/secondlife/Mesh%20Sandbox%201/131/136/23 (global coordinates 205,443.0, 178,824.0, 23.1) Second Life Server 16.08.01.318271 Retrieving...

CPU: Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz (2498.54 MHz) Memory: 8078 MB OS Version: Microsoft Windows 8 64-bit (Build 9200) compatibility mode. real ver: 10.0 (Build 10586) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce GTX 970M/PCIe/SSE2

Windows Graphics Driver Version: 10.18.0015.4281 OpenGL Version: 4.5.0 NVIDIA 372.70

J2C Decoder Version: KDU v7.2 Audio Driver Version: FMOD Ex 4.44.31 LLCEFLib/CEF Version: 1.5.3-(CEF-WIN-3.2526.1347-32) Voice Server Version: Vivox 4.6.0017.22050

Packets Lost: 2/2,969 (0.1%) September 08 2016 18:28:02 **************************************************************************************************************************************** Installed: Kokua 4.1.1 (39729) Sep 8 2016 12:08:56 (Kokua Test NORLV) Release Notes

You are at 128.0, 128.0, 23.1 in Mesh Sandbox 1 located at sim10006.aditi.lindenlab.com (216.82.48.76:13008) SLURL: secondlife://Aditi/secondlife/Mesh%20Sandbox%201/128/128/23 (global coordinates 205,440.0, 178,816.0, 23.1) In region Mesh Sandbox 1 at (802, 698) Second Life Server 16.08.01.318271 Error fetching server release notes URL.

CPU: Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz (2498.55 MHz) Memory: 8078 MB OS Version: Microsoft Windows 8 64-bit (Build 9200) compatibility mode. real ver: 10.0 (Build 10586) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce GTX 970M/PCIe/SSE2

Windows Graphics Driver Version: 10.18.0015.4281 OpenGL Version: 4.5.0 NVIDIA 372.70

J2C Decoder Version: OpenJPEG: 1.4.0, Runtime: 1.4.0 Audio Driver Version: FMOD Ex 4.44.61 LLCEFLib/CEF Version: 1.5.3-(CEF-WIN-3.2526.1347-32) LibVLC Version: 2.2.4 Voice Server Version: Vivox

Built with MSVC version 1800 Packets Lost: 120/16,471 (0.7%) September 08 2016 18:26:51

Ran these viewers side by side for 30 minutes switching between them and there was no slowdown. Graphic attached. https://jira.secondlife.com/secure/attachment/94973/BUG-37795.JPG

[sl-service-account]

Whirly Fizzle commented at 2016-09-09T05:25:15Z

Unsure if this is the same problem, but KB3176938 is also causing Open Broadcaster Software to freeze: https://obsproject.com/forum/threads/bug-obs-preview-freezes-and-terminates-the-stream-capture.54072/

[sl-service-account]

Kasumi Hayashi commented at 2016-09-09T08:18:02Z, updated at 2016-09-09T11:45:17Z

i've been affected by this issue as well, though not specifically when the window loses focus, and it seems to only happen in areas with a lot of activity. it could be running fine for as little as 5 minutes to up to an hour, but the performance will eventually tank to unplayable levels and require a relog. i tested to make sure this wasn't my pc thoroughly, including running a memory diagnostic and clean installing my graphics drivers.

[sl-service-account]

Grumpity Linden commented at 2016-09-09T17:53:53Z

Kasumi, you will need to uninstall the KB3176938 Windows update until this issue is resolved by Microsoft in order to return SL behavior to normal.

[sl-service-account]

Kasumi Hayashi commented at 2016-09-10T01:36:07Z

thank you, i did, i forgot to mention that in the post. i was just throwing in my two cents that the issue is happening to me as well, and meant to imply that reverting away from the update fixed it for me as well.

[sl-service-account]

Whirly Fizzle commented at 2016-09-14T03:16:44Z

Workaround found by [~questargon.edelmann] - run the viewer in fullscreen mode.

This has been confirmed to "fix" the problem by a couple of others so far on Firestorm. Please can someone who can easily reproduce this bug test on the LL viewerr too?

To activate fullscreen mode:

LL viewer Activate the Advanced menu in the top menu bar with CTRL+ALT+D. Advanced -> Show debug settings -> FullScreen -> Set to TRUE -> Relog.

Firestorm viewer, Go to Avatar -> Preferences -> Graphics -> General -> Tick "Fullscreen mode" -> Relog.

While running the viewer in fullscreen mode, you will need to use ALT+TAB to switch to a different program.

[sl-service-account]

Julia Umarov commented at 2016-09-14T20:32:18Z

The fullscreen mode workaround fixes the problem on LL viewer too. The bug is actually the same in all the different viewers.

Btw for a quick bug repro, you do not need to be online for hours. The FPS drop appears when viewer RAM usage is above about 3.5 GB, used by single viewer, or added up RAM usage of two viewers logged in at same time. Just go to a really crowded place with lots of dancing mesh body avatars and cam around wildly and watch the RAM usage in the task manager. Best is to log in with two viewers, so RAM fills up faster. It takes only a few minutes. Then switch back and forth between the two viewers or some other program and FPS will drop to 1 - 3 and not go up again.

Also an indicator that the bug happened again is the message "(not responding)" appearing in the title bar when you exit the bugged viewer.

(On Windows 10 64bit with 16GB RAM, GTX 970 and Intel i7-4770K.)

[sl-service-account]

ObviousAltIsObvious commented at 2016-09-14T22:25:46Z, updated at 2016-09-14T22:38:36Z

MS has not yet squashed the bug in build 14393.187 (KB3189866) update. Here, fullscreen in the viewer delays onset of the slowdown, but has not cured it in busy scenes with decked-out mesh avatars.

[sl-service-account]

Trager Alter commented at 2016-09-15T11:32:05Z

Latest MS update (KB3189866) still has same problem and needs to be deleted as well as KB3176938

[sl-service-account]

Jonna Korhonen commented at 2016-09-15T14:47:36Z

Add me to the list of users experiencing the bug. Uninstalling the KB resolved. Computer information for reference: PU: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz (2659.99 MHz) Memory: 16376 MB OS Version: Microsoft Windows 10 64-bit (Build 14393) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce GTX 960/PCIe/SSE2

Windows Graphics Driver Version: 21.21.0013.7270 OpenGL Version: 4.5.0 NVIDIA 372.70

[sl-service-account]

Torric Rodas commented at 2016-09-15T15:30:14Z

A bit of a side-bar here, but please indulge me as it may be useful for others: Uninstalling KB3176938 unfortunately turns on Cortana for all time, even if you previously had it disabled. The 'Off' switch for Cortana has now been removed as a 'feature' in Windows ae. However if you follow the steps exactly in this video you can turn it off again once you have removed KB3176938. I've done this on two pc's and it worked perfectly. It is however a registry edit, so back-up first and if you don't know what you're doing, best to leave it alone https://www.youtube.com/watch?v=iW1heCjMe3w

[sl-service-account]

Jonna Korhonen commented at 2016-09-15T19:06:56Z

Okay.. just installed KB 3189866 cause well.. no choice.. issue reappeared with todays windows update

[sl-service-account]

Shadoskill Heckroth commented at 2016-09-15T19:43:12Z

KB3176938 & KB3189866 causing the same issue for me, disabled update service, and uninstalled those updates until fixed.

[sl-service-account]

ginormous.woodget commented at 2016-09-15T20:29:48Z

Probably not a good idea to uninstall KB3189866 as it is listed as a SECURITY update in the Uninstall an update section. Because of Windows update being completely blocked and not even doing updates anymore for Adobe Flash Player and the monthly Windows Malicious Software Removal Tool, I had to do a System Restore rollback to right after I installed KB3176938. I waited a minute and I saw that the new updates were finally being downloaded and soon ready for restart. Now I have KB3189866 (KB3176938 was completely removed) and all other updates downloaded successfully . I decided to try going into Fullscreen mode in Firestorm and happy to report it working well with the FPS issue.

[sl-service-account]

Jonna Korhonen commented at 2016-09-16T01:11:30Z

I learned the work around in Firestorm at least.. go to full screen mode. Unfortunately Full Screen mode did not work for me. Noted FPS did not drop like before but the viewer still lags out terribly after a short spell.

[sl-service-account]

Julia Umarov commented at 2016-09-16T01:47:23Z

Now I am using fullscreen mode on a daily basis, on LL viewer as well as Firestorm viewer, with Windows KB3189866. No FPS drop in any situation, everything okay.

I do not want to defer Windows updates, because updates usually are good for something. Like fixing bugs or security issues.

But this is all just a workaround and Microsoft should fix it. I am afraid that will take forever. Might there be a way to change the viewer code, so that the viewer overrides the way Windows is handling this?

[sl-service-account]

ginormous.woodget commented at 2016-09-16T16:54:50Z

As usual, I was too optimistic in the performance of a workaround (full screen). I encountered the severe fps bug in 2 regions I visited yesterday that did not recover until a relog. Unchecking enable Opengl VBO does not help either, and may even cause me a slight decrease in fps. Makes me wonder if something was going on in those sims that ate up all my system resources when I was very active riding vehicles around them. Unfortunately, I decided against security prudence and uninstalled KB 3189866, but that has eliminated the severe fps drop in those, and all other regions I have visited so far.

[sl-service-account]

Kirari Kujisawa commented at 2016-09-16T23:51:09Z

I tried the Fullscreen trick but it did nothing for me, still getting 2fps with 66 installed, as soon as I uninstall it the FPS jump back to normal for me

[sl-service-account]

NogarDrevlis Lectar commented at 2016-09-17T16:18:38Z

Yep same Problem still shown with the new KB318966 , I had to install it because some other updates needed to install and hiding wasn't possible after windows updates showed them to download, soi did and no surprise yeaa the problem was still there uninstalled update again now back on build Version 1607 (14393.82)and everything is fine , now I hide the update hope it doesn't pop up any more.

[sl-service-account]

Whirly Fizzle commented at 2016-09-18T23:01:06Z

IMPORTANT!

Microsoft have requested that Linden Lab provide gpuview traces from affected systems. It is preferable that you use the Linden Lab viewer for the trace, but you may use Firestorm viewer if you prefer. We need to get as many of these traces as possible, so if those of you that can reproduce the problem can take the time to do this, that would be much appreciated.

Here is what you need to do.

• Make sure your Windows 10 is fully updated, including the problematic KB updates (KB3176938 &/or KB3189866).

• Download the Windows 10 ADK from here: https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit - you need the "Windows ADK for Windows 10, version 1607" one.

• Run the installer - adksetup.exe

• You only need to install the "Windows performance toolkit" component - http://prnt.sc/cjjwqz

• Once install is complete, the tool install location by default will be at C:\Program Files (x86)\Windows Kits

• Browse to C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\gpuview

• Your completed trace will be inside the gpuview folder.

To create the trace:

• Right click on the Windows start button & choose Command Prompt (Admin) http://prnt.sc/cjl4jg

• At the command prompt, type in cd C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\gpuview & Enter/Return key to navigate into the gpuview folder. https://gyazo.com/67ff2cfe78bd2b65786125f7ac942370 If you installed to a custom location then cd into that.

• Reproduce the poor performance problem on the LL viewer or Firestorm.

• While the viewer is still running and exhibiting the performance problem, back in the cmd window, type in log.cmd & enter/return key.

• You will see some text in the cmd window similar to this: {code} C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\gpuview>log.cmd Xperf -on LOADER+PROC_THREAD+CSWITCH+DISPATCHER+POWER+DISK_IO+HARD_FAULTS+PROFILE+MEMINFO+DPC+INTERRUPT -stackwalk @"C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\gpuview EventsForStackTrace.txt" -BufferSize 1024 -MinBuffers 120 -MaxBuffers 480 -f Kernel.etl

Xperf -start CaptureState -on 802ec45a-1e99-4b83-9920-87c98277ba9d:0x100236:5+a688ee40-d8d9-4736-b6f9-6b74935ba3b1:0xffff:5+CA11C036-0102-4A2D-A6AD-F03CFED5D3C9:0xf:6:'stack'+5d8087dd-3a9b-4f56-90df-49196cdc4f11:0xffffffffffffffff:6:'stack'+db6f6ddb-ac77-4e88-8253-819df9bbf140:0xffffffffffffffff:6:'stack'+7E7D3382-023C-43cb-95D2-6F0CA6D70381:0x1 -BufferSize 1024 -MinBuffers 120 -MaxBuffers 480 -f CaptureState.etl

Xperf -capturestate CaptureState 802ec45a-1e99-4b83-9920-87c98277ba9d:0x10FFFF:5:'stack'+a688ee40-d8d9-4736-b6f9-6b74935ba3b1:0xffff:5+CA11C036-0102-4A2D-A6AD-F03CFED5D3C9:0xf:6:'stack'+5d8087dd-3a9b-4f56-90df-49196cdc4f11:0xffffffffffffffff:6:'stack'+db6f6ddb-ac77-4e88-8253-819df9bbf140:0xffffffffffffffff:6:'stack'+7E7D3382-023C-43cb-95D2-6F0CA6D70381:0x1

Xperf -start NoCaptureState -on DX:0x2F+531A35AB-63CE-4BCF-AA98-F88C7A89E455:0xffff:4+802ec45a-1e99-4b83-9920-87c98277ba9d:0x208041:5:'stack'+f404b94e-27e0-4384-bfe8-1d8d390b0aa3+362007f7-6e50-4044-9082-dfa078c63a73:0x000000000000ffff:0x5+8f2048e0-f260-4f57-a8d1-932376291682+8cc44e31-7f28-4f45-9938-4810ff517464:0xffff:6+30336ed4-e327-447c-9de0-51b652c86108+8c416c79-d49b-4f01-a467-e56d3aa8234c:0xffff+a42c77db-874f-422e-9b44-6d89fe2bd3e5:0x000000007fffffff:0x5+8c9dd1ad-e6e5-4b07-b455-684a9d879900:0xFFFF:6+9e9bba3c-2e38-40cb-99f4-9e8281425164:0xFFFF:6+31293f4f-f7bb-487d-8b3b-f537b827352f+42C4E0C1-0D92-46f0-842C-1E791FA78D52+28cf047a-2437-4b24-b653-b9446a419a69+a6a00efd-21f2-4a99-807e-9b3bf1d90285:0x000000000000ffff:0x5+a0386e75-f70c-464c-a9ce-33c44e091623:0xffff:5 -BufferSize 1024 -MinBuffers 120 -MaxBuffers 480 -f NoCaptureState.etl

C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\gpuview>

* Wait 30 seconds (don't wait much longer then this or the trace file will be gigantic).

* After 30 seconds, type *log.cmd* again  into the cmd window & enter/return.

* You should see new text appear in the cmd window similar to this:

C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\gpuview>log.cmd Xperf -stop CaptureState The trace you have just captured "C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\gpuview\CaptureState.etl" may contain personally identifiable information, including but not necessarily limited to paths to files accessed, paths to registry accessed and process names. Exact information depends on the events that were logged. Please be aware of this when sharing out this trace with other people. Xperf -stop NoCaptureState The trace you have just captured "C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\gpuview\NoCaptureState.etl" may contain personally identifiable information, including but not necessarily limited to paths to files accessed, paths to registry accessed and process names. Exact information depends on the events that were logged. Please be aware of this when sharing out this trace with other people. Xperf -stop The trace you have just captured "C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\gpuview\Kernel.etl" may contain personally identifiable information, including but not necessarily limited to paths to files accessed, paths to registry accessed and process names. Exact information depends on the events that were logged. Please be aware of this when sharing out this trace with other people. All loggers stopped, starting merge... Merged Etl: Merged.etl Restoring Performance Counter Interval New Profile Interval = 10000 [1.0000ms] C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\gpuview> {code}

• The trace has now been stopped - you do not need to disable it manually.

• You should now see a file named Merged.etl in C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\gpuview http://prnt.sc/cjlae2 The Merged.etl file is the trace file that Microsoft need.

• Zip up Merged.etl Right click Merged.etl -> Send To -> Compressed (zipped) folder. Windows will likely tell you that it cannot created a zipped folder at this location and offer to create it on your desktop, say Yes. You should now have a file name Merged.zip either on your desktop or in the same folder as Merged.etl.

• Rename Merged.zip to BUG-37795_gpuview_trace_YourAvatarName.zip, for example BUG-37795_gpuview_trace_Whirly_Fizzle.zip

• Note that this trace will contain a lot of detailed information about your system and for this reason you will be sending your traces directly to Linden Lab who will pass them onto Microsoft.

• The zipped up trace will probably be too large to attach to an email, so you will probably have to upload it to Google Drive, DropBox or a similar file sharing service.

• Send an email to Grumpity Linden at grumpity@lindenlab.com with the subject line YourAvatarName BUG-37795 gpuview trace results

  • Include a paste of your system information from Help -> About Second Life (if using the LL viewer) or Help -> About Firestorm (if using Firestorm viewer).
  • Either attach your zipped up trace file to the email (if small enough) or provide a link where your trace can be downloaded from.

Thanks!

If you get stuck getting the trace to work, comment back here and ask for help.

[sl-service-account]

Trager Alter commented at 2016-09-21T02:05:30Z, updated at 2016-09-21T02:48:46Z

Just installed latest Windows 10 Cumulative Update KB3193494 and the problem is NOT resolved yet. All seems fine after uninstalling KB3193494. The saga continues :(

[sl-service-account]

ObviousAltIsObvious commented at 2016-09-21T03:01:22Z

Yes, KB3193494 is the same update as KB3189866. It got a new number because some copies of the original were corrupt and failing to install, but it contains no new changes that could help with the OpenGL issue.

[sl-service-account]

Ansariel Hiller commented at 2016-09-21T18:40:08Z

Attached log_de.cmd that will work on the German Windows 10 version for creating the trace.

If you are running a German Windows version, you will have to run the attached log_de.cmd instead of log.cmd Whirly mentioned in her how-to.

[sl-service-account]

ginormous.woodget commented at 2016-09-21T23:00:22Z

Windows Update KB3193494 downloaded, and with restart installed. Logged into SL using Firestorm. Within 5 mins or so experienced the FPS performance bug. Ran gpu trace , zipped file and emailed to grumpity linden.. Uninstalled and blocked KB3193494 ...Hope MS can fix this.

[sl-service-account]

Grumpity Linden commented at 2016-09-21T23:40:49Z

Thank you all for the reports! Microsoft is, at this point pretty certain that the problem lies in the nVidia OpenGL driver, and they are talking with nVidia to resolve. So, if you are able to reproduce this issue on a different GPU please send me a trace. Otherwise, I've got all we needed, thank you!