55 replies to this topic

[RuTsui]

• Was any error message provided with the crash, if so, which?
  "Mechwarrior Online has stopped working"
  
• Where in the game or menus did the crash occur?
  Sometimes at the login screen, sometimes in the launcher, sometimes immediately after a match has started.
  
• What steps had been taken prior to the crash occurring?
  Nothing. Nothing has changed since I played last night.
  
• 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?
  Everything is on lowest, I have not changed anything.
  
• What are your System specs?

Samsung 700Z
Intel Core i7 2.20GHz

6GB RAM

AMD Radeon HD 6490M

The game crashes whenever I try to play. Sometimes I crash before I can even log in, sometimes I get logged in, but then I can't launch a game; I get stuck on the home screen and every other tab is greyed out. Twice I've actually been able to make it into a game, but it crashes immediately as the game starts. I was playing last night and everything was working just fine, good as it always did. I haven't changed any settings for the game or computer.

I've also already sent an email to support about the issue.

[Vechlor]

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

Omicron reports:
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

• Where in the game or menus did the crash occur?

Alpine Assault

• What steps had been taken prior to the crash occurring?

Fired a few erppc shots at another cataphract 700m+ away while walking towards the enemy at the eastern base just seconds before both sides were about to engage.

• Does the crash re-occur for you if repeating those same steps?

NA

• What are your video settings, did you change them since last patch?

Same settings since 12vs12 patch. 1920x1200, v-sync off, full window, blur off, high quality, damage glow on.

• What are your System specs?

Spoiler

Operating System: Windows 7 Ultimate 64-bit
Memory: 16384MB RAM
Processor: Intel® Core™ i5-3550 CPU @ 3.30GHz (4 CPUs), ~3.3GHz
DirectX Version: DirectX 11
Card name: AMD Radeon HD 6900 Series
Dedicated Memory: 2027 MB
Current Mode: 1920 x 1200 (32 bit) (60Hz)

[Sharknoms]

• Was any error message provided with the crash, if so, which?
  "Mechwarrior Online has stopped working"
  
• Where in the game or menus did the crash occur?
  First time at the end of a match game frozen. Second time middle of a battle on frozen city night
  
• What steps had been taken prior to the crash occurring?
  Just played the like always
  
• Does the crash re-occur for you if repeating those same steps?
  Cant happens appearently random
  
• What are your video settings, did you change them since last patch?
  Everything maxed like always
  
• System Specs:
  Intel Core i5-3570K
  Ram 8GB
  AMD Radeon HD 7800 Series
  
  Windows 7 64bit

[Shamous13]

I wonder if allot of the crashes has any thing to do with router firewall settings. worth a try for those of you having troubble, its helped a coupple of people. http://mwomercs.com/...44#entry1709544


Posted 07 January 2013 - 07:12 PM
Stickjock, on 31 October 2012 - 03:07 PM, said:

TCP 45461
TCP 45464
UDP 21000 to 30000


These ports are still correct, and they connect over two different IP addresses, 70.42.29.74 and 70.42.29.75. The TCP ports don't include 45462 or 45463, we use only 45461 and 45464. The TCP ports are for backend server communications, things like logging in, interacting with mechbay, chat. The UDP ports are used for realtime match traffic to the dedicated servers when you're in-game.

Edited by Shamous13, 29 August 2013 - 04:03 PM.

[nrg9x]

hey ppls

it all seems to work smooth then when i fire any of my weapons or target an enemy , my screen freezes and i can still hear the game playing even as my screen is stuck , yesterday i waited to see if it would clear up . and it did after 7 minutes , but missed most of the game in the process and its happening usually on first or second game load but after that seems to clear up. not sure if anyone else is gettin this

specs
Windows 7 Pro 64-bit
Intel Core i7-3770 @ 3.40 GHz 3.40 GHz
16.0 GB Ram (2x8GB)
Intel® 7 Series/C216 Chipset Motherboard
NVIDIA GeForce GTX 560 Ti
Sound Blaster 5.1 VX 24Bit

my control set consists of Razer Naga, Razer Nostromo, Logitech G510 and a Mad Catz F.L.Y.5 Flight Stick. All operate as intended ( Disabling n52 device in device manager allows both n52 and Joystick to work in conjunction )

I play also on the highest graphics settings , so far its happened in both full-screen and windowed.

hope this helps
Thanks

[Yagyu]

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

None. Donut of Doom appears, MWOClient stops responding.

• Where in the game or menus did the crash occur?

During matches, never in mechlab. Any map, early or late, high activity or no activity.

• What steps had been taken prior to the crash occurring?

Playing the game, engaging the opposing team; random timing and action (sometimes full melee, sometimes just standing still looking at a rock).

• Does the crash re-occur for you if repeating those same steps?

If by steps you mean "playing the game," then yes.

• What are your video settings, did you change them since last patch?

Same settings since 12vs12 patch. 1920x1200, v-sync off, windowed mode, blur off, high quality, damage glow on.

• What are your System specs?

i5 3570K, 8GB RAM, RadeonHD 7750, Win7 64-bit

• Frustration level

Exceptionally high.

[Navid A1]

- game freezes mid-match after having played 2 or 3 matches with the looping hum of the cockpit.
- CPU usage after freez is 0% while memory usage is around 1.3 GB.
- no error message/log
- my video settings are low
system specs:

Spoiler

- core2duo 2.8ghz/6mb/T9600
- ati hd 4650 1gb (overclocked to 140%)
- 6GB memory

Edited by Navid A1, 30 August 2013 - 08:12 AM.

[Frij]

Keep getting session lost.

[SirDubba]

I give up playing for now. Sometimes I can play couple matches, but today only one out of six games didn't crash to desktop. No warning, no special situations, just random shutdown of the game.
Disabling steam overlay didn't help, updating drivers for Radeon didn't help, didn't try without Avast.

I'm connected through cable 100/10, right now there are lots of people online here. Come to think of it, whenever I get to play more matches without crashing it is during mid-day when internet traffic is quite mild. Have to investigate more.

E:
Nope, saturday morning, there's hardly any traffic on the lines and I'm still crashing. It's fustrating.

Edited by SirDubba, 30 August 2013 - 11:15 PM.

[Peiper]

Niko Snow, on 20 August 2013 - 09:51 AM, said:

Crashed to Desktop? Fatal Error? Frozen? Let us know what happened here!

Please attempt to respond to the following questions in your responses:

• Was any error message provided with the crash, if so, which? Mostly no, it freezes up. Sometimes it self corrects, 2/3 of the time I freeze and eventually get the 'program not responding' pop up.
  
• 
  
• Where in the game or menus did the crash occur? usually mid-match. Sometimes even at load. Sometimes upon death. No consistancy. Sometimes, though, when in groups, I will not be the only one who freezes up at the SAME moment as another. Not sure about my opponents. Not like I can ask them after I freeze. My opponents, at the beginning of the match, have said they've been having the same problems. Ran several 12 man matches tonight, but this issue is not isolated to 12 mans.
  
• 
  
• What steps had been taken prior to the crash occurring? I've run the MWO repair program today, no change. I've changed my user config files a little bit with a config that is supposed to be easier on my system for visability and framerates, but the game behavior didn't change.
  
• 
  
• Does the crash re-occur for you if repeating those same steps? I did not make the same change twice.
  
• 
  
• What are your video settings, did you change them since last patch? I did lower the resolution after getting the freezes. It did not help.
  
• 
  
• What are your System specs? (You can include them in a [spoiler] [ /spoiler]

[spoiler]
System Information
------------------
Time of this report: 9/1/2013, 00:50:58
Machine name:
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.120830-0333)
Language: English (Regional Setting: English)
System Manufacturer: To be filled by O.E.M.
System Model: To be filled by O.E.M.
BIOS: BIOS Date: 10/20/10 09:47:36 Ver: 08.00.10
Processor: AMD FX™-4100 Quad-Core Processor (4 CPUs), ~3.6GHz
Memory: 8192MB RAM
Available OS Memory: 8138MB RAM
Page File: 3016MB used, 13256MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 560 Ti
Manufacturer: NVIDIA
Chip type: GeForce GTX 560 Ti
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_1200&SUBSYS_15683842&REV_A1
Display Memory: 4047 MB
Dedicated Memory: 1999 MB
Shared Memory: 2047 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: HF237
Monitor Id: HSG1AC3
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: HDMI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 9.18.0013.1422 (English)
Driver Version: 9.18.13.1422
DDI Version: 11
Driver Model: WDDM 1.1
[ /spoiler]

Edited by Peiper, 31 August 2013 - 10:07 PM.

[Budor]

My client freezes in the startup sequence when a match starts since the latest patch. ~1/10 games.

[Navid A1]

today, i experienced mid-game freeze (same 1.3gb memory leak) in the testing grounds.
canyon network, killed the 1st,2nd and 3rd mech... and froze upon firing a LL at 4th.

[Floowid]

I have been crashing randomly since I started playing this game. It is not discernibly worse with this patch. Some nights it is as infrequent as once every hour, or as often as every other game until I get frustrated and quit.

The Omicron log always shows [Error] Runaway Thread 5 times in a row before each crash.

It is usually a hard freeze, video lock up, sometimes I can hear the sound going on, most times the sound is frozen too. Very rare I can Alt+Tab out and get it back, most times when I tab back it is a black screen that never comes back. When this happens, I can tab over to the Task Manager and watch the memory go up steadily about 300 Kb per second. Sometimes I get a crash right to desktop, which is actually more handy because I don't have to go through the trouble of opening up task manager and killing the application.

I have a Geforce 550 Ti, Drivers from June 2013. 6 GB of ram, Pentium, dual core E5200.

Oh, and I have a crown coming loose on one of my rear molars.

[Hexenhammer]

Something I am noticing with what ever patch is on the game as of 9-2-13.

When the game freezes I alt-tab-del and open the task menu Sometimes the game starts working again, sometimes it doesn't. When it does I can no longer use tab to bring up the roster.

Te other day during a game I locked up. Immediately a person invent said they locked up. The game unfroze and a person on the other team said they locked up as well. I can only conclude its a server side error.


Deleting the shaders folder seems to help but it doesn't solve the problem. I've had the game freeze with spiders and stalkers

Edited by Hexenhammer, 02 September 2013 - 10:01 PM.

[Navid A1]

Hexenhammer, on 02 September 2013 - 10:00 PM, said:

... I can only conclude its a server side error.

i have experienced freezing both in testing grounds and in online matches... so maybe the error is in the client.

[Stacko]

Had a game tonight where at least 10 people started as "disconnected"... 8 from one team, 2 from another. I took a screenshot but am not sure how to post it. Two additional were listed as "dead" within seconds of starting so I assume they were "disconnected" as well.

It's a terrible state of affairs at the moment regarding the lock-up, CTD and disconnect situation. I hope it gets sorted out soon for the sake of the future of this game.

Thanks for your hard work in resolving this.


Stax