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

[danf84]

This happened twice now with the exact same message.

I don't recognise having done anything particular - if anything, I was browsing in Windows Explorer to the Downloads folder, from the Tree View.

Guest: Windows 7 SP1 x86. Host: Windows 7 SP1 x64.

[LittleJeff1970]

I started having similar issues after upgrading from 5.0.26 to 5.1.2. I cannot produce proof, but I believe this may have something to do with the audio functionality, at least for me. My evidence is all circumstantial. What I have noticed is that this "memory could not be read error" seems to come up sporadically when I perform an operation that triggers a sound. For instance, I've seen it happen at least twice after hitting "send" on an Outlook email. I have Office's feedback with sound turned on, so each send operation triggers the typical Outlook send sound. It doesn't happen EVERY time, but I've seen the VM crash with this type of error at least twice. I've also noticed other strange behaviors such as a YouTube video losing audio playback if I pause it and then hit play. To get the audio back, I have to close IE, reopen, and replay the video.

Right now I am performing an experiment to try to confirm my suspicions. I have set the host audio driver in my VM to "null Audio Driver" for the time being. The VM still sees a sound device, but the host gets no sound interactions whatsoever. I want to see if my VM runs for several days with no issues this way. Then I'll go back to my usual Windows DirectSound setting and see if the problem resurfaces.

Again, this problem is definitely NEW with VirtualBox 5.1.2. I could run my VM (my guest is also Windows 7 Pro x64) for days or even weeks with no problems under 5.0.26. The VirtualBox log for the VM has nothing interesting as far as I can tell, and I also don't get anything at all in the host's Windows event log OR mini dump location (yes, I have it enabled in the registry). It's like VirtualBox crashes, but my host (also Windows 7 Pro x64) doesn't even know it crashed.

[danf84]

Interesting, I never have audio turned on, but on this VM it is on. I'll turn it off and report if it ever happens again

[ChuckDMan:-)]

I thought it was related to sound, but it is random. I've turned off all sound and the random aborts still happen. Had to switch back to 5.0 and it is been running ever since without a crash. My bug is 15797. I think it is related to QT.

[Frank Mehnert]

As we cannot reproduce the problem we need crash dumps, see here. Audio-related crashes were fixed in 5.1.4.

[AYSabre]

Version 5.1.4 r110228 (Qt5.5.1) Log

[AYSabre]

I'm having the crash issue too as reported on the forums here: ​https://forums.virtualbox.org/viewtopic.php?f=6&t=79123

My log files are attached to that post for 5.1.4 and the previous version. I attached the latest one to this ticket too.

I do have my audio enabled in the VM, so based on the info in the posts above, I'll try turning the audio off as well and see if this stops. This issue only started two versions ago so had no issues prior.

[Thomas C.]

I have the same issue. See this ticket https://www.virtualbox.org/ticket/15770#no3
I have disable sound and my VM has not crash since one day. I will continue testing with sound disable.

[pentagonik]

I've uploaded a new test build which hopefully should fix the problem:

The files can be downloaded from the Testbuilds page.

Scroll down to the Development Snapshots and download the build apppropriate for your host platform.

Could you please try this and provide the usual VBox log files afterwards then?

This test build is not intended for production use!

Thank you!

[pentagonik]

Please note to test with enable sound again.

[Thomas C.]

Unfortunately, I can't risk to test a beta version in my job.
Maybe someone else will be able to try.

[EricBDev]

Crah with VB 5.1.4 - log files

[EricBDev]

Crah with VB 5.1.4 - log files

[EricBDev]

As reported in the forums, I also have the issue with VirtualBox 5.1.4 on my Dell Latitude E7470 with 24 GB of RAM and latest bios. Host: Windows 10 Entreprise 1511 x64 Guest: Windows 10 Pro 1607 x64. I am using bridge network, VT/x, PAE/NX, HyperV paravirtualization; I affected 2 CPU in the guest from the 4 logical cores in the host (i5-6300U = dual core cpu with HT). Please have a look of the log files attached (and sorry for the duplicate) Any chance to have a fix soon? Thank you!

[pentagonik]

@EricBDev Can you please retry with 5.1.6 whether this fixed the issue for you? Thanks!

[Thomas C.]

The isssue seems to be resolved with 5.1.6

[AYSabre]

Crash Log for Version 5.1.6 r110634

[AYSabre]

I had the crash occur this morning again. I've attached the log file. Audio is still turned off.

[EricBDev]

I again had the issue (which mean a complete crash of my VM) twice with 5.1.6 this week. Since this bug prevent me from working properly with VirtualBox, I eventually switched my VM to HyperV. It's fortunately an easy step: convert the vdi to vhd if necessary (already used vhd from the beginning) and use it in Windows 10 HyperV!