|
|
|
I have a pc that is duo core 3ghz, 2gb ram with an integrated Nvidia GeForce 7050 graphics card, running on Windows XP. After about 5 mins the pc crashes when running Second Life. The Nvidia card is well under specs for Second life although my old pc has an Nvidia Geforce 5500 which, although is no good for Windlight can ahndle SL ok, so I see no reason why the &050 should have crashed.
To overcome this I installed an Nvidia GeForce 8600 pci express card. This helped a bit but the pc crashes after running Second Life for about 20 mins. The crash can either be the pc freezing completelly or automatically restarting. The CPU usage can be erratic when Second Life is running but wether the usage is high or low doesn't seem to affect when the pc will crash. Other in game factors also don't seem to make a difference, such as if there are a lot of people in the sim at the time or if the sim is empty, what huds I am wearing etc etc, so it doesn't seem to be a lag issue. I downloaded and tried Active Worlds to see if the problem was specific to Second Life, and if anything the problem seemed worse on Acrive Wolrds, with things taking forever to rez, and the pc crashing before the rezzing had completed. Your problem seems similar to mine in some ways. I am not very technically minded but I have assumed the problem is either a configuration issue that I can't track down, or the motherboard is a piece of cheap junk, but this is a guess as much as anythign else. If there are any solutions staring me in the face that can be pointed out to me I would be interested to hear them. Removed one paragraph and corrected the title.
At first it appeared that residents with minimal inventory were immune to this problem but I finally reproduced it with my tester alt. It may still be a factor. I am now able to avoid crashes. I keep the Window Task Manager open and I am also alert to momentary mouse movement pauses. If the mouse is showing symptoms sure enough the CPU duty cycle is maxing out. A quick minimize, then shift focus to another window, then maximize SL and the problem is gone for a while. Please try installing the latest RC and let us know if this is still a problem.
Thanks Alexa.
Second Life Server 1.22.3.89352 YES, Problem gone.!!! Unrelated item. When using a dual screen you can't enter your First Name. After the 4th character it resets. UPDATES
The First Name entry problem appears to be related to the virgin start of the RC. Having once logged in it remembers the name and the problem goes away. OK after all that my freezes may not have been related to CPU usage percentage. Since the freezes would melt with time it seemed like constipation and with CPU usage hovering around 100% it was not an unnatural assumption that they were related. However on 2 runs with 1.22.3.89352 I have frozen after about 5 minutes running and the CPU usage was less than 50%. I will add any clues here if I find them. I have to post these between crashes or start over I'm glad the new RC solved your initial problem. For the second one you mentioned re: the 2 monitors, there are a few problems (black skin seen by the owner and others) that arise when SL is running on a secondary monitor. It's always best to have it running on your main monitor.
Freeze history using Second Life Server 1.22.3.89352
(On most log-ins I got the expected SL RC Viewer notice. On 2 or 3 I got the out of date viewer warning but I ignored it.) First 3 uses all froze after about 5 minutes. I reset the computer on the first two. On the third, I left the computer sit in the frozen mode to see if it would eventually thaw. After about 3 minutes it did thaw and worked OK with no further freezes for about 10 minutes. Next two log-ins locked up in the log-in screen "not responding" Next two log-ins no problems after about 10 minutes each. Next log-in failed and I was locked out for about 3 minutes. Half an hour now in next log in and NO PROBLEMS. Why did the first three logins freeze? Did having the patience to sit it out until it thawed get rid of the problem? OO I hate that. My Log-in timed out as I was adding symptoms to this list and I lost a page of valuable data. I'll try and re-construct from memory. Grrrr. Can't we get a 1 minute time-out warning or reset the time-out while the page is active. Grrr.
Re-opened this bug. Now having the same problems on RC1.20 but not as serious as it was on 1.19 Normal CPU usage running SL is about 20 to 50% depending on activity. With no apparent activity to trigger it, CPU usage shoots up to 100% and computer freezes. With experimenting I found that if I stopped editing a 23 prim object, CPU would go back to normal%. Start editing, back to 100% -> Repeatable -> BUT after losing focus to enter data in this JIRA, and returning to SL I could no longer reproduce it. On a freeze a little later I had the following that may be helpful:- This time the left hand CPU shot up to 100%, right hand one at about 50% but computer operation was severely handicapped. Mouse interrupts about every 4 seconds. With SL minimized the partial freeze continued. I managed to switch to Processes on the WIndow Task Manager and found:- SL 12% (Normal for minimized) It seems like SL was having trouble requesting an external process. MORE CLUES using RC1.20
There is no doubt that the freezes are associated with 100% CPU duty cycles. I had to close SL using the Windows Task Manager. I had 2 open scripts that SL would want to ask me if they should be saved. That would have taken 15 minutes for the conversation at the slow processing rate during the freeze. BUT there was an interesting result. After SL shut down it still took a number of minutes to thaw! This suggests a constipation on the operating system side of SL. I have no hard evidence but I think the freezes are associated with client side calls using llTargetOmega and llSetTextureAnim. I seem to have a lot of freezes when working with these. I get the feeling that the requests are being made faster than they can be processed and the task manager is tying things up handling the growing stack. With zero knowledge of how these work, it seems that instead of issuing an animation call to the video processor and allowing it to process the request, it is bombarding it with (perhaps unnecessary) requests. So even after shutting SL down it took a while to clear the backlog even working at 3,000,000,000 cycles a second. IT IS GETTING VERY DIFFICULT TO WORK IN SL. WHAT CAN I DO?
I kept logs of 3 short sessions. These are all using RC 1.20.11 (90229) Session report 1. Session 2. Session 3. Logged back in after RL visit, Logged into SLVEC vacant lot again. In focus, doing IMs, 47% out of focus 9% I may as well move back to RL, I don't need to come here for aggravation THIS IS A NOTE REFERRING TO THE CPU GRAPH AT THE TOP OF PAGE.
Horizontal time frame is condensed in freeze zones since graph was not updating while frozen. found out that my problem is NOT SL related but hardware related. leaving this comment only for the record
I got the same problem (new PC) and added my environment as well as a pic. Happening in both, WindowsXP and Ubuntu Linux, current SL version and in the RCs (up to 20.11) independent from the graphics settings. Hardware issue? edit: Got to add that I'm NOT crashing. "Just" my client is freezing any time I got a new 100% CPU usage and continues to run o.k. afterwards. Oh dear, oh my! And here I thought it was just those of us using the fruits of Apple with this problem. The entire graphics subsystem will freeze even though there are CPU cycles and it is typically possible to gain access via a network connection. The latest RC has made it a little better, that is, the freezes now all eventually thaw (in the past it would freeze solid and never come back at times). At least the water looks pretty in the summer...
This sucks. I'm paying over US$125 for Second Life but have to log out for 5 minutes for every 5 minutes running. How about a 50% discount on my fees?
I've solved the problem somewhat. I use two computers. Work on one for 5 minutes until it freezes, then lot out and leave it to thaw for 5 minutes while I use the other computer. By oscillating between the two computers I get my on-line time up to about 75%. I can reset the computer and re-log but by the time you wait for XL to load and establish the communication it is simpler to just let it sit idle and thaw out. Unfortunately you can't just log out and log back in to SL because even after exiting SL, the freeze continues for about 5 minutes. PLEASE READ http://www.slfbi.com/LAG.htm
Can no longer use or test RC 1.20.12
It will consistently freeze the computer solid within 1 to 5 minutes. Earlier versions would give you a warning with deteriorating mouse updates but now it just halts and requires a hardware reset to recover. Second Life 1.20.12 (90824) Jun 27 2008 21:30:48 (Second Life Release Candidate) You are at 260273.7, 230371.9, 40.2 in Whanganui located at sim4819.agni.lindenlab.com (63.210.159.215:13000) CPU: Intel Pentium III/Pentium III Xeon (0.25 micron process) with external L2 cache (2982 MHz) I have gone back to 1.19.1. I can usually get an hour or two there and move focus when I see it is about to freeze. 1.19 and 1.20 both appear to have a "normal" CPU activity in the range of 20 to 50% and both unpredictably shoot up to and hover around 99% where a small overload can cause a freeze. IS THIS A CLUE OR A RED-HERRING?
Using RC20 which was failing in 1 to 5 minutes earlier today. CLUE?? The more the lag the lower the CPU overload???? For the last 2+ days, I've not had a freeze on either viewer.
The right CPU is still flatlined at 100% but the left one has been much lower so instead of hovering around 99% with risk of freeze, it is now around 60%. WHY does it change? Nothing is different. Same location, same Avatar, same settings similar activities, My problem is definitely SL related.
After 3 or 4 days of getting work done it was freezing within 5 minutes tonight. Same location, same functions, same conditions. Why I don't know. The freezes this evening were locked up so tight I had to reset the computer each time. Another thought. There are times when SL works fine with anywhere from 20 to 50% CPU Duty cycle. There are frequently times when within a few seconds of starting SL the right CPU flatlines at 100%. Tonight, after starting SL, for the 5th time, I removed focus and just let it sit. I was thinking that it may freeze, not when SL has a problem, but when XP decides to do some trash cleanup. On top of the SL constipation that causes the freeze. So I figured to let it sit for 15 minutes out of focus so XP could remove the constipation without freezing. It seemed like that worked to some extent. The right CPU was no longer flatlined but jiggling up and down at 98% and I was no longer freezing. Is SL slowly accumulating garbage that XP has to collect and XP doesn't get to clear it? It would have to be disk related trash since the problem continues after a hardware reset and RAM usage is always less than 50%. There is no disk activity when it freezes. Wow, ran fine for a month and got some work done. There were still times when I had to wait for it to unfreeze. By having a (non SL) music channel running I could get advance warning of an impending freeze from gaps in the music
But I had some total freezes again today requiring hardware reset. Despite all my attempts at analysis I can find no identifying symptoms for the changing level of occurrence. AN IDENTIFYING FACTOR HAS BEEN FOUND. IT MAY NOT BE THE ONLY ONE BUT IT MAY HELP DIAGNOSIS.
SL has not frozen significantly for a couple of weeks. I changed the level from critical to Normal. I am now able to use SL without having to reset my computer multiple times. I still get freezes (Second Life 1.21.6 (99587) Oct 14 2008 17:42:25 (Second Life Release) but if I just sit around for a few minutes they recover and that saves a reset/disc scan/re-establish all the SL settings.
The later releases have proved more stable. Freezes still occur but typically less than 60 seconds.
I solved the problem that I had on my computer, see symptoms above.
After struggling with it for over a year, checking drivers, applying stress tests, testing every viewer release, extensive testing to find related factors, replacing the video board, cleaning the registry, moving everything to a new disk, new RAM, more than one JIRA here, the only symptom that correlated with the freezes and crashes was ping time. The problem only occurs when running Second Life. My route to SL goes through about 12 hubs. Under the best of times, the lowest ping time is about 85 mSec. It typically runs twice this and as ping times get longer, freezes increase. These correspond with busier internet traffic times. My diagnosis as viewed from someone who has been an assembly language programmer for 50 years (started on UNIVAC III in 1959) is that during long ping turn around times, the SL viewer is not releasing an interrupt until it gets a response of some kind. While the operating system is waiting for SL to release, background jobs start to pile up. When SL finally releases, there is not enough time to clean up the tasks so CPU duty cycle reaches 100% and causes freezes that can last from a fraction of a second to as long as 20 minutes or require a hardware reset. If I can manage to get to Windows Task Manager and shut down SL as freezes are building up, it recovers rapidly once SL shuts down. It is a high level interrupt that is locked, presumably a communication routine. It freezes everything including mouse, sound and even the clock. Although others have experienced this problem it is not prevalent enough to deserve LL time to investigate so I found an elegant solution. I purchased a new computer. No more freezes, no more hardware resets. If LL wants to investigate it further, there is a compatibility problem specific to that hardware with the specifications on the computer listed above. I've demoted that computer to doing accounting, it works fine so long as it doesn't have to run SL. It was all top of the line equipment and actually far better on paper than the computer I bought to replace it. I have a core i7 running at about the same speed as that, what happens to me however, is that the cpu's sl is running on flat line, and then it freezes, it can get it to get moving again by oppening aan application such as media player, which kicks the cpu back....Its like the cpu's are crashing individually
I'm going to try setting the affinity to a single cpu, and remove other traffic from it. That way I can get more recordable behavior, but im crashing at a horrific rate I've tried different CPU affinity but it doesn't seem to make any difference.
What I have found is if you set Priority on the SecondLife.exe process to HIGH it is much more stable. It will still slow down but so far I've not had it crash, even when ping times are showing over 3 seconds. Perhaps there is a way to have it start in High priority but I have to do it manually each time SL is executed. Hi AnnMarie,
Have a look at VWR-5574 and see if turning off the NVIDIA controlpanel-setting "Threaded optimization" makes a difference for you. PROBLEM SOLVED.
Graphics chip was overheating. Problem got worse as the cooling fan deteriorated and finally quit. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
http://secondlife.com/support/?questionID=3886

http://secondlife.com/support/?questionID=4209
http://secondlife.com/support/?questionID=4207