Jump to content

unable to play SL due to immediate crash upon launch

Argus Zimmer

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

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

Recommended Posts

Ok so played for years on an old better box computer got some cash decided to up grade built a whole new system (specs to follow). Now when ever I log in it not only crashes the viewer I have to do a hard power down to to even get up and running agian I run other games without a hitch. So just tossing it out there I'd love to play agian so any constructive suggestions would be apreciated.


OS Name Microsoft Windows 10 Pro
Version 10.0.10586 Build 10586
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer Gigabyte Technology Co., Ltd.
System Model To be filled by O.E.M.
System Type x64-based PC
System SKU To be filled by O.E.M.
Processor AMD FX(tm)-9590 Eight-Core Processor, 4700 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. F3, 5/28/2015
SMBIOS Version 2.7
Embedded Controller Version 255.255
BaseBoard Manufacturer Gigabyte Technology Co., Ltd.
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "10.0.10586.420"
Name AMD Radeon R9 200 Series
PNP Device ID PCI\VEN_1002&DEV_679A&SUBSYS_277C1462&REV_00\4&2534E90F&0&0010
Adapter Type AMD Radeon Graphics Processor (0x679A), Advanced Micro Devices, Inc. compatible
Adapter Description AMD Radeon R9 200 Series
Adapter RAM (1,073,741,824) bytes
Installed Drivers aticfx64.dll,aticfx64.dll,aticfx64.dll,amdxc64.dll,aticfx32,aticfx32,aticfx32,amdxc32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Driver Version 16.150.2111.0
INF File oem23.inf (ati2mtag_R575 section)
Color Planes Not Available
Color Table Entries 4294967296
Resolution 1366 x 768 x 60 hertz
Bits/Pixel 32
Memory Address 0xC0000000-0xCFFFFFFF
Memory Address 0xFEA00000-0xFEAFFFFF
I/O Port 0x0000E000-0x0000EFFF
IRQ Channel IRQ 4294967292
I/O Port 0x000003B0-0x000003BB
I/O Port 0x000003C0-0x000003DF
Memory Address 0xA0000-0xBFFFF
Driver c:\windows\system32\drivers\atikmpag.sys (, 661.00 KB (676,864 bytes), 12/17/2015 3:42 AM)

Link to comment
Share on other sites

Lots of info on the hardware... it all looks good.

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:



  • 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 in the viewer 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. They indicate when the viewer died and stopped reporting.

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.

Link to comment
Share on other sites

Do you happen to have the Raptr (AMD Gaming Evolved) in-game overlay or the Asus ROG Gamefirst software installed on that system?
Both will cause the viewer to crash, usually on launch.
You will need to either disable or uninstall this software if it's on the system.

Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 2697 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

  • Create New...