freeze and crashed after Bigoron's sword retrieved from Goron Mountain #2596
Labels
No labels
accessibility
autorelease: pending
autorelease: tagged
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
testing wanted
wontfix
No milestone
No assignees
2 participants
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot#2596
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
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—the full TransferXL log was downloaded, so there is no need to upload it again. It records a null-read exception in
nvwgf2umx.dll+0x1521cfimmediately 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.