Crashing has gotten more and more often
PersianImm0rtal
Join Date: 2010-12-02 Member: 75414Members, Constellation, NS2 Map Tester
Join Date: 2010-12-02 Member: 75414Members, Constellation, NS2 Map Tester
<div class="IPBDescription">Now I crash as soon as I join a team!</div>I have not been able to play more than five minutes for the past probably 8 or so patches atleast. I used to be able to play full games most of the time. Now I crash every single time I choose a team, it does not matter if I am Marines or Aliens, I will be in the ready room running around fine, and then I will pick a team spawn in, and walk around for around 10 seconds very smoothly and then it will just crash. Anyone else having problem like this? It always does this on Tram, I have not tried rockdown yet but I normally run fine on rockdown.
System Specs:
CPU:Intel Core i7 920 @ overclocked 2.8 GHZ
RAM:6GB Corsair Triple Channel DDR3
Motherboard: MSI x58 Platinum SLI
GFX Card: EVGA 9800 GTX+ Superclocked 512mb SLI
HDD: 500GB
OS: Windows 7 Professional, 64-bit.
PS: In case it matters I was trying to play on the #156 Tram Server with 10 people in it, the server is one of the most popular USA servers and is pretty stable, I have tried Luximonster server while it was empty and I can run around in that server just fine. I tried playing at least 6 times and I would get in kill a guy or move around like normal smooth gameplay and then it would just crash
System Specs:
CPU:Intel Core i7 920 @ overclocked 2.8 GHZ
RAM:6GB Corsair Triple Channel DDR3
Motherboard: MSI x58 Platinum SLI
GFX Card: EVGA 9800 GTX+ Superclocked 512mb SLI
HDD: 500GB
OS: Windows 7 Professional, 64-bit.
PS: In case it matters I was trying to play on the #156 Tram Server with 10 people in it, the server is one of the most popular USA servers and is pretty stable, I have tried Luximonster server while it was empty and I can run around in that server just fine. I tried playing at least 6 times and I would get in kill a guy or move around like normal smooth gameplay and then it would just crash
Comments
I do believe the 156 server and supernova are running the same hardware/OS (Q6600/XP) configurations so i don't think it's server side,also I only have been running tram on the supernova server for the last 4 patches.
I would say the first thing to do is verify the game cache then take a look at your drivers (changes) followed by possible hardware changes you have made recently. I ran the game fine a few time then started crashing and steam found "vstdlib_s.dll" and 3 other dll files failed and had to be re-downloaded. I have no idea what caused the corruption as i am not running any custom content on my local machine other than maps.
i'm crashing 1 time by hour, it's very frustrating. In the log file i don't see the reason :
SoundEventInstance::SetProperty(ambient/cold hallways_synth_2, 19 = 524288): setValue(): An invalid object handle was used.
SoundEventInstance::SetProperty(ambient/cold hallways_synth_2, 16 = 16): setValue(): An invalid object handle was used.
SoundEventInstance::SetProperty(ambient/cold hallways_synth_2, 16 = 2097152): setValue(): An invalid object handle was used.
SoundEventInstance::SetProperty(ambient/cold hallways_synth_2, 17 = 6.5024): setValue(): An invalid object handle was used.
SoundEventInstance::SetProperty(ambient/cold hallways_synth_2, 18 = 17.0688): setValue(): An invalid object handle was used.
SoundEventInstance::SetProperty(ambient/cold hallways_synth_2, 1 = 0.4): setValue(): An invalid object handle was used.
SoundEventInstance::SetProperty(ambient/cold hallways_synth_2, 4 = 0): setValue(): An invalid object handle was used.
Yes i was on tram too
I would say the first thing to do is verify the game cache then take a look at your drivers (changes) followed by possible hardware changes you have made recently. I ran the game fine a few time then started crashing and steam found "vstdlib_s.dll" and 3 other dll files failed and had to be re-downloaded. I have no idea what caused the corruption as i am not running any custom content on my local machine other than maps.<!--QuoteEnd--></div><!--QuoteEEnd-->
The Team#156 West Server is running a Intel i5 with 8 GB of ram on a Sandy Bridge chipset motherboard (thankfully I have already did the RMA to get the updated version:-))
Software is Server 2008 Enterprise. I have the same problems as Persian. It crashes 1-2 minutes in every time. I get mass artifacting on structures and then it just freezes. CTRL-ALT-DEL is the only way out and I get the report log.
I have submitted all to UWE via PM. I have also submitted all the server logs from Team #156 West Coast as well.
NS2 and Overmind are the only things loaded on this unit.
Below are the specs of my gaming machine:
HAF 932 : Antec TPQ 1200 PS : i7-860 @ 3.8GHz
Corsair H50 : EVGA P55 Classified :2x EVGA 480SC SLI
8GB Corsair Dom 1600 : WD Raptor 300GB: 2x : Storage -WD 1TB
Windows 7 Pro - 64 Bit
I would say the first thing to do is verify the game cache then take a look at your drivers (changes) followed by possible hardware changes you have made recently. I ran the game fine a few time then started crashing and steam found "vstdlib_s.dll" and 3 other dll files failed and had to be re-downloaded. I have no idea what caused the corruption as i am not running any custom content on my local machine other than maps.<!--QuoteEnd--></div><!--QuoteEEnd-->
actually, i think it may have been Luximonster that was running fine for me. i can't remember which server it was but it was rockdown and i was able to complete a match. i played on supernova and 156 yesterday. both were on tram and both froze without exception. i'm not sure what the problem is, but i've verified ns2 files and even reinstalled the game. to know that others are having the same problem is slightly comforting, because maybe it is an actual problem with the game and not our computers. i think my drivers are all new, which could also be a problem. i'll keep waiting though. i have no reason to be mad at uwe.
Couple of times when I buy a gun from the armory, once when I shot a skulk, generally it seems to be whenever I do something that might need to load a new asset.
NS2 is currently very CPU bound, and so could be pushing your CPU higher than most games.
Try taking off your over-clocks. See if that helps. Updating your GFX card drivers wouldn't go amiss either.
NS2 is currently very CPU bound, and so could be pushing your CPU higher than most games.
Try taking off your over-clocks. See if that helps. Updating your GFX card drivers wouldn't go amiss either.<!--QuoteEnd--></div><!--QuoteEEnd-->
That's a good point as I crash fairly regularly, but I have OC'd my CPU. However, this is, at best, a temp fix because NS2 should be able to run on OC'd systems that are stable in every other game/program I use. Personally, I'd rather leave my CPU OC'd and see if I can track down the crashes than un-OC it so that I have stable gameplay.
corei7 860
gtx460 sc (so i guess it is overclocked, but that's manufacture oc)
8 gigs of ddr3 corsair ram
If your CPU cannot withstand the stress of NS2 (or generally speaking, a heavy-duty application), then it cannot be considered stable. A minimum of 4-6 hours Prime95 (any mode will do really) constitutes a stable CPU. You cannot hold NS2 responsible for exposing malfunctioning hardware.
<!--QuoteBegin-'ScardyBob'+--><div class='quotetop'>QUOTE ('ScardyBob')</div><div class='quotemain'><!--QuoteEBegin-->Personally, I'd rather leave my CPU OC'd and see if I can track down the crashes than un-OC it so that I have stable gameplay.<!--QuoteEnd--></div><!--QuoteEEnd-->
If it is your OC that is causing the crashes, then the cause (in a technical sense) can be found nor solved, as we're talking about random errors occuring anywhere in the CPU.
<!--QuoteBegin-'Thaldarin'+--><div class='quotetop'>QUOTE ('Thaldarin')</div><div class='quotemain'><!--QuoteEBegin-->99% of overclocked hardware on a personal computer isn't needed. It does confuse me why so many people overclock their hardware, just because they can.<!--QuoteEnd--></div><!--QuoteEEnd-->
I can get an additional 1-2 years out of my hardware that way, for free, without any real downsides. That's not a bad deal.
Turning off an overclock is easy, and you can put it right back. Try it. See if it helps. Also, if ANYTHING crashes your overclocked CPU, BUT it's fine with <b>normally clocked</b>, it means you've done your overclock wrong. Either it's getting too hot, not enough voltage or whatever.
weeschwee, try running prime95, memtest+ and get the dust out of your PC. Just in case your temps are too high.
If it is your OC that is causing the crashes, then the cause (in a technical sense) can be found nor solved, as we're talking about random errors occuring anywhere in the CPU.<!--QuoteEnd--></div><!--QuoteEEnd-->
<!--quoteo(post=1843254:date=Apr 29 2011, 06:26 PM:name=Obraxis)--><div class='quotetop'>QUOTE (Obraxis @ Apr 29 2011, 06:26 PM) <a href="index.php?act=findpost&pid=1843254"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->Turning off an overclock is easy, and you can put it right back. Try it. See if it helps. Also, if ANYTHING crashes your overclocked CPU, BUT it's fine with <b>normally clocked</b>, it means you've done your overclock wrong. Either it's getting too hot, not enough voltage or whatever.
weeschwee, try running prime95, memtest+ and get the dust out of your PC. Just in case your temps are too high.<!--QuoteEnd--></div><!--QuoteEEnd-->
Fair points. I'm only speculating that my OC may be causing crashes, though, I should actually test that to make sure. However, I'm less inclined to believe the vast majority of NS2 players with OC'd CPUs did their OC's wrong than that there are crashes unrelated to the OC'd systems.
Also, I did run Prime95 (it was stable), but that was on my original MB/OC. I had to replace my MB because I was part of the sandy bridge recall and didn't do as thorough a test when I rebuilt my system.
weeschwee, try running prime95, memtest+ and get the dust out of your PC. Just in case your temps are too high.<!--QuoteEnd--></div><!--QuoteEEnd-->
might have to do that. my computer might need a little dusting too as it has been a couple months. however, i highly doubt this is the problem since i can play bfbc2 for hours without crashes. bfbc2 is pretty cpu heavy too as i understand.
by the way, can any dev acknowledge they see our bug reports? if not i wont bother sending them anymore. or if you guys receive too many i can stop sending them. :)
I'm crashing at least once a game as commander, and it happens when I select a MAC by clicking on it. Sometimes when I drag over it, but almost ALWAYS when I'm selecting/deselecting things, namely MACs.
Hope it helps!
As for the OC theory, I doubt highly that is the issue. I was working fine on both maps until build 170. Then getting artifacts and crashing right and left after that build was released.
My temps are well within range and graphics cards are also running in decent temp range.
Yes they do, but it's not always in context with what's going on, so posting on the forums/GetSatisfaction with a description of what went on & a copy of the logs will also help.
SO it has to do something with that specific map.
SO it has to do something with that specific map.<!--QuoteEnd--></div><!--QuoteEEnd-->
I have the same problem. Tram has a bug in it for me as well. Rockdown, no issues. And turned off all overclocks and still had same results.
Glad to hear I am not alone on this one. I never would have thought that different maps would have made me crash but for some reason it is doing that, especially since a lot of people seem to not be crashing. There must be something different about us.
That's not true at all. Overclocking, when done right, can be a huge boost to your applications, whether it be FPS in games, a decrease in rendering times, or decrease in media encoding, etc.
However, I would strongly recommend that those overclocked do try to play it stock, because I know that a lot who do try to overclock, don't do it properly, or don't test their stability properly. Even if other programs seem to run fine, it doesn't mean NS2 should run on your OC. It means you need to check your OC for better stability before ruling out your overclock as the culprit.
There's a multitude of programs out there that will stress your system, such as Prime95 or Linpack, and usually 12 hours of testing, error free, is a bare minimum.