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

[scottgus1]

Folks here won't go to third party sites to get logs & screenshots. Please use the forum's Upload Attachment tab. This is available on your first post. Zip logs, and crop/resize PNG screenshots to fit under the 128kB forum limit.

For the shared folder issue, see: viewtopic.php?f=2&t=93359. Ongoing problem with 6.0.10. 6.0.8 still works.

The VboxVGA card will probably work better with Windows 7 for now. The newer video cards are supposed to be better, but are new, and need the bugs ironed out. Eventually VboxVGA is supposed to go away. See the manual, section 3.6.1, under "Graphics Controller".

[VM-F4n[2]]

That might help, seems that 6.0.8 is still OK. Start your guest again and uninstall the Guest Additions. Then shut down the guest from within the guest OS.

In the main Virtualbox window, uninstall the Extension Pack. ...

OffTopic but you don't need to uninstall Guest Additions in Guest-VM and you don't need to uninstall the Extension Pack on the Host!
I'm testet it many times before.
You can install a older version of VirtualBox and Extension Pack over a newer one, then install Guest Additions in Guest-VM.

[allisbs]

Every time I open up a window's explorer window and click on a shared network folder that is on my Mac, Windows freezes up and VB reboots windows. I am running the latest verison of VB and I have VB guest additions installed.

[dinosaur]

I have the same problem with Windows 7 Ultimate and Windows 10 VMs (64 bits for all).

I downgraded first to VirtualBox v6.0.8, not touching either the extension pack or the guest additions (both still v6.0.10's) and still got the same crashes.

Then I downgraded to the extension pack v6.0.8's, still to no avail.

Then I downgraded to v6.0.8's guest additions on all my VMs, and finally could browse my shared data folders without crashing.

Finally, I updated to VirtualBox v6.0.10 and extension pack v6.0.10, just keeping the v6.0.8 guest additions in my VMs, and things are still working fine.

Conclusion: the bug is Windows's guest additions v6.0.10.

[VM-F4n[2]]

Conclusion: the bug is Windows's guest additions v6.0.10.

That's not new (!) if you can read start-posting #1 and find the ticket-link- for you - Link.

[Real72]

I have the same error even my host is a Win10 OS.

When I start to open the Drive on the VM belonging to a Shared Folder the screen freezes and VB makes a reboot.
It seems this happen as soon as possible if there is a "larger" file (more 100MB) in the Shared Folder.
If there is only a small files (less 5MB) in the folder it seems to work.

Release of VB is 6.0.10 r132072 (Qt5.6.2) and latest guest additions installed.

Greetings

Andreas

01:14:41.674912 GIMHv: BugCheck 1e {ffffffffc0000005, fffff8002e849b20, 0, ffffffffffffffff}
01:14:41.674913 KMODE_EXCEPTION_NOT_HANDLED
01:14:41.674913 P1: ffffffffc0000005 - exception code - STATUS_ACCESS_VIOLATION
01:14:41.674913 P2: fffff8002e849b20 - EIP/RIP
01:14:41.674913 P3: 0000000000000000 - Xcpt param #0
01:14:41.674914 P4: ffffffffffffffff - Xcpt param #1
01:14:45.556671 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
01:14:48.379707 AHCI#0: Reset the HBA
01:14:48.379732 VD#0: Cancelling all active requests
01:14:48.380080 AHCI#0: Port 0 reset
01:14:48.381120 VD#0: Cancelling all active requests
01:15:01.771645 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0x1e P1=0xffffffffc0000005 P2=0xfffff8002e849b20 P3=0x0 P4=0xffffffffffffffff
01:15:01.771847 GIM: HyperV: Reset initiated through MSR
01:15:01.771924 Changing the VM state from 'RUNNING' to 'RESETTING'

[Tronmch2]

Host: Windows 10 1809
VB version: 6.0.10r132072
Guest: Windows 2012 server
Guest Extensions: Same as VB version

What I see is this:
Opening a shared folder containing a large number of files in Windows Explorer will cause a BSOD.

Logs and VM kernel minidumps attached.

[fre4kyc0de]

From what I see, the crashes only occure on 64 bit guests, while 32 bit guests don't have problems...

[fre4kyc0de]

I did some testing and failed to create a usuable ProcMon log. I've got two logs, but none of them can be viewed after the machine crashed.

Info: This time an Intel Core i7 6700, 16GB RAM (guest has 4GB), read-only network drives (K: == K: (r); L: == L: (r); M: == K:\tmp (rw)), all auto-mounted; Host-OS: Windows 10 1903 x64, Guest-OS: Windows 7 x64 (both fully updated); all VBox-related components are 6.0.10
I tried some different Host and Guest combos with the following results: I wasn't able to reproduce the crash on x86 Guests, while Windows 7 x64 crashed on all of the hosts (3) I tried. On one host the guest Windows 10 1903 x64 didn't crash, while it crashed on another one (still didn't figure out why). As I need my VBox fully working on two of the three machines, I decided to downgrade VBox to 5.2.32, so I can do tests on just one machine starting now.

Using KD/WinDbg I was able to get this stack trace, when the crash happens:
ntoskrnl.exe 6.1.7601.24499

Code: Select all   Expand viewCollapse view

nt!RtlpBreakWithStatusInstruction
nt!KiBugCheckDebugBreak+0x12
nt!KeBugCheck2+0x722
nt!KeBugCheckEx+0x104
nt!KiBugCheckDispatch+0x69
nt!KiSystemServiceExit+0x299
0x77098c92
0x35cf880

[Air Force One]

Just tested with fresh guest additions, version 6.0.11-132500. My issue (0x1e (KMODE_EXCEPTION_NOT_HANDLED) BSOD already on access of the shared folder) is gone, on both 6.0.11-132665 and 5.2.33-132658. Thanks to everybody who helped to get this fixed.

[wye]

How did you get your fresh Guest Additions? I tried to check for updates and I'm told I'm already up to date.
I'm running VirtualBox-6.0.10-132072-Win. Host is 64-bit Windows 7 pro (16GB). Guest is 64-bit Windows 10 Pro.
Two different Windows 10 builds: (1903) 18362.267 and (1903) 18956.1000.
Same results.

[scottgus1]

Go to https://www.virtualbox.org/wiki/Testbuilds. Doenload the latest version. Guest Additions are bundled with the test build as an ISO.

Probably best to uninstall Virtualbox (your guests will remain ready to use after upgrading). Reboot your PC, then install the test build. On a Windows host, right-click the Virtualbox test-build icon and choose Run As Administrator (this is essential on a Windows host, even if you already have admin privileges).

Keep the test build installer. If by chance your MSI installation database goes south (and it does at times) while the test build is installed you will need the installer to uninstall the test build. The developers do not save test builds after the next even-number build comes out, so you won't be able to download it again shortly.

[wye]

Thanks, I'll give it a shot!

[scottgus1]

One other thing, there will be a matching test build Extension Pack, too. The version numbers must match.

[wye]

One other thing, there will be a matching test build Extension Pack, too. The version numbers must match.

OK, I missed that. BTW, test build didn't work for me but again, I missed the Extension Pack.
And I haven't been able to find a test build Extension Pack as a separate download.
I've just re-installed 6.0.11-132665 but I can't find a matching Extension Pack.


This is the behavior I see when it hangs.
I get the BSOD when I go into my read/write automount Shared Folder which starts off with a list of nested folders.
I can open the 14th folder and then back out with no problems.
When I open the 15th folder and then try to back out, system hangs and eventually BSODs.