34 replies to this topic

[jay35]

Are the stability issues since Tuesday's patch being looked into? Have they been acknowledged yet? I think a lot of folks are reporting stability problems but hopefully I'm not the only one with this crash bug starting since Tuesday's patch.



That error is now happening every couple matches while playing the game, rendering MWO mostly unplayable because it happens often enough that it's hurting the ability to play well when you're CTD'ing and therefore disconnected from the match while you fire MWO back up.

Game was 100% stable before this patch.

Nothing else on my system has changed aside from patching MWO.

I've attempted to resolve by running the Repair Tool as well as updating my GPU drivers to the latest beta version (before I was running latest official). Neither has helped resolve it.

I submitted a ticket with dxdiag and omicron files.

Edited by jay35, 10 October 2015 - 05:48 PM.

[Wintersdark]

Interesting. Is your GPU overclocked?

I'm on Win10 64bit as well, and have had perfect stability since the patch (and before). Radeon HD 7870, on 15.7.1 ("Latest" is not a version, and a bad habit to use when looking for support)

[Thorqemada]

Dont Display the F9 stats (FPS + Coordinates) and avoid to have Video Streams (i.e. Twitch, Youtube, Podcasts) running while playing MWO.
Helped me alot...

Edited by Thorqemada, 10 October 2015 - 06:11 PM.

[Deathlike]

My best suggestion for you is to enforce "max performance" in the power settings option in the NVidia control panel for this game.

I don't have any others off the top of my head though.

[jay35]

Nothing overclocked, all stock. AMD GPU (R9 390X). i7-6700.

Two of the matches where it happened I had Raptr running to record. The rest of the time I did not.The error message seems to indicate the game is sending some sort of invalid D3D instruction or something.

I don't run with F9 active normally but I often have paused youtube videos open in a browser tab. But I've never had an issue. MWO was rock solid until this week.

Edited by jay35, 10 October 2015 - 08:38 PM.

[Sereglach]

jay35, on 10 October 2015 - 05:15 PM, said:

Are the stability issues since Tuesday's patch being looked into? Have they been acknowledged yet? I think a lot of folks are reporting stability problems but hopefully I'm not the only one with this crash bug starting since Tuesday's patch.



That error is now happening every couple matches while playing the game, rendering MWO mostly unplayable because it happens often enough that it's hurting the ability to play well when you're CTD'ing and therefore disconnected from the match while you fire MWO back up.

Game was 100% stable before this patch.

Nothing else on my system has changed aside from patching MWO.

I've attempted to resolve by running the Repair Tool as well as updating my GPU drivers to the latest beta version (before I was running latest official). Neither has helped resolve it.

I submitted a ticket with dxdiag and omicron files.

I've been getting the same thing, constantly, with nothing overclocked, all stock, NVidia card, Win 7, and fully updated OS & drivers across the board (in fact I got a driver update Thursday and the problem hasn't gone away), too.

It's not just you. I had a similar issue about a year and a half ago, but after the following patch it stopped just as mysteriously as it showed up. I've been sending in the automated error reports like crazy (when it lets me, sometimes it doesn't) and hoping that the same thing happens, again. Hopefully after the 20th the problem goes away as quickly as it showed up.

Edited by Sereglach, 10 October 2015 - 09:02 PM.

[Appogee]

Adopting Microsoft's new OS's at the moment of their release often leads to these kinds of time-wasting bug hunts.

Aside from the bugs in the OS that MS didn't bother to iron out prior to release, 3rd party software and drivers always take some time to get settled.

In the past, I've sometimes found that reinstalling the old OS was the only way to get everything back into working order. I usually update to the new OS about a year after it's released.

Edited by Appogee, 10 October 2015 - 10:39 PM.

[Thorqemada]

Use the Catalyst 15.9.1 Beta if you dont - the bug almost disapeared for me:
http://support.amd.c...ndows-beta.aspx

If not Report it to AMD:
http://www.amdsurvey...A1E27D23A3DE979

Edited by Thorqemada, 11 October 2015 - 03:00 AM.

[Deathlike]

It's simply possible the stuff (files+data) used by the devs on the hotfix branches are totally different from the official branch, thus this is why it occurs.

Very often... with each patch (and hotfix) alters the files in the Bin## folders (mostly a straight file replacement) before they start altering the pak files (in the most recent case, the Executioner).

Edited by Deathlike, 11 October 2015 - 09:26 AM.

[Pineapple Salad]

I've been having this issue for over a year now, with multiple different graphics cards (all nvidia). I haven't seen any increase in frequency after the latest patch. Currently running Win 8.1 on i5 4690k 16GB ram and GTX 970.

[Modo44]

The entire AMD 300 series has a known issue under DX11. About every other user experiences memory-related app/driver crashes. This is not resolved even in the most recent beta driver. Sorry to say, you just got lucky before. The only known workaround is to switch down do DX9.

[jay35]

Thorqemada, on 11 October 2015 - 02:58 AM, said:

Use the Catalyst 15.9.1 Beta if you dont - the bug almost disapeared for me:
http://support.amd.c...ndows-beta.aspx

If not Report it to AMD:
http://www.amdsurvey...A1E27D23A3DE979

Thanks, I've sent in a bug report. Am running the 15.9.1 beta. It still happens but possibly less often? Hard to tell yet.

[Modo44]

I had some luck by turning the memory clock down by a couple percent. MWO stopped crashing during matches, only crashes when closing. YMMV

[Kali Rinpoche]

I've had a few of these errors each month. Win 10 64b GTX970 I7 3770k

[amenophis]

I started getting this error after the last patch also. Not very often, only about twice, and I'm using win 7. With a GTS 970 gpu so support can't say there isn't enough memory this time. Also I have 18 gig on the mobo.

Edited by amenophis, 12 October 2015 - 07:47 PM.

[jay35]

Modo44, on 11 October 2015 - 12:26 PM, said:

I had some luck by turning the memory clock down by a couple percent. MWO stopped crashing during matches, only crashes when closing. YMMV

Interesting. I guess I could try that.

Btw, I did run memtest on the system memory and it found zero errors after completing the full 4/4 passes. Is there a similar test available for GPU memory?

Edited by jay35, 11 October 2015 - 11:26 PM.

[Grendel408]

On occasion I get this exact error posted by jay35... frustrating as all hell btw.

Things I've tried...
- Replacing the PSU from 750w to 1050w (didn't help, but I got lots of power now lol)
- Unplugged, completely cleaned GPU of dust, added new thermal paste for processor
- Rewired the PC (odd idea, got better cable management out of it lol fml)
- Contacted Nvidia (Gigabyte's GeForce GTX 660Ti factory OC) with no help on their end "we swear by our product"
- Modified MSI Afterburner profile to feed more power (newer PSU, why not?)
- Uninstalled GPU software and loaded basic drivers <--- This seemed to be the most effective so far short of finding a driver from 12 months ago that Win10 won't like...

It's not MWO, well partially MWO's fault as it's not completely optimized. It's the GPU conflicting with other hardware or encountering a bad Direct3D state and crashes then recovers. The only game this won't crash now surprisingly is War Thunder... it stutters then recovers without CTD.

[Deathlike]

amenophis, on 11 October 2015 - 06:59 PM, said:

I used to get this error a lot and support said I needed more gpu memory so I got a Nvidia GTX 970 4Gig board and haven't seen the error since. I'm running on win 7 tried win 10 but it was messing to many things up for me so I went back to 7.

That's bad.

If you are suffering from memory usage though, lowering the texture quality to low helps (you realistically need 1GB for Medium AFAIK).

jay35, on 11 October 2015 - 11:24 PM, said:

Interesting. I guess I could try that.

Btw, I did run memtest on the system memory and it found zero errors after completing the full 4/4 passes. Is there a similar test available for GPU memory?

Video Memory Stress Test:
http://sourceforge.net/projects/vmst/

That's all I'm aware of.

[Wintersdark]

Have you tried just running under DX9 re: Modo44's post above? If you're stable then, it'll at least help narrow things down.

[jay35]

Hey guys, just checking back in to report that DX9 has been stable so far! Ran it this afternoon and all night, zero crashes, including recording a few matches. So it looks like whatever the DX11 issue is, it's related to that! I'm going to reply to the ticket I submitted to note that. Thanks for the suggestion!