Son kullanma tarihi geçmiş, bayatlamış bir tarayıcı kullanıyorsanız, Mercedes kullanmak yerine tosbağaya binmek gibi... Web sitelerini düzgün görüntüleyemiyorsanız eh, bi' zahmet tarayıcınızı güncelleyiniz. Modern Web standartlarını karşılayan bir tarayıcı alternatifine göz atın.
Chrome kendi kendine kapandı. Açıyorum tekrar kapanıyor. Açıyorum tekrar kapanıyor. Sonra mavi ekran verdi. Açıklamasında BAD_POOL_CALLER yazı yazıyordu.
Reset attıktan sonra düzeldi ama tekrar yapabilir diye konu açıyorum.
TUF Gaming motherboards are built to survive and thrive on every battlefield. TUF GAMING B650M-E WIFI is an AMD AM5 mATX motherboard with DDR5, PCIe 5.0 M.2 slot with heatsink, dual M.2 slots, M.2 Q-Latch, 8+2 DrMOS, Wi-Fi 6, Realtek 2.5Gb Ethernet, two DisplayPort, HDMIâ¢, rear USB 3.2 Gen 2...
TUF Gaming motherboards are built to survive and thrive on every battlefield. TUF GAMING B650M-E WIFI is an AMD AM5 mATX motherboard with DDR5, PCIe 5.0 M.2 slot with heatsink, dual M.2 slots, M.2 Q-Latch, 8+2 DrMOS, Wi-Fi 6, Realtek 2.5Gb Ethernet, two DisplayPort, HDMIâ¢, rear USB 3.2 Gen 2...
Öncelikle teyit amaçlı olarak sormaktayım. Sisteminizde TUF GAMING B650M-E WIFI anakart, Ryzen 7 9800X3D işlemci mi bulunmakta?
Sorun TPM kaynaklı görünüyor.
Kod:
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: ffffd00356787250, Address of pool
Arg3: 00000000506d7054, Pool allocation's tag
Arg4: 000000003281d0ea, Quota process pointer (bad).
PROCESS_NAME: System
STACK_TEXT:
fffff185`5e5ece98 fffff805`99566dc6 : 00000000`000000c2 00000000`0000000d ffffd003`56787250 00000000`506d7054 : nt!KeBugCheckEx
fffff185`5e5ecea0 fffff805`2b24a63b : ffffd003`56787250 ffffd003`56787260 ffffd003`34000000 fffff185`5e5ed031 : nt!ExFreePoolWithTag+0x10f6
fffff185`5e5ecfa0 fffff805`2b249f66 : 00000000`00000000 00000000`00000000 00000005`0000001b 00000165`00000000 : tpm!Tpm20Resource::`scalar deleting destructor'+0x27
fffff185`5e5ecfd0 fffff805`2b249f1f : 00000000`00000000 00000000`00000001 fffff805`2b2888a0 000000e7`66bd8a4b : tpm!Tpm20Context::DeleteTpm20Resource+0xe
fffff185`5e5ed000 fffff805`2b24730d : 00000000`00000001 00000000`00000103 ffffd003`34707b44 00000000`00000000 : tpm!Tpm20ResourceMgr::RemovedLoadedResource+0x8f
fffff185`5e5ed040 fffff805`2b25d8a5 : ffffd003`347e2150 ffffd003`00000000 fffff185`5e5ed0f0 ffffd003`88616290 : tpm!Tpm20ResourceMgr::ProcessUpdatedTpmState+0x199
fffff185`5e5ed080 fffff805`2b259e32 : 00000000`00008001 00000000`00000009 00000000`0000001b 00000000`0000001b : tpm!Tpm20ResourceMgr::SubmitRequestOld+0x4b9
fffff185`5e5ed130 fffff805`2b25a080 : ffffd003`347e2150 00000000`00000009 00000000`00000000 fffff185`5e5ed2c9 : tpm!Tpm20ResourceMgr::SubmitRequest+0xc52
fffff185`5e5ed200 fffff805`2b25b092 : fffff185`5e5ed430 ffffa98a`25264ca0 00000000`00000001 00000000`00000000 : tpm!Tpm20Scheduler::DoUserRequest+0x220
fffff185`5e5ed330 fffff805`2b2591b8 : 00000000`00000010 ffffa98a`25264ca0 fffff805`2b259170 ffffa98a`25264ca0 : tpm!Tpm20Scheduler::SchedulerThreadFunction+0x7e2
fffff185`5e5ed540 fffff805`98ea2d1a : ffffa98a`2529a040 fffff805`2b259170 ffffb981`7a8db180 025fe07f`b8bbbdff : tpm!Tpm20Scheduler::SchedulerThreadWrapper+0x48
fffff185`5e5ed570 fffff805`990a61b4 : ffffb981`7a8db180 ffffa98a`2529a040 fffff805`98ea2cc0 00200020`00200020 : nt!PspSystemThreadStartup+0x5a
fffff185`5e5ed5c0 00000000`00000000 : fffff185`5e5ee000 fffff185`5e5e7000 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.4061
STACK_COMMAND: .process /r /p 0xffffa98a23563040; .thread 0xffffa98a2529a040 ; kb
BUCKET_ID_FUNC_OFFSET: 27
FAILURE_BUCKET_ID: 0xc2_d_tpm!Tpm20Resource::_scalar_deleting_destructor_
Scalar_deleting_destructor ifadesi ile ilk defa karşılaştım. Destructor, nesne yönelimli programlamada bir nesnenin kullanımda olmadığı zamanlarda otomatik olarak kaynakları temizleyen özel fonksiyonlara deniliyor. Bu sayede de verimli bir kaynak yönetimi sağlanabiliyor.
Ama TPM ile bu durumun alakasını gerçekten anlayamadım.
Öncelikle teyit amaçlı olarak sormaktayım. Sisteminizde TUF GAMING B650M-E WIFI anakart, Ryzen 7 9800X3D işlemci mi bulunmakta?
Sorun TPM kaynaklı görünüyor.
Kod:
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: ffffd00356787250, Address of pool
Arg3: 00000000506d7054, Pool allocation's tag
Arg4: 000000003281d0ea, Quota process pointer (bad).
PROCESS_NAME: System
STACK_TEXT:
fffff185`5e5ece98 fffff805`99566dc6 : 00000000`000000c2 00000000`0000000d ffffd003`56787250 00000000`506d7054 : nt!KeBugCheckEx
fffff185`5e5ecea0 fffff805`2b24a63b : ffffd003`56787250 ffffd003`56787260 ffffd003`34000000 fffff185`5e5ed031 : nt!ExFreePoolWithTag+0x10f6
fffff185`5e5ecfa0 fffff805`2b249f66 : 00000000`00000000 00000000`00000000 00000005`0000001b 00000165`00000000 : tpm!Tpm20Resource::`scalar deleting destructor'+0x27
fffff185`5e5ecfd0 fffff805`2b249f1f : 00000000`00000000 00000000`00000001 fffff805`2b2888a0 000000e7`66bd8a4b : tpm!Tpm20Context::DeleteTpm20Resource+0xe
fffff185`5e5ed000 fffff805`2b24730d : 00000000`00000001 00000000`00000103 ffffd003`34707b44 00000000`00000000 : tpm!Tpm20ResourceMgr::RemovedLoadedResource+0x8f
fffff185`5e5ed040 fffff805`2b25d8a5 : ffffd003`347e2150 ffffd003`00000000 fffff185`5e5ed0f0 ffffd003`88616290 : tpm!Tpm20ResourceMgr::ProcessUpdatedTpmState+0x199
fffff185`5e5ed080 fffff805`2b259e32 : 00000000`00008001 00000000`00000009 00000000`0000001b 00000000`0000001b : tpm!Tpm20ResourceMgr::SubmitRequestOld+0x4b9
fffff185`5e5ed130 fffff805`2b25a080 : ffffd003`347e2150 00000000`00000009 00000000`00000000 fffff185`5e5ed2c9 : tpm!Tpm20ResourceMgr::SubmitRequest+0xc52
fffff185`5e5ed200 fffff805`2b25b092 : fffff185`5e5ed430 ffffa98a`25264ca0 00000000`00000001 00000000`00000000 : tpm!Tpm20Scheduler::DoUserRequest+0x220
fffff185`5e5ed330 fffff805`2b2591b8 : 00000000`00000010 ffffa98a`25264ca0 fffff805`2b259170 ffffa98a`25264ca0 : tpm!Tpm20Scheduler::SchedulerThreadFunction+0x7e2
fffff185`5e5ed540 fffff805`98ea2d1a : ffffa98a`2529a040 fffff805`2b259170 ffffb981`7a8db180 025fe07f`b8bbbdff : tpm!Tpm20Scheduler::SchedulerThreadWrapper+0x48
fffff185`5e5ed570 fffff805`990a61b4 : ffffb981`7a8db180 ffffa98a`2529a040 fffff805`98ea2cc0 00200020`00200020 : nt!PspSystemThreadStartup+0x5a
fffff185`5e5ed5c0 00000000`00000000 : fffff185`5e5ee000 fffff185`5e5e7000 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.4061
STACK_COMMAND: .process /r /p 0xffffa98a23563040; .thread 0xffffa98a2529a040 ; kb
BUCKET_ID_FUNC_OFFSET: 27
FAILURE_BUCKET_ID: 0xc2_d_tpm!Tpm20Resource::_scalar_deleting_destructor_
Scalar_deleting_destructor ifadesi ile ilk defa karşılaştım. Destructor, nesne yönelimli programlamada bir nesnenin kullanımda olmadığı zamanlarda otomatik olarak kaynakları temizleyen özel fonksiyonlara deniliyor. Bu sayede de verimli bir kaynak yönetimi sağlanabiliyor.
Ama TPM ile bu durumun alakasını gerçekten anlayamadım.
