Jump to content

[Bug] Win10 64Bit Frequently Crashes To Desktop With This Error Since Tuesday's Patch


34 replies to this topic

#21 jay35

    Member

  • PipPipPipPipPipPipPipPip
  • The Hammer
  • The Hammer
  • 1,597 posts

Posted 13 October 2015 - 03:49 PM

Update from PGI tech support:

Quote


Also i started doing some research into this and discovered that unfortunately this DXGI_ERROR_DEVICE_REMOVED error is one that occurs with most Cryengine games when using an overclocked graphics card. Unfortunately your AMD R9 390X GPU is factory overclocked which is why you're running into this problem. We're currently working hard on a fix for this issue in the near future that would help eliminate players from running into this issue as much, however currently the only potential workaround for this issue would be to reduce the base clock speeds for this specific GPU through the Asus GPU Tweak II application that should be installed with your GPU. We understand that this is not something that everyone wants to do and we also can't guarantee that this will completely eliminate you from ever running into this issue(that would be up to Raedon to get sorted out with their own driver updates), however from the few users who have decided to try this out the results have been pretty positive when they lowered their clock speed.

(It should also be noted in case you've never customized GPU clock speeds and voltages before to please be careful when making adjustments in this application as raising certain items too much for example can cause issues with your PC moving forward)

Really sorry that there's no real definitive answer here to this issue, however if you have any other questions about this please feel free to let us know and we'll make sure to get back to you as soon as possible.

Thanks,

Technical Support Representative[/color]



So right now I'm stable on DX9 setting, and if I get some time I'll try downclocking my card and running DX11 again. Thought I'm not sure what benefits come with DX11 for MWO so it might be a while before I mess with downclocking the card if DX9 remains stable.

Edited by jay35, 13 October 2015 - 03:59 PM.


#22 Modo44

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bad Company
  • 3,559 posts

Posted 14 October 2015 - 01:49 AM

The DX11 MWO client is currently a bit faster across the board with a couple more effects on top. Since MWO is CPU-bound on modern rigs, downclocking the GPU should not really impact performance. I saw no difference @2560x1600.

#23 Lunatic_Asylum

    Member

  • PipPipPipPipPipPipPip
  • FP Veteran - Beta 1
  • 600 posts

Posted 14 October 2015 - 02:33 AM

I have been running into this problem since 2012 (in other games). NVidia released buggy drivers in 2011 or 2012, fixed them in 2012, and ruined them again in January 2015.
Engines affected: not only Cryengine. I saw at least 3 crashing with that.
Systems affected: Windows 7,8,10 x64.

This error occurs on any operating system with DirectX10 and DirectX11. DirectX9 crashes, but recovers.
There are a lot of games affected by this error, and a lot of cards.
I have found stable NVidia drivers that work well:

344.11 and 344.75. Try them.

This is NVidia's problem, not PGI's or your video card's.

Do not even bother with downclocking or overclocking your GPU. I tried that and installing various video cards.

After the NVidia driver crashes, always reboot your computer.

Edited by Lunatic_Asylum, 14 October 2015 - 02:40 AM.


#24 Modo44

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bad Company
  • 3,559 posts

Posted 14 October 2015 - 04:10 AM

View PostLunatic_Asylum, on 14 October 2015 - 02:33 AM, said:

This is NVidia's problem, not PGI's or your video card's.

Read the ******* posts. OP has a Radeon R9 390X.

#25 Lunatic_Asylum

    Member

  • PipPipPipPipPipPipPip
  • FP Veteran - Beta 1
  • 600 posts

Posted 14 October 2015 - 08:00 AM

View PostModo44, on 14 October 2015 - 04:10 AM, said:

Read the ******* posts. OP has a Radeon R9 390X.


I hope Radeon can get a similar fix then.

#26 Grendel408

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 2,611 posts
  • LocationBay Area, California

Posted 14 October 2015 - 11:02 AM

It's an issue with all factory OC'd GPUs, not just Radeon, but Nvidia as well. As I stated in my post on pg1, this has been happening since I upgraded my GPU to Gigabyte's GeForce GTX 660Ti back around January... prior to that I was running an ATI's XFX Radeon HD6850 with no issue, even OC'd with Catalyst Control Center.

The moment I get a factor OC'd GPU I experience this error on the following games:
MWO, Farcry, Battlefield4, War Thunder, Anno 2550, W40K DoW2, and Homeworld Remastered

Note... I can play for hours at a time, or play for 5 minutes, the time between errors varies wildly and I often restart my PC once this happens... unless it crashed during a MWO match I usually reconnect and try to finish the match... sometimes it crashes within minutes if I don't restart my PC immediately after the CTD/error.

So it's not limited to the Cryengine... it's the damned manufacturers causing the issue. And they will swear by their products and point fingers elsewhere... I'll be upgrading my GPU again after Xmas when I get my tax return and bonus in (building a newer PC basically).

Edited by Grendel408, 14 October 2015 - 11:05 AM.


#27 Nothing Whatsoever

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 3,655 posts
  • LocationNowhere

Posted 14 October 2015 - 05:05 PM

I've been having issues in the Mechlab only so far, when trying to save builds. Here's one of the screens that have not sent an error report (think one or two automatic ones have been made):

Posted Image

So, I'm gonna try and tinker with some settings. See if that might help.

Win 10 Pro 64-bit
GeForce GTX 650 Ti 358.50
AMD FX™-6300 Six-Core 3.50 GHz
32 GB Ram (31.93 usable)

#28 VXJaeger

    Member

  • PipPipPipPipPipPipPipPip
  • The Wrath
  • The Wrath
  • 1,582 posts
  • LocationFinland

Posted 14 October 2015 - 11:52 PM

Don't use/open any internet browsers when playing MWO. Solved my collapsing when I figured that.

#29 Grendel408

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 2,611 posts
  • LocationBay Area, California

Posted 15 October 2015 - 12:41 PM

View PostVXJaeger, on 14 October 2015 - 11:52 PM, said:

Don't use/open any internet browsers when playing MWO. Solved my collapsing when I figured that.

I run dual monitors with Chrome, Teamspeak, MSI Afterburner, and Steam windows running on one monitor while MWO runs on the other... I've also tried running just MWO with no other "active" programs running... that doesn't make a damn bit of difference dude unless you're running in "Fullscreen" mode. I run "Full Window" and can easily ALT-Tab with joyous freedom of MWO not crashing.

The errors are due to poor GPU manufacturing and conflicts with DX11, mostly on x64bit Windows OS computers.

Edited by Grendel408, 15 October 2015 - 12:42 PM.


#30 TyphonCh

    Member

  • PipPipPipPipPipPipPipPip
  • The Clamps
  • The Clamps
  • 1,074 posts
  • LocationDue North

Posted 15 October 2015 - 03:37 PM

I've been having this ever since I started playing MWO. It started out quite rare, then it got to the point where the game was quite literally unplayable.
I sent in a support ticket, and Bobby Jubraj (He's good at his job) looked into it for me. Here's what he had to say

Quote

May 7, 13:12
Hi there,
I looked into this issue for you and discovered that unfortunately this DXGI_ERROR_DEVICE_REMOVED error is one that occurs with all Cryengine games when using an overclocked graphics card. Unfortunately your GeForce GTX 750 Ti is factory overclocked which means there's no workaround for this error. We're trying to work on a solution for this issue that will be implemented in a future patch but until then I don't have any other ways of solving this problem for you.
Really sorry about this response and hopefully soon we'll have a fix for these DXGI errors on factory overclocked cards.
Take care,
Bobby Jubraj
Technical Support Representative
Piranha Games


I ended up doing a full wipe of my computer, and re installing windows and everything. I still get it occasionally, but I guess there's not much I can do in my case.

#31 Lictor

    Member

  • PipPipPip
  • IS Exemplar
  • IS Exemplar
  • 95 posts

Posted 15 October 2015 - 06:45 PM

Win 10 x 64 have not seen this error.

#32 Grendel408

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 2,611 posts
  • LocationBay Area, California

Posted 16 October 2015 - 01:37 PM

View PostLictor, on 15 October 2015 - 06:45 PM, said:

Win 10 x 64 have not seen this error.

Win10x64 will give the error, coming from experiencing it myself ;) I don't contact PGI because I know it's not PGI's fault... it's the GPU manufacturer.

#33 Grendel408

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 2,611 posts
  • LocationBay Area, California

Posted 17 October 2015 - 04:53 PM

and proof...

Posted Image

#34 Grendel408

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 2,611 posts
  • LocationBay Area, California

Posted 19 October 2015 - 10:00 AM

So, switching from DX11 to DX9 does prove to remove this GPU error. I get a random FPS stutter (lags for 5-10 seconds and recovers) here and there in a match, but so far no more errors of the GPU drivers crashing and recovering from a crash.

Basically... the GPUs that receive this error are likely programmed poorly to support DirectX 11... so, not PGI's fault... GPU Manufacturer errors, and no amounts of rolling back drivers or doing stress tests and whatnot will do anything but irritate you. I run tests, GPU, CPU and memory tests on my PC all the time, without error. Get into a game that can run DX11 and get pwned by GPU errors.

Gigabyte GeForce GTX 660 Ti (w/PC capable of supporting it and then some), and it's not limited to Nvidia GPUs, apparently any factory overclocked GPU will give this error.

(edit: typo)

Edited by Grendel408, 19 October 2015 - 10:02 AM.


#35 Lunatic_Asylum

    Member

  • PipPipPipPipPipPipPip
  • FP Veteran - Beta 1
  • 600 posts

Posted 19 October 2015 - 11:37 PM

Try the solution from post #23 here, Grendel.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users