VirtualBox

Opened 13 years ago

Closed 13 years ago

#8027 closed defect (fixed)

VB4.0.0 Win7x64 Host WinXPSP2x86 Guest Graphics Acceleration Crash

Reported by: alduck Owned by:
Component: 3D support Version: VirtualBox 4.0.0
Keywords: Cc:
Guest type: Windows Host type: Windows

Description

Clean Xp Guest Install in new Win7x64 installation.

Can install XP as guest, and install Guest Additions in Safe Mode. However, when rebooting and running in regular mode, VM crashes if both 3D and 2D acceleration are selected. If you select only one form of acceleration, the vm runs OK. If you select both, iut crashes when Windows initialises graphics.

Details: Host:

Windows 7 Ultimate 64-bit Intel i930 Asus P6VT-Deluxe Motherboard 12 GB RAM nVidia GeForce 9500GT, nVidia drivers 8.17.12.6099 VirtualBox 4.0.0r69151

Guest: 2 Processor 1024 MB Memory VT-X/AMD-V, Nested Paging, PAE/NX 128MB Video RAM Remote Desktop Disabled 15GB Dynamic Disk Audio Enabled Network Adapter 1: PCNetFast II (NAT)

Windows XPSP2 Clean Install Guest Additions installed in Safe Mode

Attached Logs:

VBox-2d.log 2d-Acceleration enabled, 3d disabled VBox-3d.log 2d-Acceleration disabled, 3d enabled VBox-2+3d.log Both 2-d and 3-d enabled VBox.log Neither enabled

Attachments (4)

VBox.log (71.2 KB ) - added by alduck 13 years ago.
VBox-2d.log (76.4 KB ) - added by alduck 13 years ago.
VBox-3d.log (76.0 KB ) - added by alduck 13 years ago.
VBox-2+3d.log (50.8 KB ) - added by alduck 13 years ago.

Download all attachments as: .zip

Change History (6)

by alduck, 13 years ago

Attachment: VBox.log added

by alduck, 13 years ago

Attachment: VBox-2d.log added

by alduck, 13 years ago

Attachment: VBox-3d.log added

by alduck, 13 years ago

Attachment: VBox-2+3d.log added

comment:1 by misha, 13 years ago

Unfortunately the log for the crashed session (VBox-2+3d.log) does not tell anything.
Would be nice to have a call stack for the crash. The easiest way to do it for Win7x64 is to have Debugging Tools For Windows installed on your host and have WinDbg configured as a default postmortem debugger (by running "WinDbg -I" as admin). You could also create a minidump for the crash as explained here.
Let me know if you have any issue with getting the crash call stack.

comment:2 by Frank Mehnert, 13 years ago

Resolution: fixed
Status: newclosed

No response, closing.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use