Jump to content

D3D Device Hung


19 replies to this topic

#1 C E Dwyer

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 9,274 posts
  • LocationHiding in the periphery, from Bounty Hunters

Posted 29 June 2015 - 06:58 AM

This error is getting tiresome

It only happens in MWO, my dozen or so games on this PC, do not get effected by it.

Usually happens at the start of a match game freezes crashes the game, sometimes it will restart fine, others like today, not so, as logging in results in a login screen freeze and the error message in title.

run repair tool Tracert seems fine

Will be effected for about two days, and then will resolve itself, well that's whats happened so far, hopefully something is being done to get ride of these errors.

Anyone else having these 'fun' problems ?

Edited by Cathy, 29 June 2015 - 06:59 AM.


#2 9erRed

    Member

  • PipPipPipPipPipPipPipPip
  • Overlord
  • 1,566 posts
  • LocationCanada

Posted 02 July 2015 - 07:48 PM

Greetings,

That error, DXGI_ERROR_DEVICE_HUNG 0x887A0006
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.

1. Some instances suggest checking for updated graphics drivers.
2. Some list an overheating problem as a start cause for this error.
3. Some list updating the Dx runtimes, (insuring that Dx9c and Dx11 are both installed, and up-to-date.)
4. The driver or D3D runtime could run out of memory in a place that isn't recoverable.

Are you running the game in Dx9 or Dx11 mode?
Do you have a sufficient system to run at the settings you have selected in game?

You stated that "after a few days, it corrects itself". Is this after a reboot of the computer? Or just time running and other applications opened and closed? Are you running stock or overclocked settings? Pc or laptop?

9erRed

Edited by 9erRed, 02 July 2015 - 08:05 PM.


#3 MacKJames

    Member

  • PipPip
  • The Predator
  • The Predator
  • 41 posts

Posted 14 July 2015 - 12:23 PM

Ya I've been having this issue lately.

#4 andrewkhlim

    Member

  • PipPipPip
  • The Infernal
  • The Infernal
  • 93 posts
  • LocationSydney, Australia

Posted 15 July 2015 - 01:50 AM

It happen frequently to me in the previous patch even after a fresh install of everything. Less so now, and less when I'm not running duel screens. Don't know what the solution is.

#5 CeKay

    Rookie

  • The Butcher
  • The Butcher
  • 4 posts

Posted 09 September 2015 - 04:23 AM

I have this error since one of the last patches. Normally, if I get the crash, i can restart the game normally. But yet, i get the crash in the loading screen direct after the login. Repair tool says, all is find. And MWO is the only game with that issue. A Solution would be nice.

#6 BritishBeef

    Rookie

  • 3 posts
  • LocationLondon

Posted 28 September 2015 - 02:03 PM

Same problem for me. Very annoying.

#7 Goose

    Member

  • PipPipPipPipPipPipPipPipPip
  • Civil Servant
  • Civil Servant
  • 3,463 posts
  • Twitch: Link
  • LocationThat flattop, up the well, overhead

Posted 29 September 2015 - 05:06 PM

Like this?

Posted Image

Your video cards' overclock doesn't like your current video driver revision: Adjust clocks as you see fit …

#8 SoYFooD

    Member

  • PipPip
  • Overlord
  • Overlord
  • 29 posts

Posted 01 October 2015 - 11:47 AM

i get the error even if i dont overclock. any more help is apreciatid

#9 John Cooke

    Member

  • PipPip
  • Elite Founder
  • Elite Founder
  • 21 posts

Posted 04 January 2016 - 04:55 PM

Did you guys ever found a way to resolve this?

I get the exact message Goose posted, my card is not being over clocked.

I didn't have this message until I upgraded motherboard and cpu, the rest of my components are the same as in my old rig.

Since I had to reinstall the OS I started with win 10 and the error appeared like every match, I went back to win 8.1 and it happens less but it's still there, noticed it happens the most on tourmaline desert.

All drivers are up to date, guess I should have stuck with my old cpu/mobo combo lol.

Any help is appreciated peeps.

#10 Tarl Cabot

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Tai-sho
  • Tai-sho
  • 7,643 posts
  • LocationImperial City, Luthien - Draconis Combine

Posted 04 January 2016 - 07:35 PM

What card do you have? It may have been OC from the mfg. What PSU do you have?

Did you check for an updated bios for motherboard and video card?

To test, underclock the GPU.

#11 SKOLLEVOLLE CII STAR

    Rookie

  • Mercenary
  • Mercenary
  • 8 posts
  • LocationLa Nummelha

Posted 06 January 2016 - 05:10 AM

Playes advice Broadband 100 Mgbits/s sayed to be standard speed devece for gaming. I have that same disconnection when computers line from modem to network card dislocates from leg movement under my table.

#12 John Cooke

    Member

  • PipPip
  • Elite Founder
  • Elite Founder
  • 21 posts

Posted 07 January 2016 - 06:18 PM

View PostTarl Cabot, on 04 January 2016 - 07:35 PM, said:

What card do you have? It may have been OC from the mfg. What PSU do you have?

Did you check for an updated bios for motherboard and video card?

To test, underclock the GPU.


I have a pair of evga's gtx 570's, they are running at 732 mhz which is the stock speed of these, I will under clock and see what happens.
My psu is a 1000w 80 plus gold, which is the same I have been using before the upgrade.

The mobo is an msi Z97x-SLI and the cpu is an i7 4790, oddly I found a post from another guy who had the same issues with the same mobo\cpu combo.

I've just updated BIOS and chipset drivers, issue is still happening.

This seems to happen with all games that use cryengine from what I have investigated.

#13 p4r4g0n

    Member

  • PipPipPipPipPipPipPipPip
  • Knight Errant
  • 1,511 posts
  • LocationMalaysia

Posted 07 January 2016 - 09:18 PM

Used to encounter BSDs and error messages similar to the above at least once a gaming session when still on Window 7. Fixed it with the timer resolution reset to maximum.

Used this but similar tools available online - http://www.lucashale...mer-resolution/

Since I did a clean Windows 10 install, have not had this problem.

Note: This increases power consumption.
Note 2: This tool has to be run after every reboot which is great if you want to keep your power consumption optimal when you are not gaming.

#14 Volts

    Member

  • PipPipPipPipPipPip
  • The Blade
  • The Blade
  • 204 posts

Posted 08 January 2016 - 05:21 AM

I was getting this message fairly frequently since moving to Steam, however new drivers resolved for me.

#15 Oderint dum Metuant

    Member

  • PipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 4,758 posts
  • LocationUnited Kingdom

Posted 13 January 2016 - 11:39 AM

Tarl is right usually this error is down to GPU issues be it unstable clocks or more permanent damage or overheating.

Even factory overclocked cards can develop this problem on rare occasions it could also be down to PSU age/fault

#16 IcySpy

    Member

  • PipPip
  • Ace Of Spades
  • Ace Of Spades
  • 46 posts
  • LocationPoland

Posted 15 January 2016 - 08:29 AM

Exactly same message as the one Goose posted, first crashed in the middle of a game, then twice right after loading into a match. The gpu is almost brand new, maybe a month old.

#17 jjm1

    Member

  • PipPipPipPipPipPipPipPip
  • Hell Fork
  • Hell Fork
  • 1,384 posts

Posted 16 January 2016 - 03:59 AM

I was crashing an average 30 seconds into a match once every 10 or so matches. Sent in a bunch of error reports before I started fiddling with my settings.

system: GTX 660 ti, Core i7 920, Asus P6t mobo, 12GB Ram, Corsair 450w PSU
Windows 10 on SSD, MWO on WDBlue,.

Its old but its been rock solid with many hours of CryEngine, UnrealEngine etc. which is why I didn't jump to hardware issues.

I was using Fullscreen and switched to Fullscreen windowed and continued on my way, it crashed at the roughly expected time but this time it was a BSOD PAGE_FAULT_IN NON-PAGED_AREA. I inspected the crash dump and it pointed the blame at realtek drivers (shocking I know)

I switched off two Nvidia HD Audio drivers, turned off some software I use called Voicemeeter (but not its drivers) Expecting the worst I kept playing Fullscreen window DX11 and hasn't happened so far in many matches. One (or none) of these steps fixed my problem.

hopefully that helps someone.

If not check what other driver combos are running on your system, don't ask why this game and no others have caused me so many problems.

Also I use Avast and turned it and its hardware assisted virtualisation option off as described in another thread. Seemed to make no difference, I've been running with Avast turned on since switching to fullscreen windowed.

Ill update if I end up crashing again.

tl;dr
try fullscreen windowed at your native resolution, its better in every way anyway.

#18 Tin Roof Rusted

    Member

  • PipPip
  • Philanthropist
  • Philanthropist
  • 24 posts

Posted 19 September 2019 - 03:56 PM

I've got a few of these errors lately also and it seems to be random. It just did it a few min ago when I had game minimized while looking on the web at builds.

My dxdiag is showing these errors but I have no idea what they mean so maybe someone else does.

---------------
Diagnostics
---------------

Windows Error Reporting:
+++ WER0 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffa4098a2a0040
P3: fffff807214dc988
P4: 0
P5: 20d0
P6: 10_0_18362
P7: 0_0
P8: 256_1
P9:
P10:


+++ WER1 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffa4098a2a0040
P3: fffff807214dc988
P4: 0
P5: 20d0
P6: 10_0_18362
P7: 0_0
P8: 256_1
P9:
P10:


+++ WER2 +++:
Fault bucket 1336213084316235136, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: MWOClient.exe
P2: 1.4.216.0
P3: 5d5f4dca
P4: MSVCR100.dll
P5: 10.0.40219.1
P6: 4d5f034a
P7: 40000015
P8: 00000000000761c9
P9:
P10:


+++ WER3 +++:
Fault bucket 2169677069212217939, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.Windows.ShellExperienceHost_10.0.18362.267_neutral_neutral_cw5n1h2txyewy
P2: praid:App
P3: 10.0.18362.267
P4: 5d36b38f
P5: msvcrt.dll
P6: 7.0.18362.1
P7: f5bdefd7
P8: 40000015
P9: 000000000000ae72
P10:


+++ WER4 +++:
Fault bucket 2044942504431529237, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: svchost.exe_DevicesFlowUserSvc
P2: 10.0.18362.1
P3: 32d6c210
P4: KERNELBASE.dll
P5: 10.0.18362.267
P6: f09944f9
P7: 000006d9
P8: 000000000003a839
P9:
P10:


+++ WER5 +++:
Fault bucket 2169677069212217939, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.Windows.ShellExperienceHost_10.0.18362.267_neutral_neutral_cw5n1h2txyewy
P2: praid:App
P3: 10.0.18362.267
P4: 5d36b38f
P5: msvcrt.dll
P6: 7.0.18362.1
P7: f5bdefd7
P8: 40000015
P9: 000000000000ae72
P10:


+++ WER6 +++:
Fault bucket 2044942504431529237, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: svchost.exe_DevicesFlowUserSvc
P2: 10.0.18362.1
P3: 32d6c210
P4: KERNELBASE.dll
P5: 10.0.18362.267
P6: f09944f9
P7: 000006d9
P8: 000000000003a839
P9:
P10:


+++ WER7 +++:
Fault bucket 1336213084316235136, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: MWOClient.exe
P2: 1.4.216.0
P3: 5d5f4dca
P4: MSVCR100.dll
P5: 10.0.40219.1
P6: 4d5f034a
P7: 40000015
P8: 00000000000761c9
P9:
P10:


+++ WER8 +++:
Fault bucket 2169019842620818406, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: MWOClient.exe
P2: 1.4.216.0
P3: 5d5f4dca
P4: MWOClient.exe
P5: 1.4.216.0
P6: 5d5f4dca
P7: c0000005
P8: 0000000001308908
P9:
P10:


+++ WER9 +++:
Fault bucket 2124821849995390366, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: MWOClient.exe
P2: 1.4.216.0
P3: 10.0.18362.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

#19 MrStude2r5

    Member

  • Pip
  • Elite Founder
  • Elite Founder
  • 11 posts
  • LocationCanada

Posted 02 October 2023 - 06:00 PM

[color=#959595]One other thing I can suggest, though I didn't do it personally (yet), is for you to try uninstalling the latest drivers from NVidia and installing a driver that is a few generations old--maybe 300.xx or something similar. You can find old NVidia drivers by googling or if you saved old versions (like I did) you can just use that up. (Since your card is relatively old it wouldn't make a difference in drivers detecting your card properly but it just might give you the fix to the problem?) I am pretty sure it's MWO originated, but, it maybe playing badly with the new drivers from NVidia as well. After that, I don't know what to say but to wait for a fix from either/or NVidia/MWO. Some people complain that the Community Warfare frame rate is terrible, so that may have something to do with that (for the last 2 patches). I don't know for sure myself. Also, google up iObit program called "Driver Booster" and update your drivers (it's free) and see if that helps.[/color]

[color=#959595]Win 11 x64, this worked for me, went back to end of July 2023 drivers !! Whamo, no more crashes. !![/color]

#20 Ignatius Audene

    Member

  • PipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 1,161 posts

Posted 07 November 2023 - 10:09 PM

2019... I think he solved the problem in the meantime

Edited by Ignatius Audene, 07 November 2023 - 10:23 PM.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users