50 replies to this topic

[GermanPartisan]

I now have crashes when i get killed. I go down and then "drop to desktop"-crash. Plus the freezes are now a little more often and severe, the last version of the game I could "fix" a frame-freeze by switching to desktop and back and real game freezes were very rare, now I cant always fix a framefreeze and real game freezes are much more frequent.

[Daekar]

Been having frequenty (as in 50% rate or more) occurring crash to client errors, where I get a brief black screen and then back to the client. Happens in different levels and in different mechs, while under fire and while not under fire.

There is a "crashdump" file in my USER directory. Here are the files I thought you'd like:
Omicron.log
Crashdump.dmp
DxDiag.txt

EDIT: I'd like to add that since I changed my graphics settings from High to Medium, I've only had one crash out of like 12 matches. Much better percentage, or just lucky. Might be worth a look.

Edited by Daekar, 08 September 2013 - 12:04 PM.

[Pz_DC]

Someone know will devs fix endless errors?.. 3rd patch - same ****... Game is totaly ****** up - even in closed beta it was much-much more stable - to be correct it has no errors at all! WTF?! Over mounth passed since thiose errors came into our life - now, when over 80% of players cant play it (look at poll results!) devs keep trying to makes stupid sales etc instead fix most important thing in whole game!..

[Ilmenstein]

Hey, have the same problem. Client crashed every match so far, sometimes already while loading start up animations, sometimes middle of a match. Looks like a freeze, but cannot be solved switching to desktop and back to client like in previous version. All i get after switching is a black screen and have to shut down the client by force using the task manager. Sorry, but the previous versions of the client have been much better. In this state the game is hardly playable anymore. Please have a look into this and try to fix it as soon as possible. Thanks.

Edited by Ilmenstein, 08 September 2013 - 09:08 AM.

[Daekar]

MGA121285, on 08 September 2013 - 04:42 AM, said:

Someone know will devs fix endless errors?.. 3rd patch - same ****... Game is totaly ****** up - even in closed beta it was much-much more stable - to be correct it has no errors at all! WTF?! Over mounth passed since thiose errors came into our life - now, when over 80% of players cant play it (look at poll results!) devs keep trying to makes stupid sales etc instead fix most important thing in whole game!..

Not helpful and inaccurate. Please choose another thread to troll in, this is a functional thread.

[SirDubba]

Still Crashing to Desktop. I tried uninstalling, running CCleaner to check my registry, then installing to another drive, checking the installation with MWO Repair Tool which didn't find anything wrong and then played couple battles. On the third one I crashed.

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

No messages provided, just a clean 'n' fast crash

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

Always during the game. Sometimes one or two minutes after the battle starts, sometimes during the mid-game. Today I managed to play two matches without having ctd, sometimes I crash 4 out of 5 tries.[/color]

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

1920*1080 Fullscreen, VSync enabled
motion blur: LOW
graphics: LOW with textures: MEDIUM
glow damage enabled
I've used these settings whole summer

Edited by SirDubba, 09 September 2013 - 04:53 AM.

[Grakthuul]

The game locks up in match's several times a day. I'm not getting any error messages. The lock up seems to happen randomly no matter what I'm doing. I've locked up before the match starts, in the middle of combat and even when just walking around. I play the game in 1080p with settings at Ultra. I have been using these video setting seance I started playing the game in mid April but I've only been locking up during this patch and the last one. So far I've deleted the shaders folder, used the repair tool and completely reinstalled the game and I'm still locking up several times a day.

Spoiler

AMD Phenom II X6 1090T Processor 3.20 GHz, 12GB DDR3 Ram, AMD Radeon HD 6950 Video Card

[Floowid]

So far this patch has actually been more stable for me. I used to average about 1 freeze for every 5 games, but since this last patch it took me several days of playing before my first crash. The crashes are so random this could all be coincidence.

[jay bea]

Consistent crashes. Usually takes out my entire system.

OS: Windows 7 Home Premium 64 bit
Graphics: NVidia GeForce 660, driver 320.49
CPU: Intel Core i5-2500K CPU @ 3.30GHz (4 core)


Dropping down the graphics and deleting the shader directory did not fix the issue. It appears to crash the NVidia driver completely. So far, this is the only game that does this.


Edit:

So, on testing, something is up with the shaders. Deleted the directory, and the MWO repair tool (1.1.3.0) crashes, becoming non-responsive. I'm on trial run 3. I may re-install completely.

Edit:
Got the repair tool to run through. It reports no problems, ran the repairs anyway. Driver seems Ok, but I don't get a crash to desktop. Whatever the problem is causes a full crash of the OS and video driver.

Edit:
I'm starting to think it might be due to DX11 existing on this system. Time to see if I can force MWO to use DX9 only, somehow. Isn't there a sandbox mode?

Nope. Not it. Used the "-dx9" flag to see if that did anything, and the driver listed was DirectX 9. Good, I think. Testing in the sandbox of Canyon Network had a full crash. Not even to desktop. Took out the whole machine again.

Edited by jay bea, 10 September 2013 - 05:34 PM.

[Lubuy]

Demospata, on 03 September 2013 - 07:57 PM, said:

No error messages, screen freezes have to force quit. Happened soon as match started and took a few steps

+1

Happens here too. In one out of 5-10 matches. It's the first time Im experiencing these crashes.


AMD Phenom™ II X4 965 3,4ghz
8.00 GB Ram
64 Bit Win 8
Nvidia Geforce GTX 570 Driver 320.49

Edited by Lubuy, 10 September 2013 - 12:29 PM.

[Astrus Lux]

i couldn't play 1 match, 'cause of the Cryenginge error Fread....
Everytime i log in and start a match the client crashes.

Worst thing is, that after uninstalling the client i can not reinstall, 'cause the dowloaded file is corrupt - every time i download it. Not very funny on a 2000kb downstream





My System:

Board: asus Crosshair V formula II
CPU: AMD PhenomII X4 955be - no oc
ram: corsair vengeance 4x4gb
gpu: 2x asus engtx560 dcII 1gb

[SilverlightPony]

Navid A1, on 03 September 2013 - 02:34 PM, said:

The freezing issue for me has gotten worse. right after patch, i tried the new movement tutorial... i froze up upon receiving the first waypoint command

then tried a testing ground... destroyed 4 targets and froze up upon targeting the fifth mech.

then tried a match... froze up 10 seconds after start.

- no error message
- freezing has no obvious reason and happens randomly
- sound still plays after freezing (usually the cockpit hum and such)
- the only way to get out is to kill the process using task manager.
- my settings are mostly low/medium
- i play on a low spec system (core2duo 2.8ghz / ati 4650 1gb / 6GB ram)

Identical symptoms, even though I'm running at almost max graphics.

System specs:

Spoiler

AMD Phenom II X4 975 Black Edition (quad-core 3.6GHz)
16GB DDR3 1333 RAM
GeForce GTX 470 @ 1920x1080
System drive and games drive are both Crucial SSDs.

[Konner Duko]

only issue I have experienced is occasional dumps to desktop when launching into a match. the game does not crash but is minimized in my task bar. I then have to click the program to pull it back up and I never get booted from the matches. happens about 1 out of 10 times I play a match.

[SilverlightPony]

Possibly useful bit of info: I've started running the Repair Tool after every crash, and I've noticed there's consistently 1 .pak file that turns up a mismatch. Just one, and not always the same one. Most recently, it was engine.pak; before that it was something involving sounds.

I ran it and told it to fix the errors, then ran it again and made sure it said there were no errors. After that, I was able to get in several full games with no crashing.

Then I quit the game to go eat and take care of some errands, came back a few hours later, fired up the game, launched into a match, and MWO froze up about a minute later. Running the repair tool found a mismatch in engine.pak.

[MILESPARVUS]

This version is rather less stable than the previous version for me. During a 3-4 hour session I'll have at least 2 crashes in that time, the worst being about 5. It's not unplayable, I get a good amount of playtime in between crashes, but it is a significant increase over last patch where I'd maybe get 1 crash per session.

I get no error messages, and it's a hard crash. The screen just freezes, and I need to bring up task manager to close it down. If I wasn't running 2 screens, I'd probably be resetting the system because it won't minimise to desktop.

There are no particular things that happen before the crash, it just does so at random points. Usually while I'm in spectator mode, and only occasionally while I'm in game, if that helps. I'm currently running fullscreen in 1980x1080 with DX9 on medium settings, and I haven't changed that since last patch.

System specs:
Intel E8400 Core2 duo 3GHz
4GB RAM
Radeon HD 4850 1GB, driver version Catalyst legacy 12.6
Windows 8 Pro 64 bit

Edited by Kiskatona, 13 September 2013 - 06:56 PM.

[JimLahey]

CTD fest here! Here's how it goes down:

-start client
-select mech and install modules
-click "launch"
-watch "searching icon" go round and round
-black window
-black fullscreen
-play match
-click "exit match" at stat screen after match
-black fullscreen(sometimes CTDs here)
-back to mech lab
-unload modules
-select new mech and load modules
-click "launch"
-watch "searching icon" go round and round
-black window
-CTD always(repeatable)
-swearing commences
-restart client
-mech and modules stuck "in match" for ~10 min

This has been a problem for a while now but has gotten much worse after Sept. 3rd patch.
No error messages are displayed after CTD.
Graphic settings are all maxed and runs great during gameplay(60-80fps)

system specs:

Spoiler

CPU - Intel i7 3820
MoBo - Asus Rampage IV Formula
RAM - Corsair Dominator GT 8GB 1866MHz
Hard Drive - Corsair Force GT 120GB SSD
GPU - 2x HIS HD7970 GHz BIOS(using only one)
Sound Card - Asus Xonar DGX
OS - Windows 7 Pro 64bit

[SilverlightPony]

This time the repair tool found a mismatch in forestcolony_snow/level.pak

[Pz_DC]

Daekar, on 08 September 2013 - 12:05 PM, said:

Not helpful and inaccurate. Please choose another thread to troll in, this is a functional thread.

6 times i try to run this game and 5 of it game crashes right after match start with different engine errors (sometimes doubled). Different settings, different maps and mechs. Run repair tool after each crash. No changes. Trolling?! OFC!!! Coz its unplayable!!!! Im here since closed beta start and can say for sure that game is totaly broken since august, no point to post system spec and so on - devs just need to take a look at engine changes that was done after august and fix it! Again - run repair tool after each match. Different maps. Different mechs. Different settings. Same result - 95% crashes. with engine error(s)...

P.S. few sec ago game crashes 7th time.... 30 min and 25 of it - re-start client.. perfect..

Edited by MGA121285, 14 September 2013 - 02:55 PM.

[Troutmonkey]

Been having Crash to Desktops before launching or after completing about 20% of games. Really irritating that my new mech keeps getting locked into matches that I'm not playing

[Argonin]

Since the latest patch my game freezes quite often. I never had this problem before. The game just freezes and I have to shut it down via the task manager. Quite a few times it freezes when the game just starts (when the list of players disappears) but also during a match.

System specs:
Intel Core 2 Quad Q9300, 4GB RAM, Radeon HD 6800 (Catalyst 13.4), Windows 7 Ultimate 64bit

Edited by Argonin, 15 September 2013 - 05:10 AM.