This guide will show you how to fix the Error Code 887A0005 in Black Ops Cold War.
How to fix the Error Code: 887A0005 in Black Ops Cold War
One of the most anticipated games of this year, Call Of Duty Black Ops Cold War has finally been released and the game is doing really great so far. But looks like not everything is perfect in the game at the moment.
Unfortunately, the game is not completely free from performance issues. People are constantly reporting about different error codes that are popping up every now and then. The one I am talking about here is the Error Code 887A0005. Here is what the error actually looks like:
“Unfortunately, The Application Has Unexpectedly Stopped Working
Error Code: 887A0005 (887A0006) (0xB93DE0A6) D”
How to fix
To fix the Error Code 887A0005 you need to go to Graphics settings menu of Black Ops Cold War. This error seems to occurring due to the Ray-tracing settings being turned on in-game. Here is what you need to do:
- Go to Settings
- Click on the Graphics tab
- Scroll down all the way to the Ray Tracing section
- Now disable Ray Tracing Sun Shadow, Ray Tracing Local Shadow and Ray Tracing Ambient Occlusion
- Restart the game
Additionally, you can follow our Black Ops Cold War graphics settings guide, to further optimize the performance of the game. The main aim is to reduce the load on your Graphics Card.
If you think this guide had helped you then let us know in the comment section below. Also, you can check out the other Call of Duty : Black Ops Cold War guides on Frondtech. Good luck!
That’s all folks!
Last Updated on November 30, 2020
Shoaib, 30, is a simple guy who loves to play video games, and enjoys new cuisines sporadically. He has been gaming since he was 7 years old, and with an experience of 22 years, under his belt, there is not a single AAA game in this world, that he hasn’t played. Despite being a MBA Graduate he decided to follow his passion. And because of his love for gaming, Frondtech came into existence.
I have never had ray tracing enabled and basically tried every fix I could possibly find on the internet for this error, but I still seem to get it after finishing almost every single multiplayer match.