[GH-ISSUE #617] App closes/hangs when loading a ROM on integrated Intel GPU #92

Closed
opened 2026-03-03 13:45:38 +03:00 by kerem · 7 comments
Owner

Originally created by @thekovic on GitHub (Nov 20, 2025).
Original GitHub issue: https://github.com/gopher64/gopher64/issues/617

Probably duplicate of #616 but that issue turned into a support thread so allow me to refile here.

System is a laptop with Windows 11 and an Intel Core Ultra 5 225U. No dedicated GPU. However, the integrated graphics do have Vulkan support and ares (which also consumes Parallel-RDP) is able to launch and run ROMs fine.

I tested one libultra game (Indiana Jones) and one libdragon game (Vlak 64) both with the same result.

Originally created by @thekovic on GitHub (Nov 20, 2025). Original GitHub issue: https://github.com/gopher64/gopher64/issues/617 Probably duplicate of #616 but that issue turned into a support thread so allow me to refile here. System is a laptop with Windows 11 and an Intel Core Ultra 5 225U. No dedicated GPU. However, the integrated graphics do have Vulkan support and ares (which also consumes Parallel-RDP) is able to launch and run ROMs fine. I tested one libultra game (Indiana Jones) and one libdragon game (Vlak 64) both with the same result.
kerem closed this issue 2026-03-03 13:45:39 +03:00
Author
Owner

@drewbyhk commented on GitHub (Nov 21, 2025):

This is more similar to my issue, so I'll include my video showing what happens (at least to me) - https://youtu.be/m-SyCCTRezw

Only difference for me is that I have a dedicated GPU, a Nvidia RTX 5070.

<!-- gh-comment-id:3561186139 --> @drewbyhk commented on GitHub (Nov 21, 2025): This is more similar to my issue, so I'll include my video showing what happens (at least to me) - https://youtu.be/m-SyCCTRezw Only difference for me is that I have a dedicated GPU, a Nvidia RTX 5070.
Author
Owner

@loganmc10 commented on GitHub (Nov 21, 2025):

@drewbyhk it looks like you have Bandicam installed, can you try uninstalling it?

<!-- gh-comment-id:3564288343 --> @loganmc10 commented on GitHub (Nov 21, 2025): @drewbyhk it looks like you have Bandicam installed, can you try uninstalling it?
Author
Owner

@loganmc10 commented on GitHub (Nov 21, 2025):

@thekovic do you have any screen recording software installed? (Bandicam, Mirillis Action, etc)

<!-- gh-comment-id:3564292184 --> @loganmc10 commented on GitHub (Nov 21, 2025): @thekovic do you have any screen recording software installed? (Bandicam, Mirillis Action, etc)
Author
Owner

@thekovic commented on GitHub (Nov 21, 2025):

None of those are installed on this system.

<!-- gh-comment-id:3564933571 --> @thekovic commented on GitHub (Nov 21, 2025): None of those are installed on this system.
Author
Owner

@DavidV1210 commented on GitHub (Nov 22, 2025):

@thekovic follow the steps of #616 to get your file dmp... In command prompt... type in

Navigate to the C drive with this command:

cd \

Then type in the command:

dir /s /b *gopher*

Its important to include the asterisks here. This command with show any file that includes the word "gopher"

from that return, search for your dmp file
your dump file will resemble something like this:

C:\Users\UserName\AppData\Local\CrashDumps\gopher64-windows-x86_64.exe.1234.dmp

After you find the crash dump, copy the file path and paste it into your File Explorer address bar to actually find the dmp file.

Download WinDbg (a debugger program) its free btw.

With WinDbg open, click and drag the gopher dmp file into the WinDbg window..

in the command input for WinDbg... type in

!analyze -v

it will translate the gibberish you see on the page.

When it finishes, copy all the output into a txt file and send it over

<!-- gh-comment-id:3565378722 --> @DavidV1210 commented on GitHub (Nov 22, 2025): @thekovic follow the steps of #616 to get your file dmp... In command prompt... type in Navigate to the C drive with this command: >cd \ > Then type in the command: >dir /s /b \*gopher\* > Its important to include the asterisks here. This command with show any file that includes the word "gopher" from that return, search for your dmp file your dump file will resemble something like this: >C:\Users\UserName\AppData\Local\CrashDumps\gopher64-windows-x86_64.exe.1234.dmp > After you find the crash dump, copy the file path and paste it into your File Explorer address bar to actually find the dmp file. Download WinDbg (a debugger program) its free btw. With WinDbg open, click and drag the gopher dmp file into the WinDbg window.. in the command input for WinDbg... type in >!analyze -v > it will translate the gibberish you see on the page. When it finishes, copy all the output into a txt file and send it over
Author
Owner

@m3talg3ar commented on GitHub (Feb 4, 2026):

I 2nd i have the exact same issue whenever i load rom

<!-- gh-comment-id:3848828128 --> @m3talg3ar commented on GitHub (Feb 4, 2026): I 2nd i have the exact same issue whenever i load rom
Author
Owner

@loganmc10 commented on GitHub (Feb 6, 2026):

I"m going to guess that this is the same issue as https://github.com/gopher64/gopher64/issues/586, since there is a bit more detail there, I'm going to close this in favour of that one

<!-- gh-comment-id:3862226519 --> @loganmc10 commented on GitHub (Feb 6, 2026): I"m going to guess that this is the same issue as https://github.com/gopher64/gopher64/issues/586, since there is a bit more detail there, I'm going to close this in favour of that one
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/gopher64#92
No description provided.