freeze and crashed after Bigoron's sword retrieved from Goron Mountain #2596

Closed
opened 2026-11-12 00:56:39 +00:00 by PittStone · 2 comments
PittStone commented 2026-11-12 00:56:39 +00:00 (Migrated from github.com)

Hookshot version

v2.1.0

What kind of problem

Crash, freeze or black screen

What happened

The screen froze when I got the Bigoron sword from the big Goron on the mountain. Then it crashed.

Where in the game

Goronen Mountain

How often

Once so far

Graphics card and driver version

RTX 2080 Super

CPU, RAM and operating system

Intel 10700k, 32GB RAM, Windows 10

Changes from the defaults

No response

Other software hooked into the game

No, nothing hooked in

hookshot_log.txt

the hookshot_log.txt was to big (40MB) for github upload, so i uploaded on transferXL:
https://www.transferxl.com/download/08Y4vpTkVg3HK

Screenshots or video

No response

Before you send it

  • I'm on the newest release, or the problem is still there on it.
  • I searched the open issues for this problem.
  • I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.
### Hookshot version v2.1.0 ### What kind of problem Crash, freeze or black screen ### What happened The screen froze when I got the Bigoron sword from the big Goron on the mountain. Then it crashed. ### Where in the game Goronen Mountain ### How often Once so far ### Graphics card and driver version RTX 2080 Super ### CPU, RAM and operating system Intel 10700k, 32GB RAM, Windows 10 ### Changes from the defaults _No response_ ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt the hookshot_log.txt was to big (40MB) for github upload, so i uploaded on transferXL: https://www.transferxl.com/download/08Y4vpTkVg3HK ### Screenshots or video _No response_ ### Before you send it - [x] I'm on the newest release, or the problem is still there on it. - [x] I searched the open issues for this problem. - [x] I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.
NotRexed commented 2026-11-12 03:08:23 +00:00 (Migrated from github.com)

Thanks for the report. Reports of the same kind are collected in #2507, which lists this one with your details and links back here, so one fix closes them together. Follow #2507 for the fix and add new details there (or here). If this turns out to be separate it will be reopened.

Thanks for the report. Reports of the same kind are collected in #2507, which lists this one with your details and links back here, so one fix closes them together. Follow #2507 for the fix and add new details there (or here). If this turns out to be separate it will be reopened.
Owner

@mooki000 commented on GitHub · 2026-11-12 12:46 UTC · original

Thanks—the full TransferXL log was downloaded, so there is no need to upload it again. It records a null-read exception in nvwgf2umx.dll+0x1521cf immediately after switching to windowed mode and recreating the swapchain. The session also exceeded its VRAM allowance, but that does not prove what caused the exception.

Did Alt+Enter, Alt+Tab, a fullscreen/windowed change or a display change happen just before the freeze? Please add the exact sequence, NVIDIA package version and changed graphics settings, plus the Windows application-crash entry if available. The log gives #2507 a more specific lead than the item location alone.

> [@mooki000](https://github.com/mooki000) commented on GitHub · 2026-11-12 12:46 UTC · [original](https://github.com/NotRexed/Hookshot/issues/2596#issuecomment-6823986518) Thanks—the full TransferXL log was downloaded, so there is no need to upload it again. It records a null-read exception in `nvwgf2umx.dll+0x1521cf` immediately after switching to windowed mode and recreating the swapchain. The session also exceeded its VRAM allowance, but that does not prove what caused the exception. Did Alt+Enter, Alt+Tab, a fullscreen/windowed change or a display change happen just before the freeze? Please add the exact sequence, NVIDIA package version and changed graphics settings, plus the Windows application-crash entry if available. The log gives #2507 a more specific lead than the item location alone. <!-- github-sync:c:6823986518 -->
Commenting is not possible because the repository is archived.
No milestone
No assignees
2 participants
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/Hookshot#2596
No description provided.