The memory could not be "read"

[DenisFR]

Hello, With new 5.1.2 version, I've got this error:

The instruction at "0xcc47278e" referenced memory at "0x00000010". The memory could not be "read".

This occurs only with a specific software (Movicon 11.4) when I start his runtime. But the error is not report in guest side. This crash Guest and error is reported in host.

[DenisFR]

VBox.log

[DenisFR]

VBoxHardening.log

[sergroma]

I am having similar error "The instruction at "0xe33b278e" referenced memory at "0x00000010". The memory could not be "read"." running Win8 guest OS when editing in WordPad which I can reproduce in my setup. VB Version 5.1.2 r108956

Last 4 digits in the instruction address are same as reported in this ticket.

[frg]

Another crash with latest 5.1.3 test build.

[frg]

Well this becomes a little frustrating. The vms can abort any time with the latest builds. It does not seem to be guest related. A Win 10 VM with latest guest additions also did crash and another crash also occured shortly after the last vm closed.

If its not fixed soon I might to need to go back to 5.0.26. Sigh.

FRG

[xonfug]

I am having this issue as well. Windows 7 Pro guest on Windows 7 Enterprise host. Has occurred twice within an hour of upgrading to 5.1.2. First time was when performed a windows Check for updates. The second time was when I modified my Visual Studio installation and it started to download files. So on the surface looks like related to network/internet access. Both times, rebooted the guest and the actions worked ok, so intermittent so far.

[frg]

Just happend again with a brand new Win 10 Anniversary Update VM. Latest guest additions installed. Network was disabled because I had not kicked out the snooping tasks and the junk yet. My money would be more on problems with the sound system or something general.

[xonfug]

Had it happen again today, this time at the guest Windows login screen. Screenshot and logs attached.

[xonfug]

Error message

[Frank Mehnert]

To debug these crashes we need a Windows application dump, see here.

[xonfug]

Been using 5.1.6 for two weeks now and not had a crash.

[Frank Mehnert]

Thanks. As I didn't see a recent complaint from other users in this ticket I will close it.

[TGP1994]

I'd like to request that this be reopened, as I started seeing the issue after updating to 5.1.6. Like the other users, I only receive it under strange circumstances, like when using an application within the guest. I can consistently reproduce the error by quitting a DirectX game in a Windows XP VM (host is Windows 10 64 bit). I also have Norton 360 installed on the host. I'll try to upload my logs following this comment.

Edit: Sorry frank, I just saw your request for Minidumps. I guess they weren't being saved, so I'll try to catch one next time.

[TGP1994]

Updating regarding Minidumps: following the instructions frank linked to (for Windows 10) does not appear to work; Virtualbox does not generate Minidumps when encountering this exception/error. I've realized now though that I can't 100% reproduce the issue when exiting my game, it's a little more sporadic than that. It does only occur when exiting the game though.

[TGP1994]

To frank or general Virtualbox developers: where would you like the ~1.5GB dump file uploaded to? I captured it using Task Manager when the error message popped up. I don't think the dump file is going to fit under the 512KB limit here at the ticket tracker.