Vampyr
Damianek Jun 6, 2018 @ 9:50am
Crash after 5-15 min of gameplay
Hey,
After few minutes of playing i get the monit "The UE4-AVGame Game has crashed and will close
LowLevelFatalError
Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - "HUNG")
I filed a tech support ticket but got no answer, so maybe someone here has any idea how to get this game to work?
I've got i7-6700hq and GTX1060 (laptop)
tried new drivers, old drivers, compatibility mode
Please help
< >
Showing 1-15 of 19 comments
Arc Jun 6, 2018 @ 11:03am 
You have to be more specific tho (in which part of the city, quest, cutscene, etc.).

If no specific trigger can be found and it is in fact caused just by time itself then your device is unstable (it is probably overheating or the system is unstable).
Davor Jun 6, 2018 @ 11:37am 
Are you running MSI Afterburner? I'm also struggling with this crash, and have recently read that closing afterburner helps. I was able to play for 45 minutes before it crashed, so I'm going to go as far as keeping it from running on startup, and we'll see if that clears it up.
Davor Jun 6, 2018 @ 11:46am 
Originally posted by Davor:
so I'm going to go as far as keeping it from running on startup, and we'll see if that clears it up.

Okay it seems it likes to crash during conversations, not 5 minutes into my save and I got the same error, it's shown up in the first Tavern, and at Pimbrook hospital, basically any time I have to talk to someone.

LowLevelFatalError [File:D:\farmagent11b\pg2-vampyr\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp] [Line: 824]
Rendering thread exception:
LowLevelFatalError [File:D:\farmagent11b\pg2-vampyr\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line: 176]
Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - 'HUNG')


KERNELBASE.dll!0x000000001CD1F218
AVGame-Win64-Shipping.exe!0x00000000028C915A
AVGame-Win64-Shipping.exe!0x000000000288E2F8
AVGame-Win64-Shipping.exe!0x0000000002C394B4
AVGame-Win64-Shipping.exe!0x0000000002C3A02A
AVGame-Win64-Shipping.exe!0x0000000002C26229
AVGame-Win64-Shipping.exe!0x0000000002C325D8
AVGame-Win64-Shipping.exe!0x0000000002F22F53
AVGame-Win64-Shipping.exe!0x0000000002F43877
AVGame-Win64-Shipping.exe!0x0000000002F492C3
AVGame-Win64-Shipping.exe!0x0000000002F3B316
AVGame-Win64-Shipping.exe!0x0000000002F46253
AVGame-Win64-Shipping.exe!0x0000000002D85DB4
AVGame-Win64-Shipping.exe!0x0000000002F4EEEA
AVGame-Win64-Shipping.exe!0x0000000002F42718
AVGame-Win64-Shipping.exe!0x00000000028266EA
AVGame-Win64-Shipping.exe!0x00000000028267DD
AVGame-Win64-Shipping.exe!0x0000000002D13626
AVGame-Win64-Shipping.exe!0x0000000002D136B8
AVGame-Win64-Shipping.exe!0x0000000002911FA7
AVGame-Win64-Shipping.exe!0x000000000290D377
KERNEL32.DLL!0x0000000020833034
ntdll.dll!0x0000000020981551
ntdll.dll!0x0000000020981551




Damianek Jun 6, 2018 @ 12:51pm 
Well, in my case it just crashes randomly, I also get this LowLevelFatalError - line 176
Thermals are ok (they do not exceed 75 celsius, which is not bad for a laptop), and system was pretty stable before, never had any problems like this before. Game runs smoothly at stable 60FPS and just crashes...
Damianek Jun 6, 2018 @ 1:56pm 
Originally posted by Scoucide:
https://steamcommunity.com/app/427290/discussions/1/1697174779864185373/
It is not the same problem. I can go in game, but for like 5-10 min, I don't crash at launch.
Last edited by Damianek; Jun 6, 2018 @ 1:56pm
Owen Jun 6, 2018 @ 2:58pm 
Apparently it’s been a recurring problem in UE4 for a couple of years. With no sure fire solutions. Some people have had improvements with lowering scaling but that only seems to delay the crashing not fix it
Davor Jun 6, 2018 @ 3:07pm 
I managed to fix it by running the compatability mode troubleshooter on the game's .exe, and set it for windows 8 (which was recommended by the troubleshooter). Seemed to work, just played for a couple hours straight with no crashes.

Edit: After another hour of play it eventually crashed, again during a conversation. This time with the Indian pawn broker behind the hospital.
Last edited by Davor; Jun 6, 2018 @ 9:29pm
Arc Jun 7, 2018 @ 12:29am 
Originally posted by Damianek:
...
And again, be more specific please. Also submit a ticket on their customer support service with all the necessary files as per:
https://steamcommunity.com/app/427290/discussions/1/1697174779862251361/

Originally posted by Davor:
...

Submit a ticket on their customer support service with all the necessary files as per:
https://steamcommunity.com/app/427290/discussions/1/1697174779862251361/


Also guys be sure to include the entire error message if you see one.
Hi there. I have an AORUS GTX 1080ti extreme edition. I had the same issue. Solved by downclockin the GPU with MSI Afterburner to -100/-100 MHz Core/Memory.
Owen Jun 12, 2018 @ 5:28am 
Originally posted by XxEnkiLxX:
Hi there. I have an AORUS GTX 1080ti extreme edition. I had the same issue. Solved by downclockin the GPU with MSI Afterburner to -100/-100 MHz Core/Memory.

I have the same card. I disabled all the Gamebar overlay options in Windows 10 and I had several hours of perfect playthrough. Now I seem to get the error when I leave the game paused for a few minutes and resume or after an hour or so.

I might try downclocking but I really hate have to mess with the card for individual games. I've been jumping back and forth between this & Witcher 3 and now I'm starting to get crashes in that which I'm almost certain are a result of me tweaking the 1080 ti settings.
Markaleth Jun 12, 2018 @ 12:15pm 
100% crash on the discussion with Old Bridget after talking to Harriet Jones in the Skal Sanctuary in the sewers, after the Sad Saint sends you to investigate.

I've done some digging and experimenting on this crash (which i'm also experiencing at regular intervals) and here are the results:

Firstly, the error occurs (as i understand it) because Unreal looses the reference it held of the D3D driver Object. This happens because whenever the GPU takes a bit more to process and exceeds a threshold set by Windows, the OS will restart the GPU to avoid a blue screen crash. Post GPU restart, i'd imagine the engine loses the object instance it held (i.e. the Engine no longer points to the current instance of the D3D driver).
I'm not sure why underclocking the GPU works but this HAS been reported to alleviate the issue somewhat.

What i can tell from my personal observations is:
1. Areas heavy on light/shadow effects will have a much higher crash rate
2. Lowering resolution scaling will reduce crash rate significantly
3. I've set everything to min and lowered the resolution but i still get crashes every hour or so, with the caveat explained on #1.

I'm running the game on a AMD Radeon HD 6900 series (6970 if memory serves, old, i know, but it got the job done so far).

Hope the info helps.
Owen Jun 13, 2018 @ 12:02am 
I was originally running 2 Aorus 1080 TI Extreme in SLI that I had just moved into a smaller case and I was almost certain the issue was the cards overheating before coming on here and seeing so many people with this issue. You're right Markaleth it's strange why under clocking fixes this problem in so many cases.

I reduced the power target in the Aorus software to 97% and managed to play all last night even pausing fora long times on a couple of occasions without any issues at perfect 60fps, 4k and everything max.
Markaleth Jun 13, 2018 @ 12:22pm 
I'd like to add one more odd bit of info i've noticed.

Seems that lowering resolution to 1024x768 from 1920x1080 will cause the crash to occur much more.
Ранд Jun 16, 2018 @ 3:22pm 
Install geforce driver 397.64. 398.11 crash game all game 4k
< >
Showing 1-15 of 19 comments
Per page: 1530 50