Guest Bluescreen using shared folders in VirtualBox > 6.0.9 (#18766)

[socratis]

@fre4kyc0de, @Rockcop
I merged your threads with the one that's dealing with the issue. Please search for related threads next time...

[fre4kyc0de]

@socratis
I‘m sorry, forum search was unavailable when I created the topic and the first post of this one read more like a problem causing VBox to crash...

[Air Force One]

@socratis: I respond to your questions in the ticket. I noticed that the topic starter first just mentioned BSOD and only later described, that BSOD happens on simple access of the shared folder. This is exact my situation. I still think and see, that we have two slightly different situations here, both of them leading to the BSOD in the shared folder file or network system driver. One is BSOD on accessing the folder itself with KMODE type of exception and another one happens later when the folder is already opened and one access the executable itself. Then one have an IRQL kind of exception. So it probably also import to know, beside the other information you already collection for this case, which scenario do we have, first or the second one.

The other information I forgot to give: I didn’t map or mount the shared folder as any letter drive in the guest, through net use or whatever. I’m accessing it only through SMB path.

Somebody wrote here, that even the fresh installation of Windows 7 crashes, but only the x64 one. The Windows 7 x86 on the same host has no problems. So the bitnes is also important here.

I could test the importance of the read-only access in my case in the next days. The other idea, which I have: I could start the Sysinternals Process Monitor on host and take a look on what is used by VBox just before the crash. What do you think about this?

[samsungs]

I've set up a new Windows 10 guest, when opening a shared folder it crashes.
Checked other guests (Windows 10, Server 12, Server 16), no issues with opeing shared folders.

I had another issues with this new Windows 10 guest. When I installed Guest ASdditions, the guest restarted, and when it came back online, the mouse cursor had disappeared, so i installed Guest Additions again.

Host on 10.0.18362
Guest on 10.014393

VirtualBox 6.0.10 132072

[Dave B]

In case helpful, here's my findings...

- Issue
Windows guests instant crash (Win 7), freeze > crash (Win 10) upon opening a shared folder containing just a large .exe file, such as VirtualBox-6.0.10-132072-Win.exe
GNU/Linux guests shared folder works as expected.

- Host
Linux Mint 19.2 (beta) Cinnamon x64
16GB RAM
i7 CPU 4/4 C/T
NVIDIA GPU

- Guests
Kubuntu 19.10 (daily live) x64
Linux Mint 19.1 Cinnamon x64
Linux Mint 19.2 (beta) Cinnamon x64
Linux Mint 19.2 (beta) Xfce x64
Windows 7 (official ISO) + SP1 x64
Windows 10 1903 (official ISO) x64

- Testing methodology
Guests have 4GB RAM, 2 CPU cores. Only one guest run at a time.
All guests (except Linux Mint 19.1 Cinnamon) are fresh installations, tried two Windows 7 fresh installations.
Windows 7 guest, tried VBoxVGA, and VBoxSVGA, with/without acceleration, also (just in case) both display drivers.

- Test results

• VirtualBox 6.0.10 and Guest Additions 6.0.10, shared folder crashes/freezes Windows guests if folder contains a large .exe, such as VirtualBox-6.0.10-132072-Win.exe
• Purging VirtualBox 6.0.10 > installing VirtualBox 5.2.32 and Guest Additions 5.2.32, shared folder works without issue
• Purging VirtualBox 5.2.32 > installing VirtualBox 6.0.8 and Guest Additions 6.0.8, shared folder works without issue
• Purging VirtualBox 6.0.8 > installing VirtualBox 6.0.10 while keeping Guest Additions 6.0.8, shared folder works without issue
• Keeping VirtualBox 6.0.10 and reinstalling Guest Additions 6.0.10, shared folder again crashes/freezes the Windows guest if folder contains a large .exe

Before finding this thread, also performed tests with different files, and .exe files of varying sizes, finding... larger the .exe, more likely the crash, hence mentioning VirtualBox-6.0.10-132072-Win.exe which guarantees a crash/freeze by simply opening the shared folder containing the .exe.


Windows 7 crash

Windows 7 crash.png (40.61 KiB) Viewed 1626 times

[socratis]

@samsungs
I merged your thread with the one that's dealing with the issue. Please search for related threads next time...

[RegF]

Hello,
I down graded my virtual box to 5.2.32 and everything works fine.

[socratis]

@RegF

00:00:01.863186 SharedFolders host service: Adding host mapping
00:00:01.863197     Host path '/Users/reghu/Documents', map name 'Documents', writable, automount=false, automntpnt=, create_symlinks=false, missing=false
00:00:01.863400 SharedFolders host service: Adding host mapping
00:00:01.863408     Host path '/Users/reghu/Downloads', map name 'Downloads', writable, automount=false, automntpnt=, create_symlinks=false, missing=false
...
00:00:58.966457 GIM: HyperV: Guest indicates a fatal condition! P0=0xa P1=0x0 P2=0x2 P3=0x0 P4=0xfffff8053293db98
00:00:58.966784 GIMHv: BugCheck a {0, 2, 0, fffff8053293db98}
00:00:58.966786 IRQL_NOT_LESS_OR_EQUAL

I think that you might be seeing the effects of ticket #18766. Merging your posts with the prominent thread that deals with the issue.

[Friis]

Hello

I came by 2 bugs when upgrading to 6.0.10, worked fine in 6.0.8. I make a post for each bug, this is the 2nd:
This appears to be related to Guest Additions as my VMs that hasn't been upgraded doesn't crash.
Well it is quite simple, I attempt to go to path "\\Vboxsvr\c_drive\Work\" and it crashed.

navigating to "\\Vboxsvr\c_drive\Program Files\Oracle" was ok. But crashed entering VirtualBox folder.

[andyp73]

This looks like it is the already known issue with the guest additions for 6.0.10. There is further discussion in ticket #18766 and forum topic Guest Bluescreen using shared folders in VirtualBox > 6.0.9 (#18766).

-Andy.

[socratis]

This looks like ... forum topic Guest Bluescreen using shared folders in VirtualBox > 6.0.9 (#18766).

Merged...

[JustinH]

I'm also crashing.

Win10 v1709 Pro x64 host, Win-anything guests.

Something I noticed in the host's shared folder is the creation of "System Volume Information" folder, which is a system folder created by Win OS and is normally super-hidden. I don't know if VB has created this folder in the past and hid it, or if this is a new (unwanted) feature in 6.0.10.

[socratis]

Something I noticed in the host's shared folder is the creation of "System Volume Information" folder

Quick pointer, please do not reply here, we like to observe the "One issue, one thread" rule...

See the thread "Version 6 creating System Volume Information folder on desktop (#18189)".

[GunSmoker]

Same issue, upgraded virtualized Windows to 10.0.18362.239, and it started crashing when threre is .exe in shared folder. Subscribing to thread.

[Arathor]

Hello,

I just upgraded from stretch to buster. Under strech, virtualbox (4.3) was available in the backports. Since it was completely removed in buster, I added the oracle repositories and installed the virtualbox-6.0 package. All is fine with my windows 10 guest (in which I’ve installed the guest additions), except for the shared folder. When I try to access it inside the VM, 9 times out of 10 I briefly see a BSOD, then the VM reboot. I said 9 out of 10, because I’ve seeing it work normally a couple times, without doing anything special. But the bug is almost systematic. I’ve tried with and without the extension pack.

Is that a known issue?

Thanks for any help,
Arathor.