BSOD --- BAD_POOL_CALLER (c2)

Question

BSOD --- BAD_POOL_CALLER (c2)

Anonymous

Hello, I have a friend who is experiencing constant BSOD. I got him to send his .dmp file to me, but I can not interpret it on my own. Can anyone give us some guidance?:

*******************************************************************************
*                                                                             *
*                        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: ffffbc8fb83b7e90, Address being freed
Arg3: 0000000000000000, 0
Arg4: 0000000000000000, 0

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2187

    Key  : Analysis.Elapsed.mSec
    Value: 5272

    Key  : Analysis.IO.Other.Mb
    Value: 15

    Key  : Analysis.IO.Read.Mb
    Value: 16

    Key  : Analysis.IO.Write.Mb
    Value: 46

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xc2

    Key  : Failure.Bucket
    Value: 0xc2_99_nt!MiStoreFreeWriteSupport

    Key  : Failure.Hash
    Value: {e7129fd1-6a76-c961-b3bf-0d846ae4dcdb}

    Key  : WER.OS.Branch
    Value: ni_release_svc_prod3

    Key  : WER.OS.Version
    Value: 10.0.22621.2506

BUGCHECK_CODE:  c2

BUGCHECK_P1: 99

BUGCHECK_P2: ffffbc8fb83b7e90

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  020624-9343-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MemCompression

STACK_TEXT:  
fffff600`f64e3758 fffff805`694cb3d1     : 00000000`000000c2 00000000`00000099 ffffbc8f`b83b7e90 00000000`00000000 : nt!KeBugCheckEx
fffff600`f64e3760 fffff805`68fcd891     : ffffbc8f`b83b7e90 00000000`00000330 00000000`00000057 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x14d
fffff600`f64e3800 fffff805`694acdde     : ffffbc8f`b83b79e0 00000000`00000000 00000000`00000330 00000000`00000000 : nt!VerifierFreeTrackedPool+0x41
fffff600`f64e3840 fffff805`69059e1d     : ffffbc8f`ffff8080 ffffbc8f`b83b7e90 fffffac0`00000057 00000000`00000330 : nt!ExFreePoolWithTag+0xcce
fffff600`f64e38d0 fffff805`6905a355     : ffffbc8f`b83b7ea0 00000000`00000000 ffff8080`59f12000 00000000`00000005 : nt!MiStoreFreeWriteSupport+0x4d
fffff600`f64e3900 fffff805`68fcb1ba     : ffffbc8f`b83b7ea0 ffffbc8f`8a0e1010 00000000`00000001 fffff600`f64e39d0 : nt!MiStoreModifiedWriteComplete+0xe1
fffff600`f64e3930 fffff805`68fca80f     : ffffbc8f`b83b7ea0 ffffbc8f`8a0e1010 00000000`00000001 fffff600`f64e39d0 : nt!SmIoRequestComplete+0x3e
fffff600`f64e3960 fffff805`68e5e410     : 00000000`00000000 ffffbc8f`8a0e1010 00000000`00000001 00000000`00000000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxWorkItemComplete+0x18f
fffff600`f64e39b0 fffff805`68ec35a9     : ffffbc8f`b2890000 fffff600`f64e3a88 00000000`00000001 ffffbc8f`bc328000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmWorkItemFree+0x13e
fffff600`f64e3a30 fffff805`68d3d611     : 00000000`00000000 ffffbc8f`00000000 ffffbc8f`b28d9240 00000000`8a92fab8 : nt!SMKM_STORE<SM_TRAITS>::SmStWorker+0x185f89
fffff600`f64e3ac0 fffff805`68d07167     : ffffbc8f`b2890000 fffff805`68d3d600 fffff600`f6dc3038 004fa4ef`bd9bbfff : nt!SMKM_STORE<SM_TRAITS>::SmStWorkerThread+0x11
fffff600`f64e3af0 fffff805`68e1bb94     : ffff8080`4bf6b180 ffffbc8f`b28d9240 fffff805`68d07110 00000000`00000000 : nt!PspSystemThreadStartup+0x57
fffff600`f64e3b40 00000000`00000000     : fffff600`f64e4000 fffff600`f64dd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME:  nt!MiStoreFreeWriteSupport+4d

MODULE_NAME: nt

IMAGE_VERSION:  10.0.22621.3007

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  4d

FAILURE_BUCKET_ID:  0xc2_99_nt!MiStoreFreeWriteSupport

OS_VERSION:  10.0.22621.2506

BUILDLAB_STR:  ni_release_svc_prod3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e7129fd1-6a76-c961-b3bf-0d846ae4dcdb}

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

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Answer 1

My name is Jonathan Deives. I'm an Independent Advisor and I will be happy to help you today.

The minidump log do not indicate any driver or hardware causes.

He will need try to force Windows to show failed drivers and produce minidump files, turn on Driver Verifier.

Make the BSOD happen 3 times and after that see if the files were created.

Before you run Driver Verifier, please create a new System Restore Point.

https://answers.microsoft.com/en-us/windows/for...

Share via

BSOD --- BAD_POOL_CALLER (c2)

1 answer