BSOD (MULTIPLE_IRP_COMPLETE_REQUESTS, SYNTHETIC_WATCHDOG_TIMEOUT) when using CimFS snapshotter on Windows Server 2022
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- go, kubernetes
调研方向
首先，在并发拉取 Windows 镜像时复现报告的 containerd 2.2.1 和 CimFS 配置，然后检查可用的 minidump 以及 hcsshim 中与 CimFS 相关的入口点。完成的标准是确定该故障是否可以在 hcsshim 中处理，还是属于 Windows CimFS 驱动程序，并记录经确认的复现结果和诊断结论。
由索引模型根据 Issue 内容生成。
描述
Describe the bug
Using the CimFS snapshotter with containerd 2.2.1 on Windows Server 2022 (build 20348.4773, KB5075906 Feb 2026 cumulative update) causes repeated BSODs under container workload. Two distinct bugchecks occurred within 13 minutes of enabling CimFS:
0x00000044(MULTIPLE_IRP_COMPLETE_REQUESTS). a driver attempted to complete an IRP that was already completed.0x000001ca(SYNTHETIC_WATCHDOG_TIMEOUT). system became unresponsive.
Both crashes happened while Kubernetes was pulling and starting ~15-20 container images simultaneously using the CimFS snapshotter. The system was stable before switching from the windows snapshotter to cimfs and stable again after reverting.
To Reproduce
- Install containerd v2.2.1 on Windows Server 2022 (build 20348.4773).
- Configure containerd to use the
cimfssnapshotter:version = 3 [plugins.'io.containerd.cri.v1.images'] snapshotter = 'cimfs' [plugins.'io.containerd.transfer.v1.local'] [[plugins.'io.containerd.transfer.v1.local'.unpack_config]] platform = 'windows/amd64' snapshotter = 'cimfs' differ = 'cimfs' - Start containerd and kubelet.
- Pull multiple Windows container images concurrently (~15-20 images pulled by Kubernetes daemonsets and workloads).
- System BSODs within minutes.
Expected behavior
The CimFS snapshotter should handle concurrent image pulls and container creation without causing kernel crashes.
Configuration:
- Edition: Windows Server 2022 Datacenter (21H2)
- OS Build: 20348.4773 (KB5075906, February 2026 cumulative update)
cimfs.sysdriver version: 10.0.20348.3804- Container engine: containerd v2.2.1
- Container runtime shim: containerd-shim-runhcs-v1 (bundled with containerd 2.2.1)
- Orchestrator: Kubernetes v1.34.2 (kubelet)
- Hardware: Bare metal, AMD Ryzen 9 7950X, 64GB RAM
- Base images: Various
mcr.microsoft.com/windows/servercore:ltsc2022andmcr.microsoft.com/windows/nanoserver:ltsc2022based images
Additional context
Bugcheck details from Windows Event Log:
Bugcheck 1 (12:37:07 PST):
Code: 0x00000044 (MULTIPLE_IRP_COMPLETE_REQUESTS)
Parameters: (0xffffb1075846f4c0, 0x000000000000125a, 0x0000000000000000, 0x0000000000000000)
Minidump: 030526-8984-01.dmp (1.4 MB)
Bugcheck 2 (12:50:18 PST):
Code: 0x000001ca (SYNTHETIC_WATCHDOG_TIMEOUT)
Parameters: (0x0000000019628f83, 0x00000001bf799269, 0x00000001bf7ca01d, 0x0000000000000008)
Minidump: 030526-9125-01.dmp (630 KB)
Timeline:
- Switched containerd snapshotter from
windowstocimfsand restarted services - Kubernetes began pulling ~15-20 container images concurrently (daemonset pods + workloads)
- CimFS snapshots were being created successfully (55+ active snapshots observed)
- Several containers started successfully with CimFS layers before the crash
- First BSOD at 12:37 (
MULTIPLE_IRP_COMPLETE_REQUESTS) - System rebooted, containers began re-pulling images
- Second BSOD at 12:50 (
SYNTHETIC_WATCHDOG_TIMEOUT) - Reverted to
windowssnapshotter. system has been stable since
The CimFS snapshotter was loading correctly (io.containerd.snapshotter.v1 cimfs ok, io.containerd.differ.v1 cimfs ok) and creating snapshots before the crashes. The issue appears to be in the cimfs.sys kernel driver under concurrent load.
No prior bugchecks on this system since November 2022 (over 3 years of stability). Minidumps are available if needed.
- 主要语言
- Go
- 星标
- 698
- 派生
- 305
- 平均合并
- 2 天 5 小时
- 30 天内合并 PR
- 20
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoft/hcsshim 的其他 Issue
-
难度 3/5 1-2 天 新手友好度 55/100
microsoft/hcsshim#2947 · 1 条评论 · 已指派 1 人 ·
维护者通常 2 天内回复
-
Stdin handle required to avoid conpty race condition upon WCOW container startup with terminal可能已有人在做 @mcayland-ntx 于 39 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 42/100
microsoft/hcsshim#2831 · 3 条评论 ·
维护者通常 2 天内回复
-
难度 4/5 3-5 天 新手友好度 52/100
microsoft/hcsshim#2823 · 8 条评论 ·
维护者通常 2 天内回复
-
难度 3/5 1-2 天 新手友好度 68/100
维护者通常 2 天内回复
-
难度 4/5 3-5 天 新手友好度 62/100
维护者通常 2 天内回复
查看 microsoft/hcsshim 的全部 Issue
相似的 Issue
-
documentation priority:p1
难度 2/5 1-3 小时 新手友好度 78/100
yeixio/toskar-core#697 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
keyxmakerx/Chronicle#1532 ·
维护者通常 1 天内回复
-
The acquisition fixture's search path skips the argument table production enforces (regression from #285)可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
Judgment-Pack/judgment-pack-gateway#293 ·
维护者通常 1 天内回复
-
bug desktop v3 windows
难度 2/5 1-3 小时 新手友好度 65/100
esengine/DeepSeek-Reasonix#13697 · 1 条评论 ·
维护者通常 1 天内回复
-
good first issue help wanted
难度 1/5 1 小时以内 新手友好度 95/100
eugenioenko/ttt#959 ·
维护者通常 1 天内回复