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

Blue screen when quitting Terminal during startup #4564

New Issue
Closed
opened 2026-01-30 23:50:44 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 23:50:44 +00:00
Owner
Copy Link

Originally created by @amarchino on GitHub (Oct 20, 2019).

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):
Microsoft Windows [Version 10.0.18362.418]

Any other software?
WSL (version 1, not tried on WSL2 since not on Insider Program).
Terminal (version: 0.5.2762.0)

Steps to reproduce

Set up WSL as the default terminal to be used in the application.
Start up the Terminal, and before the startup is complete (meaning, before the terminal is available to be interacted with), close it down.

Expected behavior

Closing the instance of Terminal

Actual behavior

Blue screen on the pc, with a "KMODE EXCEPTION NOT HANDLED".

I stand at disposal for whatever data might be needed.

Originally created by @amarchino on GitHub (Oct 20, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Windows Terminal version (if applicable): Microsoft Windows [Version 10.0.18362.418] Any other software? WSL (version 1, not tried on WSL2 since not on Insider Program). Terminal (version: 0.5.2762.0) ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Set up WSL as the default terminal to be used in the application. Start up the Terminal, and before the startup is complete (meaning, before the terminal is available to be interacted with), close it down. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Closing the instance of Terminal # Actual behavior <!-- What's actually happening? --> Blue screen on the pc, with a "KMODE EXCEPTION NOT HANDLED". I stand at disposal for whatever data might be needed.
claunia commented 2026-01-30 23:50:45 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 21, 2019):

/feedback

@DHowett-MSFT commented on GitHub (Oct 21, 2019): /feedback
claunia commented 2026-01-30 23:50:45 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 21, 2019):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost commented on GitHub (Oct 21, 2019): Hi there!<br><br>Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-30 23:50:46 +00:00
Author
Owner
Copy Link

@amarchino commented on GitHub (Oct 21, 2019):

Link to the feedback: https://aka.ms/AA6dgr8
I think I actually cannot attach come data to the feedback due to the Blue Screen (which would kill the recording)
If need be, I'll try and recover/send a dump via the proposed method.

@amarchino commented on GitHub (Oct 21, 2019): Link to the feedback: https://aka.ms/AA6dgr8 I think I actually cannot attach come data to the feedback due to the Blue Screen (which would kill the recording) If need be, I'll try and recover/send a dump via the proposed method.
claunia commented 2026-01-30 23:50:46 +00:00
Author
Owner
Copy Link

@dclong commented on GitHub (Aug 21, 2021):

Yesterday I encountered 2 blue screens with my Windows Insider Build. I believe it was caused by using WSL with Windows Terminal because without using Windows Terminal and keep all other apps running the blue screen never happened again and I did use Windows Terminal before (without WSL) and it didn't cause blue screen either. The stop code were SYSTEM_SERVICE_EXCEPTION and ATTEMPTED_WRITE_TO_READONLY_MEMORY.

@dclong commented on GitHub (Aug 21, 2021): Yesterday I encountered 2 blue screens with my Windows Insider Build. I believe it was caused by using WSL with Windows Terminal because without using Windows Terminal and keep all other apps running the blue screen never happened again and I did use Windows Terminal before (without WSL) and it didn't cause blue screen either. The stop code were SYSTEM_SERVICE_EXCEPTION and ATTEMPTED_WRITE_TO_READONLY_MEMORY.
claunia commented 2026-01-30 23:50:46 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 9, 2021):

Hey so, like I mentioned in #9870, I don't think we're the right folks to investigate this one. If this is still hitting for you, I'd try asking over at https://github.com/microsoft/WSL. Thanks!

@zadjii-msft commented on GitHub (Dec 9, 2021): Hey so, like I mentioned in #9870, I don't think we're the right folks to investigate this one. If this is still hitting for you, I'd try asking over at https://github.com/microsoft/WSL. Thanks!
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 Area-Server Issue-Bug Needs-Tag-Fix Priority-1 Product-Conhost Severity-Crash
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#4564
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?