51 replies to this topic

[Kyle Polulak]

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?
  
• Where in the game or menus did the crash occur?
  
• What steps had been taken prior to the crash occurring?
  
• Does the crash re-occur for you if repeating those same steps?
  
• What are your video settings, did you change them since last patch?
  
• What are your System specs? (You can include them in a [spoiler] [ /spoiler]

In some cases we've seen that deleting the shaders folder and relaunching the game will solve these crashes and related issues.


Simply delete the shaders folder located here by default:

C:\Games\Piranha Games\MechWarrior Online\USER\Shaders

Otherwise, please use our new repair tool, which will verify your game directory files and repair any file issues:
http://mwomercs.com/...public-release/

Remember to contact us at support@mwomercs.com with your dxdiag for additional 1-to-1 support from our Game Masters!

[Celtic Warrior]

Crash to desktop, I keep getting the same error "memory allocation" but now its happening on more maps. Was hoping this last update would fix the problem. The problem usually happens early on in the mission but has happened towards in end. It was mostly localized to River City but now has moved on to almost all the maps.

Monitor: 25 inch
Setting: 1920 by 1080
Processor Model : AMD Phenom™ 9850 Quad-Core Processor
Speed : 2.5GHz
System : Gigabyte Technology Co., Ltd. M78SM-S2H
Chipset AMD (Family 10h) Athlon64/Opteron/Sempron HyperTransport Technology Configuration
Video System Adapter : ATI Radeon HD 4800 Series (512MB, PCIe 2.00 x16, PS3.0, VS3.0)
Logical Storage Devices Hard Disk (C:) : 84GB (NTFS) @ OCZ-AGILITY3 90GB (SATA600, NCQ)
Network Adapter : NVIDIA nForce Networking Controller - Packet Scheduler Miniport (Ethernet, 1Gbps)
Operating System(s) Windows System : Microsoft Windows XP (2002) Home 5.01.2600 (Service Pack 3)

UPDATE: In advanced video settings I turned the texturing down from HIGH to MEDIUM. I've played for a few days now and have not had any crashes, seems to have fixed my crashing problem.

Edited by Celtic Warrior, 07 July 2013 - 10:55 AM.

[Theycallmetheworkingman]

Crash to desktop There is no error message. I am able to login, then once I click my mech on the bottom that I'd like to use, instead of having the usual mechlab appear, I am seeing a photo of what appears to be a solar system. All mech stats on the left are zero, I am unable to launch. The game then crashes without warning. The crash occurs over and over again without warning. I've never had this problem before.

This is what appears.
http://imgur.com/j0i16bX

Any options I click shows the page, but I have nothing there to work with or on. After a couple seconds on the mechlab, the game then crashes without any warning or error messages.

Specs
Nvidea Geforce 470
Intel i7 950
12 gigs of ram
1 terabyte seagate caviar green hard drive
ASUS Sabertooth X55 motherboard
Windows 7 x64 bit OS

I've sank money into this game. I'd like to be able to play it. Thanks.

Edited by Theycallmetheworkingman, 02 July 2013 - 07:12 PM.

[Lightfoot]

Game Freezes on second match, sometimes first match. No crash message and Windows Task Manager says MWO is running. Returning to game shows black screen no sound. No change to settings, was running fine yesterday and past 4 weeks.

Nvidia GTX 550 ti.

Edited by Lightfoot, 02 July 2013 - 02:50 PM.

[Einkil]

I just had a crash to mechlab, no error message. Screen froze up for a couple seconds, and then dropped me back in the Lab. I was piloting my Founders Atlas on Alpine Peaks. This is the first time I've had a crash of any variety since pretty early in the beta.

[HoppinRaven]

Since this patch the stability of this game is not good.
- ingame freezes (lasting seconds to having to alt-tab out and back in to solve it) have returned
- game stopping to respond upon trying to leave a group
- game stopping to respond midgame or at the end of a game
- out of game UI is slow as hell with refreshing suddenly.

I've already updated my Nvidia drivers but it seems to have made things even worse. Dxdiag finds no faults with the installed drivers nor do I have problems in other games.
Why is it that even though we are in beta that patches are becoming a thing I dread in this game?

[Flapdrol]

Played one game, after exiting the score screen: CryEngine Error. ***Memory allocation for 2707461280 bytes failed ****.

[RogueJello]

Consistent crash to desktop during game play. I start a new match, play for a few minutes, then the screen locks up. Sound seems to indicate that the game is continuing, and sound seem to track with game working (ie fire weapon, hear weapon sound). After being locked up for a minute client crashes to desktop w/o error message.

I've had this happen every time I play a game. Prior to this patch I had occasional problems, but nothing consistent.

Email sent to support with dxdiag's information.

[Mizore]

I had 2 freezes in the last 7 games since the new patch came out... no error message, just a freeze.

The last time I had problems with freezes was some months ago.

One freeze was during piloting a mech and one was while spectating after beeing dead.


I just deleted the shaders folder... let's see if it works.

Edit: another freeze... so deleting the shader folder didn't help!


System Specs

Spoiler

- i7-2600k 3.40GHz
- 16 GB RAM
- ATI Radeon 5800 Series

Edited by Mizore, 03 July 2013 - 01:46 PM.

[Kelito]

I am now getting hard lockups about 50% of the time, right in the middle of the game. So bad that I have to ctrl+alt+del and stop the game client from the task manager.

[Tolkien]

Lightfoot, on 02 July 2013 - 02:50 PM, said:

Game Freezes on second match, sometimes first match. No crash message and Windows Task Manager says MWO is running. Returning to game shows black screen no sound. No change to settings, was running fine yesterday and past 4 weeks.

Nvidia GTX 550 ti.

Same behaviour here, but on an ATI card. Very rarely had lockups in the last months, but have had 2 in the last two days.

[Swift Hatchet]

Hmm.. the patch seemed to have fixed the large amount of crashing/disconnecting I experienced prior to the hotfix. Which is not to say it isn't still happening, I did crash out to desktop twice yesterday. But that was out some 20 odd games, which I can reasonably accept.

And while more performance related the huge drag on my 680's (that appeared to be particle effect or similar) is also gone or at least better to the point I don't see it. Many thanks for the hotfix.

[caesar]

4 CTDs in a row on launch, no error messages. I exited, deleted the shaders folder between the third and fourth crash. 1920x1200x32, unchanged.

Intel Core i7 960, 12GB RAM, Radeon HD 7850.

Repair tool reports no mismatches found.

5 in a row.

[Braidedheadman]

• PGI still trying to sell me fancy paint schemes.
  
• PGI still trying to sell me fancy premium hero mechs.
  
• Soft locked during my second round of the evening.
  
• Be something like at least the fourth or fifth patch in the series that has not resolved this problem.
  
• ????
  
• PROFIT!!!!

Edited by Braidedheadman, 03 July 2013 - 09:16 PM.

[Deelawn]

I actually don't get an error message. When I launch game, the screen goes black for a few seconds and then it plops me back to the main menu. My mech will be "In Game". As far as I'm concerned, the "Launch" button is basically a button that turns my mechs from Ready into In game.

Interesting side note: Training grounds works fine. All maps load up fine and no crashes occur as far as I can tell, but once you try launching a normal game with people, it will freeze and kick me out to main menu.

I've ran the repair tool. Seems to do nothing as far as I know.

[caesar]

Deelawn, on 03 July 2013 - 10:14 PM, said:

I actually don't get an error message. When I launch game, the screen goes black for a few seconds and then it plops me back to the main menu. My mech will be "In Game". As far as I'm concerned, the "Launch" button is basically a button that turns my mechs from Ready into In game.

Interesting side note: Training grounds works fine. All maps load up fine and no crashes occur as far as I can tell, but once you try launching a normal game with people, it will freeze and kick me out to main menu.

I've ran the repair tool. Seems to do nothing as far as I know.

Yep, this is the same thing that happens to me. My guess is that Training Grounds is entirely local to your machine, no network access required. So it looks like they changed something network related.

[Kszyh]

Two freezes in first two matches after the patch. Alt-tabbing didn't help, I had to kill the MWO process through the task manager. First one happened after about 2 minutes during the fighting, second one - about one and a half minute after the start, with no enemy contact. Bandicam was the only application running in the background, disabling it after the freeze didn't help, and I've used it multiple times before the newest patch. System specs:
i5-3470@3.2GHz
8GB RAM
GTX 660
Win 7 Pro SP1

[Najek Yuma]

Theycallmetheworkingman, on 02 July 2013 - 02:19 PM, said:

Crash to desktop There is no error message. I am able to login, then once I click my mech on the bottom that I'd like to use, instead of having the usual mechlab appear, I am seeing a photo of what appears to be a solar system. All mech stats on the left are zero, I am unable to launch. The game then crashes without warning. The crash occurs over and over again without warning. I've never had this problem before.

I'm having this exact same error. My desktop originally froze and required a hard reboot while downloading this patch. Then when I rebooted and logged in I'm having the same issues as Workingman. I uninstalled and re-installed the entire client, but again my system froze while finalizing the patch. Can't launch at all, getting some weird screen in the mechlab, and the launcher crashes after only 3-5 clicks around.

Intel i5 3570k
Radeon 7850
16gigs ram
Win 7

[caesar]

caesar, on 04 July 2013 - 05:57 AM, said:

Yep, this is the same thing that happens to me. My guess is that Training Grounds is entirely local to your machine, no network access required. So it looks like they changed something network related.

Yep, they changed something in the network. It looks like the client no longer initiates the connection, the server does. If you have a real firewall instead of some cheap piece of **** router from BestBuy or your ISP, you'll likely have to make some adjustments:

000048: .Jul 4 17:50:17.583 UTC: %SEC-6-IPACCESSLOGP: list 101 denied udp 70.42.29.75(21207) -> w.x.y.z(62586), 1 packet

I wound up doing a "permit udp 70.42.29.75 0.0.0.255 range 21000 30000 any" and I can play now.

[Sarsaparilla Kid]

I've been having frequent disconnects since the previous patch, and tried running it after turning off all firewalls, including the one on the router, and it didn't help. I ran ping/tracert tests from both my home gaming computer and my computer at work, so 2 different ISPs, and was still seeing packet loss on both by the time the signal reached the game servers. Even PGI tech support says the connection is to blame, but beyond my ISPs (AT&T for one, Comcast for the other), there is nothing I can do to fix the loss happening between Palo Alto and Chicago, and from Chicago to Toronto. I have no issues at all with Rift or Pirate 101, so that pretty much rules out my local ISP as the root cause, or I should be seeing the same problem on the other games, too.