VirtualBox 4.3.26 Instruction 0x9474357f at Memory 0x0000028
VirtualBox 4.3.26 Instruction 0x9474357f at Memory 0x0000028
I am running Windows 10 build 10061 and I have VBoxWindowsAdditions installed. Normally my display settings are set to 2D and 3D acceleration turned off and 128MB of memory allocated. As such, the "VritualBox Graphics Adapter for Windows 8" driver is disabled "because it has reported problems. (Code 43)". If I turn 3D on, allocate 256MB to the display and start the VM, it will crash VirtualBox with the message "The instruction at 0x9474357f referenced memory at 0x00000028. The memory could not be read." It stays unbootable until I turn 3D off. As this is experimental software it is not a critical issue but the fact that VirtualBox crashes instead of exiting gracefully or disabling the feature looks like an issue.
-
loukingjr
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: just about all that run
Re: VirtualBox 4.3.26 Instruction 0x9474357f at Memory 0x000
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.
Re: VirtualBox 4.3.26 Instruction 0x9474357f at Memory 0x000
I tried flipping 2D and 3D back on, leaving memory at 128MB and got the same crash again. So I restarted without them enabled so I could get the system back up. I then went into Device Manager and deleted the VirtualBox video driver for Windows 8. Shut down, enabled 2D and 3D again, and restarted. Now it works fine. But, without that VirtualBox video driver, is it really running with 2D and 3D acceleration? I am also running in 1920x1080x32 mode by using VBoxManage to set CustomVideoMode1.
-
loukingjr
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: just about all that run
Re: VirtualBox 4.3.26 Instruction 0x9474357f at Memory 0x000
Try reinstalling the 4.3.26 GAs. When the builds are updated they do "funny" things to them. I had to reinstall the GAs to get shared folders working again.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.
Re: VirtualBox 4.3.26 Instruction 0x9474357f at Memory 0x000
I am experiencing the exact same issue.
The error message is identical - "instruction at some random address referenced memory at 0x0000028 the memory could not be read"
Host is Windows 7 SP1 64bit. Virtualbox 4.3.26.
Running with integrated Intel HD graphics 4600.
Updating the host graphics driver doesn't help.
Tried 32bit and 64bit guest, same problem.
Its been this way since I installed the .ISO, and last two build updates till current build 10074.
Tried a fresh install of 10074, doesn't help.
Guest additions reinstall, uninstall, manual install of drivers, nothing helps.
very strange..
The error message is identical - "instruction at some random address referenced memory at 0x0000028 the memory could not be read"
Host is Windows 7 SP1 64bit. Virtualbox 4.3.26.
Running with integrated Intel HD graphics 4600.
Updating the host graphics driver doesn't help.
Tried 32bit and 64bit guest, same problem.
Its been this way since I installed the .ISO, and last two build updates till current build 10074.
Tried a fresh install of 10074, doesn't help.
Guest additions reinstall, uninstall, manual install of drivers, nothing helps.
very strange..
Re: VirtualBox 4.3.26 Instruction 0x9474357f at Memory 0x000
Latest VirtualBox 4.3.28 is better.
I still can't enable 3D in the machine's settings without crashing when the driver is installed, but the vbox additions display driver is working correctly.
The guest screen resolution re-sizes according to window/full screen, which it could not do before.
I still can't enable 3D in the machine's settings without crashing when the driver is installed, but the vbox additions display driver is working correctly.
The guest screen resolution re-sizes according to window/full screen, which it could not do before.
