Firestorm RTX freeze issue with armor plates

Thanks everyone for coming back with added info. 

@d1art  @J0n1k69  @Grcmrn69  @Skotostras_APEX 

I'm assuming here if you not have tried yet can you try to reinstall the driver for the GPU and see if the same issue happens and do a clean boot to see if there any programs that is helping this to happen. 

/Atic

did not help

---

@EA_Atic wrote:

Thanks everyone for coming back with added info. 

@d1art  @J0n1k69  @Grcmrn69  @Skotostras_APEX 

I'm assuming here if you not have tried yet can you try to reinstall the driver for the GPU and see if the same issue happens and do a clean boot to see if there any programs that is helping this to happen. 

/Atic

---

Atic, this won't help. The issue is not connected only to armor plates. The game is currently unplayable with DXR / RTX enabled ! Check out my post and also other guys posts here https://answers.ea.com/t5/Technical-Issues/PC-Crashing-issue-Information-request/m-p/7775377#M11941 - one of the latest feedbacks atm. Everyone who is playing with DXR enabled is experiencing crashes to desktop.

DICE must know about this and fix it, because it's been 4 months since we have this issue !!!

---

@BoneStang wrote:

Here is my dxdiag file. Also since this issue with armor plates doesn't cause the game to crash, there is nothing in the event viewer to show regarding this issue. Its just a 1-3 second freeze, then the game resumes normally. 

I do have a crash from BFV.exe, but this crash is a different issue where the game crashes while launching/loading the new round of firestorm in a squad. Here it is below incase this helps at all:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="Application Error" />

  <EventID Qualifiers="0">1000</EventID>

  <Level>2</Level>

  <Task>100</Task>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2019-03-28T02:32:03.467586200Z" />

  <EventRecordID>2680</EventRecordID>

  <Channel>Application</Channel>

  <Computer>BD-SSD</Computer>

  <Security />

  </System>

- <EventData>

  <Data>bfv.exe</Data>

  <Data>1.0.70.49765</Data>

  <Data>5c8eb655</Data>

  <Data>KERNELBASE.dll</Data>

  <Data>10.0.17763.348</Data>

  <Data>d620e319</Data>

  <Data>887a0005</Data>

  <Data>0000000000039149</Data>

  <Data>3110</Data>

  <Data>01d4e508d3d5dfe6</Data>

  <Data>H:\Origin Games\Battlefield V\bfv.exe</Data>

  <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>

  <Data>1f30c028-1363-4054-9c46-1bf878dbe02e</Data>

  <Data />

  <Data />

  </EventData>

  </Event>

---

You will find your error code in this line - 887a0005. This is the error code you're getting. This is a DirectX error code, as well as this one 887a0006. I'm getting both of this at random ONLY with DXR enabled.

How long should we wait until we can play with DXR?

---

@EA_Atic wrote:

Thanks for the update! 

 

I have sent it on to the team and they are looking into the issue, for lag while picking up armour plate with RTX/DX12 on. 

 

/Atic 

---

Please, tell them that there are also crashes with only DXR enabled! It's not only connected to the armor plates!

Thank you in advance.

@EA_Atic 

Same..

This is not an Option, which will help to fix our issues. 

Please check and clarify this from EA  <> Developer and also NVIDIA side. 

After more then 4 months of BF5 RTX release and more then hundreds or maybe thousands, of High-End Gaming Desktop issue Reports.

It is time to got fixed as soon as possible!!!

This is an quality breach of EA.

We are aware of crashing issues with DXR and dx12 for Battlefield V, the team are investigating those issues. 
 
No eta currently for a fix has been announced, I'll try to keep this as up to date as possible. 
 
/Atic 

---

@EA_Atic wrote:

We are aware of crashing issues with DXR and dx12 for Battlefield V, the team are investigating those issues. 
 
No eta currently for a fix has been announced, I'll try to keep this as up to date as possible. 
 
/Atic 

---

I hope this won't be left in the dust. If you manage to keep this up to date and the developers fix it, you deserve a raise, because you're the first one who actually reported this for the past 4 months.