This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 81%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESR%3C/text%3E%3C/svg%3E)
Hi Team,
I have noticed some strange behaviour with WinDbg. I am getting 'Kernel stack not resident' error while trying to view the thread's call stack. But i am able to see the same thread's call stack if i analyzed the same dump file using WinDbg Preview. As per MSDN doc, WinDbg Preview is using the same underlying engine as WinDbg.
Generally we use company provided virtual machines to analyze customer reported issues and at present we can't install WinDbg Preview on those VM's. Could you please help me in understanding the reason for the above mentioned behavior?
Regards,
Sai
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 77%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Just a wild guess.
Probably different implementations in extension dlls, for error message "Kernel stack not resident" can be found in kdexts.dll.
Windbg Preview:
kd> .chain
...
Extension DLL chain:
dbghelp: image 10.0.20153.1000, API 10.0.6,
[path: C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2007.6001.0_neutral__8wekyb3d8bbwe\amd64\dbghelp.dll]
...
kdexts: image 10.0.20153.1000, API 1.0.0,
[path: C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2007.6001.0_neutral__8wekyb3d8bbwe\amd64\winxp\kdexts.dll]
Legacy windbg:
*0: kd> .chain
...
Extension DLL chain:
dbghelp: image 10.0.19041.1, API 10.0.6,
[path: C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\dbghelp.dll]
...
kdexts: image 10.0.19041.1, API 1.0.0,
[path: C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\winxp\kdexts.dll]*
Thanks for your reply. I just checked the scenario by replacing these DLLs but no luck.
FYI - I am able to see the call stack after replacing all DLLs.