134 replies to this topic

[krolmir]

Before FEB 5 2013 patch 0 ingame crashes or freezes. My average ingame FPS with all Graphics set to High-over 90-100. After Pretty Baby Patch got so bad that I stopped playing, almost every other match froze. Learned about deleting Shader files, brought crashes to 1 in every 10-ish. Crashes seam to happen most often just as I press the fire button, or something explodes. Using LRMs on my own mech brings the crash rate up, even when deleting the shaders file to 1 in every 4, not sure why.

I love new content but this bug is terrible, I won't do any challenges because every freeze is a loss. I have tried all the tricks and work arounds I have found on the forums. 99% of them didn't work, only help I have found is Shaders deletion, but its inconsistant at best.

[Khaze]

As it happens I was compelled to do a complete system wipe, not related to MWO. I was expecting the crashes and freezes to atleast diminish somewhat, but that was folly: I froze in the first match I loaded up. No error message, no nothing. The screen just went black and the application stopped responding.

I was dead at this point and in spectate mode. Doubt it's of any import, as the crashes have had no logic to them thus far. Sometimes I finish a game, sometimes I crash before even seeing the enemy. If there was a log file or an error to post, I would, but as I said the application simply hangs.

You can imagine my desire to play the game at this point isn't very high.

[thisiswhywecanthavenicethings]

Matches crash to mechbay after a minute or two without fail, but only in my RVN-3L. Any other mech (trial mechs) and I can play all day without problems. I don't know if this is an issue with all owned mechs or just that one; the RVN-3L is my only owned mech so far, I haven't been playing long.

Specs:

Spoiler

Windows 7 Pro x64
Asus Sabertooth Z77
i7-3770K
16GB DDR3
MSI GTX 670

[Kergis Tsugan]

since the patch on the 5th I've been getting dropped from games and sent to the mechlab just like I would if I had clicked "Quit Match". I can't find any error message. I've made sure to reinstall the game, update my drivers and I even went so far as to reinstall Windows 7.

[Sugomi]

Kergis Tsugan, on 10 March 2013 - 04:28 AM, said:

since the patch on the 5th I've been getting dropped from games and sent to the mechlab just like I would if I had clicked "Quit Match". I can't find any error message. I've made sure to reinstall the game, update my drivers and I even went so far as to reinstall Windows 7.

start a support ticket. they will ask you for some log files. this will help point the devs to the source of the error.

[Lugh]

Tungsten MD, on 10 March 2013 - 05:24 AM, said:

start a support ticket. they will ask you for some log files. this will help point the devs to the source of the error.

I've been providing them those files for 2 months now. The support people deem it 'solved' and the crashes continue. The developer's haven't made so much as a whimper of what it could be.

[Sunaiac]

CryAnimation: Command Buffer Overflow Happens a lot, I can't play more than one match here and there before it happens.
On fullscreen, i had to logout windows to be able to get control back !
Now on window mode, I see the error.

I'm with maximum graphics except : postprocess off, shadow medium and motion blur off.
FullHE, 120Hz, Vsync off.
7970 catalyst 13.1.

[Johnw007]

Getting crash to desktop on a regular basis.

[doro]

Probably 3 or 4 out of 4 games I get a random crash to the desktop and end up back at pregame client at some point in the match. I don't know that I've completed more than a handfull of games today. This started after the last patch.

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


No

Where in the game or menus did the crash occur?
While playing in a game.

What steps had been taken prior to the crash occurring?
Starting the game.

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?
Max settings at 1920 x 1080. No.

What are your System specs?
i5-3470, 16GB RAM, GTX670

[Levi Porphyrogenitus]

I have pretty well determined that my MWO has a good chance to crash on Alpine. It seems to be pretty much only Alpine, and the timing seems random. Some times it's while just walking, sometimes it's right when combat starts, and some times it's pretty far in to the game.

The picture freezes and I have to ctrl-alt-del and kill MWO with task manager. There is no error message, aside from a Windows message that pops up once I've tried to end the task saying that MWO has stopped working and do I want to kill it or try to find a solution online. This has screwed me over three times now I think in the last hour. It crippled my chances in the Day 3 Kills standings in the Top Gun tournament.

I'm rolling with the following:
Intel Core i7-2700k @ 3.50 GHz
16.0 GB of RAM
64-bit Windows 7
10,000 RPM Velociraptor HDD
Radeon HD 6970 DirectCUII with 2GB of GDDR5 video RAM
I run things at 1680x1050


It scores a 6.2 on the Windows Experience Index if that means anything.

I've almost never had problems with MWO before. I occasionally spawned with no radar, or no IFF, or even no HUD, but I've never had the yellow screen bug or any of those other things. I have had occasional crashes, but not anywhere near as frequently as this.

[DeKamme]

Update:

I managed to stop my game freezes, at least haven't had one in 20 games so far. I've enabled vsync and added the game to my firewall exception list (comodo). A day before that I reinstalled the game - but after the reinstall I still had some freezes.

So, I don't know which of those actions solved/diminished my problem, but I'd like to share this already. Please try one or more of these steps and report if it work. Preferably: Try one thing (say vsync), then play. If it doesn't work, revert that setting and try the next thing (firewall). I'm going to do the same to check what exactly solved it.

[Norris J Packard]

Seriously, any kind input on these CommandBuffer CTD's would be amazing.

Should I reinstall again? What?

Edited by Norris J Packard, 11 March 2013 - 11:37 AM.

[DMHas]

Hello,
since the last Patch the game crashed randomly (it is not independet of the map - in the most cases in the first 3 min of the game. The screen stops, sound is playing, after few seconds the sound stopped and the game crashed back to desktop. It's not in every game, but it happens.

error report link (as zip-file)

Edited by DMHas, 12 March 2013 - 03:34 AM.

[MourningZero]

Eureka, of sorts.

Currently suffering from constant silent crash to mechlab from match. Was instructed to test in the training grounds, and confirmed that I did not suffer from any crashes there. Support believes that the issue is likely network related then, and passed the info up to the developers.

So I've installed a network monitor, and tried a couple of games with the log running.

My silent CTDs are preceded by one of two possible messages from the game server:
"Malformed packet", followed by a response from my PC to the server: "Remote Disconnected: Malformed Packet"
or
"Received an ack for a packet newer than what we've sent (received 1234, at 1233); disconnecting", followed by the response from my PC to the server: "Remote disconnected: Received an ack for a packet newer than what we've sent (received 1234, at 1233); disconnecting"

These error messages sent as packets don't seem to be recorded in the Omicron logs or cause a crash.dmp to be generated.

So, my silent crash to mechlab is most definitely caused by a network problem of some kind. Now, what to do about that? Things tried so far (connecting by ethernet cable to router, switching cables to router, connecting by wireless to router, connecting directly by ethernet cable to cable modem, power-cycling cable modem.)

Edited by MourningZero, 11 March 2013 - 12:25 PM.

[Tizona]

Still getting hangs in Frozen City in thermal with several flights of missiles around. Not as frequent as previous patch, but still several times per session.

i5 3750K + NVidia 560 + 16gb RAM

[Sugomi]

MourningZero, on 11 March 2013 - 12:18 PM, said:

Eureka, of sorts.

Currently suffering from constant silent crash to mechlab from match. Was instructed to test in the training grounds, and confirmed that I did not suffer from any crashes there. Support believes that the issue is likely network related then, and passed the info up to the developers.

So I've installed a network monitor, and tried a couple of games with the log running.

My silent CTDs are preceded by one of two possible messages from the game server:
"Malformed packet", followed by a response from my PC to the server: "Remote Disconnected: Malformed Packet"
or
"Received an ack for a packet newer than what we've sent (received 1234, at 1233); disconnecting", followed by the response from my PC to the server: "Remote disconnected: Received an ack for a packet newer than what we've sent (received 1234, at 1233); disconnecting"

These error messages sent as packets don't seem to be recorded in the Omicron logs or cause a crash.dmp to be generated.

So, my silent crash to mechlab is most definitely caused by a network problem of some kind. Now, what to do about that? Things tried so far (connecting by ethernet cable to router, switching cables to router, connecting by wireless to router, connecting directly by ethernet cable to cable modem, power-cycling cable modem.)

Nice hunting. None of us were experiencing this issue prior, so I wouldn't sweat troubleshooting on your end. Likely an issue with netcode changes.

[Levi Porphyrogenitus]

Update: Just had a game on Forest Colony Snow. It was playing just fine, but then when I was dead and in Spectator mode suddenly the same MWO freeze-up happened as I was experiencing on Alpine Peaks. I had to ctrl-alt-del and kill MWO with task manager. This is the first time I've had it happen while spectating. I can't remember having it happen on Forest Colony Snow, either, but I don't know for sure that it hasn't.

[HarmAssassin]

Since the last patch I have also been having problems with game crashes and crashing to desktop. Doesn't seem to matter what map, or what I'm doing at the time, completely random. Happens about once every 5 games. Prior to this last patch, I rarely ever crashed (once a week at most).

[Aethon]

Aethon, on 05 March 2013 - 03:42 PM, said:

Was any error message provided with the crash, if so, which? No. The game froze, the load on my video cards disappeared, and they cooled off as though I had just closed the client. I had to Ctrl+Alt+Del to close the game.

Where in the game or menus did the crash occur? Crash during gameplay, both times a nearby mech was jumping.

What steps had been taken prior to the crash occurring? Nothing out of the ordinary...firing lasers/SRM's.

Does the crash re-occur for you if repeating those same steps? Sometimes, not always.

What are your video settings, did you change them since last patch? 1920 x 1200, max settings...no change from previous stable patch.

What are your System specs?

Spoiler

Intel Core i7 3820 @ 3.6ghz
16GB quad-channel DDR3, 1600mhz
2 x GTX580 in SLI, drivers = 314.07
Asus Xonar Essence STX sound card

I have another crash type that has never occurred before this patch, but is now occurring at least 2-3 times every night. The above crash has not occurred since the first two times, but the one below is recurring constantly.

Was any error message provided with the crash, if so, which? "FRead did not read expected number of byte from file, only 128 of 0 byes read"

Where in the game or menus did the crash occur? In game, during the pre-match screen.

What steps had been taken prior to the crash occurring? Waiting for the players to join the match.

Does the crash re-occur for you if repeating those same steps? Yes, many times.

What are your video settings, did you change them since last patch? 1920 x 1200, max settings...no change from previous stable patch.

What are your System specs?

Spoiler

Intel Core i7 3820 @ 3.6ghz
16GB quad-channel DDR3, 1600mhz
2 x GTX580 in SLI, drivers = 314.07
Asus Xonar Essence STX sound card

Edited by Aethon, 11 March 2013 - 04:38 PM.

[Krelek1000]

Mine keeps freezing and crashing too. Twice today. I haven't played for a week but patched last night and now these crashes happen while I was playing. Once with Training ground, and now with the City (night)... Memory for the game will hit 900 meg and then it tends to crash... What is recommendation for fixes? Current sys: AMD Phenom (X4) 4G RAM Radeon HD5700