积极答复者
server 2012R2 蓝屏 0x000000f5

问题
-
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F5, {6d, ffffe00199697960, ffffe00199697900, 0}
Probably caused by : fltmgr.sys ( fltmgr!FltReleaseContext+b54c )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
FLTMGR_FILE_SYSTEM (f5)
An unrecoverable failure occured inside the filter manager.
Arguments:
Arg1: 000000000000006d, The reason for the failure
Arg2: ffffe00199697960
Arg3: ffffe00199697900
Arg4: 0000000000000000
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0xF5
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff801fc39d8ac to fffff8017434d4c0
STACK_TEXT:
ffffd000`63bfe3f8 fffff801`fc39d8ac : 00000000`000000f5 00000000`0000006d ffffe001`99697960 ffffe001`99697900 : nt!KeBugCheckEx
ffffd000`63bfe400 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!FltReleaseContext+0xb54c
STACK_COMMAND: kb
FOLLOWUP_IP:
fltmgr!FltReleaseContext+b54c
fffff801`fc39d8ac cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: fltmgr!FltReleaseContext+b54c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: fltmgr
IMAGE_NAME: fltmgr.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5d73df35
FAILURE_BUCKET_ID: X64_0xF5_fltmgr!FltReleaseContext+b54c
BUCKET_ID: X64_0xF5_fltmgr!FltReleaseContext+b54c
Followup: MachineOwner
---------
0: kd> lmvm fltmgr
start end module name
fffff801`fc38e000 fffff801`fc3ea000 fltmgr (private pdb symbols) c:\mylocalsymbols\fltMgr.pdb\3F48EE3D70AA4EB3B23F4BF730FDBD4D2\fltMgr.pdb
Loaded symbol image file: fltmgr.sys
Mapped memory image file: C:\MyLocalSymbols\fltmgr.sys\5D73DF355c000\fltmgr.sys
Image path: \SystemRoot\system32\drivers\fltmgr.sys
Image name: fltmgr.sys
Timestamp: Sun Sep 08 00:47:49 2019 (5D73DF35)
CheckSum: 00063D97
ImageSize: 0005C000
File version: 6.3.9600.19482
Product version: 6.3.9600.19482
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: fltMgr.sys
OriginalFilename: fltMgr.sys
ProductVersion: 6.3.9600.19482
FileVersion: 6.3.9600.19482 (winblue_ltsb.190907-0600)
FileDescription: Microsoft Filesystem Filter Manager
LegalCopyright: © Microsoft Corporation. All rights reserved.
答案
-
你好,
根据您提供的信息来看,还是有关于fltmgr.sys文件,这个是微软的系统组件,fliter manager.通过官网的信息我们可以看到Parameter 1 0x6D意味着The context structure was dereferenced too many times. This means that the reference count on the Filter Manager's CONTEXT_NODE structure went to zero while it was still attached to its associated object.
而给出的答案是If Parameter 1 equals 0x6D, make sure that your minifilter driver does not call FltReleaseContext too many times for the given context
Bug Check 0xF5: FLTMGR_FILE_SYSTEM
这意味着你调用FltReleaseContext两次,在密切处理期间没有原因!FltMgr从FltAllocateContext释放上下文引用,引用被释放。
更新文件组件,请检查更新,安装新的安全更新。
如果回答是有帮助的, 请将其标记为答案, 可以帮助其他有相同问题的社区成员, 并快速找到有用的答复。
针对Windows 2008/2008R2的扩展支持将于2020年结束,之后微软将不再为其提供安全更新。点击此处或扫描二维码获取《在 Azure 上运行 Windows Server 的终极指南》,把握良机完成云迁移并实现业务现代化。
- 已标记为答案 santos.shen 2020年12月16日 2:01