[GH-ISSUE #586] Intel ARC A770M igvk64.dll Crash #71

Open
opened 2026-03-03 13:45:26 +03:00 by kerem · 12 comments
Owner

Originally created by @rishooty on GitHub (Sep 28, 2025).
Original GitHub issue: https://github.com/gopher64/gopher64/issues/586

I'm trying to set up some Smash Remix netplay, but I am having issues getting this emulator to run at all.

I initially believed it was just my drivers, as i was having trouble getting Ares to run right either. With Ares and the latest, games loaded but with corrupted graphics.

After a bunch of research, I found that reverting back to 32.0.101.6913 was a popular option when dealing with Vulkan issues on intel ARC gpus.

This allowed Ares to work perfectly! However, the exact same crash still occurs in gopher, even after doing a completely fresh uninstall and reinstall of 32.0.101.6913 with DDU and disabling driver updates in windows update.

From Windows Event Viewer:

Faulting application name: gopher64-windows-x86_64.exe, version: 1.1.8.0, time stamp: 0x68d8ecaf
Faulting module name: igvk64.dll, version: 32.0.101.6913, time stamp: 0x68562d18
Exception code: 0xc0000005
Fault offset: 0x00000000004b7dd0
Faulting process id: 0x3018
Faulting application start time: 0x1DC30BDF5B122CC
Faulting application path: C:\Games\gopher64\gopher64-windows-x86_64.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_ad653a309640ce11\igvk64.dll
Report Id: b3f5816e-076a-4938-b283-33bcb142bb3a
Faulting package full name: 
Faulting package-relative application ID: 

Tested Roms:
Super Mario 64 USA
Super Smash Bros USA
Smash Remix 2.0.0

Originally created by @rishooty on GitHub (Sep 28, 2025). Original GitHub issue: https://github.com/gopher64/gopher64/issues/586 I'm trying to set up some Smash Remix netplay, but I am having issues getting this emulator to run at all. I initially believed it was *just* my drivers, as i was having trouble getting Ares to run right either. With Ares and the latest, games loaded but with corrupted graphics. After a bunch of research, I found that reverting back to 32.0.101.6913 was a popular option when dealing with Vulkan issues on intel ARC gpus. This allowed Ares to work perfectly! However, the exact same crash still occurs in gopher, even after doing a completely fresh uninstall and reinstall of 32.0.101.6913 with DDU and disabling driver updates in windows update. From Windows Event Viewer: ``` Faulting application name: gopher64-windows-x86_64.exe, version: 1.1.8.0, time stamp: 0x68d8ecaf Faulting module name: igvk64.dll, version: 32.0.101.6913, time stamp: 0x68562d18 Exception code: 0xc0000005 Fault offset: 0x00000000004b7dd0 Faulting process id: 0x3018 Faulting application start time: 0x1DC30BDF5B122CC Faulting application path: C:\Games\gopher64\gopher64-windows-x86_64.exe Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_ad653a309640ce11\igvk64.dll Report Id: b3f5816e-076a-4938-b283-33bcb142bb3a Faulting package full name: Faulting package-relative application ID: ``` Tested Roms: Super Mario 64 USA Super Smash Bros USA Smash Remix 2.0.0
Author
Owner

@loganmc10 commented on GitHub (Sep 29, 2025):

Ares and Gopher64 don't use the same build of parallel-rdp (gopher64 has an updated version of Granite, the vulkan subsystem for Parallel-RDP). I'm not sure what I could do exactly, I'm hopeful that eventually a driver update for Intel ARC will fix this problem.

If you have some way to report the crash to Intel, it might be helpful

<!-- gh-comment-id:3345217625 --> @loganmc10 commented on GitHub (Sep 29, 2025): Ares and Gopher64 don't use the same build of parallel-rdp (gopher64 has an updated version of Granite, the vulkan subsystem for Parallel-RDP). I'm not sure what I could do exactly, I'm hopeful that eventually a driver update for Intel ARC will fix this problem. If you have some way to report the crash to Intel, it might be helpful
Author
Owner

@BiZkViT96 commented on GitHub (Sep 29, 2025):

@loganmc10 Not, how it works. In emulation cases, Intel has rule - only the emu devs should report the bugs, and not a regular users. Least that you can do, is to bring Parallel-RDP devs attention and make them report the issue to Intel.

Check this https://github.com/ares-emulator/ares/issues/2205

<!-- gh-comment-id:3348358017 --> @BiZkViT96 commented on GitHub (Sep 29, 2025): @loganmc10 Not, how it works. In emulation cases, Intel has rule - only the emu devs should report the bugs, and not a regular users. Least that you can do, is to bring Parallel-RDP devs attention and make them report the issue to Intel. Check this https://github.com/ares-emulator/ares/issues/2205
Author
Owner

@loganmc10 commented on GitHub (Sep 29, 2025):

@loganmc10 Not, how it works. In emulation cases, Intel has rule - only the emu devs should report the bugs, and not a regular users. Least that you can do, is to bring Parallel-RDP devs attention and make them report the issue to Intel.

Check this ares-emulator/ares#2205

I'm not going to do that, hopefully a future Intel driver update will resolve the issue.

<!-- gh-comment-id:3348400844 --> @loganmc10 commented on GitHub (Sep 29, 2025): > [@loganmc10](https://github.com/loganmc10) Not, how it works. In emulation cases, Intel has rule - only the emu devs should report the bugs, and not a regular users. Least that you can do, is to bring Parallel-RDP devs attention and make them report the issue to Intel. > > Check this [ares-emulator/ares#2205](https://github.com/ares-emulator/ares/issues/2205) I'm not going to do that, hopefully a future Intel driver update will resolve the issue.
Author
Owner

@rishooty commented on GitHub (Sep 29, 2025):

@loganmc10 Not, how it works. In emulation cases, Intel has rule - only the emu devs should report the bugs, and not a regular users. Least that you can do, is to bring Parallel-RDP devs attention and make them report the issue to Intel.

Check this ares-emulator/ares#2205

Thank you for informing me of this, I am trying to get something going:
https://github.com/Themaister/parallel-rdp/issues/54

I really do not want to make a separate linux install just to use Vulkan apps.

@loganmc10 huh, apparently parallel-rdp has this written in it's readme:
Image

<!-- gh-comment-id:3348637438 --> @rishooty commented on GitHub (Sep 29, 2025): > [@loganmc10](https://github.com/loganmc10) Not, how it works. In emulation cases, Intel has rule - only the emu devs should report the bugs, and not a regular users. Least that you can do, is to bring Parallel-RDP devs attention and make them report the issue to Intel. > > Check this [ares-emulator/ares#2205](https://github.com/ares-emulator/ares/issues/2205) Thank you for informing me of this, I am trying to get something going: https://github.com/Themaister/parallel-rdp/issues/54 I really do not want to make a separate linux install just to use Vulkan apps. @loganmc10 huh, apparently parallel-rdp has this written in it's readme: <img width="861" height="183" alt="Image" src="https://github.com/user-attachments/assets/c4459903-47f2-48b0-99dc-422bcf8fd92c" />
Author
Owner

@loganmc10 commented on GitHub (Sep 30, 2025):

Yes, this is implemented for all targets, not just Intel

github.com/gopher64/gopher64@a0237e9f7d/src/device/rdram.rs (L147)

<!-- gh-comment-id:3352551878 --> @loganmc10 commented on GitHub (Sep 30, 2025): Yes, this is implemented for all targets, not just Intel https://github.com/gopher64/gopher64/blob/a0237e9f7d51846dafb2ffcd850e1e7b55f2dcd6/src/device/rdram.rs#L147
Author
Owner

@lmcgregoruk commented on GitHub (Jan 30, 2026):

I've got the same problem with an Intel Arc B580, Gopher will open, but as soon as I do Open ROM and pick one, a second window will come up for a few seconds with just a title bar and black box before closing both windows.
The same roms opened in Simple64 b49e10e and ares-v147 although with corrupt graphics.
Intel Arc Graphics Driver 32.0.101.8425 being the most recent driver as of 30/1/2026

Faulting application name: gopher64-windows-x86_64.exe, version: 1.1.13.0, time stamp: 0x697bcf4b
Faulting module name: igvk64.dll, version: 32.0.101.8425, time stamp: 0x696a8243
Exception code: 0xc0000005
Fault offset: 0x00000000008922bb
Faulting process id: 0x4D18
Faulting application start time: 0x1DC922C00E1BD32
Faulting application path: I:\Emulators\N64\Gopher 64\gopher64-windows-x86_64.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_8b0a78c472357353\igvk64.dll
Report Id: e6e752c3-1e36-436b-8fb9-4b595786ea65
Faulting package full name:
Faulting package-relative application ID

<!-- gh-comment-id:3825930791 --> @lmcgregoruk commented on GitHub (Jan 30, 2026): I've got the same problem with an Intel Arc B580, Gopher will open, but as soon as I do Open ROM and pick one, a second window will come up for a few seconds with just a title bar and black box before closing both windows. The same roms opened in Simple64 b49e10e and ares-v147 although with corrupt graphics. Intel Arc Graphics Driver 32.0.101.8425 being the most recent driver as of 30/1/2026 Faulting application name: gopher64-windows-x86_64.exe, version: 1.1.13.0, time stamp: 0x697bcf4b Faulting module name: igvk64.dll, version: 32.0.101.8425, time stamp: 0x696a8243 Exception code: 0xc0000005 Fault offset: 0x00000000008922bb Faulting process id: 0x4D18 Faulting application start time: 0x1DC922C00E1BD32 Faulting application path: I:\Emulators\N64\Gopher 64\gopher64-windows-x86_64.exe Faulting module path: C:\Windows\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_8b0a78c472357353\igvk64.dll Report Id: e6e752c3-1e36-436b-8fb9-4b595786ea65 Faulting package full name: Faulting package-relative application ID
Author
Owner

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

@lmcgregoruk can you retry? I no longer own an intel gpu but still want to pass this on. https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/1240#issuecomment-3848860368

<!-- gh-comment-id:3849700517 --> @rishooty commented on GitHub (Feb 4, 2026): @lmcgregoruk can you retry? I no longer own an intel gpu but still want to pass this on. https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/1240#issuecomment-3848860368
Author
Owner

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

Retried, got the same thing , made a short video here https://www.youtube.com/watch?v=pcIy0wGzTKg

Faulting application name: gopher64-windows-x86_64.exe, version: 1.1.13.0, time stamp: 0x697bcf4b
Faulting module name: igvk64.dll, version: 32.0.101.8425, time stamp: 0x696a8243
Exception code: 0xc0000005
Fault offset: 0x00000000008922bb
Faulting process id: 0x67B0
Faulting application start time: 0x1DC961C161550A7
Faulting application path: I:\Emulators\N64\Gopher 64\gopher64-windows-x86_64.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_8b0a78c472357353\igvk64.dll
Report Id: 90a65abe-5a3f-405b-93f8-8d006c961b07
Faulting package full name:
Faulting package-relative application ID:

<!-- gh-comment-id:3849851990 --> @lmcgregoruk commented on GitHub (Feb 4, 2026): Retried, got the same thing , made a short video here https://www.youtube.com/watch?v=pcIy0wGzTKg Faulting application name: gopher64-windows-x86_64.exe, version: 1.1.13.0, time stamp: 0x697bcf4b Faulting module name: igvk64.dll, version: 32.0.101.8425, time stamp: 0x696a8243 Exception code: 0xc0000005 Fault offset: 0x00000000008922bb Faulting process id: 0x67B0 Faulting application start time: 0x1DC961C161550A7 Faulting application path: I:\Emulators\N64\Gopher 64\gopher64-windows-x86_64.exe Faulting module path: C:\Windows\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_8b0a78c472357353\igvk64.dll Report Id: 90a65abe-5a3f-405b-93f8-8d006c961b07 Faulting package full name: Faulting package-relative application ID:
Author
Owner

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

Please pass this on to my original thread linked above if you can, thanks!

<!-- gh-comment-id:3849870115 --> @rishooty commented on GitHub (Feb 4, 2026): Please pass this on to my original thread linked above if you can, thanks!
Author
Owner

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

I noticed for me the issue was gopher 64 closes when rtss is active when rtss is not active gopher works as normal

<!-- gh-comment-id:3862560791 --> @m3talg3ar commented on GitHub (Feb 6, 2026): I noticed for me the issue was gopher 64 closes when rtss is active when rtss is not active gopher works as normal
Author
Owner

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

Well I never had RTSS active any of the times I used Gopher64. The only thing I have that uses RTSS is MSI Afterburner, and I wasn't using it any of the times. Issue still exists with Gopher64 1.1.14 (released 13 hours ago as of this post)

<!-- gh-comment-id:3862997654 --> @lmcgregoruk commented on GitHub (Feb 6, 2026): Well I never had RTSS active any of the times I used Gopher64. The only thing I have that uses RTSS is MSI Afterburner, and I wasn't using it any of the times. Issue still exists with Gopher64 1.1.14 (released 13 hours ago as of this post)
Author
Owner

@GRAUPS commented on GitHub (Feb 27, 2026):

I'm just going to pile on and say I have the exact same issue as OP, with not only Gopher64 but anything that tries to use parallel-rdp. I'm having a terrible time because all I have are Intel GPUs (A750)!

<!-- gh-comment-id:3970392348 --> @GRAUPS commented on GitHub (Feb 27, 2026): I'm just going to pile on and say I have the exact same issue as OP, with not only Gopher64 but anything that tries to use parallel-rdp. I'm having a terrible time because all I have are Intel GPUs (A750)!
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#71
No description provided.