starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

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

New Issue
Closed
opened 2026-01-31 08:44:24 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 08:44:24 +00:00
Owner
Copy Link

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:25 +00:00
claunia commented 2026-01-31 08:44:27 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Aug 11, 2025):

The most helpful part of the dump would be the backtrace, if you know how to extract that. Otherwise, you can share it with any team member via their mail (you can find mine on my GitHub profile).

However, it's very very likely you're hitting #18040. 0x80000003 means you captured a dump while it was still running (right?), and NtUserGetMessage indicates you captured the UI thread in its idle state. This is exactly how #18040 presents itself.

@lhecker commented on GitHub (Aug 11, 2025): The most helpful part of the dump would be the backtrace, if you know how to extract that. Otherwise, you can share it with any team member via their mail (you can find mine on my GitHub profile). However, it's very _very_ likely you're hitting #18040. `0x80000003` means you captured a dump while it was still running (right?), and `NtUserGetMessage` indicates you captured the UI thread in its idle state. This is exactly how #18040 presents itself.
claunia commented 2026-01-31 08:44:27 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Aug 18, 2025):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service[bot] commented on GitHub (Aug 18, 2025): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**. <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Author-Feedback Needs-Triage No-Recent-Activity
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23515
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?