Opened 12 years ago
Closed 8 years ago
#11039 closed defect (obsolete)
"unable to allocate and lock memory" error (Prio conflict)
| Reported by: | Mike | Owned by: | |
|---|---|---|---|
| Component: | VM control | Version: | VirtualBox 4.2.0 |
| Keywords: | RAM | Cc: | |
| Guest type: | Windows | Host type: | Windows |
Description
I have 6GB of RAM and when I try to put the RAM at 1400MB or higher I get that error. It seems to only work if the RAM is set to 1000MB, but I need at least 2GB of RAM. I have read some of the other entries and tried their solutions, but it doesn't work. I don't have the Google Crash Handler process and I freed up the standby RAM using RAMMap. I have like 3GB of free RAM so it shouldn't be a problem.
Host OS: Windows 7 Home 64-bit
Guest OS: Windows 7 Ultimate 32 and 64-bit
Attachments (1)
Change History (7)
by , 12 years ago
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Thanks, I removed Prio and it works now. Is there a reason why Prio interferes with VirtualBox?
comment:3 by , 12 years ago
| Summary: | "unable to allocate and lock memory" error → "unable to allocate and lock memory" error (Prio conflict) |
|---|
comment:4 by , 12 years ago
That's a good question. Unfortunately we don't have the source code available for this tool. Thanks Andre for the hint!
comment:5 by , 12 years ago
I had the same issue with prio and that's why I know it. The tool uses AppInit to hook into all programs and this seems to causes issues with VirtualBox.
comment:6 by , 8 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
Do you use the tool Prio (http://www.prnwatch.com/prio.html)? If yes, remove it.