bsod bad_pool_caller

Question

happens whenever i open valo/league. i hope this can help. other apps work just fine.

*******************************************************************************
*                                                                             *
*                        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: ffffbc8dfbbc29e0, Address of pool
Arg3: 00000000506d7054, Pool allocation's tag
Arg4: 00000000842af68b, Quota process pointer (bad).

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3437

    Key  : Analysis.Elapsed.mSec
    Value: 5031

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29507.1001

    Key  : Analysis.Version.Description
    Value: 10.2511.5.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2511.5.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xc2

    Key  : Bugcheck.Code.TargetModel
    Value: 0xc2

    Key  : Dump.Attributes.AsUlong
    Value: 0x21008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0xc2_d_tpm!Tpm20Resource::_scalar_deleting_destructor_

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff803b1771ff1

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0xb71ff1

    Key  : Failure.Hash
    Value: {91db07c7-7710-80a4-de7a-d91ead109b25}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : WER.System.BIOSRevision
    Value: 15.30.0.0


BUGCHECK_CODE:  c2

BUGCHECK_P1: d

BUGCHECK_P2: ffffbc8dfbbc29e0

BUGCHECK_P3: 506d7054

BUGCHECK_P4: 842af68b

FILE_IN_CAB:  021226-36046-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff9b84370e6040

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

IP_IN_PAGED_CODE: 
nt!ExFreePoolWithTag+1321
fffff803`b1771ff1 cc              int     3

STACK_TEXT:  
fffffc0f`174e2588 fffff803`b1771ff1     : 00000000`000000c2 00000000`0000000d ffffbc8d`fbbc29e0 00000000`506d7054 : nt!KeBugCheckEx
fffffc0f`174e2590 fffff803`434aa6fb     : ffffbc8d`fbbc29e0 ffffbc8d`fbbc29f0 ffffbc8d`d8000000 fffffc0f`00000031 : nt!ExFreePoolWithTag+0x1321
fffffc0f`174e2690 fffff803`434aa026     : fffffc0f`174e2710 00000000`00000004 00000000`00000000 00000165`00000000 : tpm!Tpm20Resource::`scalar deleting destructor'+0x27
fffffc0f`174e26c0 fffff803`434a9fdf     : ffffbc8e`007ee9b0 fffff803`00000001 fffff803`434e88a0 ffff9b84`3c7dc230 : tpm!Tpm20Context::DeleteTpm20Resource+0xe
fffffc0f`174e26f0 fffff803`434a73cd     : 00000000`00000000 fffff803`434e8098 ffffbc8d`ee334cd0 ffffbc8d`ee334d00 : tpm!Tpm20ResourceMgr::RemovedLoadedResource+0x8f
fffffc0f`174e2730 fffff803`434b97a5     : ffffbc8d`d86ca8f0 ffffbc8e`00000000 fffffc0f`174e27d9 ffffbc8d`d84d63e4 : tpm!Tpm20ResourceMgr::ProcessUpdatedTpmState+0x199
fffffc0f`174e2770 fffff803`434b9c70     : ffffbc8d`d86ca8f0 00000000`0000000a 00000000`00008001 00000000`00000000 : tpm!Tpm20ResourceMgr::SubmitRequest+0x9d5
fffffc0f`174e2840 fffff803`434bac57     : fffffc0f`174e2a70 ffff9b84`35afe700 00000000`00000001 00000000`00000000 : tpm!Tpm20Scheduler::DoUserRequest+0x220
fffffc0f`174e2970 fffff803`434b8da8     : 00000000`00000000 ffff9b84`35afe700 fffff803`434b8d60 ffff9b84`35afe700 : tpm!Tpm20Scheduler::SchedulerThreadFunction+0x7b7
fffffc0f`174e2b80 fffff803`b108966a     : ffff9b84`370e6040 fffff803`434b8d60 0f3d0000`0115840f ffffdc81`327c5180 : tpm!Tpm20Scheduler::SchedulerThreadWrapper+0x48
fffffc0f`174e2bb0 fffff803`b12ab774     : ffffdc81`327c5180 ffff9b84`370e6040 fffff803`b1089610 4c3e448b`41000002 : nt!PspSystemThreadStartup+0x5a
fffffc0f`174e2c00 00000000`00000000     : fffffc0f`174e3000 fffffc0f`174dc000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  tpm!Tpm20Resource::`scalar deleting destructor'+27

MODULE_NAME: tpm

IMAGE_NAME:  tpm.sys

IMAGE_VERSION:  10.0.26100.7705

STACK_COMMAND: .process /r /p 0xffff9b84346c8040; .thread 0xffff9b84370e6040 ; kb

BUCKET_ID_FUNC_OFFSET:  27

FAILURE_BUCKET_ID:  0xc2_d_tpm!Tpm20Resource::_scalar_deleting_destructor_

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {91db07c7-7710-80a4-de7a-d91ead109b25}

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

Answer 1

Hello aqil03,

Welcome to Microsoft Q&A forum.

If that issue only happens with League and Valorant. I think the issue might come from the things that these 2 games have in common, the Riot Vanguard. May I know if you have tried to uninstall and reinstall the Vanguard and the games yet?

The logs also point to a kernel thread has made an invalid pool operation, which means it could be a kernel driver is having issue and making the Vanguard driver, which rely on them to work having issue.. So in this case, you can also try out these fixes.

• Update any driver update available, especially the GPU drivers.
• Update the BIOS and reset it to default, this is critical in 13th and 14th gen of Intel, which as I see Riot Games has also called this out.
• Check TPM and Secure Boot to see if it is enabled.
• Run system file scan.
  1. Type "Command Prompt" in the search bar and select "Run as administrator.
  2. Type DISM /Online /Cleanup-image/ RestoreHealth
  3. When the scan is done, type sfc/ scannow and press Enter.
  4. Restart your computer when it is done.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.