Launcher: Random crashes on Windows 11 Insider with FAST_FAIL_SET_CONTEXT_DENIED #116
Labels
No labels
area/build
area/install
area/saves
area/tooling
area/ui
area/updates
ci: approved
good first issue
gpu/amd
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
platform/linux
platform/steam-deck
platform/windows
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/LongshotLauncher#116
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?
Reported by W.- on Discord
What happened
The launcher closes suddenly without a warning or error. Initially, this was reported while navigating the UI or leaving the launcher idle, with no compilation running; the reporter confirms it still closes without an error message. A later screenshot shows the launcher closing during game-file extraction: it is extracting title 1 (v131072) from
The Legend of Zelda Ocarina of Time [0400486024DEC000][v131072].nuptoF:\ocarina\nightly (4)\.game, and the visible progress is 2979.1 MiB written / 17597 files completed. The screenshot's log includes a toolchain path fornightly-189-aa95d35f, so this also reproduces on a later nightly during extraction.The original managed exception is unidentified. Event Viewer reports BEX64, faulting module
ntdll.dll, exception0xC0000409, subcode0x30, offset0x126FE6. WinDbg reportsFAST_FAIL_SET_CONTEXT_DENIEDinclr.dll!ProcessCLRException; relevant stack:ntdll!RcContinueExit,clr!ProcessCLRException,ntdll!RtlUnwindEx,KERNELBASE!RaiseException,clr!IL_Throw. Process crashed after about 40 seconds.Versions and channel
32bf43fa)nightly-189-aa95d35fduring extraction.System
Windows 11 Insider Preview build 26340.9882; Ryzen 5 5600X, RTX 4070 SUPER, 32 GB RAM, .NET Framework 4.8.1.
Other relevant details
Loaded third-party DLLs include OBS
graphics-hook64.dll(1.8.8), NVIDIAnvspcap64.dll(11.0.9.585), andSECOH-QAD.dll(WindowsActivator); involvement is unconfirmed.Available evidence
The reporter has multiple crash dumps, WinDbg logs, and Event Viewer reports available, but none were attached. A screenshot of the extraction log shows the game file, output path, and progress when the launcher was open. Please attach a dump and the corresponding WinDbg/Event Viewer details if possible, and note whether the crash persists with overlays/injected DLLs disabled and on a non-Insider Windows build, if available.
Questions
Is this known, could Insider Windows or injected DLLs contribute, and is there a way to enable verbose logging or capture the original .NET exception? PR #93, first released in v1.0.0-rc.7, added “Copy for a bug report” on launcher failure screens with the run log; it does not establish the cause of this fail-fast crash or capture the unidentified original exception. The reporter confirms the symptom persists without an error message; the screenshot now shows it can occur while extracting game files.
From W.- on Discord:
Additional diagnostics from W.-: multiple User Mini Dumps reproduce the same failure across rc.6, rc.7, and Nightly 87, with process uptime about 39 seconds on Windows 11 Insider build 26340. WER reports BEX64,
ntdll.dll,0xC0000409subcode0x30(offset0x0000000000126FE6); WinDbg identifiesFAST_FAIL_SET_CONTEXT_DENIEDwith stackntdll!RcContinueExit→clr!ProcessCLRException→ntdll!RtlUnwindEx→KERNELBASE!RaiseException→clr!RaiseTheExceptionInternalOnly→clr!IL_Throw. The original managed exception remains unidentified. Loaded modules include OBSgraphics-hook64.dll1.8.8.0 (C:\ProgramData\obs-studio-hook), NVIDIAnvspcap64.dll11.0.9.585, andSECOH-QAD.dll1.0.1.2 (C:\ProgramData\WindowsActivator); causation is unconfirmed. Reporter asks about verbose launcher logging, capturing the original exception, and whether a full dump would help, and can provide further diagnostics privately.Updated with more from null on Discord: Recorded confirmation that the launcher still closes without an error; noted the existing failure-report logging feature and its scope.
Updated with more from null on Discord: Added screenshot evidence showing the launcher closes during game-file extraction on nightly-189, with extraction progress and destination path.
Files:
From W.- on Discord:
W.- reports the crashes stopped and the launcher now works normally after disabling NVIDIA Overlay in NVIDIA App. This is a successful workaround and, given
nvspcap64.dllwas present in the crash dumps, suggests an NVIDIA Overlay compatibility conflict, though the exact cause is not proven.