Opened 9 years ago
Closed 8 years ago
#15247 closed defect (fixed)
The instruction at 0x12465ad0 referenced memory at 0x12465ad0. The memory could not be written.
Reported by: | Josef Murcek | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.0.16 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Windows |
Description
I'm using VirtualBox 5.0.16 and getting this strange error all the time. VirtualBox let me create a new virtual machine, but when I tried to mount an ISO file, it will immediately crash with read memory access (see Error.jpg). After clickin' on OK button, I'll get another one (Error2.jpg). My colleague have the same problem, we both are using Dell Precision laptops with integrated NVIDIA Quadro graphic card, for example, I have a K3100M type. But my drivers are up-to-date (according to Dell update software) and 3D acceleration is turned off. Can you please look on this issue and tell me what should I do for fixing it?
P.S: This ticket has been created as a new, original form is [here (https://www.virtualbox.org/ticket/13580#comment:30)].
Attachments (5)
Change History (14)
by , 9 years ago
by , 9 years ago
Attachment: | Error2.jpg added |
---|
by , 9 years ago
by , 9 years ago
Attachment: | VirtualBox.7z added |
---|
comment:1 by , 9 years ago
comment:3 by , 9 years ago
follow-up: 5 comment:4 by , 9 years ago
Disabling it using its GUI might not be enough. Try to uninstall it. After uninstalling it, also check for remnants, like drivers and services. To identify them, use Autoruns
comment:5 by , 9 years ago
by , 9 years ago
Attachment: | McAfee.jpg added |
---|
comment:7 by , 8 years ago
Wrote a comment at #14363 that could eventually also relate to your problem.
comment:8 by , 8 years ago
I've just downloaded the latest version of VirtualBox (v5.1.2) and it seems that this problem is fixed, because everything works fine now!
comment:9 by , 8 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I just started getting this error last week after not using Virtual Box for a few weeks. I dropped my VMs and tried to recreate them getting this same error with different memory locations. I then upgraded to 5.0.16 and continue to get the error. Has anyone found a work around.