My system does not have overdrive enabled.
Been googling things and I found a couple of web sites… Still reviewing.
With my monthly bandwidth reset, i could download things and try them.
tried the elemental demo, was able to play in standalone, and went through it until the end. no crash.
tried unigine heaven and valley benchmark, no crash.
tried a benchmark made with unreal engine 4, “eternity benchmark”, went through the benchmark without crash. Then moved around the scenery , also without crash.
played carmaggeddon reincarnation, no crash.
played path of exile, no crash.
Moved in viewport of the editor while in elemental demo, the editor froze and became unresponsive, but there was no video driver crash. Had to teminate the process however.
confirmed again that play in standalone crashed the first person template.
i mainly shoot and move the mouse.
Then i went ahead and installed the latest visual studio, community 2015. To try and package something i know crashes to see if the packaged version also cause a video driver crash.
And i learned it’s not supported in 4.8, i’ll have to wait 4.9 to test this. [ or download visual studio 2013, but i think i’ll wait for 4.9 ]
The no crashing in elemental demo, play in standalone is surprising. i’ll have to try more things.
if i understand correctly, it means when the display driver becomes unresponsive for 2 seconds for any reasons, windows detects this and restarts it without the hassle of restarting the whole computer. We could try to lengthen the timeout to see if the hangup is permanent or not, but i do not think we will learn something there.
So we have a display driver freeze, recovered by windows.
Grim news. I swapped a 660 GTX for this card, it arrives next week. I’m in the middle of heavy development and this will really throw a wrench into my work.
i have been trying satellite reign, and i have been crashing a lot.
This is a game made in unity, as opposed to other games i have tried who all have their own engine.
A quick glance in unity support forum and i do not seem to notice anyone reporting a problem with a r9 380 so far.
It is not a clear cut video driver crash with the windows popup saying so, but it looks like it.
This was with the newly released beta driver from amd. catalyst version 15.8beta.
I’m never sure if the version number is a date or not. It seems so for catalyst, but the driver packaging version is 15.201.1151-150821a-188451E
As for unreal engine 4.9, i am not particularly motivated to spend 1/4 of my monthly bandwidth on this yet, i’ll see about that later.
Hello TJ,
Do Epic’s compatibility developers have been in touch with AMD ?
I would guess they carry way more weight than me if they complain to amd, and would also be in a way better position than me to give them more detailed information.
I have already used a contact form to make AMD aware of my issue, with a link to here, but i guess i will have to go and create an account on their support forum.
I do not have unity, but the 1 game made in unity i have is constantly crashing. Which does strongly hint to a problem with AMD driver.
Worst case, do everything in wireframe, toggling back to fully rendered to get a look without moving.
I would say do not bother installing the card for now, especially in a heavy development phase where time lost may be an issue, but i would also like to make sure it is not something particular with my system or teak421’s.
The more people complaining it does not work, the more urgent this will become.
i did not a lot of experimenting, but i have not crashed yet while using “unlit” mode either, so i can have more than just the wireframe.
alt 3 in editor, and console command “viewmode unlit” while i run in standalone.
as for the game made in unity, satellite reign, i removed all the shadows and post processing in the options, and i managed to get 2 hours without crashing.
I gave my son my R9 380 and grabbed his 280. No issues with that card.
I just got an R9 380 yesterday, I am having the same problem.
Worth noting. I tried uninstalling the 15.7.1 driver and re-installing the Aug 28th beta driver, to no avail.
Though, I haven’t yet had a crash with -DX12 mode enabled.
Hey everyone,
We have investigated this on our end and it seems to be directly related to the graphics card driver. If you haven’t already, make sure that you post on the AMD forums to help get traction on this issue.
Cheers,
TJ
Hi TJ,
Have you (Epic) also contacted AMD about this issue? I don’t think single reports from single developers like me would mean a lot to them, but if a huge company like Epic Games is telling AMD that there is a problem with their driver they will surely respond very quickly and fix the problem.
why have you marked it as resolved?
i’m glad you could test this on your side with the graphic cards [ saw a post on another thread about ordering some for compatibility: Unreal Engine has stopped working when starting up - Platform & Builds - Unreal Engine Forums ]
I was pretty much convinced it was an issue on amd’s side, but it’s better to have a confirmation like that.
I posted on amd forum a while ago, but i now just realised i haven’t posted the link here yet:
like John said, i do hope Epic does contact Amd with this, Epic carries more weight than me ! But also, i agree we do have to make it gain traction over there.
i think it’s because my goal was to make Epic aware of the problem.
I was not expecting to buy a brand new video card and having everything working flawlessly without a round of update. But now, i feel Epic did what they had to do, it is AMD who needs to work on this.
I have contacted AMD about it here since I think it’s the correct way, their forums seem to be more about general support stuff:
http://www.amdsurveys.com/se.ashx?s=5A1E27D224F144DD
It’s directly for driver issues. Have not yet received any answer from them. Have linked all the answerhub threads about the issue.
Well, since UE4 is the only software where this driver crash happens it’s probably not 100% AMDs fault or Epic is using the driver in some way no one else is doing so the bug only appears with UE4. But then Epic needs to tell AMD where exactly is the problem, like which exact Direct3D function they are calling which is then causing this crash, I don’t know too much about this low level stuff but since Epic seems to know it’s not their fault they have to know what exactly is causing this.
I just asked why he marked it as resolved since my question about whether Epic has also contacted AMD did not receive any answer yet 
i filled this twice: once in mid july when i just got my card, and a second time after i installed the first drivers for R380 included in the package.[ start of august] I have not received any answer. I honestly don’t expect an answer from this, unless they need specific details.
The only other application in which i constantly crash is a game made in unity. It’s not that much meaningful because i have not tried a lot of different games/application, and there are a lot of reasons a game may crash, but it may be worth a shot to try to see if unity crashes on your machine. I can prevent both [ the game in unity and UE4 ] from crashing if i turn off some graphical options.