134 replies to this topic

[Jonathan Paine]

MWO screen freezes randomly and frequently. Last 5 rounds , three out of four players on our team suffered similar problems. Really "amusing" when it happens to two of us in the same round.

*sigh*

[Torquemada]

For the first time since I started playing MWO I'm experiencing regular crashes. I've yet to find out why it's happening.

System specs:

AMD FX-6200
16GB DDR3 (all test as good under memtest86+)
1GB Gigabyte 7770
Samsung 256GB SSD
Windows 8 64bit
13.1 drivers for GPU.

[Karenai]

As soon as I see Alpine I can quit, not just because I do not like the map.

The overall performence went down for me, but Alpine just crashes everytime, without fail.
It is the screenfreeze and you cannot close MWO crash.

I do get them once in a while on other maps, but had no Alpine game without crash for a very long time. It occours always when I see many mechs for the first time, aka the most important moment of the game.

Intel core duo 6400@3.6Ghz
GTX260
4GB 800MHz ram

[Chia]

Been crashing with "CryEngine Error: Memory allocation for 44698328 bytes failed" when launching on Alpine Peaks: Assault. Anyone with a solution other than reinstall?

[Elder Thorn]

Niko Snow, on 05 March 2013 - 11:43 AM, said:

All Crash and Stability related posts will be merged into this thread for simplified reference and overview.

Please attempt to respond to the following questions in your responses:
Was any error message provided with the crash, if so, which?
no

Where in the game or menus did the crash occur?
At match start, both during and before startup sequence

What steps had been taken prior to the crash occurring?
i pressed Launch button

Does the crash re-occur for you if repeating those same steps?
not every time

What are your video settings, did you change them since last patch?
Medium, played on medium during last patch without problems

What are your System specs? (You can include them in a [spoiler] [ /spoiler])
[spoiler]OS: Win7 Pro
Memory: 4 GB RAM
CPU: Q6600 @2.40 GHz
GPU: ATI Radeon HD 5700 Series
[ /spoiler]

answers to your questions in the quote.
With the new patch i get way more crahses in form of client freezes. They happen at the beginning of the match, one time during the startup sequence, when betty was about to say something and sometimes during the Prematch screen

Edited by Elder Thorn, 07 March 2013 - 08:07 AM.

[Skyraxx]

Crashed again on alpine peaks. I seem to crash every single time I play this map. Other maps are fine.

[WDShivan]

Similar here. Mainly freezes on alpine peaks since last patch, but also sometimes happens on other maps.

[Flying Judgement]

crashing almost every single time in rivet city i cant play the game its rejects me crashing in other maps to but not as often as rivet city its says something about memory then lots of numbers

60 % of my game is crash one after another then i have a bit of a peace than its starts again restarting dont solve my problem as before

[Sugomi]

I hate you CDevBufferMan!

[chiXnhawk]

How is this CTD still here? I have been having this problem sine Feb 5th patch. I wasted 25 days of premium account. First game after patching and it crashes. What is going on with this problem?

[Lugh]

I was provided a 'holy fix' of an actual textures.pak to explicitly install and set to read only. I went 3 games with 3 crashes after that, making that the worst solution ever.

This is terrible. Game is completely unplayable at this time.

[Dashwood Fox]

I've had this issue 3 times where my small map glitches and is very colourful. I also experience a significant FPS drop when this glitch happens. It's only happened on Frozen City night so far.

http://twitpic.com/c9h1b6/full

Also I can't hear my Ravens' footsteps anymore :/

[Norris J Packard]

CommandBuffer CTD is still around.

Unfortunately it isn't leaving logs for me to post whenever it happens.

[Maxx Blue]

Still crashing pretty much every time a match in Alpine Peaks ends. This is the end of the Omicron.log file after I crash out to the desktop:

[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
WER: Running CryEngine Exception Handler
WER: Creating Crash Dump
WER: Attempting to load DBGHELP.DLL
WER: DBGHELP.DLL Located
WER: Creating Crash Dump File
WER: Crash Dump File Created writing dump data
Saved dump file to 'user\crashdump.dmp'

[Sir Hunter]

Since the patch on Tuesday I have been constantly been crashing through a black screen to the mechbays - what gives?? It's really annoying. My mech stays in game.

[MourningZero]

Reliably silent crashing back to mechlab in every game now, usually within the first 30 seconds. At least that behavior lets me test settings on my side to know if something works to fix it (nothing has so far).

Due to the client working fine in the training grounds, support believes that it is likely a network issue, and possibly due to packet loss judging from my 2% packet loss reported in pingtest.net. I've tried multiple ethernet cables, and a wireless connection to try to pinpoint my packet loss and it's probably at the service provider level as all PCs in the house report the same level of loss. Next step for me will be packing up the PC and heading to a friends house to try it there.

If I had to guess, my connection probably hasn't changed since the mid january/first feb patch when netcode changes started going in. So it's possible that the patches have decreased the server or client tolerance for my particular connection problems - and the game is no longer playable for me because of it. Really a shame, I love what they are doing with MWO otherwise!

Edit: A fun edit, I dropped with the twitch.tv guys this afternoon (including Garth), and promptly CTD'd. Switched over to watch them get beat on the stream and they complained about me disconnecting, what a bunch of jerks!

Edited by MourningZero, 07 March 2013 - 08:13 PM.

[frkuout]

Continual CTD with this patch. Sometimes it's right after pressing the launch button, sometimes it during the match loading sometimes it's midway through the match. The only constant is that it is happening each time I try to play I've posted the Omnicrons and the latest dump file for today's crashes below.

I have not changed my video setting before this patch. I did try changing them after the CTDs but it didn't help. Changes were turning off V-Sync and resetting the 3D settings in the NVIDIA control panel to default. I run 1280x1024 full screen. I'm going to try running full screen windowed to see if it may help.

https://www.dropbox....cron_3-7-13.log

https://www.dropbox....053%2003%29.log

https://www.dropbox....005%2004%29.log


https://www.dropbox....dump_3-7-13.dmp

System Specs:

Core i3 2.93 GHz
4GB DDR 3
EVGA GTX 560Ti w/1GB GDDR5

=edit=

Changed settings to full window at same resolution and reduced to medium settings. Finally completed a match. Hopefully it'll hold.

=edit 2=

Changed to high settings, seems to be ok.

Edited by frkuout, 07 March 2013 - 09:00 PM.

[One Medic Army]

Well, add me to the list.
Crash to mechlab 2/2 games, immediately upon loading into the match.
Did a clean reinstall of MWO, and problem persists.

Is not limited to a single map.

Training grounds work, but crashed to desktop upon exiting them. Also had no minimap in training grounds (river city) , may be unrelated issue.

I can provide specific system specs if needed, general specs:
nVidia 460 GTX card
intel quad-core ivy-bridge CPU
16gigs DDR3 1333 RAM
Windows 7 Professional (SP1) 64bit
Video drivers up to date
Game installed on separate partition from OS.

[edit] No error messages

Edited by One Medic Army, 08 March 2013 - 12:05 PM.

[Ettibber]

Was any error message provided with the crash, if so, which? Cryengine failure fread did not read expcted number of byte from file, only 128 of 0 bytes read
Where in the game or menus did the crash occur? just after loading into game
What steps had been taken prior to the crash occurring? "clicking launch, then loading into game, then crash to desktop"
Does the crash re-occur for you if repeating those same steps? yes
What are your video settings, did you change them since last patch? maxed and unchanged since last patch
What are your System specs?
cpu: Intel® Core™ i5-2500K CPU @ 3.30GHz
ram: 8.1 gb
os: win 7 64bit
video card: amd radeon hd 6900

[Batlin]

Was any error message provided with the crash, if so, which?
No

Where in the game or menus did the crash occur?
In game. Complete lock up. Had to kill with task manager.

What steps had been taken prior to the crash occurring?
Load, select mech, start match. A few minutes in to first match, complete lock up.

Does the crash re-occur for you if repeating those same steps?
\Yes, but intermittently.

What are your video settings, did you change them since last patch?
All max, no motion blur. No changes since last few patches.

Spoiler

Intel i7 3930K at stock Ghz
16 Gb RAM
nvidia GTX 680
WIndows 7

Completely brand new PC build with next to nothing else installed (but the other games run perfectly).
Reinstalled MWO yesterday, and crash occurred on first match.

Edited by Batlin, 07 March 2013 - 11:37 PM.