Engine Error 0x887A0006 - DXGI_ERROR_DEVICE_HUNG

Product: Apex Legends
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number Intel i5 4690K
Enter RAM memory size in GB 8 GB
What is your gamertag/PSN ID/EA Account name? Fullmoon123P
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible.
Which Legend were you playing (if applicable)? All of them
Which Legends were your squad mates using (if applicable)?
Where did the issue occur? In a match
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. All parts of the map, even flying in.
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. Flying in, shooting, revivng, anything... happens every 15, 30 minutes.
Did your squad mates also experience the issue? I don't know
How many matches had you played in a row before the issue occurred? Always had issue
When did this happen? (dd.mm.yy hh:mm) All the time since I downloaded
How often does the bug occur? Every time (100%)
How severe is your issue? Major impacts to gameplay
What happens when the bug occurs? I get to play some gameplay, sometimes I actually get to play games through... But whenever I play I end up crashing with the error, "0x887A0006 - DXGI_ERROR_DEVICE_HUNG The applications device failed due to badly formed commands sent by the application. This is an design-time issue that should be investigated and fixed."
What should be happening instead? Not to crash.
Steps: How can we find the bug ourselves? IDK

‌

Ive tried everything in all tutorials... even dropping my graphics to the lowest quality, bordered, borderless, restart easy anticheat on crash, revert drivers, update drivers, clean boot, anything, you name it. Please help me play this awesome game.

Bumpers

apex legends 0x887a0006 dxgi_error_device_hung problem still there no one get solve it s mostly getting by RTX CARDS.Pls dont ignore we cant play.

I'm honestly beyond frustrated at this point, could not play properly since season 2 launched because I would get this error multiple times each day (ofcourse not even including the infamous code:leaf and the newly introduced code:net).

I waited patiently for Respawn to fix this and I thought that today's update would at least make it better...Well it actually got worse as it always does with this game! I've now tried 6 times to play a game of Solo and each time I faced either the error named in the title or code:net. This is ridiculous, I play quite a few current games on my PC, NONE of which have issues.

At least call it what it is - an early Alpha (with EA's greed machine integrated into the heart of the game)

Does anyone have any clue on what to do to improve this? So I could atleast play for a couple of hours a day uninterrupted? GPU is a RX 580 8GB

Apex_crash.txt:

crash:
{
R5Apex: 000000000035A6E6
EXCEPTION_ACCESS_VIOLATION(read): 0000000001000019
}
callstack:
{
KERNELBASE: 00000000000EBDD0
ntdll: 00000000000A3167
ntdll: 000000000008B5E6
ntdll: 000000000009F7DD
ntdll: 000000000000D856
ntdll: 000000000009E70E
R5Apex: 000000000035A6E6
R5Apex: 00000000004C04BD
R5Apex: 00000000004BFEA6
R5Apex: 00000000004C0297
R5Apex: 00000000004BEAB7
R5Apex: 00000000004C0852
KERNEL32: 0000000000013DC4
ntdll: 0000000000073691
}
registers:
{
rax = 0x01000001
rbx = 0x00007FF769E0E5F0
rcx = 0x00007FF750036CF8
rdx = 0x000001AD562357D0
rsp = 0x0000007E38D5E160
rbp = 0x00007FF750036CF8
rsi = 0x000001AD562357D0
rdi = 0
r8 = 0x0000007E38D5E1C0
r9 = 0x0000007E38D5E1B0
r10 = 2047 // 0x000007FF
r11 = 0x00007FF76AE0F540
r12 = 8
r13 = 0
r14 = 222
r15 = 64
rip = 0x00007FF74437A6E6
xmm0 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm1 = [ [1, 0, 0, 1], [0x3F800000, 0x00000000, 0x00000000, 0x3F800000] ]
xmm2 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm3 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm4 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm5 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm6 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm7 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm8 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm9 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm11 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm12 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm13 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm14 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm15 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
}

Hey all,

Can you attach a DxDiag for us so we can look at your system specifications?

If you haven't searched "DXGI_ERROR_DEVICE_HUNG" in the search bar there are more than a handful of posts with fixes that have worked for various players. If there's anything specific that helped be sure to relay it here so others can give it a try.

NVIDIA Customer Care recently posted requesting info here: https://answers.ea.com/t5/Technical-Issues/Apex-legends-dxgi-error-device-hung/m-p/8116531/highlight/true#M48648

How to Pull a DxDiag

https://help.ea.com/en-us/help/pc/how-to-gather-dxdiag-information/

im a amd user that started getting this after this new patch and it's really frustating im not even getting to enjoy the game and with limited time event i hope it gets fixed before it's over and i don't get try wining it

i tried resting my pc, tld delay, adding virtual ram, changed the amd driver to older versions and nothing changed

i also found this apex crash file not sure if it's related

crash:

{

R5Apex: 000000000047DC8D

EXCEPTION\_ACCESS\_VIOLATION(read): 0000000000000026

}

cpu: "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz"

ram: 16 // GB

callstack:

{

KERNELBASE: 00000000000EBDC0

ntdll: 00000000000A3167

ntdll: 000000000008B5E6

ntdll: 000000000009F7DD

ntdll: 000000000000D856

ntdll: 000000000009E70E

R5Apex: 000000000047DC8D

R5Apex: 0000000000482D4E

R5Apex: 000000000040BA93

R5Apex: 000000000040B117

R5Apex: 000000000040D4AE

R5Apex: 00000000004B87FA

R5Apex: 00000000004B91A2

R5Apex: 00000000004BA0B2

R5Apex: 00000000004BAAE6

R5Apex: 00000000004BAE5B

R5Apex: 000000000022BD89

R5Apex: 000000000022DA26

R5Apex: 00000000002290B7

R5Apex: 000000000049DB8A

R5Apex: 000000000049DC6E

R5Apex: 000000000049DDC7

R5Apex: 00000000004C0B56

R5Apex: 00000000004C0F47

R5Apex: 00000000004BF767

R5Apex: 00000000004C1502

KERNEL32: 0000000000014034

ntdll: 0000000000073691

}

registers:

{

rax = 0         

rbx = 0x000000F072FBED00

rcx = 0x000000F072FBED00

rdx = 18        

rsp = 0x000000F072FBEC40

rbp = 524304 // 0x00080010

rsi = 0x00000274544E5838

rdi = 0         

r8  = 0x000000F072FBED00

r9  = 0         

r10 = 0x00000274544E5838

r11 = 0x00007FF7218B2278

r12 = 0x02005A52

r13 = 0x00000274872D6604

r14 = 0x00000274544E5868

r15 = 0         

rip = 0x00007FF7209BDC8D

xmm0  = \[ \[5.5491419e-43, 0, 1.1070258e-43, 0\], \[396, 0, 79, 0\] \]

xmm1  = \[ \[9.1835496e-41, 0, 0, 0\], \[65536, 0, 0, 0\] \]

xmm2  = \[ \[0, 0, 0, 0\], \[0, 0, 0, 0\] \]

xmm3  = \[ \[0, 0, 0, 0\], \[0, 0, 0, 0\] \]

xmm4  = \[ \[0, 0, 0, 0\], \[0, 0, 0, 0\] \]

xmm5  = \[ \[0, 0, 0, 0\], \[0, 0, 0, 0\] \]

xmm6  = \[ \[1, 0, 0, 0\], \[0x3F800000, 0x00000000, 0x00000000, 0x00000000\] \]

xmm7  = \[ \[3.0517578e-05, 0, 0, 0\], \[0x38000000, 0x00000000, 0x00000000, 0x00000000\] \]

xmm8  = \[ \[0, 0, 0, 0\], \[0, 0, 0, 0\] \]

xmm9  = \[ \[0, 0, 0, 0\], \[0, 0, 0, 0\] \]

xmm10 = \[ \[0, 0, 0, 0\], \[0, 0, 0, 0\] \]

xmm11 = \[ \[0, 0, 0, 0\], \[0, 0, 0, 0\] \]

xmm12 = \[ \[0, 0, 0, 0\], \[0, 0, 0, 0\] \]

xmm13 = \[ \[0, 0, 0, 0\], \[0, 0, 0, 0\] \]

xmm14 = \[ \[0, 0, 0, 0\], \[0, 0, 0, 0\] \]

xmm15 = \[ \[0, 0, 0, 0\], \[0, 0, 0, 0\] \]

}

build_id: 1554860081

ok so i just fixed it i think, played for stright two hours with no crash

basically used radeon version 18.2.2 ( saw it in another website)

with command line arguments:

+fps_max 60

hopefully they fix this though as i would rather be playing on new drivers but this will do i guess

---

@g1g2_mozo wrote:

ok so i just fixed it i think, played for stright two hours with no crash

basically used radeon version 18.2.2 ( saw it in another website)

with command line arguments:

+fps_max 60

hopefully they fix this though as i would rather be playing on new drivers but this will do i guess

---

Thank you for relaying that back to everyone, @g1g2_mozo!

@hompalumpasan  @TwonMcFry  @Pauliusenko  @YKahveci 

Does this work for you?

Also, try right-clicking on the game in Origin and select "repair." We've seen that work for this particular error recently.

Thanks for rounding everyone up @EA_Blueberry 

I'm sorry but I'm not about to downgrade my drivers 2 years back because someone said they played for 2 hours without crashing...