VirtualBox

Opened 14 years ago

Closed 13 years ago

#6153 closed defect (fixed)

Vista guest, DWM crashes in 3.1.2

Reported by: Ken Hagan Owned by:
Component: other Version: VirtualBox 3.1.2
Keywords: Cc:
Guest type: Windows Host type: Windows

Description

Since upgrading from 3.1.0 to 3.1.2, both my Windows Vista VMs have been broken. They boot up fine, but when you log in (any user) they just hang. The host CPU sticks at 50% usage (it's a 2 core chip).

The workaround was to boot into safe mode and disable the Desktop Window Manager service, then reboot the guest.

Having done that, I can log in and discover from the event log that DWM.EXE (6.0.6002.18005) has crashed in VBoxOGLpackspu.dll (3.1.2.0) at offset 0x00011102 with exception code 0xC0000005.

Both the host (Windows Server 2003) and the guest are fully patched.

Attachments (1)

VBox.log.3 (60.6 KB ) - added by Ken Hagan 14 years ago.

Download all attachments as: .zip

Change History (5)

by Ken Hagan, 14 years ago

Attachment: VBox.log.3 added

comment:1 by Sander van Leeuwen, 14 years ago

Try to go back to one CPU in the guest or try out the 3.1.4 beta announced on the forum. If neither helps, then disable 3d support for the VM.

comment:2 by Ken Hagan, 14 years ago

OK, I've run through the eight permutations of: "1 or 2 CPUs", "3D support or not", "version 3.1.2 or 3.1.4beta (with guest additions)". The mis-behaviour remains in every case. (One small difference is that when 3D support is disabled but 2 CPUs are present, the CPU usage sticks at 100%, not 50%.)

Looking through the event log, I actually find just two crash reports. Both blame VBoxOGLpackspu.dll offset 0x00011102, but one happened yesterday in DWM.EXE and is version 3.1.2.0 of the DLL whereas the other happened in December in TaskEng.exe and relates to 3.1.0.0 of the DLL. It may be a bit of a red herring, since the dominant symptom is a CPU in wheelspin, rather than crashing to a halt!

comment:3 by Ken Hagan, 13 years ago

In case anyone bumps into this bug on a search, I should point out that subsequent releases (3.2.x, certainly for larger values of x) have not exhibited this problem. Whether it was fixed or was simply pilot error to begin with, I don't know.

comment:4 by Frank Mehnert, 13 years ago

Resolution: fixed
Status: newclosed

So let's close this ticket as fixed.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use