..:: PCSX2 Forums ::..

Full Version: PCSX2 began crashing - Vulkan
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Machine used: GPD WIN 3
PCSX2 Version: PCSX2 Nightly - v1.7.2676 Compiled on Apr 29 2022

So far never had any issues with this emulator and this machine, I played a lot of hours in it.

However the emulator started not functioning anymore (i.e. it starts right at the first loading screen of Crash of Titans), giving me these errors:


Code:
(DoPresent) vkQueuePresentKHR failed:  (-4: VK_ERROR_DEVICE_LOST)
(DoSubmitCommandBuffer) vkQueueSubmit failed:  (-4: VK_ERROR_DEVICE_LOST)
D:\a\pcsx2\pcsx2\common\Vulkan\Context.cpp(1072) : assertion failed:
    Function:  Vulkan::Context::DoSubmitCommandBuffer
    Thread:    MTGS
    Condition: false
    Message:   Failed to submit command buffer.

[00] 0x00007FF7EC9D05E0                         
[01] 0x00007FF7EC2666FC                         
[02] 0x00007FF7EC5D342E                         
[03] 0x00007FF7EC3CD1BC                         
[04] 0x00007FF7EC5B101B                         
[05] 0x00007FF7EC39DCE8                         
[06] 0x00007FF7EC9C0F96                         
[07] 0x00007FF7EC9C0ED3                         
[08] 0x00007FF7EC9C0A82                         
[09] 0x00007FF7EC9C0AAE                         
[10] 0x00007FF7EC710975                         
[11] configthreadlocale                         
[12] BaseThreadInitThunk                        
[13] RtlUserThreadStart                         

(DoSubmitCommandBuffer) vkQueueSubmit failed:  (-4: VK_ERROR_DEVICE_LOST)
D:\a\pcsx2\pcsx2\common\Vulkan\Context.cpp(1072) : assertion failed:
    Function:  Vulkan::Context::DoSubmitCommandBuffer
    Thread:    MTGS
    Condition: false
    Message:   Failed to submit command buffer.

[00] 0x00007FF7EC9D05E0                         
[01] 0x00007FF7EC3F7BDD                         
[02] 0x00007FF7EC5B1169                         
[03] 0x00007FF7EC39D901                         
[04] 0x00007FF7EC9C0F96                         
[05] 0x00007FF7EC9C1577                         
[06] _C_specific_handler                        
[07] _chkstk                                    
[08] RtlUnwindEx                                
[09] _C_specific_handler                        
[10] _chkstk                                    
[11] RtlRaiseException                          
[12] KiUserExceptionDispatcher                  
[13] 0x00007FF7EC9CCD79                         
[14] 0x00007FF7EC9D05E0                         
[15] 0x00007FF7EC2666FC                         
[16] 0x00007FF7EC5D342E                         
[17] 0x00007FF7EC3CD1BC                         
[18] 0x00007FF7EC5B101B                         
[19] 0x00007FF7EC39DCE8                         
[20] 0x00007FF7EC9C0F96                         
[21] 0x00007FF7EC9C0ED3                         
[22] 0x00007FF7EC9C0A82                         
[23] 0x00007FF7EC9C0AAE                         
[24] 0x00007FF7EC710975                         
[25] configthreadlocale                         
[26] BaseThreadInitThunk                        
[27] RtlUserThreadStart                         



i already tried updating to the latest nighly build and updating my video drivers

Any idea on what this might be?
Code:
D:\a\pcsx2\pcsx2\common\Vulkan\Context.cpp(1072)

That is not my PCSX2 folder, I have my emulator in C and my games in D.


EDIT: Looks like it's something related to the Vulkan rendering method.
Any way to fix that? I rather that over D3D11

EDIT 2: Playing on NATIVE resolution prevents the crash.
Still, this is less than ideal
I'd suspect a driver problem.
You Will have to wait for someone who uses a gpd win too
(04-30-2022, 11:11 AM)jesalvein Wrote: [ -> ]I'd suspect a driver problem.
You Will have to wait for someone who uses a  gpd win too

I suspected as such, I already tried uninstalling and installing the drivers again, but with no luck
Still, there is no problem with a classic windows 10, classic pc, classic CPU/GPU here.
Maybe someone with a gpd win will be able to reproduce the error...
I solved the issue by.... Updating everything, even the OS, up to Windows 11, using GPD WIN's official update tools.

And cleaning everything in the C drive as a result.

I know it's a drastic solution, but at least it worked.


EDIT: If you want a more clean, less destructive solution, just simply roll back your drivers.
Looks like Intel screwed up something.