The Instruction at 0x... referenced memory at 0x... The memory could not be read

[Frank Breitling]

As of version 4.3.16 I cannot start my Ubuntu guest on Windows 7 64 Bit.

Instead I receive the Error message:

"Die Anweisung in 0x... verweist auf Speicher 0x.... Der Vorgan read konnte nicht im Speicher durchgeführt werden."

The English version according to Google should be:

"The Instruction at 0x... referenced memory at 0x... The memory could not be read."

This is just an update of Ticket #13580 because I cannot update its version number to 5.0.0.

[Frank Mehnert]

Do you have 3D enabled for your VM? If so, does disabling 3D in the VM settings make any difference? And did you already try VBox 5.0.2?

In case it still crashes with 5.0.2 and 3D disabled, could you provide an application dump (see here, scroll down)?

[Frank Breitling]

I have not tried disabling 3D in the VM settings but the problem could be resolved by updating my ATI graphic card drivers from 2010 to the latest version of Oct 15 2013 (Catalyst Software Suite 13.9). Further details are described in the previous ticked #13580 mentioned above.

I should also point out that the method for application dumps listed at the VirtualBox page above is unnecessarily complicated and confusing. A much simpler method is provided by the ​Process Explorer. Could anybody please add this method to this page?

[Frank Mehnert]

I've added a note about using the process explorer for creating minidumps on Windows. However, this works only if the process didn't crash.

[BenjaHex]

My comment relate to #13580 #14363 and eventually #15247. I have the VBox version 5.0.24.r108355 and observed the same behaviour with the previous version of VBox.

My Observations

I have a two monitor system and configured vbox to have a two monitor system as well.
One monitor is connected to onboard intel and the other to amd graphics card.
Both drivers are up-to-date!
I get the error "The Instruction at 0x... referenced memory at 0x... The memory could not be read." under the following circumstances:

• 3D Acceleration enabled
• at least one window of the virtual monitors is on intels graphic card
• under one of the follwing actions so far observed:
  • directly between after password entered and loading of desktop
  • resuming a saved state (where one virtual monitor is again on the intel graphics card)

As workaround works for me either disabling 3D Acceleration or to make sure that, while the above discribed actions, all windows of vbox are on the amd graphics card.
I hope this helps someone!
I will also mark this ticket as unfixed.