microsoft / microsoft/PowerToys
PowerToys Run crash with a 0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 139k
- Forks
- 8.6k
- PR merge metrics
- PR metrics pending
Description
### Microsoft PowerToys version
KernelPower BugcheckCode=209 decimal / 0xD1 - FAILURE_BUCKET_ID=MEMORY_CORRUPTION_LARGE
### Installation method
Microsoft Store
### Area(s) with issue?
General
### Steps to reproduce
Just using the machine.
### ✔️ Expected Behavior
_No response_
### ❌ Actual Behavior
VM crashed...
0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
KernelPower BugcheckCode=209 decimal / 0xD1
PROCESS_NAME=PowerToys.Peek
IMAGE_NAME=memory_corruption
FAILURE_BUCKET_ID=MEMORY_CORRUPTION_LARGE
computer crashed and had to reset from my server
### Upload Bug Report ZIP-file
[PowerToysReport_2026-05-23-06-54-29.zip](https://github.com/user-attachments/files/28171668/PowerToysReport_2026-05-23-06-54-29.zip)
### Additional Information
_No response_
### Other Software
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached PowerToysReport ZIP and the reported KernelPower 0xD1 details, especially PROCESS_NAME=PowerToys.Peek and IMAGE_NAME=memory_corruption. Check whether the report identifies a reproducible PowerToys cause; done requires an identified cause and a verified fix or clear evidence that the crash is external to PowerToys.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100