Game: Crash during Great Deku Tree intro fade to black on nightly-486 (Intel GPU) #1731

Open
opened 2026-11-19 10:51:29 +00:00 by BeanBot · 9 comments
Member

Reported on Discord

Longshot version and channel

nightly-486-09a20cd6 (nightly)

What happened and steps

The reporter says Longshot crashes during the title intro cutscene, when Navi is sent to Link by the Great Deku Tree, during the fade to black. They observed VRAM use around 4.5 GB before the crash and believed the VRAM limit was exceeded. Setting RX_VK_VRAM_MB=11264 did not prevent the crash. They prefer the very low frame rate they experienced before over being unable to get past the cutscene.

The crash occurs every time, when Navi and the Great Deku Tree begin talking about Link or during the transition into the cutscene. Dropping all resolutions slightly improved the progress: they could hear the music in Link's tree house, but the display remained black and the game still crashed, after FPS dips then settling around 30 FPS. The longshot_env.txt modification did not help and the file has since been removed. Exact graphics-setting comparison beyond lowering resolutions is unknown.

Where in the game

Great Deku Tree intro cutscene, at Navi's delivery to Link / fade to black and transition to Link's tree house.

GPU and driver

Integrated Intel UHD graphics, driver version 32.0.101.7088. The reporter describes it as having 8 GB VRAM; the log identifies Intel XeSS 2.0.2.

CPU, RAM and operating system

11th Gen Intel Core i3-1115G4 @ 3.00 GHz, 16 GB RAM, Windows 11.

Graphics settings and environment override

Logs show output resolution 2048x1152, graphics scale 1, Intel XeSS 2.0.2, and frame rate cap 30. In the runs with these settings, Longshot reports VRAM around 4.8 GB used of 7.2 GB allowed (e.g. 4938 MB used), not an exceeded budget. Lowering all resolutions slightly advanced playback but did not avoid the black screen/crash. The reporter says RX_VK_VRAM_MB=11264 did not help and has removed longshot_env.txt. Other settings are unknown.

Additional logs

The reporter supplied five more longshot_log.txt files from nightly-486. They document multiple restarts and do not show the same crash trace in the excerpts; one has a logged Intel driver fault while compiling a graphics pipeline:

[hos host] vk: the driver faulted compiling a graphics pipeline (exception 0xc0000005): that one is left out

Other excerpts show the game running around 22–30 FPS and VRAM below the reported 7.2 GB allowed budget. These additional logs are attached to the issue.

Original crash log

The initial attached longshot_log.txt ends with an access violation in Intel's igvk64.dll on the Presentation Thread:

[hos Presentation Thread] CRASH: exception 0xc0000005 (read 0x107e, guest 0xfffff0000000107e) at igvk64.dll+0x87793
[hos Presentation Thread] CRASH: host backtrace: igvk64.dll+0x87793 igvk64.dll+0x101855 igvk64.dll+0xe37d8 igvk64.dll+0x725ac longshot_vk.dll+0x2344b3 longshot_vk.dll+0x2033e5 longshot_vk.dll+0x1e84da longshot_vk.dll+0x3b0ca0 longshot_vk.dll+0x3a6a73 longshot_vk.dll+0x3a566a longshot_vk.dll+0x3a2f26 longshot_vk.dll+0x399c01 longshot.exe+0x1c692cec longshot.exe+0x500dc62 longshot.exe+0x1c5f0f92 longshot.exe+0x1c5f0bcb longshot.exe+0x11281957 longshot.exe+0x1c5f0bcb longshot.exe+0x9dadfab longshot.exe+0x1c630f3a

Still needed

Effects of changing upscaling or other graphics settings; confirmation of actual available/shared VRAM capacity if relevant.

This is not established as the same issue as #668 (RTX 5050 hard hang in Castle Town) or #837 (GTX 1050 Ti VRAM pressure/freezes); this report is an Intel driver access violation during the Great Deku Tree intro. PR #1291 handles Windows commit-limit allocation failures, but these later logs show VRAM below Longshot's allowed budget and do not establish that fix as applicable. PR #1685 concerns NVN device mode getters and does not address this game crash.

Reported on [Discord](https://discord.com/channels/1569849200047427645/1570984952651055114/1572769730903941234) ### Longshot version and channel nightly-486-09a20cd6 (nightly) ### What happened and steps The reporter says Longshot crashes during the title intro cutscene, when Navi is sent to Link by the Great Deku Tree, during the fade to black. They observed VRAM use around 4.5 GB before the crash and believed the VRAM limit was exceeded. Setting `RX_VK_VRAM_MB=11264` did not prevent the crash. They prefer the very low frame rate they experienced before over being unable to get past the cutscene. The crash occurs every time, when Navi and the Great Deku Tree begin talking about Link or during the transition into the cutscene. Dropping all resolutions slightly improved the progress: they could hear the music in Link's tree house, but the display remained black and the game still crashed, after FPS dips then settling around 30 FPS. The `longshot_env.txt` modification did not help and the file has since been removed. Exact graphics-setting comparison beyond lowering resolutions is unknown. ### Where in the game Great Deku Tree intro cutscene, at Navi's delivery to Link / fade to black and transition to Link's tree house. ### GPU and driver Integrated Intel UHD graphics, driver version 32.0.101.7088. The reporter describes it as having 8 GB VRAM; the log identifies Intel XeSS 2.0.2. ### CPU, RAM and operating system 11th Gen Intel Core i3-1115G4 @ 3.00 GHz, 16 GB RAM, Windows 11. ### Graphics settings and environment override Logs show output resolution 2048x1152, graphics scale 1, Intel XeSS 2.0.2, and frame rate cap 30. In the runs with these settings, Longshot reports VRAM around 4.8 GB used of 7.2 GB allowed (e.g. 4938 MB used), not an exceeded budget. Lowering all resolutions slightly advanced playback but did not avoid the black screen/crash. The reporter says `RX_VK_VRAM_MB=11264` did not help and has removed `longshot_env.txt`. Other settings are unknown. ### Additional logs The reporter supplied five more `longshot_log.txt` files from nightly-486. They document multiple restarts and do not show the same crash trace in the excerpts; one has a logged Intel driver fault while compiling a graphics pipeline: ```text [hos host] vk: the driver faulted compiling a graphics pipeline (exception 0xc0000005): that one is left out ``` Other excerpts show the game running around 22–30 FPS and VRAM below the reported 7.2 GB allowed budget. These additional logs are attached to the issue. ### Original crash log The initial attached `longshot_log.txt` ends with an access violation in Intel's `igvk64.dll` on the Presentation Thread: ```text [hos Presentation Thread] CRASH: exception 0xc0000005 (read 0x107e, guest 0xfffff0000000107e) at igvk64.dll+0x87793 [hos Presentation Thread] CRASH: host backtrace: igvk64.dll+0x87793 igvk64.dll+0x101855 igvk64.dll+0xe37d8 igvk64.dll+0x725ac longshot_vk.dll+0x2344b3 longshot_vk.dll+0x2033e5 longshot_vk.dll+0x1e84da longshot_vk.dll+0x3b0ca0 longshot_vk.dll+0x3a6a73 longshot_vk.dll+0x3a566a longshot_vk.dll+0x3a2f26 longshot_vk.dll+0x399c01 longshot.exe+0x1c692cec longshot.exe+0x500dc62 longshot.exe+0x1c5f0f92 longshot.exe+0x1c5f0bcb longshot.exe+0x11281957 longshot.exe+0x1c5f0bcb longshot.exe+0x9dadfab longshot.exe+0x1c630f3a ``` ### Still needed Effects of changing upscaling or other graphics settings; confirmation of actual available/shared VRAM capacity if relevant. ### Related reports This is not established as the same issue as #668 (RTX 5050 hard hang in Castle Town) or #837 (GTX 1050 Ti VRAM pressure/freezes); this report is an Intel driver access violation during the Great Deku Tree intro. PR #1291 handles Windows commit-limit allocation failures, but these later logs show VRAM below Longshot's allowed budget and do not establish that fix as applicable. PR #1685 concerns NVN device mode getters and does not address this game crash.
Author
Member

Files from the Discord report:

Files from the Discord report: - [longshot_log.txt](https://git.magicbean.dev/attachments/7f2276be-b0e6-4d63-90a3-9979dd83c9fa)
Author
Member

Updated with more from Discord: Added the reported Intel UHD integrated GPU, Intel i3, 16 GB RAM, and Windows 11 details; driver and reproduction details remain unknown.

Updated with more from [Discord](https://discord.com/channels/1569849200047427645/1572769730903941234/1572927822723416109): Added the reported Intel UHD integrated GPU, Intel i3, 16 GB RAM, and Windows 11 details; driver and reproduction details remain unknown.
Author
Member

Updated with more from Discord: Added the exact CPU and Intel graphics driver version supplied by the reporter.

Updated with more from [Discord](https://discord.com/channels/1569849200047427645/1572769730903941234/1572929684285689969): Added the exact CPU and Intel graphics driver version supplied by the reporter.
Author
Member

From Discord:

Reporter confirms the crash occurs every time: when Navi and the Great Deku Tree begin talking about Link, or during the transition into their cutscene. They report nearly 30 stable FPS during the intro now, versus about 3 FPS previously, but cannot skip or get past the cutscene. Exact override confirmation and effects of graphics-setting changes remain unknown. Discord follow-up: https://discord.com/channels/1569849200047427645/1572769730903941234/1572930288261140643

From [Discord](https://discord.com/channels/1569849200047427645/1570984952651055114/1572769730903941234): Reporter confirms the crash occurs every time: when Navi and the Great Deku Tree begin talking about Link, or during the transition into their cutscene. They report nearly 30 stable FPS during the intro now, versus about 3 FPS previously, but cannot skip or get past the cutscene. Exact override confirmation and effects of graphics-setting changes remain unknown. Discord follow-up: https://discord.com/channels/1569849200047427645/1572769730903941234/1572930288261140643
Author
Member

From Discord:

Reporter says the longshot_env.txt modification did not change the crash and the file is currently removed. This confirms the VRAM override did not help; no new graphics-settings comparison was provided.

From [Discord](https://discord.com/channels/1569849200047427645/1570984952651055114/1572769730903941234): Reporter says the `longshot_env.txt` modification did not change the crash and the file is currently removed. This confirms the VRAM override did not help; no new graphics-settings comparison was provided.
Author
Member

Updated with more from Discord: Added that lowering all resolutions slightly advances the intro but leaves a black screen and eventual crash, with dips before stabilizing at 30 FPS.

Updated with more from [Discord](https://discord.com/channels/1569849200047427645/1572769730903941234/1572936353703006441): Added that lowering all resolutions slightly advances the intro but leaves a black screen and eventual crash, with dips before stabilizing at 30 FPS.
Author
Member

Updated with more from Discord: Added five nightly-486 logs; they show VRAM below budget and include a separate Intel driver pipeline-compilation fault, not a confirmed reproduction of the original access violation.

Files:

Updated with more from [Discord](https://discord.com/channels/1569849200047427645/1572769730903941234/1572970590774755341): Added five nightly-486 logs; they show VRAM below budget and include a separate Intel driver pipeline-compilation fault, not a confirmed reproduction of the original access violation. Files: - [longshot_log.txt](https://git.magicbean.dev/attachments/aaf3a115-0471-445d-9d46-63a57997ac26) - [longshot_log.1.txt](https://git.magicbean.dev/attachments/b6071ca9-8e1a-4937-b275-87d185684221) - [longshot_log.2.txt](https://git.magicbean.dev/attachments/45f888ec-5ba6-449f-8d49-10b6a050349d) - [longshot_log.3.txt](https://git.magicbean.dev/attachments/eefcf4f7-170e-4059-97ef-2ab9dd7b2623) - [longshot_log.4.txt](https://git.magicbean.dev/attachments/882d6b04-7b54-4ae6-a788-87ae7eea79b9)
Author
Member

From Discord:

Reporter notes that at the moment of the crash, the on-screen VRAM meter's cap drops and displayed usage then exceeds that limit before crashing. They can provide a real-time video if useful. Existing logs sampled earlier show usage below budget, so a recording capturing the meter immediately before failure may clarify this discrepancy.

From [Discord](https://discord.com/channels/1569849200047427645/1570984952651055114/1572769730903941234): Reporter notes that at the moment of the crash, the on-screen VRAM meter's cap drops and displayed usage then exceeds that limit before crashing. They can provide a real-time video if useful. Existing logs sampled earlier show usage below budget, so a recording capturing the meter immediately before failure may clarify this discrepancy.
Contributor

Claimed: investigating the repeated Intel UHD / driver 101.7088 intro access violation at igvk64.dll+0x87793. Worklist score is S0 × 3.5% reach × 0.7 confidence ≈ 0.20; #1676 reports the same driver offset. I’ll build current main from the local dump and test on RX 9070 XT; Intel-specific reproduction still needs an Intel tester. Prior work: #404 addressed a different over-budget dispatch crash, not established by these logs.

Claimed: investigating the repeated Intel UHD / driver 101.7088 intro access violation at igvk64.dll+0x87793. Worklist score is S0 × 3.5% reach × 0.7 confidence ≈ 0.20; #1676 reports the same driver offset. I’ll build current main from the local dump and test on RX 9070 XT; Intel-specific reproduction still needs an Intel tester. Prior work: #404 addressed a different over-budget dispatch crash, not established by these logs.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
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
MagicBeanDev/Longshot#1731
No description provided.