City of Heroes crashing very frequently.
I came back after a long absence after I14, and I've been experiencing random Freeze ups. I updated my drivers, and keep my top cool, and it still happens. Sometimes in the first couple minutes. Sometimes after a long while. I'd like to know what it is, and how to stop it.
Specs
Edit, properly updated graphics driver
Edit 2: after updating graphics, having problem with mouse being invisible until i move it.
---System information gathered by CoH Helper version 0.1.1.7---
DxDiag gathered at May 7, 2009 01:31 (-07:00)
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.090206-1234)
System Manufacturer: TOSHIBA
System Model: Satellite A105
BIOS: BIOS Version 1.90
Central Processor: Genuine Intel(R) CPU T2250 @ 1.73GHz (2 CPUs)
Memory: 2038MB
.Net Memory Report: 1196MB out of 2037MB available
Page File: 3190MB (743MB currently in use)
C Drive: (TOSHIBA MK1234GSX) 36359MB out of 60000MB (60%) free
D Drive: (MATSHITA DVD-RAM UJ-841S) zero-size drive
E Drive: (TOF 5AZ8TE7K SCSI CdRom Device) zero-size drive
Windows directory location: C:\WINDOWS
DirectX: DirectX 9.0c (4.09.0000.0904)
DirectX Diag version: 5.03.2600.5512 (32-bit version)
Display Notes: No problems found.
Sound Notes: No problems found.
Input Notes: No problems found.
Monitor: Generic Television
Monitor's Max Resolution: 640,480
Video Device Name: Mobile Intel(R) 945 Express Chipset Family
Manufacturer / Chip: Intel Corporation / Intel(R) GMA 950
Video Memory: 128.0 MB
Driver Version: 6.14.0010.4926
Driver Date: 2/15/2008 1:12:06 PM
Driver Language: English
Sound Device Description: Realtek HD Audio output
Driver File: RtkHDAud.sys
Driver Version: 5.10.0000.5253
Driver Date: 5/5/2006 8:13:52 AM
WMI Information
Motherboard Manufacturer: Intel Corporation
Motherboard Model: (empty)
Motherboard Product: MPAD-MSAE Customer Reference Boards
Motherboard Version: Not Applicable
BIOS Manufacturer: Phoenix Technologies LTD
BIOS Name: BIOS Version 1.90
BIOS Version: TOSINV - 6040000
BIOS Release: 20060705000000.000000+000
Registry Information for Current User
Resolution: 1280x800
3D Resolution: 1280x800 (Not using renderscale)
Full Screen: Yes
Maximized: No
Screen Position: 0, 0
Refresh Rate: 60Hz
Vertical Sync Enabled: Yes
Physics Quality: Medium
Maximum Particles: 50000
Max Particle Fill? 10.000
Physics Card Enabled: No
Anti-aliasing: None
Anisotropic Filtering: None
Texture LOD Bias: Crisp
Water Effects: None
Bloom: 1.000 (turned off)
Depth of Field Enabled: No
Desaturation Effects (Sepia) Enabled: No
Shader Detail: Low (with world bumpmaps)
World Texture Level: Very High
Character Texture Level: Very High
World Detail Level (Vis_Scale): 1.000
Entity Detail Level: 1.000
Shadows Enabled: Yes
Gamma Correction: 1.000
Geometry Buffers (VBOs) Enabled: Yes
Suppression of Extra Player FX Enabled: No
Suppression of FX When Camera Close Enabled: No
Close Suppression Range: 3.000
Show Advertisements: Yes
Audio Mode: Performance
3D Audio: No
FX Sound Volume: 1.000
Music Sound Volume: 0.600
Show Advanced Graphics Options: No
Overall Graphics Quality: 0.600
Reverse Mouse Buttons: No
Save Login Username: Yes
Transfer Rate: 465800 bytes/second
Current Game Version: 18.20090422.2T
Installation Directory: C:\Program Files\City of Heroes
Mod files in the Data directory
No modifications found
Something I noticed.
In all the CoH Helper posts above almost everybody has Realtek HD audio. The one exception is Ravendas.
And the audio drivers for everybody are at least a couple years old. The one exception to that being Scaywee whose audio drivers look to be corrupted since they are showing a date of 01/01/0001.
You might want to do some searching around and see if you can find a more recent driver version. Audio drivers have caused CoH crashes in the past.
Don't count your weasels before they pop dink!
I just edited my post. I installed SP2 just now, and have the new updated info in my post. I still get the same Nvidia Error 14 crashes as before. First one was after 10 minutes of playing, 2nd time I got about an hour in before it crashed, both times same error.
Edit: Nvidia released new drivers yesterday, gonna try those out...
Just wanted to chime in and report that I've experienced no crashes since the last patch (18.20090422.5T). Thus, I feel my suspicions were correct in assuming the issue was not client related.
ditto. but these aren't the bugs you're looking for. you aren't having any problems. you'll keep paying your monthly fee. *does dev mind tricks*
Debt is temporary, prestige is forever
My Screenies and Videos :: My Toon List
With all the anger about farms. this bug is important to fix
I am desperatly trying to do ae stoy arcs. But like in everyday missions people come and go. the biggest and most violent crashes occur when you add a team member.
If the story arc is more than 1 map its trouble!
Guys if you can't finish a story because half or more of your team drops when you add a member. there's nothing left but farms.
Ya I know you can do missions etc etc. doesn't stop 90% or more of the people that won't. In the hopes they will get on a farm. its is absolutely faster exp than regular missions.
PLEASE fix this!!
Cappy
The Bug crashes have nothing to do with system make up. Those who crashed regularly before know who they are. I certainly have no objection to trying to help them. However, the adding and subtracting of players to a team has been a problem for AE since its beggining. players going to different maps, team crashes when adding a player and so on. this game like others does have minimum system requirements but... these are crashes revolving strictly around the mission architech patch. hundreds or thousands of players who never had any real problems before are now having problems with MA stories.
I don't have any crash issues to any regular missions or tf's.
If it is preformance related (since the MA patch)then the game has evolved beyond reasonable expectations.
Especially since my computer is within the published minimum game requirements. ( actually more )
Folks this is a programming issue.
[ QUOTE ]
Very frequent crashes since Issue 14.
Nothing was changed on my computer.
The majority of these crashes are a frozen "loading" screen, in which the loading bar fills about 1 inch and stays there indefinitely.
[/ QUOTE ]
I have that with one machine, but it's a laptop so I chalked it up to that.
[ QUOTE ]
The majority of these crashes are a frozen "loading" screen, in which the loading bar fills about 1 inch and stays there indefinitely.
[/ QUOTE ]
I have seen enough crashes lately to know that what your fellow team mates see is that you simply disappear the moment (from your prospective) you go into the frozen screen.
I don't know how many times I've seen 2-5 people just go Poof gone the moment they clicked to enter the M.A. mission.
And when it happens like that, it always after adding a new player to the team. In between missions. Now if you add a player during the mission there's about a 75% chance that they can't get on the same map as you.
Or if you just have a player that enters after you've begun to do battle. Again, good chance they will be on a different map.
I think what's happened is that the dev's have taken Task force "code" parameters and merged it with Mission "code" parameters and there are some kind of "if/then" code statements that conflict. In other words they left some crumbs laying around and they are going to have to go find and delete or change them.
Considering that there are thousands of lines of code I'm betting that there are probably quite a few of these "crumbs" laying around they're going to have to clean up.
I hope it becomes more like missions instead of task force's because anytime someone takes the time to really make a decent story its going to take 1-3 hours to complete.
With that said, when your doing just regular missions you have recruit new players almost every time at the end of each mission.
It's worse now because people are so worried about getting "fast Exp" that the "polite players" can't barely wait for the mission to be over so they can go try to get on a farm team.
A lot of these kind of players will quit after 2 or 3 mobs.
when I'm the team leader I make a big deal about what we are doing before we start and more often get through 2 missions before someone drops. But when they do leave the team that's when the trouble starts. Its doesn't matter whether they quit or just log off it's going to be computer crash time if you add new team mates on these M.A. Missions.
People are complaining in game alll the time about it.
Farms on the other hand are only one mission long. so someone drops they finish the map then it gets reset. no problems. Some farms have a single glowie for mission complete in case there are to many people leaving or if there is some kind of problem. Just ckick on the glowie and its reset.
well that's all i guess I'm really frustrated that that we can't enjoy making and doing new interesting stories.
^^^
Try This thread