Yup even me too.
CRASHING OUT OF SL.
Now. I didn't give 2 hoots when it was happening to everyone else. Now I have lots of hoots to give. I will give some here now.
I thought it was just me.
Then I thought, well its just some of US. US unlucky ones. US not doing something right.
Not the latest OS.
Not enough hardware horsepower. Too poor to play SL, crash free.
My graphics settings are too high.
Avoid crowded places.
Don't cam around.
Someone is out to get me. Someone got me. They keep getting just me.
Yup I played victim. Why me? Poor me.
Different levels of 'crashing' is what I was experiencing
Level 1 - SL crashes, have to relog into SL. Sometimes you will get a message "Display Driver Has Stopped Responding But Has Recovered" message.
Level 2 - SL crashes, I get a flickering single-colored screen, pink, blue, or black. I have to reboot my computer. *sad face*. This is a HARD POWER-OFF reboot and not a RESTART.
Level 3 - SL crashes and causes my computer to REBOOT on its own.
It appears to me, personally that the problem, has been exacerbated by mesh and the cost to rez with the onset of mesh and more mesh...not just clothes and feet and bodies but now heads and more mesh objects (non-avi related mesh). It appears as if SL is sending too much graphical information in 2 seconds. This causes the system to freeze up and or reboot.
Mesh objects are a culprit it appears and not just mesh avis. Also multiple large (1024x1024) textures on multiple faces on big multi-linked items like jewelry are a contributing factor. Also poorly or over vertexed mesh designs cause more work to be done....prolly more than needs to be. Thus the introduction of Avatar Complexity to try and shame creators down to more reasonable resource-laden creations. Just my 2 cents. Maybe only 1 1/2 cents.
Sooo...finally after waking up my super-lazy self and poking around and sleuthing and googling....
It appears the problem lies between nVidia driver and Windows OS updates. I will stop short of pointing a finger. Suffice it to say that they don't seem to play well with each other. nVidia asked me for a screen-shot of my Windows Updates so that lends credence to Windows.
Also I read someone in blog posts said they were ok until a certain Win update.
Then , i went back to an nVidia driver 2 years ago...seemed to fix it but SL ran slow as molasses. I got too used to a faster SL experience where I am not typing in slow-motion...and can pivot around my camera so....
I tried lowering my SL graphics and lowering monitor display resolution. Nothing worked.
I went to an nVidia driver that was one year old. (I had been running with one 2 years old...refusing to update out of fear that this very thing would happen). The latest nVidia drivers did not fix the problem. That's the thing everyone says to do. But with the latest all i got was was blank screens and forced reboots.
By going to a driver (1-year-old), in between what I had been using (and the most current, i was able to at least now get an error message. TADA!!!!!!!!!!
"A TDR has been detected. Application must close."
It pointed me to a working solution having to do with TDR. Timeout Detection and Recovery. The changes took me 30 seconds to make, if that long. You have to ADD the entries. They don't exist. Took me awhile to figure that out.
I don't suggest you make them on your own if you never have made changes to your Windows Registry before, just to be safe. Get a skilled friend or tech to help you or walk you thru it or take it into a computer shop and have them make it or let a tech have online access so they can make the changes for you.
Make a backup before making the changes if its your 1st time. And you have to reboot your computer after making the changes.
Timeout Detection and Recovery (TDR)
This is what Microsoft has to say about it.
And another helpful thread for Win10 users (I am on Win7 64-bit - nVidea 560ti)
Long story short, I made changes to my Windows Registry and have been crash-free for a couple days (knock-on-wood). I was normally crashing 2 to 4 times a day, almost always upon my 1st login attempt.
Caveat: "You can use the following TDR-related registry keys for testing or debugging purposes only. That is, they should not be manipulated by any applications outside targeted testing or debugging."
So I don't know what if any downside there may be to making these changes permanent. Technically I manually made the changes and it wasn't an application that made them. Maybe they don't trust applications to make them safely. An app could screw up and you might never know what happened if you got a blank screen upon reboot as an example. eeek.
But for now I am crash-free. Also my friend seems to be crash-free so far and reports a much smoother experience so far. WOOHOO! Knocking on more wood. Knock Knock.
Do your own research. Everyone's situation is unique. There are no guarantees. There is another solution that I found that cleans up corrupt Windows files that has seemed to fix peoples crashing issues when the TDR didn't work for them.
Here are the settings I chose....don't ask me why I chose these particular values. Its likely you get way with a TdrDelay that is smaller than 16 seconds. I have heard 8 and 10 as other workable values.