SYSTEM_SERVICE_EXCEPTION BlueScreen BSOD

[MoonKid2]

I am using VirtualBox 6.1.34 with Debian 11 as Host since years and some Windows VMs. No problem at all.

But since one week all Windows VMs are givin me a BOSD blue screen with

Code: Select all   Expand viewCollapse view

SYSTEM_SERVICE_EXCEPTION

after some minutes running.

Also when creating a fresh VM with a fresh created hard disk the installer gives me the BOSD after some minutes. This is for Windows 10 and Windows 7 also.

[scottgus1]

Did a host OS kernel update happen? You may need to run the 6.1.35 test build. The newest Linux kernels aren't compatible with 6.1.34. (Note that the development snapshots 6.1.97 on the Test Builds page are also not compatible with the new kernel, only 6.1.35.)

BTW, I deleted your other post on the 2020 topic, since that topic's subject is probably not the cause of your problem.

[MoonKid2]

Current running Kernel is

Code: Select all   Expand viewCollapse view

5.10.0-15-amd64 #1 SMP Debian 5.10.120-1 (2022-06-09) x86_64 GNU/Linux

from Debian 11 (stable).

[fth0]

VirtualBox 6.1.34 and 6.1.97r150532 do not support Debian Linux kernel 5.10.120 on the host and will produce random crashes in the guest (pun intended ). See 20914 and Windows 10 Guest on Linux host dies seconds after boot for details.

The VirtualBox test builds 6.1.35r151864 (and newer) are supposed to support Linux kernels 5.18, 5.17.12+, 5.15.44+, 5.10.119+ and more on the host and in the guest.

[elliot15]

...and you can download an older iteration or build of VirtualBox?

[scottgus1]

@elliot15, yes, one can download older versions of Virtualbox, at https://www.virtualbox.org/wiki/Download_Old_Builds or https://download.virtualbox.org/virtualbox/.

But if you have a new kernel for which earlier Virtualbox is incompatible, as this topic is discussing, then there'd be no purpose in getting an older version.

[MoonKid2]

It seems this problem is related to some versions of the Linux Kernel.
There is an open ticket: https://www.virtualbox.org/ticket/20914

Using the current development build of VBox (6.1.35) seems to "fix" the problem.

[scottgus1]

It seems this problem is related to some versions of the Linux Kernel.
...
Using the current development build of VBox (6.1.35) seems to "fix" the problem.

Yup, just like fth0 said above, and even posted the same Bugtracker link. And, curiously, I posted about too, above.......

It's good to read the topic responses before posting again, else one might post a discovery that someone else above already discovered and posted about days ago.