VM abort with error message, log has rtR3WinUnhandledXcptFilter

[Mark Cranness]

At seemingly random times, my VM aborts with an error dialog:

VirtualBoxVM.exe - Application Error : The instruction at 0x00007FFD9D2E8201 referenced memory at 0x0000000000000021. The memory could not be written.

Log shows that the VM had started recording audio (no idea why), then shortly after aborted.

[Mark Cranness]

I was not suspending the VM at the time, nor changing the window size. I think I had just set focus to the VM from a window on the host.

[Mark Cranness]

Many references to Audio in this log

[Mark Cranness]

In the 2020-02-24 log, frequent reoccurrences of:

41:45:53.731362 Audio: Enabling input for driver 'DSoundAudio'
41:45:53.731918 Audio Mixer: Setting recording source of sink '[Recording] Line In' to '[Line-In] DirectSound'
41:45:53.753873 Audio: Disabling input for driver 'DSoundAudio'
41:45:54.067072 Audio Mixer: Setting recording source of sink '[Recording] Line In' to '<None>' 41:45:54.084694 Audio: Enabling input for driver 'DSoundAudio'
41:45:54.085039 Audio Mixer: Setting recording source of sink '[Recording] Line In' to '[Line-In] DirectSound'

The VM host had recently resumed from sleep, and the VM then also resumed.

On the host, powercfg /requests showed that an audio stream was in progress for my webcam, and that was preventing the host from sleeping, and the webcam had been turned off.

Upon resuming the host from sleep, I had turned the webcam off and on a few times to reset it, followed by VM failure.

[Mark Cranness]

The VM apparently affecting the webcam for recording, even though I had cleared OFF the Settings, Audio, Enable Audio Input checkbox.

[Mark Cranness]

Per https://www.virtualbox.org/ticket/19123, I also have

07:25:42.918390 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffd9d2e8201
07:25:42.918399 ExceptionInformation[0]=0000000000000001
07:25:42.918405 ExceptionInformation[1]=0000000000000021

Hardening log attached.

[Mark Cranness]

Sorry, hardening log is a current one, not related to a crash.

[Mark Cranness]

This one just after a crash

[Mark Cranness]

This one just after a crash

[Mark Cranness]

This one just after a crash

[Mark Cranness]

Another crash. I restarted the VM, then sent the host to sleep and woke again, powered the webcam off and on a few times, then:

Ran a program in the VM that happened to make a beep, and immediate crash with message:
VirtualBoxVM.exe - Application Error : The instruction at 0x00007FFD9D2E8201 referenced memory at 0x0000000000000021. The memory could not be written.

There was a repeating partial beep that kept playing while the error message was shown.

This problem does not happen for VirtualBox 5.2.12. I first noticed it I think on 5.2.14 or 16 or 18, and reverted back to 5.2.12. Recently I updated to 6.2, and still crashing.

[Mark Cranness]

This one just after a crash

[Mark Cranness]

Hardening log associated with crash

[Dattatray]

VirtualBoxVM.exe - Application Error : The instruction at 0x00007FF9C200F671 referenced memory at 0x0000000000000000. The memory could not be written.