Opened 9 years ago
Closed 8 years ago
#15091 closed defect (obsolete)
memory could not be written
| Reported by: | Oregszun | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.0.14 |
| Keywords: | Cc: | ||
| Guest type: | all | Host type: | Windows |
Description
I have installed latest Virtualbox on a Win7 Enterprise 64 bit, and shortly(1-5 sec) after starting a VM it crashes "The memory could not be written" application error.
I have tried different OS selection, and the issue occurs even if there is no OS installed/booted.
Attachments (4)
Change History (10)
by , 9 years ago
by , 9 years ago
| Attachment: | VBox.log.1 added |
|---|
by , 9 years ago
| Attachment: | VBoxHardening.log added |
|---|
by , 9 years ago
| Attachment: | jessie3.vbox added |
|---|
comment:3 by , 9 years ago
Yes, its independent of that. Also tried to increase/reduce video memory.
comment:5 by , 9 years ago
What is the function of the c:\temp\ammemb64.dll file, which is found on your system? At the end of your VBoxHardening.log file, there are two "supR3HardenedDllNotificationCallback: Unload" lines, one of which is related to ammemb64.dll
comment:6 by , 8 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The issue occurs with and without extension pack. I have also experienced the same with latest version 4 of VBOX.