starred/shadPS4

Fork 0

mirror of https://github.com/shadps4-emu/shadPS4.git synced 2026-04-27 00:36:00 +03:00

[GH-ISSUE #793] Invalid device on startup #206

New issue

Closed

opened 2026-02-27 21:05:08 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 21:05:08 +03:00

Owner

Originally created by @bdzerr on GitHub (Sep 5, 2024).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/793

I have all perquisites, tried different builds and also building it myself and I must be missing something as i get the error below while trying to start the app,it happens after I select the install location for games, could someone point out what I'm doing wrong?

ERROR: vkDestroyFramebuffer: Invalid device [VUID-vkDestroyFramebuffer-device-parameter]

14900K
RTX 4090, Driver Ver: Latest 560.94

Originally created by @bdzerr on GitHub (Sep 5, 2024). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/793 I have all perquisites, tried different builds and also building it myself and I must be missing something as i get the error below while trying to start the app,it happens after I select the install location for games, could someone point out what I'm doing wrong? ERROR: vkDestroyFramebuffer: Invalid device [VUID-vkDestroyFramebuffer-device-parameter] 14900K RTX 4090, Driver Ver: Latest 560.94

kerem closed this issue

2026-02-27 21:05:08 +03:00

kerem commented

2026-02-27 21:05:09 +03:00

Author

Owner

@bdzerr commented on GitHub (Sep 11, 2024):

Further looking with event viewer shows the error in vulkan-1.dll, Ive tried reinstalling NV drivers, using the Vulkan installer standalone, neither has helped codes are:

Exception code: 0xc0000409
Fault offset: 0x00000000000b5345

@bdzerr commented on GitHub (Sep 11, 2024): Further looking with event viewer shows the error in vulkan-1.dll, Ive tried reinstalling NV drivers, using the Vulkan installer standalone, neither has helped codes are: Exception code: 0xc0000409 Fault offset: 0x00000000000b5345

kerem commented

2026-02-27 21:05:09 +03:00

Author

Owner

@Hermiten commented on GitHub (Oct 1, 2024):

I'm clsing it because little information and not followed up

@Hermiten commented on GitHub (Oct 1, 2024): I'm clsing it because little information and not followed up

kerem commented

2026-02-27 21:05:09 +03:00

Author

Owner

@bdzerr commented on GitHub (Oct 3, 2024):

Well the issue is still present, I was asking for help and gave every but of information i could what information is needed rather then closing it?

@bdzerr commented on GitHub (Oct 3, 2024): Well the issue is still present, I was asking for help and gave every but of information i could what information is needed rather then closing it?

kerem commented

2026-02-27 21:05:09 +03:00

Author

Owner

@Hermiten commented on GitHub (Oct 4, 2024):

Maybe which platform and which version ?

@Hermiten commented on GitHub (Oct 4, 2024): Maybe which platform and which version ?

kerem commented

2026-02-27 21:05:09 +03:00

Author

Owner

@Devirex commented on GitHub (Oct 21, 2024):

I had a similar issue with one layer blocking my device on windows. Run Powershell:

$env:VK_LOADER_DEBUG="error,warn,layer"
run software

Output:

LAYER:             vkCreateInstance layer callstack setup to:
LAYER:                <Application>
LAYER:                  ||
LAYER:                <Loader>
LAYER:                  ||
LAYER:                VK_LAYER_NV_optimus
LAYER:                        Type: Implicit
LAYER:                            Disable Env Var:  DISABLE_LAYER_NV_OPTIMUS_1
LAYER:                        Manifest: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ea7f458f0e49497d\nv-vk64.json
LAYER:                        Library:  C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ea7f458f0e49497d\.\nvoglv64.dll
LAYER:                  ||
LAYER:                VK_LAYER_someotherapp_layer
LAYER:                        Type: Implicit
LAYER:                            Disable Env Var:  DISABLE_VK_LAYER_someapp_layer_1
LAYER:                        Manifest: D:\....
LAYER:                        Library:  D:\...
LAYER:                  ||
LAYER:                <Drivers>
ERROR: vkDestroyFramebuffer: Invalid device [VUID-vkDestroyFramebuffer-device-parameter]
app crash

I had to set the disable env var of the someotherapp layer to true '$env:DISABLE_VK_LAYER_someapp_layer_1="true"'
running software again and issue was gone

@Devirex commented on GitHub (Oct 21, 2024): I had a similar issue with one layer blocking my device on windows. Run Powershell: `$env:VK_LOADER_DEBUG="error,warn,layer"` run software Output: ``` LAYER: vkCreateInstance layer callstack setup to: LAYER: <Application> LAYER: || LAYER: <Loader> LAYER: || LAYER: VK_LAYER_NV_optimus LAYER: Type: Implicit LAYER: Disable Env Var: DISABLE_LAYER_NV_OPTIMUS_1 LAYER: Manifest: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ea7f458f0e49497d\nv-vk64.json LAYER: Library: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ea7f458f0e49497d\.\nvoglv64.dll LAYER: || LAYER: VK_LAYER_someotherapp_layer LAYER: Type: Implicit LAYER: Disable Env Var: DISABLE_VK_LAYER_someapp_layer_1 LAYER: Manifest: D:\.... LAYER: Library: D:\... LAYER: || LAYER: <Drivers> ERROR: vkDestroyFramebuffer: Invalid device [VUID-vkDestroyFramebuffer-device-parameter] app crash ``` I had to set the disable env var of the someotherapp layer to true '$env:DISABLE_VK_LAYER_someapp_layer_1="true"' running software again and issue was gone

kerem referenced this issue

2026-02-27 21:12:22 +03:00

[PR #206] [MERGED] Add more shader instructions and some memory functions #1392