Hello
For some time now and now (it feels) more and more often, my VM guests are crashing and I get error messages like this.
ATTENTION: This message comes from a previous crash, not the last one from which the logs come.
They only differ in the value 0x0000nnnnnn...
I use RAM with ECC and have no other problems on the host.
SFC /scannow runs error-free for both the host and the guests.
Can someone help me?
I have attached the two logs of the last crash of a VM.
Unfortunately I had to cut them off (in the middle) because they would have been too big.
Thank you.
VG ACX_Com
VM crashes - Error: 0x0000... + 0xFFFF...
VM crashes - Error: 0x0000... + 0xFFFF...
- Attachments
-
- Screenshot 2023-12-22 102804.png (10.01 KiB) Viewed 963 times
-
- Server-Java+minecraft-2023-12-22-14-10-33.log
- (25.44 KiB) Downloaded 63 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: VM crashes - Error: 0x0000... + 0xFFFF...
Zipped logs almost always fit and don't need cutting out of all the important data. Please try that log again.
Meanwhile, the hardening log shows an exit code 0xC0000005, which is covered in Diagnosing VirtualBox Hardening Issues. In addition to that information, try uninstalling (full uninstall not just disable) any non-Microsoft antivirus, web-safety, nanny, banking, etc security software as a test, then reboot and try Virtualbox again. You may need to also uninstall and reinstall Virtualbox, after the uninstall of 3rd-party security software:
Meanwhile, the hardening log shows an exit code 0xC0000005, which is covered in Diagnosing VirtualBox Hardening Issues. In addition to that information, try uninstalling (full uninstall not just disable) any non-Microsoft antivirus, web-safety, nanny, banking, etc security software as a test, then reboot and try Virtualbox again. You may need to also uninstall and reinstall Virtualbox, after the uninstall of 3rd-party security software:
- Uninstall Virtualbox and reboot.
- Go to "C:\Windows\System32\drivers", look for any files called 'Vbox*.sys' (there could be up to 5) and delete them.
- Reboot again.
- Reinstall Virtualbox using right-click-Run-As-Administrator.
-
- Volunteer
- Posts: 5678
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: VM crashes - Error: 0x0000... + 0xFFFF...
If the addresses always end with "6DB2", you're probably experiencing a known issue in the audio implementation that is currently being worked on:
See #21931 RDP to windows crashes VM for details, workarounds and test builds. Note that it doesn't really matter if you're using RDP or not.
Re: VM crashes - Error: 0x0000... + 0xFFFF...
Hello and thank you for your help.
Since I don't need audio on the VMs, I disabled it in the machines' VM settings.
I haven't used the increased debugging setting yet because I have deactivated audio.
So that should work then?
I uploaded the same log file again as 7z.
Since it currently points to audio, I haven't uninstalled/reinstalled it yet.
Best regards
Since I don't need audio on the VMs, I disabled it in the machines' VM settings.
I haven't used the increased debugging setting yet because I have deactivated audio.
So that should work then?
I uploaded the same log file again as 7z.
Since it currently points to audio, I haven't uninstalled/reinstalled it yet.
Best regards
- Attachments
-
- Server-Java+minecraft-2023-12-25-16-13-28.7z
- (21.92 KiB) Downloaded 53 times
-
- Volunteer
- Posts: 5678
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: VM crashes - Error: 0x0000... + 0xFFFF...
Yes, that should work. If it doesn't, provide a (zipped) VBox.log file of a VM run.
Re: VM crashes - Error: 0x0000... + 0xFFFF...
Thank you.
Disabling the virtual audio hardware seems to have solved the problem.
The VMs have been running since then.
Best regards.
Disabling the virtual audio hardware seems to have solved the problem.
The VMs have been running since then.
Best regards.