藍屏 Badpoolcaller解決問題

Question

想請問為什麼用一段時間電腦就會藍屏 提示跑出BADPOOLCALLER?

以下為用windbg查看DMP的東西 想請問該如何解決

Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\121521-11953-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`14c00000 PsLoadedModuleList = 0xfffff807`1582a2d0
Debug session time: Wed Dec 15 20:42:41.919 2021 (UTC + 8:00)
System Uptime: 1 days 21:00:32.966
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
...................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`14ff72a0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffab8b`7b7796d0=00000000000000c2
8: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 000000000000000d, Attempt to release quota on a corrupted pool allocation.
Arg2: ffffad8c52e0ead0, Address of pool
Arg3: 000000006578652e, Pool allocation's tag
Arg4: 930563a0d3066ca6, Quota process pointer (bad).

Debugging Details:
------------------

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3671

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 36539

    Key  : Analysis.Init.CPU.mSec
    Value: 655

    Key  : Analysis.Init.Elapsed.mSec
    Value: 77338

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 81

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

FILE_IN_CAB:  121521-11953-01.dmp

BUGCHECK_CODE:  c2

BUGCHECK_P1: d

BUGCHECK_P2: ffffad8c52e0ead0

BUGCHECK_P3: 6578652e

BUGCHECK_P4: 930563a0d3066ca6

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

STACK_TEXT:  
ffffab8b`7b7796c8 fffff807`1503d526     : 00000000`000000c2 00000000`0000000d ffffad8c`52e0ead0 00000000`6578652e : nt!KeBugCheckEx
ffffab8b`7b7796d0 fffff807`155b1149     : 4bedb1bf`eaa8c12b ee76b827`61b3ddad ffffad8c`45aed810 01000000`00100000 : nt!ExFreeHeapPool+0x1b45d6
ffffab8b`7b7797b0 fffff807`14e69f24     : ffffad8c`430f6ae0 ffffad8c`45b1a030 ffffad8c`5770eb70 fffff807`152dbeec : nt!ExFreePool+0x9
ffffab8b`7b7797e0 fffff807`152791b2     : ffffad8c`5770eb70 ffffad8c`5770eb70 ffffab8b`7b779a39 00000000`00000000 : nt!IopDeleteFileObjectExtension+0xc0
ffffab8b`7b779830 fffff807`15273440     : ffffab8b`7b779a39 00000000`00000000 ffffad8c`430f6ae0 ffffad8c`00000000 : nt!IopDeleteFile+0x212
ffffab8b`7b7798b0 fffff807`14e08357     : 00000000`00000000 00000000`00000000 ffffab8b`7b779a39 ffffad8c`5770eb70 : nt!ObpRemoveObjectRoutine+0x80
ffffab8b`7b779910 fffff807`151f3b79     : ffffad8c`5770eb40 00000000`00000000 ffff9b86`00000000 ffffad8c`5770eb40 : nt!ObfDereferenceObjectWithTag+0xc7
ffffab8b`7b779950 fffff807`151f79ac     : 00000000`00000484 000001f2`b9fa0000 00000000`00000000 fffff807`15200daa : nt!ObCloseHandleTableEntry+0x6c9
ffffab8b`7b779a90 fffff807`15008cb8     : ffffad8c`4d484500 000001f2`b9fa0000 ffffab8b`7b779b80 ffffad8c`4d78a340 : nt!NtClose+0xec
ffffab8b`7b779b00 00007ff9`6374cf54     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000005d`51a7d6d8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`6374cf54

SYMBOL_NAME:  nt!IopDeleteFileObjectExtension+c0

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.1348

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  c0

FAILURE_BUCKET_ID:  0xc2_d_nt!IopDeleteFileObjectExtension

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3b8a7571-7a82-7faa-d740-ec0cece272a9}

Followup:     MachineOwner
---------

Answer 1

您好，我是独立顾问 Yu Huang。很高兴能为您提供技术支持！

了解到您的情况，当您遇到蓝屏问题时，需要上传 dump 日志文件以供我们进行分析。

您可以通过以下方式收集 dump 日志文件：

在任务栏搜索框中输入 “控制面板”，回车。将查看方式调整为 “大图标”，选择 “系统”>“高级系统设置”>“高级”>“启动和故障恢复”>“设置”>“写入调试信息”>选择 “小内存转储 (256KB)”，路径选择默认，确定并重启设备。

当您再次蓝屏后，请您前往 C:\Windows\Minidump 中提取 dump 日志文件，将 dump 日志文件上传至百度网盘或其他国内网盘，然后通过分享生成链接，将链接回复至此问题或重新提问以供我们分析。

希望您的问题能够早日得到解决！

感谢您的支持。