Mindflux 1 Posted January 24, 2023 Posted January 24, 2023 I have been having sporadic reboots, mostly in the evening or early morning when I am not at my desk. I had one happen last night after checking event viewer and analyzing the minidump: nt!KeBugCheckEx: fffff807`7e820fb0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffd03`c17b77f0=0000000000000153 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_LOCK_ENTRY_LEAKED_ON_THREAD_TERMINATION (153) A thread was terminated before it had freed all its AutoBoost lock entries. This is typically caused when a thread never released a lock it previously acquired (e.g. by relying on another thread to release it), or if the thread did not supply a consistent set of flags to lock package APIs. Arguments: Arg1: ffff8887295e4080, The address of the thread Arg2: ffff8887295e47e0, The address of the entry that was not freed Arg3: 0000000000000002, Thread pointer reserved bits were set Arg4: 0000000000000000 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1296 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 1319 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: 186 Key : Analysis.Init.Elapsed.mSec Value: 6911 Key : Analysis.Memory.CommitPeak.Mb Value: 92 Key : Bugcheck.Code.DumpHeader Value: 0x153 Key : Bugcheck.Code.Register Value: 0x153 Key : Dump.Attributes.AsUlong Value: 808 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 FILE_IN_CAB: 012323-5984-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x808 Kernel Generated Triage Dump BUGCHECK_CODE: 153 BUGCHECK_P1: ffff8887295e4080 BUGCHECK_P2: ffff8887295e47e0 BUGCHECK_P3: 2 BUGCHECK_P4: 0 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: ekrn.exe STACK_TEXT: fffffd03`c17b77e8 fffff807`7e893fa0 : 00000000`00000153 ffff8887`295e4080 ffff8887`295e47e0 00000000`00000002 : nt!KeBugCheckEx fffffd03`c17b77f0 fffff807`7eb17d0e : 00000000`00000000 ffff8887`295e4050 fffffd03`c17b7a09 00000000`00000000 : nt!KeCleanupThreadState+0x1c88d0 fffffd03`c17b7840 fffff807`7eacdb0e : ffff8887`295e4080 ffff8887`295e4050 fffffd03`c17b7a09 ffffffff`ffffffff : nt!PspThreadDelete+0x1e fffffd03`c17b78b0 fffff807`7e692f63 : 00000000`00000000 00000000`00000000 fffffd03`c17b7a09 ffff8887`295e4080 : nt!ObpRemoveObjectRoutine+0x7e fffffd03`c17b7910 fffff807`7eaca418 : 00000000`00000001 00000000`00000001 00000000`00001050 fffff807`7eacac17 : nt!ObfDereferenceObjectWithTag+0xc3 fffffd03`c17b7950 fffff807`7eac7b09 : 00000000`00000000 000000b2`45364000 00000000`00001050 000000b2`45364000 : nt!ObpCloseHandle+0x2d8 fffffd03`c17b7a70 fffff807`7e833968 : ffff8887`360d6080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtClose+0x39 fffffd03`c17b7aa0 00007fff`1f84ef54 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28 000000b2`47dff8e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`1f84ef54 SYMBOL_NAME: nt!KeCleanupThreadState+1c88d0 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.525 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 1c88d0 FAILURE_BUCKET_ID: 0x153_KERNEL_LOCK_ENTRY_LEAKED_ON_THREAD_TERMINATION_RESERVED_BITS_SET_nt!KeCleanupThreadState OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {aeb5bb18-b52c-51eb-af16-9ae73af5d4a8} Followup: MachineOwner This is actually Windows 11 Enterprise, but I'm guessing Windbg hasn't been updated to detect the Windows 10 version number.
Administrators Marcos 5,468 Posted January 24, 2023 Administrators Posted January 24, 2023 Please provide the minidump and configure Windows to generate complete memory dumps which may be needed to determine the root cause.
Mindflux 1 Posted January 24, 2023 Author Posted January 24, 2023 Attached is the minidump. 012323-5984-01.zip
ESET Moderators Peter Randziak 1,186 Posted January 27, 2023 ESET Moderators Posted January 27, 2023 Hello @Mindflux, I checked the minidump briefly, but I wasn't able to find any useful info. Please provide us with the complete memory dump and output from ESET Log Collector so we can analyze the issue properly. Feel free to send the download details to me and Marcos via a private message with reference to this forum topic. Peter
Mindflux 1 Posted January 27, 2023 Author Posted January 27, 2023 1 hour ago, Peter Randziak said: Hello @Mindflux, I checked the minidump briefly, but I wasn't able to find any useful info. Please provide us with the complete memory dump and output from ESET Log Collector so we can analyze the issue properly. Feel free to send the download details to me and Marcos via a private message with reference to this forum topic. Peter Thanks. I'll have to wait for the next BSOD and report back. Peter Randziak 1
Recommended Posts