BSOD on Windows 7 Pro and Windows 10 Pro guests with VBox 6.0.10

Discussions related to using VirtualBox on Windows hosts.
Post Reply
jc508
Posts: 3
Joined: 7. Aug 2019, 09:22

BSOD on Windows 7 Pro and Windows 10 Pro guests with VBox 6.0.10

Post by jc508 »

Hi
I have an issue with my guest windows systems crashing.
The two I have tried both get BSOD crashes after the following steps
* Windows Explorer
* select a drive shared with the Host
* sort the file set on type or size (anything other than what it is currently sorted on)
Note these guests are Win7Pro and Win10Pro

History.
My Host recently updated to Win10 1903 which caused issued which were fixed with the following commands from topic 87327

Code: Select all

bcdedit /set hypervisorlaunchtype off
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V
followed by a re-boot

Since that time I have upgraded Virtual box to 6.0.10 r132072 and the appropriate guest additions.
So this is probably the first time I have done this simple sequence of steps with this build.
Any ideas ?

Thanks
JC
Attachments
VirtualBox_error_logs.zip
Two machine logs
(61.43 KiB) Downloaded 12 times
andyp73
Volunteer
Posts: 1631
Joined: 25. May 2010, 23:48
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation

Re: BSOD on Windows 7 Pro and Windows 10 Pro guests with VBox 6.0.10

Post by andyp73 »

This is probably the known issue with the 6.0.10 Guest Additions. More details can be found in Guest Bluescreen using shared folders in VirtualBox > 6.0.9 (#18766).

-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
jc508
Posts: 3
Joined: 7. Aug 2019, 09:22

Re: BSOD on Windows 7 Pro and Windows 10 Pro guests with VBox 6.0.10

Post by jc508 »

Thanks Andy,
It does seem to match the other issues (dont know why my search failed to see these)
anyway dropping back to 6.0.8 for a while fixes my problem
Post Reply