Bad pool Caller (c2)

Question

Dears, my machine from DELL model Latitude 5440 is having a bad pool caller error frequently. Following is the minidump extract.

Microsoft (R) Windows Debugger Version 10.0.22621.755 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Temp\DUMP Files\070623-18343-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 22621 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Edition build lab: 22621.1928.amd64fre.ni_release_svc_prod3.230622-0951

Machine Name:

Kernel base = 0xfffff8051b200000 PsLoadedModuleList = 0xfffff8051be13480

Debug session time: Thu Jul 6 09:45:28.482 2023 (UTC + 4:00)

System Uptime: 0 days 14:21:02.719

Loading Kernel Symbols

...............................................................

................................................................

................................................................

................................................................

...........

Loading User Symbols

Loading unloaded module list

..................................................

For analysis of this file, run !analyze -v

7: 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: 0000000000000099, Attempt to free pool with invalid address (or corruption in pool header)

Arg2: ffff9104798ddd18, Address being freed

Arg3: 0000000000000000, 0

Arg4: 0000000000000000, 0

Debugging Details:

---

*** WARNING: Unable to verify timestamp for zapprd.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 4655 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 77338 

Key  : Analysis.Init.CPU.mSec 

Value: 2718 

Key  : Analysis.Init.Elapsed.mSec 

Value: 141235 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 123 

Key  : WER.OS.Branch 

Value: ni\_release\_svc\_prod3 

Key  : WER.OS.Timestamp 

Value: 2023-06-22T09:51:00Z 

Key  : WER.OS.Version 

Value: 10.0.22621.1928 

FILE_IN_CAB: 070623-18343-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

BUGCHECK_CODE: c2

BUGCHECK_P1: 99

BUGCHECK_P2: ffff9104798ddd18

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:

ffff85045b167038 fffff8051bcaf03e : 00000000000000c2 0000000000000099 ffff9104798ddd18 0000000000000000 : nt!KeBugCheckEx

ffff85045b167040 fffff8051ee5ee41 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!ExFreePoolWithTag+0x7de

ffff85045b1670d0 fffff8051f110402 : 0000000000000000 ffff85045b167360 ffff910454688510 0000000000000002 : NETIO!NetioFreeMdl+0xd061

ffff85045b167100 fffff8051ee32994 : ffff91043b999008 ffff910460c492a0 ffff85045b167360 ffff910454688510 : tcpip!FlpReturnNetBufferListChain+0xa7062

ffff85045b167160 fffff8051f0f339d : 0000000000000002 ffff910454688510 0000000000000009 ffff85045b1672a0 : NETIO!NetioDereferenceNetBufferList+0x1b4

ffff85045b1671a0 fffff8051f0240f1 : 0000000000000001 ffff91046076c010 0000000000000000 ffffd601955d1180 : tcpip!InetInspectReceiveTcpDatagram+0xcd25d

ffff85045b167310 fffff8051f03d239 : ffff01376e5fb32f 0000000000000000 0000000000000001 ffff9104766b9010 : tcpip!TcpTcbReceive+0x1e1

ffff85045b1674b0 fffff8051f03c20f : ffff91043b999008 0000007849615976 00000000b1a68c27 839a8ba566922018 : tcpip!TcpMatchReceive+0x539

ffff85045b167660 fffff8051f03be97 : ffff91043b6a3d00 ffff910474c1bb01 0000000000000000 000000000000b9f2 : tcpip!TcpReceive+0x35f

ffff85045b167770 fffff8051f09ba02 : ffff85045b167a70 ffff910460c492a0 0000000000000000 0000000000000006 : tcpip!TcpNlClientReceivePreValidatedDatagrams+0x17

ffff85045b1677a0 fffff8051f05090b : ffff91047287bdd0 0000000000000000 ffff85045b167e06 fffff8051b51e800 : tcpip!IpFlcReceivePreValidatedPackets+0x14a2

ffff85045b167a10 fffff8051b4638ba : 0000000000000007 fffff8051f0507c0 ffff91046210b0f4 0000000000000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x14b

ffff85045b167b60 fffff8051b46382d : fffff8051f0507c0 ffff85045b167ca8 ffff91043b658080 0000000000000000 : nt!KeExpandKernelStackAndCalloutInternal+0x7a

ffff85045b167bd0 fffff8051f051c20 : ffff85045b167d10 ffff910460c492a0 ffff85045b167d03 ffff85045b167d20 : nt!KeExpandKernelStackAndCalloutEx+0x1d

ffff85045b167c10 fffff8051ecb27c1 : 0000000000000000 0000000000000000 0000000000000000 000000002020444e : tcpip!FlReceiveNetBufferListChain+0x530

ffff85045b167ef0 fffff8051ecb21da : ffff9104723e2aa0 ffff85045b160800 ffff850400000000 ffff850400000001 : ndis!ndisMIndicateNetBufferListsToOpen+0x141

ffff85045b167fd0 fffff8051ecd63d8 : ffff9104547e8030 ffff910400000000 ffff850400000000 ffff9104547e8030 : ndis!ndisMTopReceiveNetBufferLists+0x24a

ffff85045b1680b0 fffff8051ecd8b7b : 0000000000000000 0000000000000100 ffff910460c492a0 000000000000000a : ndis!ndisInvokeNextReceiveHandler+0x54

ffff85045b168110 fffff8051f32382d : ffffd60195390000 ffff910460c492a0 0000000000000000 ffff910400000001 : ndis!NdisFIndicateReceiveNetBufferLists+0x344fb

ffff85045b1681c0 fffff8051f323c11 : 0000000000000100 ffff910454718010 ffff85045b168280 ffff9104619b9930 : wfplwfs!L2NdisFIndicateReceiveNetBufferLists+0xa3

ffff85045b168220 fffff8051ecd6365 : 0000000000000001 ffff910460c492a0 ffff910454718010 0000000000000000 : wfplwfs!LwfUpperRecvNetBufferLists+0x101

ffff85045b1682b0 fffff8051ecd5dd3 : 00000000000063e8 ffff85045b1683d0 0000000000000100 fffff8051b492ec5 : ndis!ndisCallReceiveHandler+0xb9

ffff85045b168300 fffff8051ecdcb4a : ffff85045b1683e8 ffff910453f97aa0 0000000000000000 0000000000000000 : ndis!ndisCallNextDatapathHandler<2,void * __ptr64 & __ptr64,void (__cdecl*& __ptr64)(void * __ptr64,_NET_BUFFER_LIST * __ptr64,unsigned long,unsigned long,unsigned long),void * __ptr64 & __ptr64,_NET_BUFFER_LIST * __ptr64 & __ptr64,unsigned long & __ptr64,unsigned long & __ptr64,unsigned long & __ptr64>+0x3f

ffff85045b168350 fffff8051ecd645f : ffff910460c492a0 0000000000000000 0000000000000001 0000000000000100 : ndis!ndisExpandDataPathStack<2,void __cdecl(void * __ptr64,_NET_BUFFER_LIST * __ptr64,unsigned long,unsigned long,unsigned long)>+0xae

ffff85045b1683f0 fffff8051ecd8b7b : 0000000000000000 0000000000000100 ffff910460c492a0 ffff910453f97aa0 : ndis!ndisInvokeNextReceiveHandler+0xdb

ffff85045b168450 fffff80526c05960 : 0000000000000000 0000000000000001 ffff910400000000 fffff80500000001 : ndis!NdisFIndicateReceiveNetBufferLists+0x344fb

ffff85045b168500 0000000000000000 : 0000000000000001 ffff910400000000 fffff80500000001 ffffd60100000100 : zapprd+0x5960

SYMBOL_NAME: NETIO!NetioFreeMdl+d061

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

IMAGE_VERSION: 10.0.22621.1972

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: d061

FAILURE_BUCKET_ID: 0xc2_99_NETIO!NetioFreeMdl

OS_VERSION: 10.0.22621.1928

BUILDLAB_STR: ni_release_svc_prod3

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {2def513e-002b-95b4-9931-f6ae0e497574}

Followup: MachineOwner

---

Answer 1

Hello Muhammad,

Good to see you in Microsoft Community.

Firstly, could you let me know the specific system version? You can check it by pressing the Win key + R key, and typing "winver", then press Enter, please take a screenshot/photo of it, and only send the relevant information without PII in the next reply.

Did this occur recently, or has it been going on for a while? If it was recent, did you have any special actions (such as installing system updates*,* hardware changes*, etc.*) before that?

The error code "0xc2_99_NETIO!NetioFreeMdl" indicates a specific type of system crash called a Bug Check or Blue Screen of Death (BSOD). In this case, the crash is related to the NETIO module and specifically the NetioFreeMdl function.

The NETIO module is a core component of the Windows operating system responsible for network I/O operations. The NetioFreeMdl function is used to free a memory descriptor list (MDL) object, which is used to describe and manage memory buffers involved in network operations.

The error code 0xc2 usually corresponds to a BAD_POOL_CALLER bug check, indicating that a kernel-mode process made an invalid memory pool request. The number 99 is typically associated with specific bug check parameters that provide additional information about the error.

To troubleshoot this issue, you can try the following steps:

1. Automatic virtual memory management You may set the virtual memory to be managed automatically by the system, which will optimize your system performance to some extent. Win + R to open "Run", type "sysdm.cpl", press Enter to open 'System Properties"> "Advanced" tab > "Performance" > "Settings"> "Advanced" tab"> "Virtual memory"> "Change" , check "Automatically manage paging file size for all drives", and press Enter to confirm.
2. Memory Diagnostic Win + Q to open the search box, type "MdSched", press Enter to open the program, select "Restart now and check for problems(recommended)", then restart the system and start memory diagnosis.
3. Repair possible corrupted system files Run the following commands to fix possible corrupted system files. Run Command Prompt as an administrator ("Win" logo key + "Q", type "cmd", select "Run as administrator"), and type the following commands one by one. These commands require network support, please keep your network stable and smooth.

    sfc /scannow
   
    DISM /Online /Cleanup-Image /RestoreHealth
   
    wsreset.exe
   
    for %i in (%windir%\\system32\\*.dll) do regsvr32.exe /s %i
   
    chkdsk C: /f
   

   Disclaimer*: Running* chkdsk can check the file system and file system metadata of a volume for logical and physical errors. To avoid any trouble for you, please follow them step-by-step, do not cancel or interrupt chkdsk, and back up important data. For more information, please refer to this chkdsk article.

If anything is unclear, please do not hesitate to let me know.

Best Regards,

Mosken_L - MSFT | Microsoft Community Support Specialist