Constant Crashing everytime Im start moving around. I have a really good computer and 100 down 20 up

[Alwin Alcott]

still... your machine can be top... your speed can be top... and still have a crappy connection.

It might be the last ... if sl can't get a real steady connection it won't run properly.

and... if you'r using wifi, try wired.

 

post your system specs... what graphics?... please edit your post and add those

 

Stop deleting cache, it's only making things worse, it has to reload all what you see over and over again.

 

[Alwin Alcott]

still... your machine can be top... your speed can be top... and still have a crappy connection.

It might be the last ... if sl can't get a real steady connection it won't run properly.

and... if you'r using wifi, try wired.

 

post your system specs... what graphics?... please edit your post and add those

 

Stop deleting cache, it's only making things worse, it has to reload all what you see over and over again.

 

[Madelaine McMasters]

Hi JellO,

I think Alwin's right. Your connection may be a li'l too flaky to support an SL session. You may find remedies here...

http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/

Good luck!

[JellOHSHIT]

Ok, So Connection would cause my SL to stop responding?

[JellOHSHIT]

Ok, So Connection would cause my SL to stop responding?

 

 

http://prntscr.com/a88o3p

 

Also thats my connection speed to cali

[Madelaine McMasters]

Speed isn't the most important thing. SL is very intolerant of both connection latency and quality. Dropped packets can crash the viewer. Also make sure your graphics drivers are up-to-date.

[Nalates Urriah]

Once you are sure your conneciton to the SL servers is good, go through the Firestorm troubleshooting.

http://wiki.phoenixviewer.com/firestorm_troubleshooting

Remember! A good Internet connection is not the same as a good connection to the SL servers.

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 Second Life logs in: (Replace SecondLife with the name of the viewer you are using.)

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

• 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).
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.

Most of these files are erased when the viewer starts. If you plan to send the files in with a trouble ticket or bug report, place copies in another folder before starting the viewer.

Marker files are temporary and may or may not exist at any given time.

Entries in the files associated with errors and warnings are labeled as such. That makes them easy to find by searching. Warning entries are common and do NOT necessarily mean there is a problem. Some warnings are a part of normal operation. Some errors are trivial and do not indicate a ‘noticeable’ problem in the viewer’s operation.

.

[Whirly Fizzle]

Are you using Webroot antivirus software?

The corrupted textures shown in your image plus a swift viewer crash (especially on a clean cache) match the symptoms of having something installed on your system thats barfing all over Pipelining in the viewer.

If this is the problem then ultimately, Webroot (or whichever antivirus/Firewall software you are using) need to fix their bug .

You can work around the problem by disabling Pipelining in the viewer.

• Activate the Advanced menu in the top menu bar with CTRL+ALT+D
• Advanced -> Show Debug Settings -> HttpPipelining -> Set this to FALSE.
• I would actually do this from the login screen because you will likely crash when logged in & the settings change will revert. From the login screen, it's Debug -> Show Debug Settings -> HttpPipelining -> Set this to FALSE.
• You then MUST purge viewer cache because it will be full of corrupted textures that you fetched with Pipelining. You only need to purge cache once after changing the Pipelining setting.
• For Firestorm from the login screen: Viewer -> Preferences -> Network & Files -> Directories -> Clear Cache -> Apply -> OK.
• Restart the viewer & everything should be back to normal.

 

For details about the Webroot problem:

LL JIRA: https://jira.secondlife.com/browse/BUG-11314 - Graphical Errors - Webroot + Pipelining incompatibility

Firestorm JIRA: http://jira.phoenixviewer.com/browse/FIRE-17661 - HttpPipelining - Webroot Crash with fault error ntdll.dll mesh fails to render, texture corruption

 

Hope that helps.