F5F Stay Refreshed Hardware Desktop System restarts, BAD_POOL_CALLER detected (c2) – Image: rcbottom.sys

System restarts, BAD_POOL_CALLER detected (c2) – Image: rcbottom.sys

System restarts, BAD_POOL_CALLER detected (c2) – Image: rcbottom.sys

Z
Zegazel
Member
Find
87
04-15-2024, 06:44 AM
#1
Hi everyone! I've been struggling with this issue for a while now. I'm not sure how to exactly tackle this issue and I'm having a hard time. See the memory dump bugcheck analysis below. I can't reproduce the issue. It seemingly occurs at random as far as I can understand. There is no BSOD, the computer simply reboots. So far I noticed that RCBottom (AMD Raid Driver) is responsible for the crashes. However I'm uncertain on how to fix or how to resolve this. Any advice would be appreciated as I've struggled figuring this out on my own. Thank you kindly for reading this, and I hope we can solve this together. Spoiler ******************************************************************************* * * * 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: ffff870a27eeda28, Address being freed Arg3: 0000000000000000, 0 Arg4: 0000000000000000, 0 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1500 Key : Analysis.Elapsed.mSec Value: 2923 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 108 Key : Analysis.Init.Elapsed.mSec Value: 2528 Key : Analysis.Memory.CommitPeak.Mb Value: 90 Key : Bugcheck.Code.LegacyAPI Value: 0xc2 Key : Failure.Bucket Value: 0xc2_99_rcbottom!unknown_function Key : Failure.Hash Value: {a6553b95-574d-da1a-8189-76cae45ae61e} Key : WER.OS.Branch Value: ni_release_svc_prod3 Key : WER.OS.Version Value: 10.0.22621.1928 BUGCHECK_CODE: c2 BUGCHECK_P1: 99 BUGCHECK_P2: ffff870a27eeda28 BUGCHECK_P3: 0 BUGCHECK_P4: 0 FILE_IN_CAB: 091123-9921-01.dmp BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffff30e`4b107628 fffff804`52caee04 : 00000000`000000c2 00000000`00000099 ffff870a`27eeda28 00000000`00000000 : nt!KeBugCheckEx fffff30e`4b107630 fffff804`54e5d355 : ffff870a`121022f0 ffff870a`121a4cf0 ffff870a`27eed850 00000000`00000000 : nt!ExFreePoolWithTag+0xae4 fffff30e`4b1076c0 ffff870a`121022f0 : ffff870a`121a4cf0 ffff870a`27eed850 00000000`00000000 fffff30e`4b107ad0 : rcbottom+0xd355 fffff30e`4b1076c8 ffff870a`121a4cf0 : ffff870a`27eed850 00000000`00000000 fffff30e`4b107ad0 fffff804`54e57555 : 0xffff870a`121022f0 fffff30e`4b1076d0 ffff870a`27eed850 : 00000000`00000000 fffff30e`4b107ad0 fffff804`54e57555 ffff870a`121022f0 : 0xffff870a`121a4cf0 fffff30e`4b1076d8 00000000`00000000 : fffff30e`4b107ad0 fffff804`54e57555 ffff870a`121022f0 ffff870a`121022f0 : 0xffff870a`27eed850 SYMBOL_NAME: rcbottom+d355 MODULE_NAME: rcbottom IMAGE_NAME: rcbottom.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: d355 FAILURE_BUCKET_ID: 0xc2_99_rcbottom!unknown_function OS_VERSION: 10.0.22621.1928 BUILDLAB_STR: ni_release_svc_prod3 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {a6553b95-574d-da1a-8189-76cae45ae61e} Followup: MachineOwner --------- NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\ObjectiveC.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Usb4Kd.natvis' ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 36 Microsoft ® Windows Debugger Version 10.0.25921.1001 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\HCWin\OneDrive - ITYM\Documenten\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. Primary dump contents written successfully ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22621 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 22621.1928.amd64fre.ni_release_svc_prod3.230622-0951 Kernel base = 0xfffff804`52200000 PsLoadedModuleList = 0xfffff804`52e130e0 Debug session time: Mon Sep 11 12:41:33.261 2023 (UTC + 1:00) System Uptime: 0 days 0:00:46.850 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............... Loading User Symbols Loading unloaded module list ........ For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff804`52631250 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff30e`4b107630=00000000000000c2 9: 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: ffff870a27eeda28, Address being freed Arg3: 0000000000000000, 0 Arg4: 0000000000000000, 0 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2077 Key : Analysis.Elapsed.mSec Value: 2444 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 202 Key : Analysis.Init.Elapsed.mSec Value: 1688 Key : Analysis.Memory.CommitPeak.Mb Value: 103 Key : Bugcheck.Code.KiBugCheckData Value: 0xc2 Key : Bugcheck.Code.LegacyAPI Value: 0xc2 Key : Dump.Attributes.AsUlong Value: 1000 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 100 Key : Failure.Bucket Value: 0xc2_99_rcbottom!unknown_function Key : Failure.Hash Value: {a6553b95-574d-da1a-8189-76cae45ae61e} Key : Hypervisor.Enlightenments.Value Value: 0 Key : Hypervisor.Enlightenments.ValueHex Value: 0 Key : Hypervisor.Flags.AnyHypervisorPresent Value: 0 Key : Hypervisor.Flags.ApicEnlightened Value: 0 Key : Hypervisor.Flags.ApicVirtualizationAvailable Value: 1 Key : Hypervisor.Flags.AsyncMemoryHint Value: 0 Key : Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key : Hypervisor.Flags.CpuManager Value: 0 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 0 Key : Hypervisor.Flags.DynamicCpuDisabled Value: 0 Key : Hypervisor.Flags.Epf Value: 0 Key : Hypervisor.Flags.ExtendedProcessorMasks Value: 0 Key : Hypervisor.Flags.HardwareMbecAvailable Value: 1 Key : Hypervisor.Flags.MaxBankNumber Value: 0 Key : Hypervisor.Flags.MemoryZeroingControl Value: 0 Key : Hypervisor.Flags.NoExtendedRangeFlush Value: 0 Key : Hypervisor.Flags.NoNonArchCoreSharing Value: 0 Key : Hypervisor.Flags.Phase0InitDone Value: 0 Key : Hypervisor.Flags.PowerSchedulerQos Value: 0 Key : Hypervisor.Flags.RootScheduler Value: 0 Key : Hypervisor.Flags.SynicAvailable Value: 0 Key : Hypervisor.Flags.UseQpcBias Value: 0 Key : Hypervisor.Flags.Value Value: 16908288 Key : Hypervisor.Flags.ValueHex Value: 1020000 Key : Hypervisor.Flags.VpAssistPage Value: 0 Key : Hypervisor.Flags.VsmAvailable Value: 0 Key : Hypervisor.RootFlags.AccessStats Value: 0 Key : Hypervisor.RootFlags.CrashdumpEnlightened Value: 0 Key : Hypervisor.RootFlags.CreateVirtualProcessor Value: 0 Key : Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key : Hypervisor.RootFlags.HostTimelineSync Value: 0 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key : Hypervisor.RootFlags.IsHyperV Value: 0 Key : Hypervisor.RootFlags.LivedumpEnlightened Value: 0 Key : Hypervisor.RootFlags.MapDeviceInterrupt Value: 0 Key : Hypervisor.RootFlags.MceEnlightened Value: 0 Key : Hypervisor.RootFlags.Nested Value: 0 Key : Hypervisor.RootFlags.StartLogicalProcessor Value: 0 Key : Hypervisor.RootFlags.Value Value: 0 Key : Hypervisor.RootFlags.ValueHex Value: 0 Key : SecureKernel.HalpHvciEnabled Value: 0 Key : WER.OS.Branch Value: ni_release_svc_prod3 Key : WER.OS.Version Value: 10.0.22621.1928 BUGCHECK_CODE: c2 BUGCHECK_P1: 99 BUGCHECK_P2: ffff870a27eeda28 BUGCHECK_P3: 0 BUGCHECK_P4: 0 FILE_IN_CAB: MEMORY.DMP DUMP_FILE_ATTRIBUTES: 0x1000 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System STACK_TEXT: fffff30e`4b107628 fffff804`52caee04 : 00000000`000000c2 00000000`00000099 ffff870a`27eeda28 00000000`00000000 : nt!KeBugCheckEx fffff30e`4b107630 fffff804`54e5d355 : ffff870a`121022f0 ffff870a`121a4cf0 ffff870a`27eed850 00000000`00000000 : nt!ExFreePoolWithTag+0xae4 fffff30e`4b1076c0 fffff804`54e57555 : ffff870a`121022f0 ffff870a`121022f0 fffff30e`4b107839 fffff804`54798bc0 : rcbottom+0xd355 fffff30e`4b1076f0 fffff804`54798c77 : 000078f5`edff53c8 00000000`00000000 ffff870a`0d457080 ffffac81`66546180 : rcbottom+0x7555 fffff30e`4b107720 fffff804`54798bf5 : fffff30e`4b107839 fffff804`52549a02 fffff30e`4b1077c2 fffff804`52424400 : Wdf01000!FxTimer::TimerHandler+0x73 [minkernel\wdf\framework\shared\core\fxtimer.cpp @ 343] fffff30e`4b107750 fffff804`525481a9 : ffff870a`1200c740 fffff804`54798bc0 00400a02`00000010 00000032`80998200 : Wdf01000!FxTimer::_FxTimerExtCallbackThunk+0x35 [minkernel\wdf\framework\shared\core\fxtimer.cpp @ 450] fffff30e`4b107790 fffff804`52546294 : 00000000`00000003 fffff30e`4b1078d8 ffffac81`66546180 00000000`00000000 : nt!KiExpireTimer2+0x419 fffff30e`4b1078a0 fffff804`52543238 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff804`4d91b1e8 : nt!KiTimer2Expiration+0x154 fffff30e`4b107950 fffff804`5263604e : 00000000`00000000 ffffac81`66546180 ffff870a`0d457080 ffff870a`20ca9080 : nt!KiRetireDpcList+0xa08 fffff30e`4b107c00 00000000`00000000 : fffff30e`4b108000 fffff30e`4b101000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e SYMBOL_NAME: rcbottom+d355 MODULE_NAME: rcbottom IMAGE_NAME: rcbottom.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: d355 FAILURE_BUCKET_ID: 0xc2_99_rcbottom!unknown_function OS_VERSION: 10.0.22621.1928 BUILDLAB_STR: ni_release_svc_prod3 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {a6553b95-574d-da1a-8189-76cae45ae61e} Followup: MachineOwner ---------
Reply
Reply
Z
Zegazel
04-15-2024, 06:44 AM #1

Hi everyone! I've been struggling with this issue for a while now. I'm not sure how to exactly tackle this issue and I'm having a hard time. See the memory dump bugcheck analysis below. I can't reproduce the issue. It seemingly occurs at random as far as I can understand. There is no BSOD, the computer simply reboots. So far I noticed that RCBottom (AMD Raid Driver) is responsible for the crashes. However I'm uncertain on how to fix or how to resolve this. Any advice would be appreciated as I've struggled figuring this out on my own. Thank you kindly for reading this, and I hope we can solve this together. Spoiler ******************************************************************************* * * * 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: ffff870a27eeda28, Address being freed Arg3: 0000000000000000, 0 Arg4: 0000000000000000, 0 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1500 Key : Analysis.Elapsed.mSec Value: 2923 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 108 Key : Analysis.Init.Elapsed.mSec Value: 2528 Key : Analysis.Memory.CommitPeak.Mb Value: 90 Key : Bugcheck.Code.LegacyAPI Value: 0xc2 Key : Failure.Bucket Value: 0xc2_99_rcbottom!unknown_function Key : Failure.Hash Value: {a6553b95-574d-da1a-8189-76cae45ae61e} Key : WER.OS.Branch Value: ni_release_svc_prod3 Key : WER.OS.Version Value: 10.0.22621.1928 BUGCHECK_CODE: c2 BUGCHECK_P1: 99 BUGCHECK_P2: ffff870a27eeda28 BUGCHECK_P3: 0 BUGCHECK_P4: 0 FILE_IN_CAB: 091123-9921-01.dmp BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffff30e`4b107628 fffff804`52caee04 : 00000000`000000c2 00000000`00000099 ffff870a`27eeda28 00000000`00000000 : nt!KeBugCheckEx fffff30e`4b107630 fffff804`54e5d355 : ffff870a`121022f0 ffff870a`121a4cf0 ffff870a`27eed850 00000000`00000000 : nt!ExFreePoolWithTag+0xae4 fffff30e`4b1076c0 ffff870a`121022f0 : ffff870a`121a4cf0 ffff870a`27eed850 00000000`00000000 fffff30e`4b107ad0 : rcbottom+0xd355 fffff30e`4b1076c8 ffff870a`121a4cf0 : ffff870a`27eed850 00000000`00000000 fffff30e`4b107ad0 fffff804`54e57555 : 0xffff870a`121022f0 fffff30e`4b1076d0 ffff870a`27eed850 : 00000000`00000000 fffff30e`4b107ad0 fffff804`54e57555 ffff870a`121022f0 : 0xffff870a`121a4cf0 fffff30e`4b1076d8 00000000`00000000 : fffff30e`4b107ad0 fffff804`54e57555 ffff870a`121022f0 ffff870a`121022f0 : 0xffff870a`27eed850 SYMBOL_NAME: rcbottom+d355 MODULE_NAME: rcbottom IMAGE_NAME: rcbottom.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: d355 FAILURE_BUCKET_ID: 0xc2_99_rcbottom!unknown_function OS_VERSION: 10.0.22621.1928 BUILDLAB_STR: ni_release_svc_prod3 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {a6553b95-574d-da1a-8189-76cae45ae61e} Followup: MachineOwner --------- NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\ObjectiveC.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2308.2002.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Usb4Kd.natvis' ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 36 Microsoft ® Windows Debugger Version 10.0.25921.1001 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\HCWin\OneDrive - ITYM\Documenten\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. Primary dump contents written successfully ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22621 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 22621.1928.amd64fre.ni_release_svc_prod3.230622-0951 Kernel base = 0xfffff804`52200000 PsLoadedModuleList = 0xfffff804`52e130e0 Debug session time: Mon Sep 11 12:41:33.261 2023 (UTC + 1:00) System Uptime: 0 days 0:00:46.850 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............... Loading User Symbols Loading unloaded module list ........ For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff804`52631250 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff30e`4b107630=00000000000000c2 9: 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: ffff870a27eeda28, Address being freed Arg3: 0000000000000000, 0 Arg4: 0000000000000000, 0 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2077 Key : Analysis.Elapsed.mSec Value: 2444 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 202 Key : Analysis.Init.Elapsed.mSec Value: 1688 Key : Analysis.Memory.CommitPeak.Mb Value: 103 Key : Bugcheck.Code.KiBugCheckData Value: 0xc2 Key : Bugcheck.Code.LegacyAPI Value: 0xc2 Key : Dump.Attributes.AsUlong Value: 1000 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 100 Key : Failure.Bucket Value: 0xc2_99_rcbottom!unknown_function Key : Failure.Hash Value: {a6553b95-574d-da1a-8189-76cae45ae61e} Key : Hypervisor.Enlightenments.Value Value: 0 Key : Hypervisor.Enlightenments.ValueHex Value: 0 Key : Hypervisor.Flags.AnyHypervisorPresent Value: 0 Key : Hypervisor.Flags.ApicEnlightened Value: 0 Key : Hypervisor.Flags.ApicVirtualizationAvailable Value: 1 Key : Hypervisor.Flags.AsyncMemoryHint Value: 0 Key : Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key : Hypervisor.Flags.CpuManager Value: 0 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 0 Key : Hypervisor.Flags.DynamicCpuDisabled Value: 0 Key : Hypervisor.Flags.Epf Value: 0 Key : Hypervisor.Flags.ExtendedProcessorMasks Value: 0 Key : Hypervisor.Flags.HardwareMbecAvailable Value: 1 Key : Hypervisor.Flags.MaxBankNumber Value: 0 Key : Hypervisor.Flags.MemoryZeroingControl Value: 0 Key : Hypervisor.Flags.NoExtendedRangeFlush Value: 0 Key : Hypervisor.Flags.NoNonArchCoreSharing Value: 0 Key : Hypervisor.Flags.Phase0InitDone Value: 0 Key : Hypervisor.Flags.PowerSchedulerQos Value: 0 Key : Hypervisor.Flags.RootScheduler Value: 0 Key : Hypervisor.Flags.SynicAvailable Value: 0 Key : Hypervisor.Flags.UseQpcBias Value: 0 Key : Hypervisor.Flags.Value Value: 16908288 Key : Hypervisor.Flags.ValueHex Value: 1020000 Key : Hypervisor.Flags.VpAssistPage Value: 0 Key : Hypervisor.Flags.VsmAvailable Value: 0 Key : Hypervisor.RootFlags.AccessStats Value: 0 Key : Hypervisor.RootFlags.CrashdumpEnlightened Value: 0 Key : Hypervisor.RootFlags.CreateVirtualProcessor Value: 0 Key : Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key : Hypervisor.RootFlags.HostTimelineSync Value: 0 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key : Hypervisor.RootFlags.IsHyperV Value: 0 Key : Hypervisor.RootFlags.LivedumpEnlightened Value: 0 Key : Hypervisor.RootFlags.MapDeviceInterrupt Value: 0 Key : Hypervisor.RootFlags.MceEnlightened Value: 0 Key : Hypervisor.RootFlags.Nested Value: 0 Key : Hypervisor.RootFlags.StartLogicalProcessor Value: 0 Key : Hypervisor.RootFlags.Value Value: 0 Key : Hypervisor.RootFlags.ValueHex Value: 0 Key : SecureKernel.HalpHvciEnabled Value: 0 Key : WER.OS.Branch Value: ni_release_svc_prod3 Key : WER.OS.Version Value: 10.0.22621.1928 BUGCHECK_CODE: c2 BUGCHECK_P1: 99 BUGCHECK_P2: ffff870a27eeda28 BUGCHECK_P3: 0 BUGCHECK_P4: 0 FILE_IN_CAB: MEMORY.DMP DUMP_FILE_ATTRIBUTES: 0x1000 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System STACK_TEXT: fffff30e`4b107628 fffff804`52caee04 : 00000000`000000c2 00000000`00000099 ffff870a`27eeda28 00000000`00000000 : nt!KeBugCheckEx fffff30e`4b107630 fffff804`54e5d355 : ffff870a`121022f0 ffff870a`121a4cf0 ffff870a`27eed850 00000000`00000000 : nt!ExFreePoolWithTag+0xae4 fffff30e`4b1076c0 fffff804`54e57555 : ffff870a`121022f0 ffff870a`121022f0 fffff30e`4b107839 fffff804`54798bc0 : rcbottom+0xd355 fffff30e`4b1076f0 fffff804`54798c77 : 000078f5`edff53c8 00000000`00000000 ffff870a`0d457080 ffffac81`66546180 : rcbottom+0x7555 fffff30e`4b107720 fffff804`54798bf5 : fffff30e`4b107839 fffff804`52549a02 fffff30e`4b1077c2 fffff804`52424400 : Wdf01000!FxTimer::TimerHandler+0x73 [minkernel\wdf\framework\shared\core\fxtimer.cpp @ 343] fffff30e`4b107750 fffff804`525481a9 : ffff870a`1200c740 fffff804`54798bc0 00400a02`00000010 00000032`80998200 : Wdf01000!FxTimer::_FxTimerExtCallbackThunk+0x35 [minkernel\wdf\framework\shared\core\fxtimer.cpp @ 450] fffff30e`4b107790 fffff804`52546294 : 00000000`00000003 fffff30e`4b1078d8 ffffac81`66546180 00000000`00000000 : nt!KiExpireTimer2+0x419 fffff30e`4b1078a0 fffff804`52543238 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff804`4d91b1e8 : nt!KiTimer2Expiration+0x154 fffff30e`4b107950 fffff804`5263604e : 00000000`00000000 ffffac81`66546180 ffff870a`0d457080 ffff870a`20ca9080 : nt!KiRetireDpcList+0xa08 fffff30e`4b107c00 00000000`00000000 : fffff30e`4b108000 fffff30e`4b101000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e SYMBOL_NAME: rcbottom+d355 MODULE_NAME: rcbottom IMAGE_NAME: rcbottom.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: d355 FAILURE_BUCKET_ID: 0xc2_99_rcbottom!unknown_function OS_VERSION: 10.0.22621.1928 BUILDLAB_STR: ni_release_svc_prod3 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {a6553b95-574d-da1a-8189-76cae45ae61e} Followup: MachineOwner ---------

Reply
Reply
M
Magister_Magi
Member
Find
151
04-15-2024, 06:44 AM
#2
It varies based on the reason rcbottom is active—it could be the AMD RAID driver. If you're using RAID, fixing it isn't straightforward since you don’t regularly use it. The main issue seems to be StoreMI being installed. Uninstall it if possible. Another possibility is that your disks are set up as Dynamic Disks, which is for pooling and part of Windows Storage Spaces. Use Disk Management (Win + R → diskpart) and run "list disk." Look for any drives marked with a star (*) in the Dyn column. If you intend to use a pool intentionally, it’s risky to remove drives directly—consider using Storage Spaces instead. Finally, verify your storage controllers via Device Manager; update or replace components like StoreMI, AMD-RAID Bottom Device, or AMD-RAID Controller as needed.
Reply
Reply
M
Magister_Magi
04-15-2024, 06:44 AM #2

It varies based on the reason rcbottom is active—it could be the AMD RAID driver. If you're using RAID, fixing it isn't straightforward since you don’t regularly use it. The main issue seems to be StoreMI being installed. Uninstall it if possible. Another possibility is that your disks are set up as Dynamic Disks, which is for pooling and part of Windows Storage Spaces. Use Disk Management (Win + R → diskpart) and run "list disk." Look for any drives marked with a star (*) in the Dyn column. If you intend to use a pool intentionally, it’s risky to remove drives directly—consider using Storage Spaces instead. Finally, verify your storage controllers via Device Manager; update or replace components like StoreMI, AMD-RAID Bottom Device, or AMD-RAID Controller as needed.

Reply
Reply
W
warmtheguy
Member
Find
71
04-15-2024, 06:44 AM
#3
In typical situations I wouldn't rely on RAID. But to try and fix the problem, I switched to using RAID to check if that would help. It didn’t work. I have a dynamic disk set up to split one drive into two partitions, and making it a basic disk could risk losing some important files. I’ll consider doing the final step once I disable RAID again in my BIOS, as it didn’t resolve the issue. Thanks for your prompt reply—other suggestions are always welcome. I’ll keep you informed. (Can’t reproduce the crash, so it may take time to find a solid solution! Confused )
Reply
Reply
W
warmtheguy
04-15-2024, 06:44 AM #3

In typical situations I wouldn't rely on RAID. But to try and fix the problem, I switched to using RAID to check if that would help. It didn’t work. I have a dynamic disk set up to split one drive into two partitions, and making it a basic disk could risk losing some important files. I’ll consider doing the final step once I disable RAID again in my BIOS, as it didn’t resolve the issue. Thanks for your prompt reply—other suggestions are always welcome. I’ll keep you informed. (Can’t reproduce the crash, so it may take time to find a solid solution! Confused )

Reply
Reply
D
DontSpeak
Junior Member
Find
11
04-15-2024, 06:45 AM
#4
Reply
Reply
D
DontSpeak
04-15-2024, 06:45 AM #4

Reply
Reply
B
BossTurtles
Junior Member
Find
7
04-15-2024, 06:45 AM
#5
Thank you for your feedback and suggestions. I haven’t managed to fix the issue yet, and it seems the latest crashes aren’t producing minidumps anymore, making it hard to identify the cause. I’ll keep monitoring this post for any updates that could help. I hope this doesn’t affect my ability to resolve the problem. Wishing everyone a happy holiday season!
Reply
Reply
B
BossTurtles
04-15-2024, 06:45 AM #5

Thank you for your feedback and suggestions. I haven’t managed to fix the issue yet, and it seems the latest crashes aren’t producing minidumps anymore, making it hard to identify the cause. I’ll keep monitoring this post for any updates that could help. I hope this doesn’t affect my ability to resolve the problem. Wishing everyone a happy holiday season!

Reply
Reply