Opened 2 weeks ago
Last modified 12 days ago
#22389 new defect
Absturz von VirtualBox 7.1.8 - crash of VirtualBox 7.1.8
| Reported by: | mh-01 | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox-7.1.8 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Windows |
Description
Virtual Box is running on a host (Win10 Enterprise 22H2) hosting a Win10 virtual machine. A client is running remote desktop to the host. After client disconnects (not signing out) VirtualBox reports this error and crashes:
Attachments (1)
Change History (3)
by , 2 weeks ago
| Attachment: | VirtualBox crash.png added |
|---|
comment:1 by , 2 weeks ago
When using VirtualBox 7.1.8 and locking the desktop, returning to the computer to unlock the desktop causes this crash also.
This didn't happen in 7.1.6.
Addendum, while the error report displays, I have found that if I ignore it, VirtualBox continues to operate successfully and without any issues.
Below are copies of the errors I receive every time I come back to my machine after it has been locked.
VirtualBoxVM.exe - Application Error
The instruction at 0x00007FF988064E2F referenced memory at 0x0000000000000000. The memory could not be written.
Click on OK to terminate the program Click on CANCEL to debug the program
OK Cancel
VirtualBoxVM.exe - Application Error
The instruction at 0x00007FFA998D4E2F referenced memory at 0xFFFFFFFFFFFFFFFF. The memory could not be read.
Click on OK to terminate the program Click on CANCEL to debug the program
OK Cancel
comment:2 by , 12 days ago
I can confirm this behaviour. I had to downgrade to 7.1.4 (7.1.6 had a problem with USB devices).
VirtualBox error message