9 replies to this topic

[Dutchoper72]

So my game keeps getting this error. This is the only game that is giving me this.



Operating System
Windows 10 Home 64-bit
CPU
AMD Phenom II X6 1050T 45 °C
Thuban 45nm Technology
RAM
8.00GB Dual-Channel DDR3 @ 669MHz (9-9-9-24)
Motherboard
Gigabyte Technology Co. Ltd. M68MT-S2P (Socket M2) 52 °C
Graphics
E24-C1 (1920x1080@60Hz)
2236 (1920x1080@60Hz)
4096MB ATI Radeon RX 480 Graphics (XFX Pine Group) 66 °C
Storage
931GB Hitachi HDS721010CLA SCSI Disk Device (SATA) 37 °C
931GB Western Digital WDC WD10 EZEX-00BN5A0 SCSI Disk Device (SATA) 36 °C
930GB Western Digital WD My Book 1110 USB Device (USB (SATA)) 36 °C
Optical Drives
HL-DT-ST BD-RE BH14NS40 SCSI CdRom Device
Audio
Realtek High Definition Audio

Any help would be nice. Most of the time it happens is during a battle.

[Dutchoper72]

Any info on this? Or am I the only one with this issue?

[Twilight Fenrir]

I get a similar crash, once every time I reboot my PC. My graphics card driver crashes in my first match every time, then after I reopen my client, the game runs flawlessly until I restart my computer again. This is also the only game that does this.

I have an Nvidia GTX 5800, and have updated my drivers several times. This has been a problem for me for a year or so with this game.

[Jemmer]

as of the December patch my client crashed on average once to twice a week with a similar error message. Throughout January the crashes increased in frequency until as of this week its happening about once every hour. I have been playing for 2 years regularly, and I have never had a client crash or or had any kind of error before now - not just you suffering from this Dutchoper72. Running the repair tool, removing/reinstalling drivers, updating drivers, rolling back newly updated drivers, uninstalling/reinstalling MWO has not helped at all.

However I remember reading somewhere - or maybe from viewing a roundtable? - that they are aware of client crashes and players experiencing unstable clients, and have started to soft release (still in alpha) a new launcher portal. So very soon we may be getting a new client to download and use from now on anyway.

Edited by Jemmer, 02 February 2017 - 04:01 PM.

[Dutchoper72]

Jemmer, on 02 February 2017 - 03:48 PM, said:

as of the December patch my client crashed on average once to twice a week with a similar error message. Throughout January the crashes increased in frequency until as of this week its happening about once every hour. I have been playing for 2 years regularly, and I have never had a client crash or or had any kind of error before now - not just you suffering from this Dutchoper72. Running the repair tool, removing/reinstalling drivers, updating drivers, rolling back newly updated drivers, uninstalling/reinstalling MWO has not helped at all.

However I remember reading somewhere - or maybe from viewing a roundtable? - that they are aware of client crashes and players experiencing unstable clients, and have started to soft release (still in alpha) a new launcher portal. So very soon we may be getting a new client to download and use from now on anyway.

Hmm, i use to use their launcher, but moved onto steams, just because i prefer everything on 1 platform rather having to have so many things running. I hope it gets fixed soon. I have been around since the game first came out, but had a lot of off and on play. Recently I got back into it, but the crashes are slowly pushing me out.

[Cocomax]

I really miss playing MWO, I played for 2 years no problems at all. Since the December 2016 patch the game crashes every time on the map loading screen. I can always restart the client and rejoin the game, but I get into the game 4 to 8 minutes late and half the time I am already dead.

[ET Penang]

The game crashed twice in 1 hour.....this is new to me as it never happen before.

And bloody get the disconnect penalty twice! This is not right.

Edited by ET Penang, 06 February 2017 - 02:23 AM.

[xeromynd]

This is just one of those MWO things. I had this issue myself for about a year, on and off seemingly at random. It's most certainly NOT your graphics card, because MWO is the only game that does this in my collection, and I've seen lots of posts from users with many different GPUs about this issue.

I tried countless driver versions, even going back more than a year. Worked for a time, but the error would always come back at random.

The only thing that prevented this was switching from DX11 back to DX9. Haven't had this crash since, not once. It sucks to not be able to use DX11, but oh well. This error is unacceptable for streaming.

I'm into computer hardware a little bit, I understand SOME things, but this is beyond my scope. As far as I understand (from all the posts I used to read) this has to do with MWO (a game with terrible/no graphics optimization) calling for your GPU to do something that it just can't do, which makes the GPU have an aneurysm and crashes the game. (This would also crash my display drivers too, and left me with a black screen for a few seconds until my monitor's autodetect kicked back in after about 20 seconds).

[M T]

I dont think its an MWO thing, as much as this game is crappy i have not crashed a single time, ever.

Git gud!

[Krist Smith]

The real answer is that most likely this both is and isn't due to MWO (although MWO is not the only game to have this exact issue, according to a quick Googling). It is due to MWO because, as any MWO player knows, CryEngine is quite a power hog (or, at least our specific version atm). The actual reason for the crash is that your GPU is keeling over for any one (or more) of a number of reasons, such as the card itself demanding more power than you system can give it, driver updates (not likely to happen more than once), overheating, DirectX corruption, and so on.
There are ways to avoid the problem and there are ways to identify the problem. The easiest avoidance method is to simply tone down your in-game video settings (down-res, turn off AA, etc.) You can start with broad strokes and turn everything down, and, once you find a stable point, turn things back up one at a time on a session-to-session basis (not just match-to-match, since some maps/mechs are more intense than others).
To fully identify the problem with the aim of a proper fix (with the understanding that a proper fix can mean replacing hardware in a worst-case scenario), you will need to take many steps. Of course, starting point is making sure your video drivers are up-to-date, which many of you have already stated is the case. From there, ensure DirectX is solid by running the installer (make sure you're getting that installer straight from Microsoft). Going further down the rabbit hole, you will likely need to download some software to monitor systems temperatures (GPU in particular), and power drains (again, focusing on GPU). There are plenty of discussions in other game forums that I hesitate to link to here, but if you're interested in really nailing down the cause, Google the error code from the ss in the first post ("DXGI_ERROR_DEVICE_REMOVED").
And feel free to contact our support team to work with them on correctly identifying your problem.

PS - Twilight Fenrir, if you're getting this crash once per reboot, my first guess is that there's a program you have set to start with Windows that is already taxing your GPU, and MWO comes along to push it over the limit. But when the device crashes, that auto-start program no longer has a handle on your GPU to be a drain on it, which allows MWO to run under the crash limit. That's just a guess, but you might wanna just look through your auto-start programs. Might also be as simple as NVidia or ATI software imposing some rendering rules on top of what the game is doing (like having anti-aliasing enabled through the NVidia control panel, and also turning it on in-game, essentially multiplying the workload).