234 replies to this topic

[Monky]

Game seems less stable on my end this patch. Have had my 4th hard lock since the patch. Will try reinstalling tonight.

Just before I apparently lost connection to MWO, I got 4 FPS bug which seemed to be nearly a crash but it recovered simply making the game unplayable rather than exiting outright. - It may be related to display drivers, as after this I exited MWO and all my web pages in google chrome where displaying nothing but black. This was not like that prior to the patch. Had chrome's homepage and MWO website open. using Nvidia, and I know they rolled out a patch recently but it says I'm up to date and I don't have it set to auto update. bizarre. *correction, it was not yet updated to Nvidia's latest drivers. doing so now.


Operating System? (please also specify 32/64-bit) Win 7, 64 bit
Re-installed the game: yes/no? No
Default installation folder: yes/no? Yes (as always)
Solid State Drive: yes/no? No (there is one in the computer, but that is not where MWO is installed).

Edited by Monky, 20 February 2013 - 08:54 PM.

[mastergenera1]

I've also had game crash issues with it telling me that "the session was lost" or"server connection was lost"(every 3-5 min) on a connection in which i get 50 ping in any other game,not to mention that right b4 one of the crashes i was customizing a mech,bought the parts i wanted and lost the parts on login but i was still billed for them which cost me like 960k in weapons and ammo that i dont have.this happened 10min ago btw.

win7x64
didnt reinstall
default install folder,no i dont install games on my C:/
SSD is a no, C:/ is a SSD but my games are installed on a regular 2TB drive

Edited by mastergenera1, 20 February 2013 - 09:15 PM.

[Warma]

Last patch I reported game freezing problems when a large number of missiles hit targets or the ground. I will again collect here everything I know about the bug to provide you with as much information as possible.

Most reliable steps to reproduce:
1. Take a scout mech
2. Have a friend take an LRM boat.
3. Paint target, have friend launch a ton of missiles. Stay relatively close to target.
4. Look into explosion, game freezes.

The freeze happens almost every time if I actively try to reproduce it using the aforementioned method, or approximately once in three games if I try to avoid it (someone takes LRMs anyway).

The game does not recover from the freeze and must be killed from the task manager. What is interesting is, that disconnect message pops up on killing the program, not on freeze (this was reported to me by my friends). In other words, some subsystems of the game must still be running during the freeze.

The bug has been present since the Feb 5 patch, and Feb 19 patch does not seem to have had an effect on its frequency. Crashes seem to mostly happen on NVidia 600-series GPUs (confirmed 660, 660TI, 670, 680) and almost exclusively on very high-spec machines (i7 3770K, 16G RAM, etc). None of my friends with AMD GPUs or low-spec machines report crashes, and say the game is more stable than it has ever been.

I have done a reinstall and have tried various graphical settings with no apparent effect to frequency or presence of crahses. My friends report less frequent crashes on lower graphical settings, but my personal experience says otherwise. The game crashes the same amount even when all settings are low and motion blur/AA are off.

CPU: i7 3770K
GPU: Asus NVidia 660
OS: Windows 7
Re-installed: yes
Default installation folder: no
SSD: yes

(edited with new info)

After setting the monitor refresh to 60Hz and turning on vsync, the game has not crashed during the last two nights of playing. This suggests that the bug has something to do with framerate and timings.

Edited by Warma, 22 February 2013 - 01:56 AM.

[TopDawg]

Matthew Craig, on 20 February 2013 - 11:12 AM, said:

I'd really like to get to the bottom of the CTD issues currently being experienced to best help us out please post the following if you are still experiencing this issue:

1. Look in your C:\Games\Piranha Games\MechWarrior Online\USER for a file crashdump.dmp if it exists please log a support ticket support@mwomercs.com and we can look it up via your Pilot Name

2. If that file does not exist but the game hangs rather than kill it in task manager, right click on the process and click Create Dump File then attach that to a support ticket (again we can look it up via your Pilot Name)

3. Try enabling V-Sync in the options screen to see if it lessens/stops the crashes

4. Ensure you've shut down all third party software to ensure there is nothing that could be interacting with MWO

5. Post these details (help us see if there is any commonality):

Operating System:
Re-installed the game: yes/no
Default installation folder: yes/no
Solid State Drive: yes/no

Thanks for any assistance tracking this down for you all.

My MWO has been 'hanging' I guess it's referred to, whereby it freezes in game and the only way to make the computer responsive again is by ctrl + alt + del to task manager and ending the process. It's been doing this a lot lately (since the Feb 5th patch, and never before then). It still does this with V-Sync on.

The dump file exists in the MWO folder, but is never dated from when my MWO hangs. Alternatively, I tried creating the dump file from the task manager when I crashed, but that file is 1.03 GB (and then a second one was 1.35 GB), which I don't know how to send a file that large through e-mail to support.

As per the rest of your post:


Operating System: Windows 7 Ultimate 64 bit
Re-installed the game: Yes
Default installation folder: Yes
Solid State Drive: Yes

[TopDawg]

To go off what Warma above me posted, it does seem to be an issue with LRMs going off on screen (maybe the old one reoccurring with too many sounds, or a new one based visually). I also have a high end PC with a, i7-2600K (overclocked), a GTX 670, and 16GB RAM.

I never had this problem until the Feb 5th patch, and also like Warma, has made playing extremely frustrating. So anything to help the process along, please let me know.

[Monky]

Updated to latest nvidia drivers, no in-game crashes (so far), but just crashed in mechlab switching from TBT-5J that was in combat to a ready RVN-3L. Mech did not have time to render before the crash.


Operating System? (please also specify 32/64-bit) Win 7, 64 bit
Re-installed the game: yes/no? No
Default installation folder: yes/no? Yes (as always)
Solid State Drive: yes/no? No (there is one in the computer, but that is not where MWO is installed).

Edited by Monky, 21 February 2013 - 01:58 AM.

[Von Falkenstein]

Krist Smith, on 20 February 2013 - 01:23 PM, said:

Could you guys post your answers to Matt's questions please? Just to help collect useful information that may help us track the cause of these problems. For reference, here are the questions:

Operating System? (please also specify 32/64-bit)
Re-installed the game: yes/no?
Default installation folder: yes/no?
Solid State Drive: yes/no?

OS: Windows 7 64bit
Reinstall: Yes
Default folder: No (using 2 different hard drives, one for OS etc., the other one for games and misc.)
SSD: OS on SSD, client on SATA

[Grrzoot]

Niko Snow, on 19 February 2013 - 11:18 AM, said:

All Crash and Stability related posts will be merged into this thread for simplified reference and overview.

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])

Recently had a crash, was tabbed out while spectating and got an error: Cryanimation:command buffer overflow.
was on river city night, first match of the day. no changes to sys spec

[ChaosGrinder]

I am crashing as soon as the startup sequence at the beginning of the match starts. I drop in the match, everything is fine, but as soon as the startup should appear, blackscreen-> CTD

on every game i´ve played so far

[Darokin Korin]

I'm in exactly the same fix. As soon as the level loads I crash back to the mech lab. This occurs either during the start up sequence or immediately after it finishes. This has occurred for 4 out of the 5 games I've tried to play. I've sent the Crashdump file as will as the Omicron Build file to support@mwomercs.com.

I'm running:
Toshiba Qosmio 580
i7 Intel
8GB ram
GTS 360M 314.07 driver
Windows 8 64-bit

Default Install: Yes
Reinstallation: No
SSD: No

Here is a sample from the Omicron file:

Spoiler

============================ PrepareLevel frozencity_night ============================
Initializing default materials...
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'objects/environments/skyboxes/forestcolony_clouddome_a.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/forestcolony_clouddome_a.dds]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'objects/environments/skyboxes/frozencity_night_clouddome_a.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/frozencity_night_clouddome_a.dds]
[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]
[Error] locomotion-group not found: animations/mechs/stalker/lmg_files/land_to_fwd_fp.lmg
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetName
======== frozencity_night is loaded in 20.8 sec ========
CGameClientChannel::Release
could not free all buffers from CDevBufferMan!
UnLoadLevel End: 0.7 sec
sv_gamerules = mechlab []

Edited by Darokin Korin, 21 February 2013 - 10:08 AM.

[zmeul]

Surtr, on 19 February 2013 - 01:28 PM, said:

Nope. Just finished downloading and installing the 314.07 drivers and it did the same thing, I wasn't even looking at the client this time. :/ I am sad

I found out from a 3rd party source that 314.07 drives contain same bug as 310.90 ones
my advice at this point is to try an even earlier set than 310.90

[pjnt]

I get the black screen. I seems the game runs in the background but ctrl-alt-del brings up the task manager and also brings up the quit/exit buttons. Which when I hit esc returns me to the game. Very frustrating.

Running at 60 hz, no diff.
V-sync on. no help.
reinstall. nadda.
Sacrificed 3 chickens over a boiling cauldron while dancing naked in a snow storm with a perverted monkey. Beak marks on my chest, shrinky dink and a bad case of the runs from the monkey. Game still crashes.

Trying different drivers.

[Gooner]

I'm encountering the same freeze/crash problem as others are reporting. The only thing I can do is kill the process on task manager (except for the very first time it happened, when the game somehow fixed itself). It happens on all maps and I've been playing in the Ilya Muromets. I know others are suggesting its linked to LRM impacts, but I don't recall any specific common event immediately before my crashes. It doesn't happen in every match I play, right now it seems to be every 4 or 5 games.

This problem started for me IMMEDIATELY after installing the previous patch. Literally the first game I played. Before that patch I honestly don't remember crashing at all. The only settings I've changed have been after the first crash.

I've got a crashdump file, which I'll add to a support ticket. I've just enabled Vsync, and will investigate if it helps.

Operating System: Windows 7 64 bit
Re-installed the game: no
Default installation folder: yes
Solid State Drive: no

Processor: Intel Core i7 2600k @ 3.40ghz
RAM: 8GB 1333MHz DDR3
GPU: GeForce GTX 580, drivers 9.18.13.697 (very stable in all other games I've played recently - for example just 1 CTD in over 30 hours of Skyrim last 2 weeks).

[Tolkien]

This patch has caused the game to become unstable including both blackscreen crashes at the end of matches as well as a hard locks of the game during combat and one complete system power off. I have not experienced *any* of these crashes before prior to this patch, so I am 110% sure it is the patch.


Please attempt to respond to the following questions in your responses:
Was any error message provided with the crash, if so, which?
- no error messages, black screen or lockup.
Where in the game or menus did the crash occur?
- in the game or just after the end of a match.
What steps had been taken prior to the crash occurring?
- no apparent commonalities. One crash on river city night, one crash on the desert map, and another the hard power event on frozen city.
Does the crash re-occur for you if repeating those same steps?
- no known commonalities, so I cannot repeat. Playing 10 matches has been enough to get 3 crashes though.
What are your video settings, did you change them since last patch?
- They were the same as last patch during which I experienced no crashes. After the 2nd crash (power off) when I upgraded to the latest 13.1 catalyst drivers I experienced a 3rd crash so the update did not resolve this. The 3rd crash leads me to believe it is the game patch.
What are your System specs? (You can include them in a [spoiler] [ /spoiler])
[spoiler]core i7 2600, 16 GB ram, radeon 6990m with 1GB Vram, Win7 64 bit [ /spoiler]

[MightyBolamite]

It appears to be getting worse the longer I play. I am getting very frustrated.
Operating System? (please also specify 32/64-bit) Win 7 64
Re-installed the game:no
Default installation folder: yes
Solid State Drive: no


EDIT:
And it stopped working again...
I sure hope this helps in letting you know what's happening, because it is becoming increasingly unplayable.

Spoiler

Time of this report: 1/22/2013, 22:43:57
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: System manufacturer
System Model: System Product Name
BIOS: BIOS Date: 02/05/10 19:13:52 Ver: 08.00.10
Processor: Intel® Core™ i7-2600K CPU @ 3.40GHz (8 CPUs), ~3.4GHz
Memory: 8192MB RAM
Available OS Memory: 8166MB RAM
Page File: 3891MB used, 12441MB 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 64bit Unicode

Edited by MightyBolamite, 21 February 2013 - 02:15 PM.

[Darokin Korin]

I'm still having the dump to client situation. I reinstalled a previous version of my display driver and sent the Crashdump file and Omicron log file to support@mwomercs.com. I actually got an email back saying that a fix was implemented so I'm guessing the results of my Crashdump file pointed toward a previous issue.

Got back on and played three rounds successfully then failed about 6 minutes into the fourth round. Dropped right back to the mech bay. Never had this issue before the latest patch.

[Julian Tifflor]

ok...installed newest nvidia driver

new patch:

caustic valley i get more freezes than usual for like 2-3 seconds when turning. was slightly better before this patch...some patchs ago i had no freezes at all.
now those freezes or stuttering even happened on river city today with thermal vision on...this never happened before and even a friend gets them now who nevver had this issue before.

his system runs like 40fps normally and the frames dont go down it just stutters here and there.
while mine is a low end system which had problem in the past...then went to playabale...till great and since then its going downhill again.


i get black screens after a mech is finished, total freezes (taskmanager helps) and sometimes just crash to desktop with stopped working message.

amd 5200+ 2.7ghz
zotac 560ti 2gb ram
3gb ram ddr2

all low details, everything turned off.

whatever you did...everything went from fine and playable to worse.

[Taron]

Well, just for trying, i removed the frame rate restriction form the user.cfg (sys_MaxFPS = 45). As soon i did, every 2nd or 3th match i got a crash (freeze frame). WITH the settings in user.cfg - no crash, no matter how long i play. Only some textures issues (Frozen city, all in grey), and sometimes a broken minimap.

Quote

so I'm guessing the results of my Crashdump file pointed toward a previous issue

Did you look at the date of the crashdump? Often the client does not create a new one, so better delete the old one and have a try.

Edited by Taron, 21 February 2013 - 07:44 PM.

[jay bea]

Pretty consistent crashes as of this evening. Never had a full freeze that required quitting and restarting the game. No process dump available, sorry.


OS: Windows 7 "Home Premium" 64bit
CPU: Intel Core i5-2500K 3.30GHz.
RAM: 8 GB
SSD: No.
Fresh Install: Not yet.


Random consistency: started with a non-selected mech (cataphract) in both the crash games.

Edited by jay bea, 21 February 2013 - 08:25 PM.

[HypeR70]

Crashes much more frequently after latest patch and latest nvidia whql drivers - 314.07 - 2/18/2013

Application crashes hard and takes away the competitive nature of the game as being down 1-2 people every match reduces the willingness to play when you enter a game short-handed on such an inconsistent basis.

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

No, MWO app just hangs/freezes and goes "Not Responding."

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

Game loads, shows player list, player list disappears, crashes out during mech start-up sequence. Usually app freezes, or it boots me out to main menu.

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

Since the last patch this Tuesday, and updating the video card drivers, the game stability is trash. It crashes I would say 25% of the time on mech start-up.

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

Yeps, about 25% of the time I get into a game.

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

Maximum. I have taken remediation steps such as enable V-sync and changing settings to a lower setting, but it hasn't made a difference.

• What are your System specs?

i7-3770k
32gb ram
gtx670
ocz vertex4