BSOD accessing \\VboxSvr. Win10 + Win10

[hexaae]

VBox 6.0.12 + Extension Pack for 6.0.12 + Guest Additions for 6.0.12
Host: Win 10 Pro 1903
Guest: Win 10 Pro 1903

BSOD opening from Explorer "\\VboxSvr\Downloads" pointing to host's Downloads and scrolling file list shown by details.
BSOD with error code information (for example: 0x0000001E, KMODE_EXCEPTION_NOT_HANDLED).
Uninstalling GuestAdditions to access host's dir of course solves the issue.

Laptop ASUS GL703GS (BIOS 310)
CPU i7-8750H (iGPU disabled)
GTX 1070 8GB (vbios 86.04.7c.00.24, Samsung VRAM)
Windows 10 Pro 1903
Desktop res: 1080p (1920x1080)
Screen: 144Hz + g-sync AUO B173HAN03.2 [AUO329D]
Audio: Realtek HD Audio (ALC295 chipset)
Hard disks: NVMe Samsung, SSD Crucial
USB Blu-Ray 4K drive: Verbatim 43888 (Pioneer BDR-UD04)

[socratis]

<Image uuid="{4e234217-c872-4b66-9781-513db13a1cc5}" location="xxxx/VBoxGuestAdditions.iso"/>
<Image uuid="{7fa6a43d-8437-46ac-a898-ac6dcd6520eb}" location="xxxx/Downloads/VBoxGuestAdditions_6.0.10.iso"/>
<Image uuid="{000730ec-806b-45c3-a892-8dbec22449b6}" location="xxxx/addons/VBoxGuestAdditions_6.0.10.iso"/>
<Image uuid="{37636250-2688-4844-93d0-d7c249da46d5}" location="xxxx/addons/VBoxGuestAdditions_6.0.12.iso"/>

It's a ReallyBadIdea™ to obfuscate the information. No one in the history of computers has been hacked based on their username alone. Security is a GoodThing™. Paranoia is a BadThing™.

It's a WorseIdea™ to download the Guest Additions (GAs) as a standalone ISO, it's a recipe for a disaster. Always use the GAs that come already bundled with your VirtualBox installation. See ch. 4.1. Introduction to Guest Additions:

The Oracle VM VirtualBox Guest Additions for all supported guest operating systems are provided as a single CD-ROM image file which is called VBoxGuestAdditions.iso. This image file is located in the installation directory of Oracle VM VirtualBox. To install the Guest Additions for a particular VM, you mount this ISO file in your VM as a virtual CD-ROM and install from there.
...
In the Devices menu in the virtual machine's menu bar, Oracle VM VirtualBox has a menu item Insert Guest Additions CD Image, which mounts the Guest Additions ISO file inside your virtual machine.

While the .vbox file is a useful diagnostic tool, we need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe or recreate the problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response.

[hexaae]

Attached the log.

This is in detail what happens:
- boot into Win 10 Pro 1903 Guest (GA already installed and shared drive visible from Explorer)
- open shared drive (pointing to my host Download dir)
- while viewing contents (details mode) when (and only if) I move down the scrollbar suddenly freezes the whole VM, also mouse pointer. In a few seconds it automatically reboots (I see VBox boot screen). Under Event Viewer of Guest machine I can see the log with the BSOD.

[hexaae]

No reply (just because I obfuscated irrelevant file paths)?
Here is again my FULL .vbox file.

Please help, in current state Guest Additions shared folders are unusable!

[fth0]

Your VBox log file starts with GA 6.0.10 (00:00:27.486703) and contains your update to GA 6.0.12 including the typical reboot (00:02:21.890370), and then the crash (00:03:07.586610). In a discussion in another thread someone noticed that a reboot had not been sufficient (while downgrading to GA 6.0.8 ) to eliminate the problem, but it was necessary to completely shut down the VM. In consequence, I suggest the following procedure: Start your VM, update the GA, reboot the VM, shutdown the VM. Then start the VM anew, verify that GA 6.0.12 is running, reproduce the crash, shutdown the VM, and post the corresponding VBox log file from this last run.

If the crash still occurs: The crash possibly depends on the files contained in the shared folder (Windows does a lot in the background while just displaying the folder contents). You could narrow this down by creating subfolders in your shared folder on your host, moving all files to the subfolders, then starting the guest VM, selectively accessing the folders, beginning with the top folder only containing subfolders, and thereby reproducing the crash. Note that the file type is not alone decisive (there have been executable files producing and not producing the crash).

[hexaae]

Thanks for your reply, and heads up on folder and subfolder scanning...
Indeed it looks like a Windows Defender (Guest) issue (!!?): I added to the exclusion paths R:\ (host shared Download dir into the guest emu) and… no more freeze+BSOD just srcolling R:\ contents!
Will re-open the case if it's just luck because by chance I deleted some problematic files from Download in the meanwhile…

P.S.
If you're still interested in the logs and explore the technical reason behind VM's BSOD I can try to reproduce the issue anyway… just tell me.

[fth0]

If you're still interested in the logs and explore the technical reason behind VM's BSOD I can try to reproduce the issue anyway… just tell me.

IMHO it is only of interest if you still have the problem in a VM started from the power-off state with GA 6.0.12 already installed. A lot of people had similar problems with GA 6.0.10, and the problems were solved with GA 6.0.12 for the majority of them. Only very few people (like you) claimed to still have the problem.

[socratis]

No reply (just because I obfuscated irrelevant file paths)?

Not really, we help everyone, even if they're making our help more difficult, most of the times by inadvertently increasing their security level to a DEFCON 2...

Personally, I've had a boatload on my to-do list, if it's not something simple it get replied even a week later, it's not a personal thing. When the time comes and I have free time to reply, some posts have already been answered and get back on the to-check bag, some don't make sense to reply because they're too old. If the OP cares enough, they'll bump the thread.

00:03:07.586610 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffffc0000005 P2=0xfffff80431c4ae90 P3=0x0 P4=0xffffffffffffffff
00:03:07.586666 GIMHv: BugCheck 1e {ffffffffc0000005, fffff80431c4ae90, 0, ffffffffffffffff}
00:03:07.586667 KMODE_EXCEPTION_NOT_HANDLED

That's the classic sign of the Shared Folder bug (#18766) that was introduced with 6.0.10; a 0x0000001E BSOD on the guest.

Indeed it looks like a Windows Defender (Guest) issue (!!?)

Most probably not. It's got to do more with the Win10 version (I don't get it on 1607) and the GAs (≥6.0.12).

Only very few people (like you) claimed to still have the problem.

And there was a report that it was fixed with the latest 6.0.13 builds:

Version '12' had still failed but that version '13' shares the files without issue.

Could be that they followed proper procedures though, just like 'hexaae' here...

[socratis]

Since I replied, another two more users in the ticket reported a failure with 6.0.12 and a success with 6.0.13.

I'll start suggesting the test builds from now on, just to play it safe...

[hexaae]

Just for the record: I could reproduce the issue (guest Win 10 1903 + GA 6.0.12) also after VM full shutdown and restarting the VM.
Will install ASAP .13

[socratis]

Will install ASAP .13

Will install ASAP .13 and I'll let you know how it went...

You forgot the last part... right?