Hello,
I'm getting the following error on Windows 10 host, using a FreeBSD 11 guest: The instruction at 0x00007FF815B5D896 referenced memory at 0x0000000000000000. The memory could not be read.
I've done a lot of research on this problem and I can't quite figure out how to make it away. I'm thinking it might be related to my ATI Radeon 4290 graphics card, but I can't be sure and I'm not sure how to fix it.
The problem has persisted for quite some time. I have upgraded the host, swapped RAM on the host, re-installed the graphics drivers on the host, switched the VBox graphics controller, and disabled the VBox audio card.
Previously, on Windows 7, this would blue screen and crash the whole server. On Windows 10, I get this error and this VirtualMachine is the only one to ever do this.
I'm running several Debian guests without issue. I tried to setup a FreeBSD 12 and then a 13 guest to migrate to but these two machines would crash the same way without any setup beyond installation.
This FreeBSD machine generally just encodes MP4 and WEBM videos using FFMpeg, and also serves them using NginX.
Current host is Windows 10 v. 2004 (build 19041.867) and current VBox is 6.1.18r142142 (Qt5.6.2).
Thanks in advance. Any help is greatly appreciated.
FreeBSD Guest: The instruction referenced memory at 0x... The memory could not be read
Re: FreeBSD Guest: The instruction referenced memory at 0x... The memory could not be read
Can anyone help me? I tried to be detailed and make this easy to answer. I'm not sure how to read the VBox log.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: FreeBSD Guest: The instruction referenced memory at 0x... The memory could not be read
I looked at this one before but couldn't pin it down. Looking again, your VM has a slew of these:
PIIX3 and ATA imply a failure in the VM's disk access. The VM's disk files are all on the R: drive:
before crashing in "VBoxVMM.DLL", which if I understand correctly is a fairly fundamental DLL to run the VM.39:50:59.902287 PIIX3 ATA: Ctl#1: ABORT DMA
PIIX3 and ATA imply a failure in the VM's disk access. The VM's disk files are all on the R: drive:
Is the R: drive failing? Is it a platter drive? Is the VM's OS heavily accessing all three vdi's at the same time? I have had heavy disk access on two disk files on the same platter drive kill the accessing VM.00:00:06.388516 File system of 'R:\VirtualMachines\FreeBSD 11 - Grand Cameo CDN\Snapshots' (snapshots) is ntfs
00:00:06.388528 File system of 'R:\VirtualMachines\FreeBSD 11 - Grand Cameo CDN\FreeBSD 11 - Grand Cameo CDN.vdi' is ntfs
00:00:06.389392 File system of 'R:\VirtualMachines\FreeBSD 11 - Grand Cameo CDN\GC_CDN2b.vdi' is ntfs
00:00:06.390640 File system of 'R:\VirtualMachines\FreeBSD 11 - Grand Cameo CDN\GC_CDN2c.vdi' is ntfs