积极答复者
bugcheck 0x00000019

问题
-
我的多台工作站在下午的时候同时出现了蓝屏,错误代码是:
0x00000019(0x0000000020,0xfffffa802c24b660,0fffffa802c24b880,0x00000004220016)
我检查了日志,没有特别的报错,检查了dump文件,检查的结果如下:
BAD_POOL_HEADER (19)The pool is already corrupt at the time of the current request.This may or may not be due to the caller.The internal pool links must be walked to figure out a possible cause ofthe problem, and then special pool applied to the suspect tags or the driververifier to a suspect driver.Arguments:Arg1: 0000000000000020, a pool block header size is corrupt.Arg2: fffffa80307585c0, The pool entry we were looking for within the page.Arg3: fffffa80307587e0, The next pool entry.Arg4: 000000000422001f, (reserved)
Debugging Details: ------------------ KEY_VALUES_STRING: 1 STACKHASH_ANALYSIS: 1 TIMELINE_ANALYSIS: 1 DUMP_CLASS: 1 DUMP_QUALIFIER: 400 BUILD_VERSION_STRING: 7601.24214.amd64fre.win7sp1_ldr_escrow.180801-1700 SYSTEM_MANUFACTURER: Hewlett-Packard SYSTEM_PRODUCT_NAME: HP Z440 Workstation BIOS_VERSION: M60 v02.34 BIOS_DATE: 05/18/2017 BASEBOARD_MANUFACTURER: Hewlett-Packard BASEBOARD_PRODUCT: 212B BASEBOARD_VERSION: 1.01 DUMP_TYPE: 2 BUGCHECK_P1: 20 BUGCHECK_P2: fffffa80307585c0 BUGCHECK_P3: fffffa80307587e0 BUGCHECK_P4: 422001f BUGCHECK_STR: 0x19_20 POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80003ef5100 Unable to get MmSystemRangeStart GetUlongPtrFromAddress: unable to read from fffff80003ef52f0 GetUlongPtrFromAddress: unable to read from fffff80003ef54a8 GetPointerFromAddress: unable to read from fffff80003ef50d8 fffffa80307585c0 Nonpaged pool CPU_COUNT: 8 CPU_MHZ: da3 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 3f CPU_STEPPING: 2 CPU_MICROCODE: 6,3f,2,0 (F,M,S,R) SIG: 39'00000000 (cache) 39'00000000 (init) CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 ANALYSIS_SESSION_TIME: 11-12-2018 16:35:02.0404 ANALYSIS_VERSION: 10.0.18239.1000 amd64fre LAST_CONTROL_TRANSFER: from fffff80003e33ada to fffff80003cea9a0 STACK_TEXT: fffff880`11ee31e8 fffff800`03e33ada : 00000000`00000019 00000000`00000020 fffffa80`307585c0 fffffa80`307587e0 : nt!KeBugCheckEx fffff880`11ee31f0 fffff880`10678f26 : 00000000`00000004 00000000`00000000 fffff880`78456651 fffffa80`31453a68 : nt!ExFreePool+0xd82 fffff880`11ee32a0 00000000`00000004 : 00000000`00000000 fffff880`78456651 fffffa80`31453a68 00000000`00000004 : Qfmon+0x1f26 fffff880`11ee32a8 00000000`00000000 : fffff880`78456651 fffffa80`31453a68 00000000`00000004 fffffa80`31453a68 : 0x4 THREAD_SHA1_HASH_MOD_FUNC: facda2237c266b7d99bbc7e8e0f5cb0a4e3b22e0 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d5a1c31cad06f40c0583f96c1724630cb67f2eda THREAD_SHA1_HASH_MOD: ae652936ca1cdde4162a7ecb142dcc1d85cbb58a FOLLOWUP_IP: Qfmon+1f26 fffff880`10678f26 ?? ??? SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: Qfmon+1f26 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Qfmon IMAGE_NAME: Qfmon.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5620d21f STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: X64_0x19_20_Qfmon+1f26 BUCKET_ID: X64_0x19_20_Qfmon+1f26 PRIMARY_PROBLEM_CLASS: X64_0x19_20_Qfmon+1f26 TARGET_TIME: 2018-11-08T07:14:09.000Z OSBUILD: 7601 OSSERVICEPACK: 1000 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 272 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 7 OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2018-08-02 10:18:10 BUILDDATESTAMP_STR: 180801-1700 BUILDOSVER_STR: 6.1.7601.24214.amd64fre.win7sp1_ldr_escrow.180801-1700 ANALYSIS_SESSION_ELAPSED_TIME: 44f ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0x19_20_qfmon+1f26 FAILURE_ID_HASH: {4e6414c5-7ea7-eaf9-42e5-d55fb5bf5af3} Followup: MachineOwner ---------
还请帮忙看看问题出在哪里?
答案
-
您好,
感谢您的回复。
1.我查看了minidump, 发现都是Qfmon.sys 导致的蓝屏, 我们可以更新或者禁用这个驱动,看问题是否复现。
2.由于minidump含有的信息比较少, 我们可以配置个kernel dump或者complete memory dump,如果等到下次问题再出现时,再次上传dump。
- 右击我的电脑,选择属性。
- 点击高级系统设置,选中高级栏。
- 点击Startup and Recovery下面的设置
- 设置系统失败的时候生成kernel memory dump.
- 重启电脑生效。
---------------------------
Best regards,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- 已标记为答案 ZhuZeLin 2018年11月27日 9:03
全部回复
-
您好,
感谢您在我们论坛发帖。
1.可以把dump压缩上传到OneDrive,分享链接。您贴出的dump无法看出太多信息,可能是symbol没有设置正确。
2.另外,这里有两篇文章关于bugcheck 0x00000019 ,我们可以参考下。
http://www.faultwire.com/solutions-fatal_error/BAD-POOL-HEADER-0x00000019-*1040.html?order=date
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x19--bad-pool-header
Cora
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. -
您好,
请问现在进展如何?
如果还有其他问题,可以在下面回帖,
Best regards,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. -
您好,
请问现在进展如何?
如果还有其他问题,可以在下面回帖.
Best regards,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. -
您好,
感谢您的回复。
1.我查看了minidump, 发现都是Qfmon.sys 导致的蓝屏, 我们可以更新或者禁用这个驱动,看问题是否复现。
2.由于minidump含有的信息比较少, 我们可以配置个kernel dump或者complete memory dump,如果等到下次问题再出现时,再次上传dump。
- 右击我的电脑,选择属性。
- 点击高级系统设置,选中高级栏。
- 点击Startup and Recovery下面的设置
- 设置系统失败的时候生成kernel memory dump.
- 重启电脑生效。
---------------------------
Best regards,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- 已标记为答案 ZhuZeLin 2018年11月27日 9:03