************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.015 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 44 Microsoft (R) Windows Debugger Version 10.0.27829.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\35134\Desktop\1\051125-12359-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 26100 MP (32 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0xfffff805`cde00000 PsLoadedModuleList = 0xfffff805`cecf49c0 Debug session time: Sun May 11 23:01:41.060 2025 (UTC + 8:00) System Uptime: 0 days 0:04:16.667 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ........................................................ Loading User Symbols PEB is paged out (Peb.Ldr = 0000008f`5c37b018). Type ".hh dbgerr001" for details Loading unloaded module list ............ For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff805`ce2b5520 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa90c`16e0e2f0=000000000000001e 31: kd> !analyze -v Loading Kernel Symbols .. Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. ............................................................. ................................................................ ................................................................ ........................................................ Loading User Symbols PEB is paged out (Peb.Ldr = 0000008f`5c37b018). Type ".hh dbgerr001" for details Loading unloaded module list ............ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common BugCheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc000001d, The exception code that was not handled Arg2: fffff8055f9ac099, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: fffff8055f9ac080, Parameter 1 of the exception Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: ExceptionRecord *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: ContextRecord *** *** *** ************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1515 Key : Analysis.Elapsed.mSec Value: 95221 Key : Analysis.IO.Other.Mb Value: 17 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 28 Key : Analysis.Init.CPU.mSec Value: 859 Key : Analysis.Init.Elapsed.mSec Value: 476259 Key : Analysis.Memory.CommitPeak.Mb Value: 111 Key : Analysis.Version.DbgEng Value: 10.0.27829.1001 Key : Analysis.Version.Description Value: 10.2503.24.01 amd64fre Key : Analysis.Version.Ext Value: 1.2503.24.1 Key : Bugcheck.Code.LegacyAPI Value: 0x1e Key : Bugcheck.Code.TargetModel Value: 0x1e 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: 0x1E_C000001D_BAD_IP_FLTMGR!FltInsertExtraCreateParameter Key : Failure.Exception.IP.Address Value: 0xfffff8055f9ac099 Key : Failure.Exception.IP.Module Value: FLTMGR Key : Failure.Exception.IP.Offset Value: 0x6c099 Key : Failure.Hash Value: {39430fe1-1055-a459-79df-d7786e3454f2} BUGCHECK_CODE: 1e BUGCHECK_P1: ffffffffc000001d BUGCHECK_P2: fffff8055f9ac099 BUGCHECK_P3: 0 BUGCHECK_P4: fffff8055f9ac080 FILE_IN_CAB: 051125-12359-01.dmp DUMP_FILE_ATTRIBUTES: 0x21008 Kernel Generated Triage Dump FAULTING_THREAD: ffffe48fc21dd080 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: fffff8055f9ac080 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: WerFault.exe FAILED_INSTRUCTION_ADDRESS: FLTMGR!FltInsertExtraCreateParameter+19 fffff805`5f9ac099 28c3 sub bl,al STACK_TEXT: ffffa90c`16e0e2e8 fffff805`ce17aff6 : 00000000`0000001e ffffffff`c000001d fffff805`5f9ac099 00000000`00000000 : nt!KeBugCheckEx ffffa90c`16e0e2f0 fffff805`ce48fa45 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff805`00000012 : nt!KiDispatchException+0xb16 ffffa90c`16e0ea00 fffff805`ce488a8f : ffffbd8a`28000000 ffffa90c`16e0ecc9 00000000`00000000 fffff805`ce0f6dc4 : nt!KiExceptionDispatch+0x145 ffffa90c`16e0ebe0 fffff805`5f9ac099 : ffffa90c`16e0ed78 fffff805`82c974d0 ffffbd8a`335d8cb0 ffffe48f`bee9d748 : nt!KiInvalidOpcodeFault+0x34f ffffa90c`16e0ed70 00000000`00000000 : 00000000`00000000 fffff805`82c79100 ffffa90c`16e0ee00 00000000`00000000 : FLTMGR!FltInsertExtraCreateParameter+0x19 SYMBOL_NAME: FLTMGR!FltInsertExtraCreateParameter+19 MODULE_NAME: FLTMGR IMAGE_NAME: FLTMGR.SYS IMAGE_VERSION: 10.0.26100.3624 STACK_COMMAND: .process /r /p 0xffffe48fc21d0080; .thread 0xffffe48fc21dd080 ; kb BUCKET_ID_FUNC_OFFSET: 19 FAILURE_BUCKET_ID: 0x1E_C000001D_BAD_IP_FLTMGR!FltInsertExtraCreateParameter OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {39430fe1-1055-a459-79df-d7786e3454f2} Followup: MachineOwner ---------