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

[socratis]

@VirtualBSB
I merged your thread with the one that is more focused. Please read it from the beginning...

[RegF]

Hello,
Thank you. I will try to downgrade. My Virtual Box just crashed when I tried to access the folders mounted from my MacOSX. I think this is part of the problem. I have attached the log files.

Thanks and regards.

[TGVoid]

After I upgraded the guest additions software to 6.0.10 (after updating VirtualBox), having a automount shared folder enabled makes the guest crash after a log in. I tried reinstalling the guest additions software multiple times to no available. Are there any other solutions?

Edit:
Both my guest and host are running Windows 10 1903. I upgraded my guest from 1809 to 1903 to attempt to fix the problem.

[andyp73]

Can you temporarily remove this shared folder from the guest and repeat the same process with a new VirtualBox shared folder created to an empty directory on the host.

-Andy.

[socratis]

@TGVoid
I merged your thread with an existing one that's dealing with the same issue. Please read it from the beginning...

[Air Force One]

I opened a different ticket (#18704) with a different cause (selecting the folder with the file and not the file itself) and different BSOD code (0x1e (KMODE_EXCEPTION_NOT_HANDLED) and not the 0x04 IRQL_GT_ZERO_AT_SYSTEM_SERVICE). The rest is the same in my case: the guest video resolution was reduced and the one just see the BSOD and restart of the guest. I put my information about the host and the guest here and hope that this would help somebody to find the issue.

• Host: Windows 10 x64 1809 July 2019 Update (17763.615).
• Guest: Windows 10 x64 1809 July 2019 Update (17763.615).
• Share: Read-Write, NOT auto mounted.
• Result: CRASH

• Host: Windows 8.1 x64 July 2019 Update.
• Guest: Windows 7 SP1, build 7601, July 2019 Update, 32-bit.
• Share: Read-Write, NOT auto mounted.
• Result: NO CRASH

[socratis]

@Air Force One
I don't know if it's the exact same line or not, I try to see it not at the minute detail, more of an overview, read the title of the thread, does it match what you observe or not? The details (once gathered) will help the developers. What *I* see is that a lot of people are reporting crashes when shared folders are involved. Now, we have to find what's common...

@ALL
Can we please have some more detailed reports, just like the one from "Air Force One"? TIA...

[TGVoid]

Host: Windows 10 Pro 1903 build 18362.239
Guest: Windows 10 Pro 1903 build 18362.239
Share: R/W
The guest crashes after login with automount on but doesn't crash with automount off. Accessing the share while automount is off works, but mapping the drive in Windows manually and rebooting results in a crash after login. The crashing also occurred before I updated my guest from 1809 to 1903, but didn't occur before I updated the guest additions software from 6.0.4 to 6.0.10.

[VM-F4n[2]]

On VirtualBox 6.0.10:

Host: Windows 7 Build 7601 64-Bit
Guest: Windows 7 Build 7601 64-Bit
Share-Type: Full writeable folder on usb-drive, Letter manually assigned with "net use"
Result: Crash in BlueScreen by opening drive in explorer The blue screen only appears when an executable (.exe) is on a shared drive

Host: Windows 7 Build 7601 64-Bit
Guest: Windows 7 Build 7601 64-Bit
Share-Type: readable folder on usb-drive, no Letter manually assigned with "net use"
Result: No crash by opening drive (\\vboxsvr\...) in explorer The blue screen only appears when an executable (.exe) is on a shared drive

You can find my 3 minidumps here:
https://www50.zippyshare.com/v/Ud1y1pfd/file.html

Edit:
Edit in blue above!

[valerius]

I have no blue screen. It freezes, and, after some seconds, reboots.
I have Win 10 (x86_64) guest, Linux (x86_64, Debian 9) host. VBox version 6.0.10r132072 (official
version from Oracle's site), I use the ISO image downloaded from Microsoft site:
Win10_1903_V1_Russian_x64.iso. Installed version 6.0.10 additions. After I access a shared folder,
it shows directory listing, and then shortly freezes and reboots. I see no BSOD (though, win10
may be configured to reboot after a trap).

The same symptoms if I:
1) Attach a shared folder automounted, read-write, access a drive letter
2) Attach a shared folder, without automounting, read-only, access an UNC name: \\vboxsvr\download,
from a Network Neighbourhood folder.

Shared folder is a subdirectory on a JFS-formatted volume.

I uploaded a VBox log here. People above uploaded some minidumps. Do I need to upload these?
Where they are located in windows NT?

[socratis]

I have no blue screen. It freezes, and, after some seconds, reboots.

Actually, you are getting a BSOD:

00:02:05.965236 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffffc0000005 P2=0xfffff8067b43cd00 P3=0x0 P4=0xffffffffffffffff
00:02:05.965317 GIMHv: BugCheck 1e {ffffffffc0000005, fffff8067b43cd00, 0, ffffffffffffffff}
00:02:05.965318 KMODE_EXCEPTION_NOT_HANDLED

People above uploaded some minidumps. Do I need to upload these?

Not yet, let it be Monday and the developers will tell you what they want or not, chances are that they might need them if they can't reproduce the problem locally...

[bvhoesel]

Experiencing the same issue with VBox 6.0.10 for both host and guest additions and vboxsrv share read/write
Used hosts are 64 bit Linux Mint Mate 19.1 (amd and intel). Up to date on updates with kernel 4.15.0.54.
With Guests both Windows 7 and 10 (1903). At least Win 10 is up to date!

The weird thing is that it is not happening with all exe files. For example the latest rufus 3.6 installation exe from https://rufus.ie/ does not expose the issue. But a system font change utility advchange.exe from https://www.wintools.info/index.php/adv ... nt-changer does expose the issue.
In my example as soon as the advchange.exe is in a vboxsrv shared directory the Windows 10 machine hangs on accessing the directory and reboots after a few seconds. Windows 7 gives a BSOD first. At the moment the BSOD disappears to fast to see the error. But I assume it is the same as mentioned earlier.

For me a working r/w configuration is alse vbox 6.0.10 with guest additions 6.0.8. For a r/o share 6.0.10 guest additions do work.

After experiencing a lot with different versions for vbox and additions I noticed that is did matter whether or not I rebooted the host machine. For example after testing the r/o situation and then switching to r/w to expose the problem and next switching back to r/o the issue stil exists. Tried to restart several vbox services but could not replicate a clean reboot.

Similar when down grading the guest additions from 6.0.10 to 6.0.8, again the issue was only solved after a reboot of the host.

The log snippet below from the last try where the issue was reproduced:

Code: Select all   Expand viewCollapse view

00:00:39.624016 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:51.684516 VMMDev: Guest Log: VBOXNP: DLL loaded.
00:01:36.000458 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffffc0000005 P2=0xfffff80626049b20 P3=0x0 P4=0xffffffffffffffff
00:01:36.000549 GIMHv: BugCheck 1e {ffffffffc0000005, fffff80626049b20, 0, ffffffffffffffff}
00:01:36.000550 KMODE_EXCEPTION_NOT_HANDLED
00:01:36.000550 P1: ffffffffc0000005 - exception code - STATUS_ACCESS_VIOLATION
00:01:36.000550 P2: fffff80626049b20 - EIP/RIP
00:01:36.000550 P3: 0000000000000000 - Xcpt param #0
00:01:36.000550 P4: ffffffffffffffff - Xcpt param #1
00:01:38.700119 AHCI#0: Reset the HBA
00:01:38.700146 VD#0: Cancelling all active requests
00:01:38.700655 AHCI#0: Port 0 reset
00:01:38.701710 VD#0: Cancelling all active requests
00:01:39.903206 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:01:49.172459 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0x1e P1=0xffffffffc0000005 P2=0xfffff80626049b20 P3=0x0 P4=0xffffffffffffffff
00:01:49.172635 GIM: HyperV: Reset initiated through MSR
00:01:49.172670 Changing the VM state from 'RUNNING' to 'RESETTING'
00:01:49.175454 GIM: HyperV: Resetting MMIO2 regions and MSRs
00:01:49.175672 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:01:49.175985 Stopping the host clipboard service


I was watching the log with tail -f so I can connect actions to the time-stamps.
At 00:00:51.684516 I was logged on and started browsed some directories.
On 00:01:36.000458 I clicked on the directory containing the advchange.exe file.

[fre4kyc0de]

Hello forums,

I've got a problem with VBox 6.0.10 running with the following config:
Host: Windows 7 x64
Guest: Windows 7 x64
CPU: AMD FX-6300
RAM: 16GB (Host), 6GB (Guest)
GPU: VBoxVGA
Storage: 50GB virtual HDD (pre-allocated)
Audio: default config
USB: up to USB 2.0
Shared folders: "C:\" and "K:\" (both read-only)
Guest additions: 6.0.10

When trying to access a folder conainting the attached file [a program for running commands in the context of TrustedInstaller] on one of the shared folders (accessed using networtk drive and using "\\vboxsrv") the machine BSODs with IRQL_GT_ZERO_AT_SYSTEM_SERVICE (0x0000004A). Parameters were (I just screenshoted one of them): 0x0000000077319D2A, 0x0000000000000002, 0x0000000000000000, 0xFFFFF880046EEB60).
It does not depend on the file path on the host, I also tried simple paths such as "C:\tmp".
As the host isn't connected to any network, there is no AV software running neither on host nor inside the VM. Windows Defender has been disabled by policy.

I will set up a second VM and try to reproduce the issue there, as I cannot provide memory dumps of this VM as it contains sensitive data.

I hope, I provided enough information for you to help finding the issue. If you need more info, please tell me.

[fre4kyc0de]

I can confirm, this is happening in a fresh Windows 7 x64 VM with just Guest additions installed.
It does not happen with a virtual Windows 7 x86.
(I tried both: a fully slipstreamed ISO and an original MS one (Windows 7 SP with Setup-Fix))

[Rockcop]

Installed Virtualbox 6.0.10 and getting a blue screen when trying to access a shared folder on the host machine from Windows 7 64bit Enterprise guest. Host machine is Windows 10 64bit with feature update 1903. In addition guest machine window resizing is hinky. This happens on all my Windows 7 guests. I have rolled back to Virtualbox 6.0.8 and everything is fine. This is just a heads up.