Game freeze or black screen during cutscenes or gameplay
Validation
- [ ✓ ] I have checked the Issues page to see if my problem has already been reported
- [ ✓ ] I have confirmed that this bug does not occur in the original game running on original Xbox 360 hardware
If you have DLC installed, please specify which ones you have.
- [ ✓ ] Apotos & Shamar Adventure Pack
- [ ✓ ] Chun-nan Adventure Pack
- [ ✓ ] Empire City & Adabat Adventure Pack
- [ ✓ ] Holoska Adventure Pack
- [ ✓ ] Mazuri Adventure Pack
- [ ✓ ] Spagonia Adventure Pack
I don't have any modes enabled.
I don't have any codes enabled.
At the start of the cutscenes or during the gameplay, game screen just freezes or gives black screen with sound still playing. It runs normal for a short amount of time after I change GI Texture Filtering between BICUBIC and BILINEAR but shortly after I get the same error. The issue is still there after the update. Please help me.
Steps to Reproduce
Just by playing it.
Expected Behavior
To play the game without freezing? Dunno, I couldn't get it.
Footage
It's just a black screen.
Specifications
Fill out the following details:
- CPU: Intel I3 1005G1 Mobile CPU
- GPU: Intel G1 Graphics
- OS: Windows 10 Home
- Version: (e.g. 1.0.2)
Try a RelWithDebInfo build and see if you can gather anything of interest from the console output when it happens.
Ok I installed it, played the game until the problem occur again and here's what the console kept spamming after the problem: (It kept spamming it until I close it, and my screen was frozen in the meanwhile, not a black screen this time.)
vkQueueSubmit failed with error code 0xFFFFFFFC. vkGetQueryPoolResults failed with error code 0x1. vkQueueSubmit failed with error code 0xFFFFFFFC. vkQueueSubmit failed with error code 0xFFFFFFFC. vkGetQueryPoolResults failed with error code 0x1. vkQueueSubmit failed with error code 0xFFFFFFFC. vkQueueSubmit failed with error code 0xFFFFFFFC. vkGetQueryPoolResults failed with error code 0x1. vkQueueSubmit failed with error code 0xFFFFFFFC. vkQueueSubmit failed with error code 0xFFFFFFFC. vkQueueSubmit failed with error code 0xFFFFFFFC. vkQueueSubmit failed with error code 0xFFFFFFFC. vkGetQueryPoolResults failed with error code 0x1. vkQueueSubmit failed with error code 0xFFFFFFFC. vkQueueSubmit failed with error code 0xFFFFFFFC. vkGetQueryPoolResults failed with error code 0x1. vkQueueSubmit failed with error code 0xFFFFFFFC. vkQueueSubmit failed with error code 0xFFFFFFFC. vkQueueSubmit failed with error code 0xFFFFFFFC. vkQueueSubmit failed with error code 0xFFFFFFFC. vkGetQueryPoolResults failed with error code 0x1.
0xFFFFFFFC is VK_ERROR_DEVICE_LOST.
It seems your device's driver is crashing.
- Try updating your drivers from Intel's website.
- Try lowering your graphics settings like anti-aliasing, resolution scale, shadow resolution. All of these have a big impact on video memory consumption.
- Check how much memory is assigned to your GPU in Task Manager on the GPU tab. If it's a very low amount (like 512 MB), you can try increasing the dedicated memory in your BIOS.
I just checked and my drivers are already up to date.
As for the in-game settings and VRAM allocation, here are the footages:
The game goes black screen if I do ALT+TAB so I had to use my phone, sorry.
This all looks fairly normal. Can you tell if the issue only happens between loading screens? Or can it happen during regular gameplay too?
You kind of skipped over anti-aliasing btw. Is it set to 1x?
Sorry, yes anti aliasing is set to the lowest value. Freezing and black screen problems happen in-game, too. For example when on the loading screen, game freezes on Miles gadget screen even though the scene is loaded and sound is playing and while playing the game, game instantly freezes even though I can still hear the footsteps when I try to move around without seeing anything.
FIXED : I've created an administrator account with CMD and run the game as administrator on that account and I've been playing it without any problems for hours. My main account is the one that is created during the installation of Windows and apparently it's not the same with the account I've created with CMD.
Closing as OP no longer gets the issue.