30 replies to this topic

[Gallowglas]

Since the Tuesday before last, I've been getting occasional game lockups wherein the sound and video freezes and I am forced to open task manager to kill the process. This is new to this patch.

[Reech Strykemoore]

This is regarding Patch Feb 5 2013... should prob move this.


. At first it was only once a day, now I am getting it 3 times in a couple hours.

This is a Freeze Frame, full color shot of whatever is going on at the time. Can not alt tab, but can ctl alt tab to task manager to see that MWO is not responding. So far no work arround has worked.

Edited by Reech Strykemoore, 14 February 2013 - 12:00 PM.

[Gallowglas]

One of two situations typically occur: 1) My screen freezes, but I can alt-tab out of the game and when I go back in, it clears, or 2) I get a total video and audio lockup and I have to close the game from task manager.

[Inveramsay]

I've started getting these as well now, not loads but still enough to be annoying

[Kaillith]

Been getting these freezes since the patch on the 29th, The screen just freezes and i've tried the alt-tab trick but it doesnt work. The game goes to a black screen.

[lsp]

Yes, it's so much fun.

[sycocys]

Have you tried anything outside of alt-tab to work around this? Or done a routine checklist to try to narrow down any causes to help replicate it?

[Kaillith]

sycocys, on 14 February 2013 - 07:09 AM, said:

Have you tried anything outside of alt-tab to work around this? Or done a routine checklist to try to narrow down any causes to help replicate it?

Im not quite sure what you mean by routine, i did a fresh reinstall yesterday and it played fine, then today i've crashed 6 times. I'm not sure what would be causing this issue in the first place.

[Randolph Yuan]

Kojengod, on 14 February 2013 - 08:16 AM, said:

Im not quite sure what you mean by routine, i did a fresh reinstall yesterday and it played fine, then today i've crashed 6 times. I'm not sure what would be causing this issue in the first place.

Do you remember any lrm hitting scense when your screen freezed.

If you check the crash feedback thread, there are dozens of victims, including me... X(

[Kaillith]

Randolph Yuan, on 14 February 2013 - 08:24 AM, said:

Do you remember any lrm hitting scense when your screen freezed.

If you check the crash feedback thread, there are dozens of victims, including me... X(

Actually, yes, the crashes happened when i was hitting with LRMs... >_>
Thouh i only started running the LRM boat today, and the times before today it was crashing almost at random (dont usually run LRMs) and i was running the Flame with ac20 and i'd crash on that too.

[Randolph Yuan]

Kojengod, on 14 February 2013 - 08:28 AM, said:

Actually, yes, the crashes happened when i was hitting with LRMs... >_>
Thouh i only started running the LRM boat today, and the times before today it was crashing almost at random (dont usually run LRMs) and i was running the Flame with ac20 and i'd crash on that too.

When you saw your teammate's LRM hitting, it might also causes the freezing. I have experienced that.

[Kaillith]

Randolph Yuan, on 14 February 2013 - 08:32 AM, said:

When you saw your teammate's LRM hitting, it might also causes the freezing. I have experienced that.

It's possible, i wasnt paying much attention to the rest of my lance. (Tunnel vision yay!)

[sycocys]

Routine checklists when debugging include things like -
What is ALL running at the time of an error, including things you think have zero consequence on your games performance.
What has changed since your last stable running build, including other software, firmware, hardware and o/s updates.
Is you UPS kicking in? Voltage problems.

In-game specifically -
What mech and load are you running?
What situation are you in at the time of crash?
Are you clicking through a menu from a certain menu?

Lists can be greatly expanded upon, but these are some of the basic things you need to log and check when trying to source a bug, with windows any of a number of seemingly minor changes on your system can cause havoc on software performance.

[Randolph Yuan]

Kojengod, on 14 February 2013 - 08:34 AM, said:

It's possible, i wasnt paying much attention to the rest of my lance. (Tunnel vision yay!)

Now I just play laser boat and with my central torso downwards for leg shooting...

sycocys, on 14 February 2013 - 08:37 AM, said:

Routine checklists when debugging include things like -
What is ALL running at the time of an error, including things you think have zero consequence on your games performance.
What has changed since your last stable running build, including other software, firmware, hardware and o/s updates.
Is you UPS kicking in? Voltage problems.

In-game specifically -
What mech and load are you running?
What situation are you in at the time of crash?
Are you clicking through a menu from a certain menu?

Lists can be greatly expanded upon, but these are some of the basic things you need to log and check when trying to source a bug, with windows any of a number of seemingly minor changes on your system can cause havoc on software performance.

The only change was the damn feb 5th patch, which brought the endless screen freezing.

[StalaggtIKE]

I haven't changed anything. Yet, I did not have any freezes last night, how strange. Perhaps the issue was server side?

[Kaillith]

So, apparently turning off Particles helps. I've played 10 matches and havent crashed yet...

Match 15... crashed.. never mind

Edited by Kojengod, 14 February 2013 - 09:32 AM.

[Gallowglas]

On at least one occasion, a lockup occurred at the beginning of a match when no one was firing any weapons. I was simply throttling up. In fact, I do not think the problem has occurred when I was personally in combat. That could be coincidence though. I don't really think there's any evidence that would point at a specific contributing in-game factor.

It doesn't happen all the time, mind you. Perhaps 2-3 times a night. It happened to a fellow Swiftslayer last night and the alt-tab trick worked.

Edited by Gallowglas, 14 February 2013 - 09:45 AM.

[sycocys]

Randolph Yuan, on 14 February 2013 - 08:39 AM, said:

The only change was the damn feb 5th patch, which brought the endless screen freezing.

So you are certain nothing like java, adobe, windows, antivirus, firewall, ts/VoIP, browser, anything did not update anytime since the last patch? Any of a number of things can cause weird errors/glitches in windows memory/priority system.

I don't know your system or how you maintain it so these are things that should be logged when you are testing out software so you can eliminate some of the factors that can make minor tweaks to your system. Especially when you are testing out actual beta products you need to be aware of more of the surrounding environment than just client changes. There very well might be something on their end, but there is also the same probability that a portion of people that have a particular update make a change to their system can be the root cause of the bug issue.

[Randolph Yuan]

Kojengod, on 14 February 2013 - 07:00 AM, said:

Been getting these freezes since the patch on the 29th, The screen just freezes and i've tried the alt-tab trick but it doesnt work. The game goes to a black screen.

Try this. it worked for me.

http://mwomercs.com/...k/page__st__280

[color=#959595]Right guys, since it's all highend systems mostly running medium settings getting the "freeze" lockup it might have something to do with a very high framerate.[/color]

[color=#959595]I limited my fps to 45 by using a user.cfg entry. (if you dont have a user.cfg file you can create one with notepad, place it in the mwo dir)[/color]

[color=#959595]sys_MaxFPS = 45[/color]

[color=#959595]I've played quite a few games without freezing now, it doesn't prove anything yet, but so far so good. turning on vsync with a 60hz monitor might do the trick too. You guys running with or without?[/color]

[DevilReaper666]

I'm having the same issues since the patch. Played three games tonight and was only able to make it through one without a freeze-up or having the program quit to the desktop