Re: [Vol-users] diagnose problematic ram dump?
6 Nov
2013
6 Nov
'13
4:49 a.m.
Hi Rob,
It looks to me like volatility can not find the correct kdbg
location. Can you please also try the kdbgscan module? When you
acquired the image did you use the default mode ("physical" - maps
\\.\PhysicalMemory device)?
Thanks
Michael.