Windows 10 x64 Build 20206 - KMODE_EXCEPTION_NOT_HANDLED

[Jacob Klein]

Issue persists on:
Windows 10 Build 20215
Oracle VirtualBox v6.1.15 Test Build 140351

[AndyMidd]

Issue persists on:
Windows 10 Build 20215. 64bit. AMD Ryzen.
VB 6.1.12.
No surprises.

Microsoft admit there may be a problem....

[Karkass]

This was in build 20215 announcement:
Known issues:
We’re investigating reports of some devices experiencing a KMODE_EXCEPTION bugcheck when using certain virtualization technologies.

So i suppose we only need wait to microsoft solve it.

[Jacob Klein]

Thanks.
I understand that Microsoft is diagnosing it, and that Oracle has not yet acknowledged it.
And I will continue to report the issue, on new Builds of Windows and VirtualBox, until it is fixed by Microsoft or Oracle.

[Ace of Tunes]

Hey, I just created an account to say that I am on build 20211.1000 (rs_prerelease) and I am still running into the KMODE_EXCEPTION_NOT_HANDLED issue. I can't roll my windows back, it failed when I tried to, and I don't have an easy way to reinstall and reconfigure my software, since I can't afford any down time right now, apparently my image backups stopped a few months ago, so I am totally frozen in regards to VB until this is resolved

Please Oracle, take note that this needs a resolution, Microsoft may be working on it, but it would be great to have a second team looking into it; especially since there is a huge overlap between the devs on the dev ring of Windows and users of VirtualBox

My specs are

i7-4770k
16 GB RAM

Running VB 6.1.12r139181 (Qt5.6.2)

[Jacob Klein]

I can't afford any down time right now

Why in the world are you using a Dev Channel version of Windows, if you don't have a plan for when things don't work on it?

From my experience, this type of issue won't be investigated by Oracle until it happens on a Release Channel version of Windows.
And from my experience, if Microsoft is going to fix it, it will take them several Dev Channel builds to get info and get a fix. Weeks/Months.

I have my PCs setup to triple-boot between 1) Dev Channel, 2) Beta Channel, 3) Release Channel. Yes, that's 3 installs of Windows, on each PC. And, since this GSOD issue happened, I've switched to my Beta Channel partitions until it gets resolved by Oracle/Microsoft, even if that takes months.

Get yourself a plan!
Maybe now is a good time for you to backup your data, resize your partition, and set up a new Beta Channel install of windows, to dual boot.

[Ace of Tunes]

I can't afford any down time right now

Why in the world are you using a Dev Channel version of Windows, if you don't have a plan for when things don't work on it?

A year ago I activated it (and then forgot) because I was stuck in an update/rollback loop, and I decided if I jumped to a prerelease and then stopped it from installing them, that would be a good solution.... apparently I never put myself back into a less fast ring face_palm

From my experience, this type of issue won't be investigated by Oracle until it happens on a Release Channel version of Windows.
And from my experience, if Microsoft is going to fix it, it will take them several Dev Channel builds to get info and get a fix. Weeks/Months.

That makes a lot of sense

I have my PCs setup to triple-boot between 1) Dev Channel, 2) Beta Channel, 3) Release Channel. Yes, that's 3 installs of Windows, on each PC. And, since this GSOD issue happened, I've switched to my Beta Channel partitions until it gets resolved by Oracle/Microsoft, even if that takes months.

Wish I had the ssd/hdd capacity for something well thought out like that haha

Get yourself a plan!

I actually do have a plan, it just failed without me getting notifications, it has been fixed and I am monitoring for any new issues with my back ups

Maybe now is a good time for you to backup your data, resize your partition, and set up a new Beta Channel install of windows, to dual boot.

Unfortunately I don't have the space, and money, for this, but I do have image backups being properly taken once a day again

[Jacob Klein]

I'm glad to hear that you have a workaround. And I'm hopeful that Microsoft will fix this soon actually, since they've included it on their blogs as a "known issue", which is lucky for us and means that they'll either fix it or get Oracle to fix it. Patience will prevail, and workarounds will get us through

[Jacob Klein]

I believe Oracle has resolved this issue
... with their latest Test Build, from:
https://www.virtualbox.org/wiki/Testbuilds

Issue resolved on:
Windows 10 Build 20221
Oracle VirtualBox v6.1.15 Test Build 140463

[AndyMidd]

Confirm problem still exits:
Insider 20221 64bit, VB 6.1.12. AMD 16GB ram.
When will VB6.1.14 get released? Hoping....

[Jacob Klein]

AndyMidd:
Did you read my post right above yours?!?

6.1.14 was released already about 3 weeks ago, on 9/4/2020, but does NOT have the fix.
https://www.virtualbox.org/wiki/Downloads
... HOWEVER
As I said previously, the fix is in the latest 6.1.15 Test Build,
Oracle VirtualBox v6.1.15 Test Build 140463
https://www.virtualbox.org/wiki/Testbuilds

Can you please confirm the fix?

[pokemonlover1234]

Currently installing 20221, as well as the test build. Once complete I will edit with the results of the test.

EDIT:
Posted reply with results but as I said I would edit here, here goes nothing.

Latest test build succeeded on 20221

[AndyMidd]

Jacob,
That was a finger faster than brain moment. Whoops. And your post did not show up until I posted mine. Oh dear: I wasn't trying to be silly! Also as the KMODE issue wasn't fixed, I hadn't done a check for VB releases. My bad.

[Jacob Klein]

AndyMidd:
Okay. Are you able to confirm success with the Test Build?

[RyanMcGill]

Unfortunately, this 6.1.15-140463 test build continued to send me to a green screen of death (GSOD) on the current Win10 x64 Insiders build 20221.

Interestingly, a different error was shown!
UNEXPECTED_KERNEL_MODE_TRAP

I'm not quite sure what to make of this.
My host uses an Intel i5-6600, and my guest is based on Ubuntu 16.04 (I know, it's behind the times.) This information may be irrelevant, but I saw others were providing it.