test content
Logo
What is the Arc Client?
Install Arc
Options
[PC]Game Crash - Suspect DX11
veepeeza
Member Posts: 3 Arc User
Hi guys. Had this problem for quite some time, thought I'd post here as a last resort.
For some reason my game has been crashing since the 'swap' to Direct X11. Running the game in Safe Mode seems to solve the issue, but any other setting crashes the game after +-5 minutes of play (seems random) with a Direct X error message (sadly I've not saved it, but it was something along the lines of Direct 3D hanging/D3D device not responding).
I've tried many fixes (including the ones found in this forum and on Steam discussion pages, as well as those I've found through Google) to no avail.
I'd like to know if the command line command -d3d9 still does anything? I doubt it, but thought I'd check. If i can force the game to run Dx9 I think it may solve my problem, but as far as I'm aware this isn't possible with the current version?
PC Specifications:
Windows 7 Ultimate 64b
i5 - 3570k
8GB Corsair Vengeance DDR3 Ram
Radeon R7 360 (worst mistake I've ever made was swapping from nVidia to Radeon, but don't think this is the cause of the issue, as other games work fine - as long as they don't run DX11).
Evident by running both Warframe and Path of Exile in Dx9 mode vs Dx11 mode, as the latter also causes crashes in those games.
Any ideas? I don't mind playing in Safe Mode, but hard to enjoy new content when everything is this ugly!
Thanks in advance! Will update if I get the same error message with aforementioned message.
For some reason my game has been crashing since the 'swap' to Direct X11. Running the game in Safe Mode seems to solve the issue, but any other setting crashes the game after +-5 minutes of play (seems random) with a Direct X error message (sadly I've not saved it, but it was something along the lines of Direct 3D hanging/D3D device not responding).
I've tried many fixes (including the ones found in this forum and on Steam discussion pages, as well as those I've found through Google) to no avail.
I'd like to know if the command line command -d3d9 still does anything? I doubt it, but thought I'd check. If i can force the game to run Dx9 I think it may solve my problem, but as far as I'm aware this isn't possible with the current version?
PC Specifications:
Windows 7 Ultimate 64b
i5 - 3570k
8GB Corsair Vengeance DDR3 Ram
Radeon R7 360 (worst mistake I've ever made was swapping from nVidia to Radeon, but don't think this is the cause of the issue, as other games work fine - as long as they don't run DX11).
Evident by running both Warframe and Path of Exile in Dx9 mode vs Dx11 mode, as the latter also causes crashes in those games.
Any ideas? I don't mind playing in Safe Mode, but hard to enjoy new content when everything is this ugly!
Thanks in advance! Will update if I get the same error message with aforementioned message.
1
Comments
In my case, this happens specifically when quickly swapping or using lots of encounter powers within a 1-2s timeframe. I don't believe that this is a driver issue with any input device however, as the crash has been caused by both a laptop integrated keyboard, mechanical and non mechanical keyboard as well.
I also don't think that this is a windows related error as no such crash occurs when typing, which handles a lot more key-presses per second than the game engine does.
I'm also pretty sure it's only a HR Trapper related bug as I log no where near the number of key-presses per second on any of the other classes or builds.
Point is, something in the DX11 update has seemingly changed the way the game engine interacts with the computers drivers that causes an error on a certain number of key-presses per second (Also includes mouse inputs).
So if the OP notices that this crash occurs for them after seemingly pressing keys, please let me know.
On a more positive note, I've managed to update to Direct X 11.1 and since then have experienced only one crash in about 12 hours worth of play. Seems to have solved the issue. In fact, even my Warframe runs better since disabling DX10/11 (but only after updating to 11.1).
Hope this can help someone else around, mods can lock this post as it seems to be solved.
Here is the screenshot of the message when game crashes: https://prnt.sc/gmfwxy
Yet I navigate internet without probs
suggestions?
thanks
@skandranon68 bud this isn't the right post for your problem, you should probably create a new thread for that.
The application's device failed due to badly formed commands sent by the application. This is an design-time issue that should be investigated and fixed.
Apparently other games besides NWO haven encountered this problem when switching to DX11 back over the past 2 years. This is what the developers came up with over at EA came up with on another BIOWARE game they own. The issue is encountered on high-end Nvidia and AMD GPUs, when a "graphics spike" occurs in the game. Their workaround was to "dumb down" or "underclock" your graphics card.
This error was posted to several gaming forums and apparently current drivers and top of the line graphics cards are not the solution. In my opinion, this is a good example of Microsoft having this universal tool (DirectX) and too many games with old 32 bit code wanting to be top of the food chain. Who is to blame? No one or everyone, as MS is clearly passing the blame to the application for sending "badly formed commands" and the game company blames you the end user for not having the latest version of DirectX drivers. Then you blame the manufacturer of the video card for bad drivers, and they put the blame back on DirectX. Around and around it goes... it hasn't been fixed since 2015 and we are almost to 2018.
I wish you the very best.
Timeout Detection and Recovery is a Windows feature that can detect when the video adapter hardware or a driver on your computer has taken longer than expected to complete an operation. When this occurs, Windows attempts to recover and reset the graphics hardware. If the GPU is unable to recover and reset the graphics hardware in the time permitted (two seconds), your system may become unresponsive, and display the error message Display driver stopped responding and has recovered. Giving the Timeout Detection and Recovery feature more time to complete (8 seconds) this operation by adjusting the registry value, may resolve this issue. To do this, follow these steps: 1. Exit all Windows based programs. 2. Select Start, type regedit in the Search box, and then double-click regedit.exe from the results above. 3. Locate to the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers 4. On the Edit menu, select New, and then select the following registry value from the drop-down menu specific to your version of Windows (32 bit, or 64 bit): 5. (a) For 32 bit Windows Select DWORD (32-bit) value. Type TdrDelay as the Name and then select Enter. Double-click TdrDelay and add 8 for the Value data and then select OK. 5. (b) For 64 bit Windows Select QWORD (64-bit) value. Type TdrDelay as the Name and then select Enter. Double-click TdrDelay and add 8 for the Value data and then select OK. 6. Close Registry Editor and then restart your computer for the changes to take effect.He said, it works like a charm. I hope it works for you too.
win 7 64 bit, 290x vga
i get the device hung, and device removed? error. mainly in certain dungeons but a few during transition screen loading as well.