Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\062422-11187-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 Personal Machine Name: Kernel base = 0xfffff801`13c00000 PsLoadedModuleList = 0xfffff801`1482a2b0 Debug session time: Fri Jun 24 23:03:27.382 2022 (UTC 8:00) System Uptime: 0 days 7:06:41.130 Loading Kernel Symbols .. Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. ............................................................. ................................................................ ................................................................ ................... Loading User Symbols Loading unloaded module list .................................................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff801`13ff7dd0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffff8685`00cf4a30=00000000000000c2 2: 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: 0000000000000061, type of pool violation the caller is guilty of. Arg2: ffffde0117b07500 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 5421 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 58884 Key : Analysis.Init.CPU.mSec Value: 1655 Key : Analysis.Init.Elapsed.mSec Value: 197835 Key : Analysis.Memory.CommitPeak.Mb Value: 90 Key : Bugcheck.Code.DumpHeader Value: 0xc2 Key : Bugcheck.Code.Register Value: 0xc2 Key : Dump.Attributes.AsUlong Value: 8 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 FILE_IN_CAB: 062422-11187-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: c2 BUGCHECK_P1: 61 BUGCHECK_P2: ffffde0117b07500 BUGCHECK_P3: 0 BUGCHECK_P4: 0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffff8685`00cf4a28 fffff801`14072c77 : 00000000`000000c2 00000000`00000061 ffffde01`17b07500 00000000`00000000 : nt!KeBugCheckEx ffff8685`00cf4a30 fffff801`13f7ffac : 00000000`00060001 ffff8685`00000000 8a000000`ce189863 00000000`00000000 : nt!MmFreeContiguousMemory 0x14a347 ffff8685`00cf4ab0 fffff801`1911f8a5 : fffff801`1911fb00 ffff9a8b`b4703d50 00000000`01000200 ffff9a8b`b96448f0 : nt!HalFreeCommonBuffer 0xc ffff8685`00cf4ae0 fffff801`1911fb56 : ffff9a8b`a7a151a0 fffff801`1911fb30 ffff9a8b`a248ba70 ffffde01`17b07500 : ndis!ndisFreeSharedMemoryInternal 0xb9 ffff8685`00cf4b30 fffff801`13ebfae5 : ffff9a8b`bb9a2040 fffff801`1911fb30 ffff9a8b`a248ba70 ffff9a8b`0000000d : ndis!ndisMQueuedFreeSharedHandler 0x26 ffff8685`00cf4b70 fffff801`13eeea75 : ffff9a8b`bb9a2040 00000000`00000080 ffff9a8b`a2492240 ffffffff`00000001 : nt!ExpWorkerThread 0x105 ffff8685`00cf4c10 fffff801`13fff428 : ffffde01`130ce180 ffff9a8b`bb9a2040 fffff801`13eeea20 ffffffff`ffffffff : nt!PspSystemThreadStartup 0x55 ffff8685`00cf4c60 00000000`00000000 : ffff8685`00cf5000 ffff8685`00cef000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread 0x28 SYMBOL_NAME: ndis!ndisFreeSharedMemoryInternal b9 MODULE_NAME: ndis IMAGE_NAME: ndis.sys IMAGE_VERSION: 10.0.19041.1526 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: b9 FAILURE_BUCKET_ID: 0xc2_61_ndis!ndisFreeSharedMemoryInternal OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {12731988-0c61-4c46-21d2-68a97fe0949d} Followup: MachineOwner --------- 2: 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: 0000000000000061, type of pool violation the caller is guilty of. Arg2: ffffde0117b07500 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4343 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 4378 Key : Analysis.Init.CPU.mSec Value: 7077 Key : Analysis.Init.Elapsed.mSec Value: 256719 Key : Analysis.Memory.CommitPeak.Mb Value: 92 Key : Bugcheck.Code.DumpHeader Value: 0xc2 Key : Bugcheck.Code.Register Value: 0xc2 Key : Dump.Attributes.AsUlong Value: 8 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 FILE_IN_CAB: 062422-11187-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: c2 BUGCHECK_P1: 61 BUGCHECK_P2: ffffde0117b07500 BUGCHECK_P3: 0 BUGCHECK_P4: 0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffff8685`00cf4a28 fffff801`14072c77 : 00000000`000000c2 00000000`00000061 ffffde01`17b07500 00000000`00000000 : nt!KeBugCheckEx ffff8685`00cf4a30 fffff801`13f7ffac : 00000000`00060001 ffff8685`00000000 8a000000`ce189863 00000000`00000000 : nt!MmFreeContiguousMemory 0x14a347 ffff8685`00cf4ab0 fffff801`1911f8a5 : fffff801`1911fb00 ffff9a8b`b4703d50 00000000`01000200 ffff9a8b`b96448f0 : nt!HalFreeCommonBuffer 0xc ffff8685`00cf4ae0 fffff801`1911fb56 : ffff9a8b`a7a151a0 fffff801`1911fb30 ffff9a8b`a248ba70 ffffde01`17b07500 : ndis!ndisFreeSharedMemoryInternal 0xb9 ffff8685`00cf4b30 fffff801`13ebfae5 : ffff9a8b`bb9a2040 fffff801`1911fb30 ffff9a8b`a248ba70 ffff9a8b`0000000d : ndis!ndisMQueuedFreeSharedHandler 0x26 ffff8685`00cf4b70 fffff801`13eeea75 : ffff9a8b`bb9a2040 00000000`00000080 ffff9a8b`a2492240 ffffffff`00000001 : nt!ExpWorkerThread 0x105 ffff8685`00cf4c10 fffff801`13fff428 : ffffde01`130ce180 ffff9a8b`bb9a2040 fffff801`13eeea20 ffffffff`ffffffff : nt!PspSystemThreadStartup 0x55 ffff8685`00cf4c60 00000000`00000000 : ffff8685`00cf5000 ffff8685`00cef000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread 0x28 SYMBOL_NAME: ndis!ndisFreeSharedMemoryInternal b9 MODULE_NAME: ndis IMAGE_NAME: ndis.sys IMAGE_VERSION: 10.0.19041.1526 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: b9 FAILURE_BUCKET_ID: 0xc2_61_ndis!ndisFreeSharedMemoryInternal OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {12731988-0c61-4c46-21d2-68a97fe0949d} Followup: MachineOwner ---------

Hi展周YourminidumpfileindicatesitisthenetworkcarddevicedriveronyourPCcausingthebluescreens.GotothesupportpageforyourPCorMotherboardonthemanufacturerswebsite,thenfromthere,downloadandinstalltheversionofnetworkcardevicedriverstheyrecommend.


点赞(46) 打赏

微信小程序

微信扫一扫体验

立即
投稿

微信公众账号

微信扫一扫加关注

发表
评论
返回
顶部