Unreal Engine Error 887a0006

0 views
Skip to first unread message

Mahmod Ohner

unread,
Aug 5, 2024, 9:46:33 AM8/5/24
to quivoidaha
Ijust upgraded my graphic card from a 5700 XT to a 7900 XT as I am developing a game in UE 5.1. Well after I changed the card I get constant crashes in UE5.1 editor and also in the game. It is always the same error and it always happen when the same actor/model is loaded into the map (I need to do some research to figure out which one), It is some part of my city so some building or something like that I guess. If I switch to directX11 then everything runs perfectly. I have seen some other posts related to this issue from some months ago but it seems they did not fix the issue. I tried all the different solutions I found online and none worked for me.

EDIT: For example to reproduce the error with the Hong kong kit from kitbash and enable nanite with the mesh : KB3D_HOK_BldgLgCondos_A_BuildingD.

It seems the crashes are related to Nanite and some meshes.


Hoping someone on team red will work with EPIC over some of these issues please. Radeon cards have been broken on Unreal Engine for about 4 months now. I'm talking about working in the actual game engine...not playing UE games. So please understand that. Ray-tracing has been giving all kinds of glow issues when enabled. There's a few threads on UE forums over this. And with UE 5.2 preview 2, the issues still persist making me think no one is trying to resolve this. Having to disable sm6 or roll back to 5.0.3 is only a temporary fix.


I've done alot of testing and found that I just can't get nanite working with this card in my project. It works in very small amounts, but my project is large and I get immediate crashes with the driver error: 'UE 5.1 gpu crashed or d3d device removed' and the following UE error.


The best part of this all... AMD is completely silent on it. They aren't even acknowledging this is an issue, possible consumers aren't even warned that 6XXX and 7XXX is are completely incompatible with several DX12 applications. If you force DX11 via argument these crashes go away completely, which makes AMD cards... literally valueless, nearly a scam and AMD is saying NOTHING.


Can you please try adjust your TDRDelay etc via the registry.



Copy and past this into a .reg file, apply it, reboot then see.

Make sure to back up old settings if unsure, this is a step we have to do to run substance painter properlly as well and it fixed crashes in UE for me...



Side note: I've noticed in UE5, DX11 performance is horrible on AMD, even with Virutal Shadow Maps turned off, its still like 20fps slower than DX12 for me on my 6900xt.






Yeah forcing DX11 arguments I noticed a massive drop in performance, as well as games made for it natively like Deus Ex Mankind Divided I am seeing a drop to 15fps from a consistent vsynced 60 no drops what-so-ever.


HUMM I will give that a shot, XFX wants me to send the card in so they can test and validate it, my hopes is they see the issue and they talk to AMD and maybe AMD will stop pretending this doesn't exist... TDR Delays are just to detect driver timeouts I assume by the name of it?


Why is this happening when I am getting like 110 FPS in Phantom brigade no hitches etc, and soemtimes the game can go for 8-10 hours no driver hangs and others 20 mins. It's so bizarre. I'll give it a shot though, and I'll send the information to XFX.


I had already tried playing with my TDR and it did not help. Also the crash happens instantly with DX12 and never with DX11 which makes it seem very unlikely that it is related to the TDR. I'm fairly certain it is the result of some specific DX12 driver issue.


There are absolutely no fixes, and you are rolling the dice with this GPU. AMD is not acknowledging this. But looking more into it, this issue is affecting hundreds of users who have started hardware surveys, they are spending hundreds of hours trying to fix their own GPUS... and AMD is completely stonewalling us.




This affects random games, you have no idea what you will be able to run, or not. It is driver side, it is AMD side. They have somehow made the 7900 XTX and 7XXX series completely unstable across multiple random games while stable on others. Hundreds of hardware configs, all have this intermitted and random issue, all of it are driver hangs and crashes. AMD is completely ignoring this.


I have been talking to AMD for months now... and they just keep asking me for DXDiag and MSinfo, over, and over, and over again. Some people get lucky and the majority of their games work... others do not. One thing that is actually consistent is that Gamers Nexus, Hardware Unboxed, AMD, etc are all ignoring this and sweeping it under the rug while they focus on nothing but modern games and addressing whatever inherent driver issues are here.


By updating Unreal Engine, Windows, and Steam, you make sure that all components speak the same language and work together smoothly. Updates often include important patches for bugs or compatibility issues that, if left unaddressed, could cause errors. Regular updates maintain system stability and can often be the simplest fix to such frustrating problems.


When you disable the onboard graphics, you basically optimize the process by which your system decides which graphics unit to use for rendering. This action eliminates any confusion that might occur when both onboard (integrated) and dedicated graphics cards are trying to run simultaneously.


These security programs scan every operation on your system to intercept malicious activities. Sometimes, they are overprotective and mislabel legitimate software, like Unreal Engine, as a potential threat, thereby restricting its access to essential system resources.


Overclocking forces your CPU and GPU to operate at speeds higher than their factory settings to enhance performance. However, this can introduce instability and lead to errors with demanding applications like Unreal Engine. Restoring these components to their default speeds can eliminate these conflicts.


Similarly, SLI technology links multiple NVIDIA GPUs to produce a combined output, which can also cause compatibility issues with certain programs. Deactivating SLI can ensure that Unreal Engine only utilizes a single graphics processor, thereby preventing the error from occurring.


By switching to Windowed mode, you allow the system to manage these interactions better, potentially avoiding the issue causing Unreal Engine to lose connection with the D3D device. This small adjustment often results in increased stability, especially if the error is related to display or graphics driver conflicts.


By adjusting your FreeSync monitor settings, particularly toggling the Full-Screen option or enabling settings for a selected display, you can create a more stable environment for the engine to operate in, potentially avoiding the D3D device errors.


fellow StackExchange community.Probably everyone who has worked with Unreal Engine 5 has had this error.

In general, it is associated with incorrectly configured video card drivers.

But as my own experience has shown, this is not the end of the matter.

Most of the projects I work on do not have files that require serious graphics processing (complete or almost no shaders, detailed textures, and so on).

I want to ask more experienced professionals, are there any possible ideas to solve this problem?In advance, sincerely grateful for your suggestions.


Unfortunately, I did not solve it entirely, but found out why it occurred. First, the problem was switching to a different monitor, especially when switching from one screen where the engine is located to another where a browser is. The monitor was not new, and a VGA to Display Port converter was used to connect it to the video card. Subsequently, the monitor was replaced with a new one, and the cable was upgraded from digital HDMI to HDMI.The main problem, given the factors described above, was a sharp change in the image digitization rate. A game engine was running on one monitor and a browser on the other. When switching from the first screen, the video frequency drops sharply, and when switching back to the first monitor, the video card does not have time to overclock. I would be grateful if someone familiar with software applications like MSI Afterburner could tell me how to adjust the frequency correctly for stable operation.


Venture into a world of captivating transformation and exhilarating puzzles in Changed3D, an UE5 remake of DragonSnow's acclaimed original. Developed by a small team of like-minded people, this immersive experience invites you to rediscover the beloved 2D levels of Changed in breathtaking 3D environments, enhanced with fully functional game mechanics and an array of exciting features.






Changed3D is offered completely free of charge, made possible by the generosity of our community. If you've enjoyed your time in this captivating world, consider supporting us through donations or joining our Patreon for exclusive benefits, ensuring the continued development of Changed3D, and future projects!


Become part of the conversation by joining our Discord community, where you'll gain access to news, updates, and information. Your feedback and support are invaluable as we continue to evolve and expand the world of Changed3D.


No, the game is not cancelled!, we have decided to push forward and continue developing Changed3D. Your amazing support and inspiring feedback has made us so happy, that we just want to see this project finalized and in the best state possible.

Personally speaking as TheWarTank, I thank my family, my friends and the community, who have all inspired me to move forward in life, and in this project, thank you.




If you're wondering if the owner of the original game would allow the nature of this project, the answer is "yes!", we have received approval from DragonSnow to undertake this ambitious project, and we're committed to delivering an experience that honors the spirit of the original while pushing the boundaries of what's possible in the world of Changed.

3a8082e126
Reply all
Reply to author
Forward
0 new messages