If You Have Changed Any Debug Settings

Several creators recommend specific settings in order for you to be able to better see their products. Sadly, some of these recommendations will lead to many people crashing more. For example, go to the top menu, Advanced → Debug Settings (press Ctrl-Alt-D to enable Advanced, if it isn't):

  • RenderVolumeLODFactor should never be set over 4; a good value is between 2 and 3.
  • TextureLoadFullRes should never be enabled (in other words, it should be set to FALSE).

If you are advised to raise LOD above 4, please disregard that advice.

Similarly, there is a notecard going round which suggests settings to prevent graphics crashes. Sadly, those settings can often result in perfectly ordinary content refusing to render. So if you have changed debug settings per such a notecard, revert them.

For both the cases above, should you not remember what settings you changed, then proceed as follows:

  1. Back up your settings as explained here.
  2. Then wipe settings by following the instructions on this page.
  3. Log back in and see if this fixes your problem. If it does, you can try a restore and see if the issue returns.
  4. If the problem does return, wipe settings again and set them from scratch.

Rainbow Colors after Logout

Note: This is not the same as rainbow colors in-world.

If you see rainbow colors after logout and you have MSI True Color or f.lux installed on your system, do the following steps in order:

  1. Uninstall MSI True Color if installed.
  2. Install f.lux from https://justgetflux.com/ if not installed.
  3. Uninstall f.lux using the f.lux uninstaller, not the Windows uninstaller from Windows programs & features / add/remove programs.
  4. When running the uninstaller it will give you the option to reset to the windows default color profile; say Yes. (Running this uninstaller is the only way we have found to get rid of the MSI True Color profile.)

Refer to http://jira.phoenixviewer.com/browse/FIRE-12561. Also see the alternate workaround at the comment dated 13/Apr/17

Driver Not Responding

"Display driver stopped responding and has recovered" error in Windows

If you are getting the error in the title, then please refer to this page, this page or this page for those using Intel graphics for possible solutions.

With thanks to Skua Sarrasine for having found the first of these.

nVidia Driver Error Code 7 (or 3)

Symptom: “This is a bug thats only experienced with Firestorm running. Basically, at seemingly random, but very infrequent times, my dual screens will bug out, producing two displays of solid colour, randomly. Sometimes Windows will return saying it recovered from an error code 7 or 3.”

Some research turned up this for error code 7; it suggests setting physX to CPU. And that seems to have solved the issue.

Note also the (apparent) interaction with Chrome.

Viewer Not Responding

This is a known issue with Windows 7, 8.1, and 10 with a 64-bit operating system; it affects other programs in addition to Second Life viewers.

Please try the following - but NOT while logged in.

Windows 7

  • Go to the Start button
  • Type services.msc and then press enter.
  • Wait until the services window pops up.
  • You may have to expand the window a bit to see the services.
  • Look for DesktopWindowManager.
    • If it is running, right click it and select Stop. Wait until it stops.
    • You will probably see your desktop transparency window borders go flat. No worries.
  • Right click again and select Properties.
    • In the Startup type, select Manual. Click OK.

Windows 8.1/10

  • Open the Task Manager, by one of the following methods…
    1. Right click the task bar and choose Task Manager.
    2. Click the Start button and type Task Manager, then click on the result.
    3. Press Ctrl+Alt+Del and choose Task Manager from the list.
    4. Press Ctrl+Shift+Esc.
  • Click More Details link at the bottom if needed
  • Look at the several column headers, they will show a percentage of use. Memory or Disk may show a high percentage when Firestorm is not responding.
  • Click on one of the high-percentage column headers to sort the processes. The top one is likely the cause. If it's your antivirus, make sure you have whitelisted Firestorm and its cache (refer to this page for whitelisting guidance).

Viewer Freezing

If you find the Firestorm seems to freeze up every so often, then try these things, one at a time, testing after each one:

  • If you have chat saving enabled, and have a large number of chat transcript files, these could be causing the freezes. (Ref. FIRE-11322.) Try moving your chat transcripts elsewhere and see if the freezing stops.
    You can find your chat transcripts by going to PreferencesNetwork & Files -> Directories → Conversation logs and transcripts location; click the Open button.
  • Set Preferences → Network & Files → Directories → Cache Size to maximum (9984MB or the maximum space available, whichever is less)
  • Ensure that your antivirus software is not scanning the viewer cache folder. See Whitelisting the Viewer in Anti Virus Software for more information.
  • If you have ever enabled “Full Res Textures”, disable this setting. Top menu bar, Develop → Rendering → Full Res Textures (dangerous). Ensure that this is NOT checked. (Ctrl-Alt-Q to enable Develop, if it isn't.)
  • Advanced → Debug Settings → Set FastCacheFetchEnabled to FALSE - then relog.
    Ctrl-Alt-D to enable Advanced, if it isn't.
  • Preferences → Graphics → Hardware Settings → Viewer Texture Memory Buffer - raise this as high as it will go. Then relog. (64-bit version only)
  • Tip from a user: Windows users: If you're running CrashPlan, open the “Advanced” section of “Backup” settings and uncheck “Back up open files.
  • Tip from a user: linux users: Turn off compositing, see if it helps.

For additional suggestions, see the page on Severe Lag.

  • graphics_crashes_and_glitches.txt
  • Last modified: 2018/08/02 18:36
  • by miro.collas