virtualbox.org

My Windows 11 Pro VM, hosted on a Windows 11 Pro PC, always comes up with a critical error when a restart is made. The VM starts perfectly well when started after it has closed following the critical error. This behaviour occurs during Windows updates which require a restart. However, if I do a restart manually, the same critical error occurs so it is somehow triggered by the restart process.

I can't upload the VBox.log as it exceeds the maximum file size of 128Kb but here is a link to it - https://1drv.ms/u/s!Ag8aQ52IE8ZpnFtuyPG ... e?e=LzAckO

I think you'll find that zipped log files fit.

Thanks - attached.

00:00:35.123741 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:35.123742 !!
00:00:35.123742 !! VCPU2: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
00:00:35.123891 !!
00:00:35.123894 !! Skipping ring-0 registers and stack, rcErr=VINF_EM_TRIPLE_FAULT
00:00:35.123897 !!
00:00:35.123897 !! {mappings, <NULL>}
00:00:35.123897 !!
00:00:35.123907 !!

As you see, you're suffering from a triple fault exception. Unfortunately that makes it impossible to know what the original cause was. I should mention that I am running 6.1.32 on a Win11 host myself, and I have restarted my Win11 guest when prompted by Windows Update, and I do not get this exception.

The only objectionable point I see is that you have the GAs ISO still mounted - it is good practice to eject that. I mention it because we have had occasions in the past where rebooting the VM with any CD in the drive caused a crash, but that hasn't been seen in a long time. Also "triple fault" would indicate a corrupted ISO.

I don't expect that is your problem, but nothing else jumps out at the moment.

Thanks for looking. I have removed the GA disk but the problem persists. I have set up another Windows 11 VM which restarts OK so I will just delete the problem VM.