VirtualBox

Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#7577 closed defect (fixed)

GraphOn Go-Global on X64 virtual machine causes BSOD on real machine -> fixed in SVN

Reported by: Piotr Zborowski Owned by:
Component: other Version: VirtualBox 3.2.10
Keywords: Cc:
Guest type: Windows Host type: other

Description

Host: Windows XP Pro SP3 X86. Guest: Windows Server 2008 SP2 X64. BSOD occurs on host after installing GraphOn Go-Global 4.0.0.8304 (terminal services/application publishing software) and rebooting Win 2008).

Attachments (4)

VBox hardware accel Full.log (41.1 KB ) - added by Piotr Zborowski 14 years ago.
Display Settings -> Advanced Settings -> Troubleshoot -> Hardware acceleration set to Full
VBox hardware accel None.log (47.5 KB ) - added by Piotr Zborowski 14 years ago.
Display Settings -> Advanced Settings -> Troubleshoot -> Hardware acceleration set to None
Mini101510-01 hardware accel Full.dmp (88.0 KB ) - added by Piotr Zborowski 14 years ago.
Mini101510-02 hardware accel None.dmp (88.0 KB ) - added by Piotr Zborowski 14 years ago.

Download all attachments as: .zip

Change History (16)

comment:1 by Sander van Leeuwen, 14 years ago

This information is not useful without a VBox.log of this session (no, you don't need to wait for your system to crash). A wild guess based on zero information is: turn off 2d & 3d in the guest settings.

by Piotr Zborowski, 14 years ago

Display Settings -> Advanced Settings -> Troubleshoot -> Hardware acceleration set to Full

by Piotr Zborowski, 14 years ago

Display Settings -> Advanced Settings -> Troubleshoot -> Hardware acceleration set to None

comment:2 by Piotr Zborowski, 14 years ago

2d and 3d acceleration is disabled in the guest settings. I've also changed at guest this: Display Settings -> Advanced Settings -> Troubleshoot -> Hardware acceleration from Full to None - it didn't help (BSOD on host again), but log file seems to be longer now. I've attached 2 log files - first with hardware acceleration set to Full on guest system and second with hardware accelearation set to None.

in reply to:  1 comment:3 by Piotr Zborowski, 14 years ago

More details from BSOD: STOP: 0x0000008e (0x80000003,0x9bec9b28,0x9c3328d4,0x00000000) VMMR0.r0

comment:4 by Sander van Leeuwen, 14 years ago

Could you attach the minidump of the BSOD here?

by Piotr Zborowski, 14 years ago

by Piotr Zborowski, 14 years ago

comment:5 by Piotr Zborowski, 14 years ago

Go-Global is application publishing and virtualization solution, something like Microsoft Terminal Services, but it uses their own protocol. Go-Global installs Go-Global Display Driver - maybe this driver causes this problem.

comment:6 by Sander van Leeuwen, 14 years ago

Ok, found the problem. Basically related to running 64-bit guests on 32-bit hosts. You'll have to wait until the next maintenance release, but I can send you a test build if you want.

comment:7 by Sander van Leeuwen, 14 years ago

Summary: GraphOn Go-Global on X64 virtual machine causes BSOD on real machineGraphOn Go-Global on X64 virtual machine causes BSOD on real machine -> fixed in SVN

in reply to:  6 comment:8 by Piotr Zborowski, 14 years ago

If that's not a problem, then please send me a test build. Thanks.

comment:9 by Sander van Leeuwen, 14 years ago

You can download a test build here.

comment:10 by Piotr Zborowski, 14 years ago

I've installed test build and there is no BSOD now, but there is another problem - guest system can't start successfully. It displays "Microsoft Corporation" logo while booting and then it freezes with black screen. Should I create a new ticket for this or use this one?

comment:11 by Frank Mehnert, 14 years ago

Resolution: fixed
Status: newclosed

Yes, please create a new ticket if the same still happens with the final 3.2.12 release (which was released just now).

comment:12 by Piotr Zborowski, 14 years ago

I've already created a new ticket here: #7612

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette