fatal error: [File:c\B\tech_exiles\code\engine\source\Runtime\windows\D3D11RHI\private\D2D11Util.cpp[Line 181]
Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - ‘Hung’)
I hame many game : Throne and Libertyy , Gta5 , gw2 Path of Exile , all game are ok
this error cames when open game in every mode i can select.
Already yupdate windows and driver my pc is update
Greetings @flagello and welcome to the forums,
Thank you for your report. Please follow the steps to verify your game files:
Thanks in advance.
sure, thanks for the answer but now can you tell me something I don’t know?
Just do a little research on the internet and you will find thousands of users asking how to solve this problem on Reddit, YouTube and other forums not yours.
With this crash you should see another folder created by unreal with some more information.
This crash is related to the graphics driver.
Is this happening everytime or occasionally?
Which version of windows are you using?
The crash occurs every time I start the game, in any mode I try to start, online, pve single player etc.
If I may:
Do you have any idea how many times I have to see the initial cinematic because every time I crash it’s like I restart the game from the beginning?
But do I really have to go and modify an ini file because in all these years you haven’t introduced a way to avoid it?
Seriously?
I repeat it’s not my PC and it’s not the drivers if I can start 99.9% of the games except Conan Exile the problem is yours.
Windows 11 : last update 24H2 build So 26100.3775
Last Amd driver for my RX 7600 and i update last night driver wihtout avoiding this problem.
Tell me how i can, today, start , in order Throne And Liberty, For honor , Assassin Creed Valhalla, Mirage and syndacate , Guild Wars 2, Everscape , Dragon dogma 2 , Elder Ring , Starfield , GTA 5 , Red Dead Redempion 2 online and syngle player and many other game without any problems except Conan Exile?
If memory serves me correctly there is a setting in the bios regarding how amd handles graphics or something similar, it is either on this forum or ue4 forum I will have a look around to see if I can find it.
Yes you are right it is the game however the crash is graphics/driver related, as is shown by
The fact that the line from the unreal engine source code is used this is an unreal engine crash
Regarding windows 11 other than helping my boy’s install it upon their pc’s I have zero experience with the operating system, and whilst it is a continuation of windows it handles things differently, maybe someone with more experience with windows 11 can assist you here.
I have found a few amd specific’s relating to crashes and unreal, still not found the one I was looking for but it may offer an insight into your situation.
good evening, can you close this support request, after reading more than 50 articles on the forums of microsoft, nvidia, amd, intel and Reddit and watched about 30 videos on youtube (almost all regarding the crash of this title) including the guides listed here, I have solved the problem for now.
all these articles and solution are outdated and useless
I can only tell you that it seems that this error also occurs with unreal Engine 5. So I advise you for Dune Awekening to find the solution very quickly because this problem will also occur on your next game.
I won’t give you the solution because I found it after hours and hours of reading and listening but I will tell you as advice that the problem is the driver update. So advising those who ask you for support to update them is the biggest mistake you can make.
Happy reading
It is nice to know that you have resolved your issue, maybe you could actually point the way for the others that are having this issue, as you pointed out there are many people with this issue, and have had varying degrees of success, and as outdated as these issues are demonstrates how old this issue is.
If you have indeed solved this then by sharing this somewhere on the internet for others who have this issue would be a good thing to do, or point people the way to the current dated articles, as this is what a public forum embodies, groups of players trying to assist others.
As for myself I have no such issue as I have not used amd for about 20+ years, but others do and would appreciate I am sure your sharing with them your insights that have solved this long standing issue.
The problem is not only on amd but also happens with the nvidia or intel, the problem is in the unreal engine and driver updates, it is not a product problem.
I’m sorry but no one has helped me and the f u n con company does not care, why should I do their job?
I am nobody and I’m not interested in having glory
Let me ask you a question.
If a solution had been found by another wouldnt you have wanted to know how and why?
You finding a soultion has no impact upon Funcom but does upon your fellow gamers who like yourself come here looking for possible solutions, there is no glory to be had just helping others in need, but hey what do I know I am from an older generation that find something good about assisting others for no reward or glory, just the fact that another is in need regardless of that need.
As for yourself solution found problem solved well done, at least now you are able to play conan, which is all this was about.
Except that Cyc has gone out of their way to try to help you - asking questions to narrow down what the issue might be, providing the benefits of their knowledge and experience, searching for articles that might solve your problem, trying to find possible answers for you. That is another player (not a Funcom employee as you seem to believe) choosing to spend their time trying to help you simply because you asked for help.
You were also helped by all of the people who wrote things on Reddit, wrote articles, made videos - sure some of them may have been out of date and you had to search through them until you finally found the right solution for you - but all of these resources exist because people chose to try to help others. They could have just said “I’ve solved it and I’m not telling anyone how I did it” - just like you - and you would still be looking for a solution because then they wouldn’t have put the answers out there for you to find.
You are free to hide what solved it for you - it is your right to be as selfish as you wish - but to claim that ‘no one helped you’ is simply dishonest. If truly no one had helped you, you would not have found the solution unless you went and learned Unreal programming, and all of the technology that could possibly have interacted with it, and then personally tested and examined every possible way that the interactions could occur until you found the exact one. Instead, you relied on the experiences of others, who chose to share them so that it would be easier for the next person to try to resolve a similar problem - because that is what decent people do.
I was a little tired last night but realised a few things that you had stated and would just like to highlight them for you.
1:
This was all we had to go on.
I stated that this was a driver hang crash and gave you a link to unreals how to deal with a gpu driver crash this was 5.5 most current docs from unreal.
If you had actually read this then you would see how up to date and relevant that this article was especially the reason as to why the driver hangs, as was the error you posted.
But as you pointed out here
For you only to come back with a solution that has nothing to do with Funcom
Updated drivers are not always the answer as you have pointed out, this has always been the case, although updating drivers,bios from motherboards to firmware devices is almost always a good place to start.
Your pc and it’s drivers are your responsibility not Funcom’s and the game engine crashing would be down to those who make the game engine not the makers of the game, the reason companies use others products such as Funcom using Unreals engine is because it works for their particular needs, and why reinvent the wheel, I would also assume that they would leave much of the core source code untouched regarding certain aspects of the engine.
In the case of every crash of conan that I have been scouting the forums on that has to do with unreal crashing you will always see the source code line reference, and comparing this to the source code for unreals same version that conan was compiled with demonstrates to me that indeed Funcom have not reinvented the wheel and have left much of this type of source code as is.
But like you stated
Unless you can still see normally that line is a lie.
That would suck. It works on Playstation now. I’m getting through the cinematic just fine (well, few nudges). It logs itself in during the movie. I hope Funcom didn’t inherit a gimmick.
Please explain how this is a lie, I would love to hear your explaination of the source code stating that the D3D device was lost is a lie?
I’ve already stated I’m not looking at the source code. That book is closed on my table, for now.
The loss of the D3D device is a generic error. It doesn’t really have a complete stack to examine. It is better than nothing, however.
I’m saying there is the lie. It can still work together. It could examine the stack. It can still reflect.
Do you think that is not enough?
Yes I would agree it is a generic error but I think a lie has probably come out mistranslated in the sense of what is determined to be a lie.
The unreal crashes generate optional data to run through a debugger in a seperate folder within the log folder but again without the actual source code of Conan which Funcom have it is alot more difficult if not neigh on impossible to actually find the reason.
One thing that I thought of was interesting is the way that unreal handle this particular error, was the information regarding the timeout that windows specifies for gpu drivers and that this can be adjusted by a registry entry, this I have done for running the devkit as it just used to hang, now it does not, so maybe therin lies part of the soultion.
Another piece of information that caught my eye was with regards to debug settings that can be applied via concole or command line and that command line takes priority over console settings, I have added the gpu debug to my command line settings but will have to wait and see what this produces when my game crashes with regards to drivers.
Yes, and UE5.5 is then needed, as suggested. It should be fun at this point, or you need more memory to hold those extra symbols (and switch context if needed). It’s a big step without the fixes (that Funcom has applied to UE4.x). I guess that looks like spaghetti code. It’s tempting to submit more fixes.
P.S. I haven’t messed with steamCMD.