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

Popup about graphics driver issue #13112

New Issue
Closed
opened 2026-01-31 03:34:11 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 03:34:11 +00:00
Owner
Copy Link

Originally created by @vefatica on GitHub (Mar 20, 2021).

image

I almost always leave a WT running at night. Sometimes I initiate a shutdown of the monitors, sometimes not, in which case Windows turns them off after half an hour. Last night I let Windows handle it. This morning I found the popup pictured above. I have never seen anything like it before. Having pressed resume, all seems OK. Is there anywhere I can look for more info?

Microsoft Windows 10 Pro for Workstations
10.0.19042.867 (2009, 20H2)
WindowsTerminal: 1.7.572.0
Display adapter: Intel UHD Graphics P630
Driver: Intel, Date 2020-10-14, Version 27.20.100.8853 (Microsoft signed)

Originally created by @vefatica on GitHub (Mar 20, 2021). ![image](https://user-images.githubusercontent.com/61856645/111873956-3c3af400-8969-11eb-8958-b5fe3c05a0b3.png) I almost always leave a WT running at night. Sometimes I initiate a shutdown of the monitors, sometimes not, in which case Windows turns them off after half an hour. Last night I let Windows handle it. This morning I found the popup pictured above. I have never seen anything like it before. Having pressed resume, all seems OK. Is there anywhere I can look for more info? Microsoft Windows 10 Pro for Workstations 10.0.19042.867 (2009, 20H2) WindowsTerminal: 1.7.572.0 Display adapter: Intel UHD Graphics P630 Driver: Intel, Date 2020-10-14, Version 27.20.100.8853 (Microsoft signed)
claunia added the Issue-QuestionNeeds-TriageNeeds-Tag-FixResolution-Answered labels 2026-01-31 03:34:11 +00:00
claunia commented 2026-01-31 03:34:12 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Mar 20, 2021):

According to the System event log, the driver was updated overnight.

image

I don't see that version in Device Manager. In fact, when I search for an update, DevMgr says the best driver (the version from my previous post) is already installed. [So what's up with the Windows update?] I'll see what a restart does.

@vefatica commented on GitHub (Mar 20, 2021): According to the System event log, the driver was updated overnight. ![image](https://user-images.githubusercontent.com/61856645/111875148-ab671700-896e-11eb-93c1-0dc208b452f2.png) I don't see that version in Device Manager. In fact, when I search for an update, DevMgr says the best driver (the version from my previous post) is already installed. [So what's up with the Windows update?] I'll see what a restart does.
claunia commented 2026-01-31 03:34:12 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 20, 2021):

So, when Terminal tries to present a rendered frame using the Direct3D device it might encounter an error. If that error is anything except “the device was not ready and must be recreated,” it will try again three more times with a backoff interval of 150, 300, and 450 milliseconds.

You’ll only see that message when all three retries have failed. Sometimes the graphics driver goes away for longer than Terminal is willing to wait!

All it means is that we are going to stop retrying until you tell us your system is in a safe and stable state.

We used to simply crash in this circumstance ... 😄

@DHowett commented on GitHub (Mar 20, 2021): So, when Terminal tries to present a rendered frame using the Direct3D device it might encounter an error. If that error is anything except “the device was not ready and must be recreated,” it will try again _three more times_ with a backoff interval of 150, 300, and 450 milliseconds. You’ll only see that message when all three retries have failed. Sometimes the graphics driver goes away for longer than Terminal is willing to wait! All it means is that we are going to stop retrying until you tell us your system is in a safe and stable state. We used to simply crash in this circumstance ... 😄
claunia commented 2026-01-31 03:34:13 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Mar 20, 2021):

Sounds like no big deal. After a restart, DevMgr still shows 27.20.100.8853 as the driver version. I have no clue what the WindowsUpdate event was all about.

@vefatica commented on GitHub (Mar 20, 2021): Sounds like no big deal. After a restart, DevMgr still shows 27.20.100.8853 as the driver version. I have no clue what the WindowsUpdate event was all about.
claunia commented 2026-01-31 03:34:13 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 20, 2021):

(I’m glad that that popup is working as intended!)

@DHowett commented on GitHub (Mar 20, 2021): (I’m glad that that popup is working as intended!)
claunia commented 2026-01-31 03:34:13 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Mar 20, 2021):

Regarding the update ... apparently "extension" and "display [driver]" are different things. I'm not so puzzled now,

image

I wonder what actually happened that caused the interruption.

@vefatica commented on GitHub (Mar 20, 2021): Regarding the update ... apparently "extension" and "display [driver]" are different things. I'm not so puzzled now, ![image](https://user-images.githubusercontent.com/61856645/111885162-62c65280-899c-11eb-98d0-d018164b2d45.png) I wonder what actually happened that caused the interruption.
claunia commented 2026-01-31 03:34:13 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Jun 13, 2022):

This morning I noticed a few things. There was a display driver update last night and WT crashed. There was no local crash dump (local crash dumps are enabled). It was elevated when it crashed and un-elevated after being restarted. It was restarted in the wrong place (i.e., on the wrong monitor). The restarted instance did not respond to my (home-grown) toggle_the_monitor program (assigned to a key combo via AutoHotKey).

@vefatica commented on GitHub (Jun 13, 2022): This morning I noticed a few things. There was a display driver update last night and WT crashed. There was no local crash dump (local crash dumps are enabled). It was elevated when it crashed and un-elevated after being restarted. It was restarted in the wrong place (i.e., on the wrong monitor). The restarted instance did not respond to my (home-grown) toggle_the_monitor program (assigned to a key combo via AutoHotKey).
claunia commented 2026-01-31 03:34:14 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Jun 13, 2022):

On second thought, maybe the restarted instance was elevated; that would explain toggle_the_monitor not working. But I looked and don't recall seeing the elevated-indicating shield.

@vefatica commented on GitHub (Jun 13, 2022): On second thought, maybe the restarted instance was elevated; that would explain toggle_the_monitor not working. But I looked and don't recall seeing the elevated-indicating shield.
claunia commented 2026-01-31 03:34:14 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 13, 2022):

If you're encountering a new issue, I'd encourage you to file a separate workitem -- it's easier for us to track that way :)

@DHowett commented on GitHub (Jun 13, 2022): If you're encountering a new issue, I'd encourage you to file a separate workitem -- it's easier for us to track that way :)
claunia commented 2026-01-31 03:34:14 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Jun 13, 2022):

I didn't know if any of it was issue-worthy. It's no big deal, only some observations.

@vefatica commented on GitHub (Jun 13, 2022): I didn't know if any of it was issue-worthy. It's no big deal, only some observations.
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-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
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#13112
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?