Long time tech, total noob to VM management. Always had a sysadmin to shunt those tasks off to! I have been running for a few months now, a Win10 Guest OS, on a Win10 Host. I rarely reboot the host (weeks /months in between reboots.)
Sometime in the last 2 days, I saw the notification for an update to VirtualBox, and decided to go ahead and install said update. I did not reboot iirc at the time, but kept on working for the day.
Separately, had been needing to enable TPM 2.0 in my BIOS to check out Win11. Up until last night, maybe 11pm or so, VBx was working great. This morning, I decided to reboot and enable that TPM. That went well, great! Tried to start a couple hours later with VBx, powered on my Guest, logged in, all was good.
Shortly after logging in, I opened my browser, my routine tabs- about 3, to specific sites. Second to that, opened up the main program I use daily. About then, the GuestVM completely crashed - like a Thanos blip, it was gone, and VirtualBox was already trying to restart it while I stared stupidly at the screen (this has never happened before!)
Tried a few more times, same routine (couldn't happen twice right?) Yeah, it did. At first, I thought it was the webpage - it would crash each time I hit "Restore Session" when reopening Chrome, and the 3rd tab began to load (never loads.) After changing the Advanced Startup to create a DMP instead of auto reboot, it stopped crashing totally, and changed to just freezing in place for eternity. The VirtualBox window does NOT lock up - just the GuestOS within the window.
There has been no Windows Update tmk, in the last 48hrs on this Guest. I have re-disabled the TPM and rebooted. I have turned 3D Acceleration on and off, gave it more CPU's, less CPU's, more Ram, less Ram, changed paravirtualiztion from Default to HyperV, etc - none of this has helped. SOMETIMES, not often, the lockup actually happens when on the Login screen, about 3 characters into typing. I have also updated video driver during all this. I have NOT done a scrub of dirty uninstall left overs; going to try that next while hoping the logs attached mean something to someone here.
I've read every post here that sounds remotely similar and touches on the latest .32 update. I have uninstalled .32, rebooted, installed .30, did not resolve. Uninstalled .30, installed .24, did not resolve.
I cloned the GuestVM to another drive, seeing a post in here about underlying drive issues... the lockup followed the ClonedVM to the other drive. (SSD to Sata move.) So no help there.
I'm at a huge loss, and way outside my zone here. Really need it working before a battery of meetings I have tomorrow! Grabbed some log files per notes I've seen in here, attaching those. Somewhere along all this mess, I did find two sets of interesting log info, but in the GuestOS's Event Viewer. Those are below:
Code: Select all
Faulting application name: dwm.exe, version: 10.0.19041.746, time stamp: 0x6be51595
Faulting module name: VBoxDispD3D.dll, version: 6.1.32.49290, time stamp: 0x60899173
Exception code: 0xc0000005
Fault offset: 0x000000000000c8b0
Faulting process id: 0x44c
Faulting application start time: 0x01d8139c80a419f4
Faulting application path: C:\Windows\system32\dwm.exe
Faulting module path: C:\Windows\system32\VBoxDispD3D.dll
Report Id: e8d2acd3-06c1-404e-8a0c-a86386fd64ba
Faulting package full name:
Faulting package-relative application ID: {ends here, no ID shown}Code: Select all
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffca0b872e3050, 0xfffff80483471850, 0xffffca0b874ba920). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 67a79caf-b9a8-4b74-bb34-e32812e216b7.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffda089da51050, 0xfffff80457071850, 0xffffda089d366a20). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: a53a7d80-2493-4c11-bf6e-be87fe4f4e03.I need an Obi-Wan here.
Thanks,
AnamraKarman