Crash after crash after..

Seems to be a pretty common problem from what I've been reading here on the forums. I just wanted to throw my post up so in case there's someone keeping track of this I guess. I don't really have high hopes of it getting fixed any time soon but maybe someone does have a suggestion.

I really doubt that it's hardware-related or driver related. It's SL related.

Here's my system:

MSI K8N Neo2 Platinum Mainboard
AMD Athlon64 3000+
2GB RAM
EVGA NVidia GeForce 6800 Ultra (AGP)
Sound Blaster XFi
SATA Hard Drive (120GB, Attached to mainboard)
USB Keyboard (Logitech G15) and USB Trackball (Microsoft Trackball Explorer)
3Com 3C905C-TX-NM NIC
DVD-R/W (Plextor)

Running Windows XP (fully patched). Latest drivers for everything (including mainboard). Fresh install of XP (reformatted/reinstalled everything within the last week.5).

Everything worked fine until 1.10 .. now it seems to crash pretty much randomly. Sometimes I can stay on for up to 20 minutes at a time, sometimes I crash almost as soon as I log in. I've tried clearing the cache to no avail. I've tried doing a complete reinstall and still have the same problems. I've tried turning on and off various settings that have been recommended here and I still have the same problem.

I can run everything else (other games like EVE Online, CoH, World of Warcraft) with no issues at all. They all run fine. My other applications work fine too. SL is the only thing that I have crashing problems with.

As usual with SL problems, I'll just wait this out. It'll (hopefully) get fixed eventually. I have another PC to use SL on that doesn't crash at all with SL (or at least hasn't yet), so this isn't a huge issue. I'll keep trying and post my error log file if I can ever find it.

Hi!!!

I'm in the same situation and started the topic /111/3f/114567/1.html where my computre specs are listed.

I've been working with live tech support during the week and email (extremely slow and probably overwhelmed with crash reports). Everytime I try to run SL on the desktop, it crashes and I send support the log file. Here is where to find the file they need.

To get to the secondlife log:
- click on My computer
- click on the C drive
- click on Documents and settings
- click on the ID you are usuing (I use administrator)
- click on Application Data

If you do not see that dir, go to tools and then the view tab and make sure you have it checked so you can see hidden dir's.

- click on Secondlife
- click on logs
- there you will find Secondlife.log

That is the file you need to send to [email]support@secondlife.com[/email] when you want to see if they can help with a problem.

They seem to be very slow responding on weekends as I haven't gotten a reply since early this am when I sent my latest log in for them to check.

Best of luck!
Katrina Keen

Aah.. thanks! Found it!

Here's the end of the log log:

2006-06-18T11:02:38Z WARNING: Getting ASCII text from unicode line editor!
2006-06-18T11:03:11Z INFO: Transmitting sessions stats
2006-06-18T11:03:11Z INFO: STAT: Fullscreen mode: 0
2006-06-18T11:03:11Z INFO: STAT: Seconds below 8 FPS: 9.61062
2006-06-18T11:03:11Z INFO: STAT: Seconds with sim FPS below 20: 2.02099
2006-06-18T11:03:11Z INFO: STAT: Seconds with physics FPS below 20: 2.02099
2006-06-18T11:03:11Z INFO: STAT: Seconds with packet loss > 5%: 0
2006-06-18T11:03:11Z INFO: STAT: Ratio of frames 2x longer than previous: 0.0056333
2006-06-18T11:03:11Z INFO: STAT: Number of objects that want to display web pages: 0
2006-06-18T11:03:11Z INFO: STAT: Increase/Decrease in bandwidth based on packet loss: 366.211
2006-06-18T11:03:11Z INFO: STAT: Max bandwidth setting: 732.422
2006-06-18T11:03:11Z INFO: STAT: Lighting Detail: 1
2006-06-18T11:03:11Z INFO: STAT: Visible Avatars: 3
2006-06-18T11:03:11Z INFO: STAT: Object Shaders: 0
2006-06-18T11:03:11Z INFO: STAT: Environment Shaders: 0
2006-06-18T11:03:11Z INFO: STAT: Draw Distance: 128
2006-06-18T11:03:11Z INFO: STAT: Chat Bubbles Enabled: 0
2006-06-18T11:03:11Z INFO: STAT: Avatar Shaders: 0
2006-06-18T11:03:11Z INFO: STAT: FRAME_SECS: 0.032912
2006-06-18T11:03:11Z INFO: STAT: UPDATE_SECS: 0.0172364
2006-06-18T11:03:11Z INFO: STAT: NETWORK_SECS: 0.000515768
2006-06-18T11:03:11Z INFO: STAT: IMAGE_SECS: 0.00124157
2006-06-18T11:03:11Z INFO: STAT: REBUILD_SECS: 0.00164598
2006-06-18T11:03:11Z INFO: STAT: RENDER_SECS: 0.011449
2006-06-18T11:03:11Z INFO: STAT: CROSSING_AVG: 0
2006-06-18T11:03:11Z INFO: STAT: CROSSING_MAX: 0
2006-06-18T11:03:11Z INFO: STAT: LibXUL Widget used: 0
2006-06-18T11:03:11Z INFO: STAT: Window width: 1280
2006-06-18T11:03:11Z INFO: STAT: Window height: 904
2006-06-18T11:03:38Z C:\builds\2006-06-15\indra\newview\llviewerimage.cpp(440) : error
2006-06-18T11:03:38Z ERROR: C:\builds\2006-06-15\indra\newview\llviewerimage.cpp(440) LLViewerImage trying to create texture with no Raw Image

I seem to see that "Getting ASCII Text from UNICODE line editor" message a lot. It only seems to be a warning, though and not an error. The error at the bottom? Could be I suppose. I'll have to keep an eye on this on the next time that it crashes.

Thanks for your tip on how to find this though!

Just wanted to post a follow-up to this, since I fixed the problem. I hadn't used this computer for SL in about a months because I couldn't play for 3 or 4 minutes without it crashing. (I'd used my other PC instead. It's not as nice but it works)..

I did a little research one day when I had some free time, though, and apparently the memory that I used /sometimes/ has problem at the advertised voltage (2.6v). The company mentioned that if there were problems with applications, try bumping it up to 2.7v. I did so and SL has only crashed once since then.

It's odd that SL would be the only application that would cause problems but the more I read up, the more it made sense because SL is very processor intensive.

Anyhow, this thread can be marked closed, or resolved or whatever.

Iris i have the same problem as you, about every two minutes crash on my main pc, could you specify more detailed about the memory thingy because i sure wanna try that on out

She'll be talking abotu the DDR voltage. It's a setting in the system BIOS and something that can improve stability... but done too far can damage PC components. Upping 0.1v though won't cause any harm and if stability is an issue is worth trying.

Yes. The only reason that I did it, really, was because it recommended doing it (to that voltage level) on the manufacturer's site.

I figured that way, if it broke then it's their fault.

I tried this and it doesnt help, the crashing continues...

I have Kingston ValueRAM two sticks of 1GB

2 sticks: KVR400X64C3A/1G.
My BIOS gives the option: 2.5V, 2.6V, 2.7V
It was on 2.5, i tried on 2.6 and log in SL, then 2.7 and log in SL.

Is it safe to higher this volatage as my bios gives me these options? Or should i stay on 2.5 V?

Your ram is rated at 2.6V. If you wanna go any higher you risk frying your ram and voiding your warranty. The BIOS gives those options for any ram for the overclockers who want to take the risk.

i take it u guys do know what a memory manager does?
without a memory manager windows tends to use as much ram as possible while freeing as little as possible. When it gets down to 1.5MB (this is even on a 512MB system)
it tends to just use that little peice of memory till the system crashes. The best working manager i have found so far is by Dachshund software but after awhile even that fails so its reboot time - however this is only after a few hours of severe usage