Jump to content

Poll About The Game Freezing/crashing.


17 replies to this topic

Poll: Game freeze/crash and used display mode. (55 member(s) have cast votes)

In what mode do you run MWO?

  1. Fullscreen. (48 votes [78.69%])

    Percentage of vote: 78.69%

  2. Windowed. (8 votes [13.11%])

    Percentage of vote: 13.11%

  3. Full window. (5 votes [8.20%])

    Percentage of vote: 8.20%

Vote Guests cannot vote

#1 F lan Ker

    Member

  • PipPipPipPipPipPipPip
  • 827 posts
  • LocationArctic Circle

Posted 23 February 2013 - 02:17 PM

S!

Decided to make a poll about the game freeze/crash a lot of players have experienced after the two latest patches on 5th and 19th of February. In which mode do you run the game and are you experiencing freezes/crashes in game?

I run fullscreen and get the freeze with looping sound randomly, but quite often after these 2 patches. I have tried the VSync, re-install and whatnot without any effect.

Edited by F lan Ker, 23 February 2013 - 02:19 PM.


#2 Glucose

    Member

  • PipPipPipPipPipPip
  • Elite Founder
  • Elite Founder
  • 286 posts

Posted 23 February 2013 - 06:11 PM

I've had this bug twice tonight. What's odd is that my game eventually responds. However, it appears to go into some sort of windowed mode when it comes back -- as my mouse cursor is visible in the game. This has *something* to do with the windowing mode.

#3 Glucose

    Member

  • PipPipPipPipPipPip
  • Elite Founder
  • Elite Founder
  • 286 posts

Posted 23 February 2013 - 07:55 PM

Update: I have had it happen in Windowed mode as well.. Doesn't seen to matter. It also just took down the Windows7 "Desktop Manager' on the last freeze. It seems to happen more and more frequently as time goes on (video memory leak?)

#4 F lan Ker

    Member

  • PipPipPipPipPipPipPip
  • 827 posts
  • LocationArctic Circle

Posted 24 February 2013 - 03:59 AM

S!

On 2nd game today game froze at beginning of game, map was River City. First map working normally was Caustic Valley.

#5 Lugh

    Member

  • PipPipPipPipPipPipPipPipPip
  • The Widow Maker
  • The Widow Maker
  • 3,910 posts

Posted 24 February 2013 - 11:08 AM

I have done them all. Today after 2 full windows and driver reinstalls, 6+reinstalls of the game client and countless graphics card driver revisions, I am setting a new crash record.

12 in a row

It's almost always after a Runaway thread int he game followed with DXinput shutdown

When it isn't that it some random occurance in the game engine sending this command:
CGameClientChannel::Release
-in the middle of combat, just walking around etc.

The code in the engine is getting more and more sloppy.

CGameClientChannel::Release


The big reveal
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/laser_beam_1x4_lop0.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/laser_beam_1x4_lop0.dds]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/ppc_beam_b.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/ppc_beam_b.dds]
======== mechlab is loaded in 3.9 sec ========
[Error] Runaway thread
[Error] Runaway thread
[Error] Runaway thread
[Error] Runaway thread
[Error] Runaway thread
could not free all buffers from CDevBufferMan!
UnLoadLevel End: 0.0 sec
Ammo Pool Statistics:
[Error] Runaway thread
[Error] Runaway thread
System Shutdown
[Error] Runaway thread
DXInput Shutdown
Closing PAK file: game\animations.pak
Closing PAK file: game\bumpers.pak
Closing PAK file: game\gamedata.pak
Closing PAK file: game\objects.pak
Closing PAK file: game\scripts.pak
Closing PAK file: game\shadercache.pak
Closing PAK file: game\shadercachestartup.pak
Closing PAK file: game\shadersbin.pak
Closing PAK file: game\sounds.pak
Closing PAK file: game\textures.pak
Closing PAK file: engine\engine.pak
Closing PAK file: engine\shaders.pak
Closing PAK file: game\localized\english.pak
Closing PAK file: game\causticvalley_ig.pak
Closing PAK file: game\desert_ig.pak
Closing PAK file: game\forestcolony_ig.pak
Closing PAK file: game\frozencity_ig.pak
Closing PAK file: game\industrial_ig.pak
Closing PAK file: game\rivercity_ig.pak
Closing PAK file: game\skyboxes_ig.pak

Yesterday I even had an error that was 'Caustic Valley' Not authorized to run in mode 'conquest'

Edited by Lugh, 24 February 2013 - 11:08 AM.


#6 F lan Ker

    Member

  • PipPipPipPipPipPipPip
  • 827 posts
  • LocationArctic Circle

Posted 25 February 2013 - 06:35 AM

S!

Giving a bump. Testing now in Full window for results. LAst night a few matches without a crash but reduced performance.

#7 tehgraarg

    Rookie

  • 9 posts

Posted 25 February 2013 - 07:37 AM

Ever since yesterday afternoon, I will crash to mech lab in 100% of the matches I join. The crash happens anywhere from the beginning of the match up to 8 minutes. I've started experiencing this problem 2 major patches ago but never this badly. I have the same runaway thread errors in the logs. I have a feeling it has something to do with Networking. I tried so many things to ifx it including updating my realtek drivers to the latest version. I've reinstalled 4 times and installed an older nVdia driver.

Doing a tracert to the servers doesn't reveal any real issues with the hops and packet loss. Usually I run at a 38 poing so something must be happening to desync the client and makes it exit.

Log file

Spoiler

Edited by tehgraarg, 25 February 2013 - 07:41 AM.


#8 BongoBong

    Member

  • PipPip
  • 20 posts
  • LocationCanada

Posted 25 February 2013 - 09:53 AM

I will freeze in the middle of a match and like 10 seconds later the game just completely crashes, no error or anything. Running on fullscreen. Never had it happen before, but has happened in like 2 out of 4 games today.

#9 Snib

    Member

  • PipPipPipPipPipPipPip
  • 689 posts

Posted 25 February 2013 - 10:00 AM

Playing full window, getting mid game freezes often since the last patch (and sometimes after the patch or two before that). It never recovers.

Also if I'm alt-tabbed out while the client tries to change resolution from the full window res during the battle to the smaller client window resolution it will 100% freeze.

#10 That Dawg

    Member

  • PipPipPipPipPipPipPipPip
  • FP Veteran - Beta 1
  • 1,876 posts

Posted 25 February 2013 - 10:03 AM

Memory leak.
Last freeze, task manager said mech was using 90% of all available memory.
No wonder it locked down tighter than (insert witticism here)
I'm getting game lock ups on exit as well. fairly often

#11 sycocys

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Moderate Giver
  • Moderate Giver
  • 7,697 posts

Posted 25 February 2013 - 10:58 AM

I have only experienced this once or twice, and just towards the end of the stress test this weekend. Seemed more to me to be something server-side holding up everything in my case.

#12 Tom Sawyer

    Member

  • PipPipPipPipPipPipPipPip
  • The Widow Maker
  • The Widow Maker
  • 1,384 posts
  • LocationOn your 6

Posted 25 February 2013 - 12:22 PM

I thought it might have been linked to mass LRM launches as I seemed to get the hard freeze requiring task manager when spamming missle launches.

Then I noticed the lock outs where just all over the place. If it is a memory leak then why when i relaunch the game after using task manager to get out of the not responding error does the crash occur in the very next game? Seems odd/

#13 MourningZero

    Member

  • PipPipPip
  • Ace Of Spades
  • 80 posts

Posted 25 February 2013 - 12:35 PM

Also experiencing the silent and immediate crash back to mech-lab frequently since about Friday of last week.

Did the full reinstall with data cache folder delete on Saturday night, and again on Sunday. Neither has had an impact on the frequency of this crash. I've now started dialing back the graphics options after each crash, hoping to find one key component that is causing the problem. VSync now enabled, AA & motion blur off, now the sliders are just moving their way down to medium/low settings.

Edit: just crashed out of a game 20 seconds after match startup on lowest settings possible, so that witch hunt can now end.

Spoiler

Edited by MourningZero, 25 February 2013 - 12:40 PM.


#14 Asmosis

    Member

  • PipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • 2,118 posts

Posted 25 February 2013 - 04:30 PM

only bug i've experienced since 5th patch (inc 19th) was one match i lost my mini-map/battlegrid. other than that its been smooth sailing.

#15 MourningZero

    Member

  • PipPipPip
  • Ace Of Spades
  • 80 posts

Posted 25 February 2013 - 06:00 PM

Four identical crashes in a row. Tried reverting all ATI card settings to be overridden by the application, then tried exiting teamspeak (grasping at straws here)

Spoiler


#16 skullman86

    Member

  • PipPipPipPipPipPipPip
  • 703 posts
  • LocationTexas

Posted 25 February 2013 - 07:05 PM

I get lock ups every once in a while (would probably get more if crashes to mechlab weren't such a common occurrence). Sometimes I can get the game to recover by doing a quick alt+tab when it locks, but most of the time I end up having to close it through taskmanager.

#17 Glucose

    Member

  • PipPipPipPipPipPip
  • Elite Founder
  • Elite Founder
  • 286 posts

Posted 25 February 2013 - 08:49 PM

Lower resolution seemed to help a little.. But still got a freeze while spectating. 13.2 beta catalyst drivers didn't help. Something funky is just happening with the latest two patches. It's definitely blocking on some resource.

#18 Badconduct

    Dezgra

  • PipPipPipPipPipPip
  • Knight Errant
  • 364 posts

Posted 26 February 2013 - 07:00 AM

Hardware would be a better indicator of the problem, not whether it's window'd or not.

What brand graphic card and CPU combo is a better question intel nvdia, intel ati, amd nvidia, amd ati.

Edited by Badconduct, 26 February 2013 - 07:01 AM.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users