sl viewer causes my computer to crash and reboot

[deadlycreature1]

this started today. has anyone else had issues?

[Quinn Lysette]

is it the sl default viewer ?

 

if it is just delete all the cache n try again ?

[Bitsy Buccaneer]

If you have a Mac with a nVidia graphics card, take a look at this thread - especially if you've upgraded to Sierra OS recently.

https://community.secondlife.com/t5/Second-Life-Viewer/Anyone-tried-Apple-MacOS-Sierra-with-SL-Viewer-yet/td-p/3068974/highlight/true

Short version: LL is still using graphics code that Apple stopped supporting several OSs ago and with a nVidia graphics card it crashes the GPU. Sometimes it crashes and reboots the computer as well. :matte-motes-confused:

[arton Rotaru]

With this little information given, I'll place my bet on a dying PSU.

[deadlycreature1]

It doesn't crash on firestorm just the official viewer. It is windows 8. i have enough ram 16gb gaming computer nvidia graphics card i7 processor

[arton Rotaru]

If it only happens with the official default SL viewer, I would try one of the official alternative viewers. The Second Life Maintenance Viewer, which I usually run regularly for example. Or the Second Life Project Alex Ivy 64-Bit Viewer which I use right now.

http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers

It could still be a hardware failure though. Like different settings in Firestorm, and the default viewer (shadows vs no shadows for example) which would cause different loads on your machine.

Running some stress testing tool could rule that out.

[Nalates Urriah]

To give applicable answers we need to know about your computer and viewer. Get the detail we need from the viewer's HELP->ABOUT... Paste that information in your post.

When all else is failing and when you and those helping have no clue, look in the viewer’s log files. The viewer has various log files you can read to get an idea of what has gone wrong. Look at the log immediately after you crash or exit the viewer. Logs are replaced the next time a viewers starts. You’ll find the logs in:

C:\Users\[Win_login_ID]\AppData\Roaming\SecondLife\logs\

 

• .crashreport.log – This log is generated when the viewer crashes, the previous version of the file is overwritten. Rename this file if you plan to restart the viewer before examining the file. Otherwise, just read it with a text viewer (Notepad is good).
• .debug_info.log – This file is internally formatted as an XML file. I never find it of much use. It is mostly the specs of your machine.
• .SecondLife.log – This is the main log file. I find it the most useful. Start from the end of the file and work toward the beginning. Search for ‘WARNING’ and ‘ERROR’. With any luck the messages there will give you an idea of the problem. Recent changes have added section heading to parts of the file that can identify the general nature of the problem. There are lots of performance stats included. At the end of a non-crash log there are secession stats;  Run Time, Average Packet Size, Dropped Packets, Resent Packets, etc. The file is replaced and recreated for each viewer secession.
• .SecondLife.error_marker – I don’t know what information is inside. I don’t have a copy to examine as I write this. The presence of the file indicates where, when, and what error happened. I think this is a disaster backup file for crash reporting in which information about the crash is retained in the event the crash handlers are destroyed before they can create the other more complete crash files.
• .SecondLife.start_marker – There is no information inside. The presence of the file indicates how far into the start process the viewer has gotten. Whether the file exists or not is the pertinent information.
• .SecondLifeCrashReport.log – This is another file internally formatted to XML.  It is created when the viewer crashes. I think this is the new version of the crash log. It is mostly text.
• .stats.log – This is a short file containing network statistics. Similar information is in other log files. It is an easy to read set of stats that show how many packets were dropped and resent in a secession.

I find the SecondLife.log is the most useful file for tuning and troubleshooting the viewer. It is verbose and reasonably easy to understand. There is a Debug Setting that allows you to increase or decrease the level of reporting.

[LinuxGod4u]

Since you did not state you are using Windoze I am going to assume you are. Let's begin with performing a clean install of your current viewer. This means after removing it from the "uninstall programs" list you need to go to your Drive C: (hardrive) & remove the viewer file, ex. firestorm, singularity,etc  & the additional secondlife file too. Re-boot your pc & re-install your viewer of choice again. You may wish to try another viewer to see if the issue still exists. If this does not solve your problem run a full virus scan to see whether you have a malicious program issue. When I used Windoze for SL I used ZoneAlarm for pc protection. It works better than Windoze Defender & it is free.

http://www.zonealarm.com/

Also make sure ALL drivers on your pc are up to date. IF none of what I suggest fix your issue you may wish to explore the possibility that a hacker may be at work; however I hope I am wrong! I hope this helps some of you.

"I Relish Simplicity"