Windbg c0000005 Exception in ext.analyze debugger extension.

B

Brokoliy

Member
Joined
Jul 8, 2024
Posts
12
When I try to open the dump file, this error comes in the first analysis output and when I get the analysis output again, the file opens but as follows:

First:

Code: 
READ_ADDRESS: fffff80137afb390: Unable to get MiVisibleState
c0000005 Exception in ext.analyze debugger extension.
      PC: 00007ffb`3bbb06f5  VA: 00007ffb`3be1c000  R/W: 1  Parameter: 00000000`00000000

Second:
Code: 
READ_ADDRESS: fffff80137afb390: Unable to get MiVisibleState
Unable to get nt!_MI_SYSTEM_VA_ASSIGNMENT.BaseAddress at ffffffc000000bc8
Unable to get nt!_MI_SYSTEM_VA_ASSIGNMENT.BaseAddress at ffffffc000000bd8
Unable to get nt!_MI_SYSTEM_VA_ASSIGNMENT.BaseAddress at ffffffc000000be8
Unable to get nt!_MI_SYSTEM_VA_ASSIGNMENT.BaseAddress at ffffffc000000bf8
Unable to get nt!_MI_SYSTEM_VA_ASSIGNMENT.BaseAddress at ffffffc000000c08
Unable to get nt!_MI_SYSTEM_VA_ASSIGNMENT.BaseAddress at ffffffc000000c18
Unable to get nt!_MI_SYSTEM_VA_ASSIGNMENT.BaseAddress at ffffffc000000c28
Unable to get nt!_MI_SYSTEM_VA_ASSIGNMENT.BaseAddress at ffffffc000000c38
Unable to get nt!_MI_SYSTEM_VA_ASSIGNMENT.BaseAddress at ffffffc000000c48
Unable to get nt!_MI_SYSTEM_VA_ASSIGNMENT.BaseAddress at ffffffc000000c58
Unable to get nt!_MI_SYSTEM_VA_ASSIGNMENT.BaseAddress at ffffffc000000c68
Unable to get nt!_MI_SYSTEM_VA_ASSIGNMENT.BaseAddress at ffffffc000000c78
Unable to get nt!_MI_SYSTEM_VA_ASSIGNMENT.BaseAddress at ffffffc000000c88
Unable to read MiSystemVaType memory at ffffffc000000000
GetUlongFromAddress: unable to read from fffff80137a16aac
 0000000000000060

I tried the windbg version change, deleted and reinstalled, but nothing changed. SDK windbg has this problem while windbg prewiev does not have this problem.
 
Hello Brokoliy,

Could you please provide details of what you are trying to do with Windbg tool? Did you get any Bsod?

Thank you.
 
Brokoliy said:
I tried the windbg version change, deleted and reinstalled, but nothing changed. SDK windbg has this problem while windbg prewiev does not have this problem.
Click to expand...
I would try using an older version of the SDK debugger, that seems to be a problem with the SDK debugger installation.
 
Back
Top