Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No suitable address space mapping found #698

Closed
leandroflxsilva opened this issue Apr 8, 2020 · 7 comments
Closed

No suitable address space mapping found #698

leandroflxsilva opened this issue Apr 8, 2020 · 7 comments
Labels

Comments

@leandroflxsilva
Copy link

Hello, i have a problem with Volatility version 2.6. I'm using Windows 10 but the copy is Windows 7 32bits.
First command:
01

Second command:
02

@gleeda
Copy link
Member

gleeda commented May 7, 2020

Could you try to use the other Win7SP1x86_23418 profile? If that doesn't work, could you run kdbgscan and see what comes back from that?

@gleeda gleeda added the Windows label May 7, 2020
@leandroflxsilva
Copy link
Author

I tried with the profile Win7SP1x86_23418
01

The result of the command kdbgscan is this:
02
03

@atcuno
Copy link
Contributor

atcuno commented May 13, 2020

Can you try with --profile= instead of profile: ? I have never seen that form of command line argument and I am not sure if Volatility will support it.

Also, how was memory acquired?

@leandroflxsilva
Copy link
Author

I tried with the command "--profile"
01

I acquired the memory with the FTK IMAGER.

@atcuno
Copy link
Contributor

atcuno commented May 13, 2020

it would be --profile=Win7SP1x86_23418

note the = instead of :

@leandroflxsilva
Copy link
Author

Wow, it worked.Thank you so much.
01

@atcuno
Copy link
Contributor

atcuno commented May 15, 2020

Glad it worked!

@atcuno atcuno closed this as completed May 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants