Terminal becomes unresponsive when a game is running (GUI freeze with EXCEPTION_CODE: 80000003) #23512

Open
opened 2026-01-31 08:44:20 +00:00 by claunia · 0 comments
Owner

Originally created by @Akarie64 on GitHub (Aug 10, 2025).

Windows Terminal version

1.22.12111.0

Windows build number

10.0.26100.0

Other Software

Any games (e.g., Limbus Company, Delta Force).

Steps to reproduce

  1. Launch Windows Terminal.
  2. Launch a game.
  3. Attempt to interact with the terminal's UI (e.g., by typing).
  4. Observe that the terminal's GUI is frozen.

Expected Behavior

The Windows Terminal should remain responsive and usable, even when a resource-intensive game is running in the background.

Actual Behavior

The terminal's GUI becomes unresponsive. Keystrokes are buffered but not rendered, and the UI does not
update. After a long, indeterminate period, the terminal might process the buffered commands all at once
before freezing again.

We have captured crash dumps during these periods of unresponsiveness and identified the following consistent exception details:

  • Exception Code: 0x80000003 (A breakpoint was reached)
  • Faulting Modules & Call Stacks:
    * Scenario 1: Playing Delta Force
    * Faulting Module: Win32u.dll
    * Stack Trace: in32u!NtUserGetMessage
    * Scenario 2: Playing Limbus Company
    * Faulting Module: Win32u.dll
    * Stack Trace: coreclr!Thread::DoAppropriateAptstateWait
    Dump files are available upon request.
Originally created by @Akarie64 on GitHub (Aug 10, 2025). ### Windows Terminal version 1.22.12111.0 ### Windows build number 10.0.26100.0 ### Other Software Any games (e.g., Limbus Company, Delta Force). ### Steps to reproduce 1. Launch Windows Terminal. 2. Launch a game. 3. Attempt to interact with the terminal's UI (e.g., by typing). 4. Observe that the terminal's GUI is frozen. ### Expected Behavior The Windows Terminal should remain responsive and usable, even when a resource-intensive game is running in the background. ### Actual Behavior The terminal's GUI becomes unresponsive. Keystrokes are buffered but not rendered, and the UI does not update. After a long, indeterminate period, the terminal might process the buffered commands all at once before freezing again. We have captured crash dumps during these periods of unresponsiveness and identified the following consistent exception details: * Exception Code: 0x80000003 (A breakpoint was reached) * Faulting Modules & Call Stacks: * Scenario 1: Playing Delta Force * Faulting Module: Win32u.dll * Stack Trace: in32u!NtUserGetMessage * Scenario 2: Playing Limbus Company * Faulting Module: Win32u.dll * Stack Trace: coreclr!Thread::DoAppropriateAptstateWait Dump files are available upon request.
claunia added the Needs-TriageIssue-BugNeeds-Author-FeedbackNo-Recent-Activity labels 2026-01-31 08:44:20 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23512