VirtualBox-6.0.10-132072-Win BSOD

[jcstaquet]

Steps to reproduce: -create or use an existing Windows7 VM -download VNC viewer standalone -run it inside the VM => BSOD

No BSOD with VirtualBox-5.2.30-130521

[Socratis]

1. It's usually better and faster, if issues get first addressed in the ​VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

Plus a discussion and analysis on the bug tracker is going to help me, you, and potentially a future drive-by user or two. Not so in the forums, many more tend to benefit...

Please, open a new thread in the ​VirtualBox on Windows Hosts section of the forums. Please be sure to mention that you came from the bug tracker and include the ticket number.

2. You're really short on the details. Which VNC viewer? Be specific, provide the link. Do you run it locally or from a shared folder? I tested it with "https://www.realvnc.com/download/file/viewer.files/VNC-Viewer-6.19.325-Windows-32bit.exe" and couldn't reproduce it, maybe the steps are not exact?

3. You were supposed to follow these steps when you filed the bug, and provide a VBox.log:

   Attach a (full) log file ("Machine" menu/"Show Log" in the main VirtualBox Manager window) straight away to save time for you and for us. The log file contains a lot of useful information about both the host and the guest systems as well as information about what happened during a particular machine run. Please do not cut and paste it.