search

microsoftfeedback / WinDbg-Feedback

Public issue and feedback tracking for WinDbg Preview.
Creative Commons Attribution 4.0 International
48 stars 12 forks source link

WinDbg The engine has been disconnected unexpectedly. #166

Open Camios opened 8 months ago

Camios commented 8 months ago

Reinstalled Windows 11 Pro and getting bluescreen Open a minidump from c:\Windows\Minidump or c:\Windows\Memory.dmp and immediately get "The engine has been disconnected unexpectedly."

Application log as follows"

***** 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.093 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25921.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\020124-8546-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 22621 MP (32 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 22621.1.amd64fre.ni_release.220506-1250 Kernel base = 0xfffff8025d400000 PsLoadedModuleList = 0xfffff8025e0134a0 Debug session time: Thu Feb 1 23:28:08.545 2024 (UTC + 10:00) System Uptime: 0 days 0:15:39.140

Camios commented 8 months ago

Tried an earlier minidump and it got a little further but still disconnects

WinDbg Application log as follows: Loading Dump File [C:\Windows\Minidump\020124-8593-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 22621 MP (32 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 22621.1.amd64fre.ni_release.220506-1250 Kernel base = 0xfffff8057a200000 PsLoadedModuleList = 0xfffff8057ae134a0 Debug session time: Thu Feb 1 23:12:06.377 2024 (UTC + 10:00) System Uptime: 0 days 0:01:00.971 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .............. Loading User Symbols PEB is paged out (Peb.Ldr = 00000008f52be018). Type ".hh dbgerr001" for details Loading unloaded module list .......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff8057a616b00 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffaf88`56aaf220=00000000000000fc 11: kd> !analyze -v

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc) An attempt was made to execute non-executable memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name is printed on the BugCheck screen and saved in KiBugCheckDriver. Arguments: Arg1: ffffd10cb72d3880, Virtual address for the attempted execute. Arg2: 8a00000162c009e3, PTE contents. Arg3: ffffaf8856aaf3d0, (reserved) Arg4: 0000000000000003, (reserved)

Debugging Details:

Camios commented 8 months ago

Loading the C:\Windows\Memory.dmp file into the old version of windbg and analysis works

windbg.txt

lzybkr commented 6 months ago

It looks like the debugger is crashing. If you can share a dump that you are trying to debug or a dump of the debugger crashing, then we can investigate.