Jump to content
  • 0

Second Life random crashes (All Viewers)


cgross220
 Share

You are about to reply to a thread that has been inactive for 3802 days.

Please take a moment to consider if this thread is worth bumping.

Question

I recently got back into SL (on the same computer as before) except now at random times throghout playing it'll crash, with nothing but an empty white box popping up with only the option to click "Ok".  This never happened before and I've been unable to stay online for more than 20 minutes (though a lot of times it'll crash within 2 minutes of opening SL).  I've tried all viewers, and tried a clean install to no prevail.  Any help would be appreciated.  Below is the crash log and laptop specs.

 

Samsung Electronics Intel Core i5-3210M CPU @ 2.50GHz

Running Windows 8

Graphics card is Intel HD Graphics 4000

ISP Download Speed: 32.43 Mbps, Upload: 13.30 Mbps, Ping: 12 ms

I'd give you chocolate if I had any.

 

2013-11-23T19:50:19Z INFO: llcrashlogger/llcrashlogger.cpp(609) : LLCrashLogger::init: Loading crash behavior setting
2013-11-23T19:50:19Z WARNING: llcommon/llfile.cpp(127) : warnif: Couldn't remove 'C:\Users\000\AppData\Roaming\Firestorm\logs\SecondLife.exec_marker' (errno 2): No such file or directory
2013-11-23T19:50:19Z INFO: win_crash_logger/llcrashloggerwindows.cpp(271) : LLCrashLoggerWindows::init: Loading dialogs
2013-11-23T19:50:19Z INFO: win_crash_logger/llcrashloggerwindows.cpp(313) : LLCrashLoggerWindows::mainLoop: CrashSubmitBehavior is 0
2013-11-23T19:50:22Z INFO: llcrashlogger/llcrashlogger.cpp(576) : LLCrashLogger::updateApplication: Gathering logs...
2013-11-23T19:50:22Z INFO: llcrashlogger/llcrashlogger.cpp(203) : LLCrashLogger::gatherFiles: Using log file from debug log C:\Users\000\AppData\Roaming\Firestorm\logs\Firestorm.log
2013-11-23T19:50:22Z INFO: llcrashlogger/llcrashlogger.cpp(204) : LLCrashLogger::gatherFiles: Using settings file from debug log
2013-11-23T19:50:22Z INFO: llcrashlogger/llcrashlogger.cpp(576) : LLCrashLogger::updateApplication: Gathering hardware information. App may appear frozen.
2013-11-23T19:50:22Z INFO: llwindow/lldxhardware.cpp(552) : LLDXHardware::getDisplayInfo: CoCreateInstance IID_IDxDiagProvider
2013-11-23T19:50:22Z INFO: llwindow/lldxhardware.cpp(579) : LLDXHardware::getDisplayInfo: dx_diag_providerp->Initialize
2013-11-23T19:50:22Z INFO: llwindow/lldxhardware.cpp(586) : LLDXHardware::getDisplayInfo: dx_diag_providerp->GetRootContainer
2013-11-23T19:50:22Z INFO: llwindow/lldxhardware.cpp(596) : LLDXHardware::getDisplayInfo: dx_diag_rootp->GetChildContainer
2013-11-23T19:50:24Z INFO: llwindow/lldxhardware.cpp(604) : LLDXHardware::getDisplayInfo: devices_containerp->GetChildContainer
2013-11-23T19:50:24Z INFO: llcrashlogger/llcrashlogger.cpp(576) : LLCrashLogger::updateApplication: Encoding files...
2013-11-23T19:50:24Z INFO: llcrashlogger/llcrashlogger.cpp(576) : LLCrashLogger::updateApplication: Sending reports...
2013-11-23T19:50:25Z INFO: llmessage/llcurl.cpp(183) : LLCurl::Responder::completedRaw: Failed to deserialize LLSD. http://crashlogs.phoenixviewer.com/upload [200]: OK
2013-11-23T19:50:25Z INFO: llcommon/llapp.cpp(496) : LLApp::setQuitting: Setting app state to QUITTING
2013-11-23T19:50:28Z INFO: win_crash_logger/win_crash_logger.cpp(51) : WinMain: Crash reporter finished normally.
2013-11-23T19:50:28Z INFO: llcommon/llapr.cpp(73) : ll_cleanup_apr: Cleaning up APR

Link to comment
Share on other sites

2 answers to this question

Recommended Posts

  • 0

Sorr,

Our Mind Reading abilities are totally offline for now:

crystalball-little.jpg 

So we can help your further, please update your question with the following information as follows: Select the Options drop-down menu to the right of your question and select Edit Question.

1) The make and model of your PC or Laptop

2) Your Operating System

3) The make and model of your computer's Graphics Card or Subsystem.

4) The Speed and quality of your ISP.

5) [Optional] A bag of Chocolate for the SL Answers Volunteers

Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 3802 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...