VirtualBox

Ticket #5963 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

Guest Additions Service Crash in Windows 7 64bit Guest => Page fusion -> fixed in SVN

Reported by: mvrazel Owned by: pentagonik
Priority: major Component: guest additions
Version: VirtualBox 3.2.0 Keywords: 64-bit
Cc: Guest type: Windows
Host type: Windows

Description

I'm responding to this posting in the forum --

 http://forums.virtualbox.org/viewtopic.php?f=2&t=26156

I can confirm this behavior as well. Every time Version 3.1.2 VBoxService.exe attempts to start (manual start, reboot, etc.), it crashes with the following being posted in the event log:

Date: 1/11/2010 Source: Application Error Time: 1:06:59 PM Category: (100) Type: Information Event ID: 1004 User: N/A Computer: MOSSAPP1

Reporting queued error: faulting application VBoxService.exe, version 3.1.2.0, faulting module VBoxService.exe, version 3.1.2.0, fault address 0x000000000000c53b.

For more information, see Help and Support Center at  http://go.microsoft.com/fwlink/events.asp.

I get this issue on both Windows Server 2003 R2-64 and Windows Server 2008 R2-64 guests. I'm running on a Windows 7-64 host. Version 3.1.0 Additions do seem to work OK, at least in my environment.

I've attached a log file.

Attachments

VBox.log Download (44.8 KB) - added by mvrazel 4 years ago.
Guest log file
Win2008R2-2010-05-27-09-14-09.log Download (71.3 KB) - added by gnordli 4 years ago.

Change History

Changed 4 years ago by mvrazel

Guest log file

comment:1 Changed 4 years ago by oetiker

I saw that behavior too on 2k3r2 64bit ... interestingly enough the beast did run when started on the commandline with -f and --disable-exec

cheers tobi

comment:2 Changed 4 years ago by pentagonik

  • Owner set to pentagonik
  • Status changed from new to assigned

Thanks for the report! I already found the error and will fix it, so a patch will be included in the next upcoming version of VBox + (in SVN soon).

comment:3 Changed 4 years ago by frank

  • Summary changed from Guest Additions Service Crash in Windows 7 64bit Guest to Guest Additions Service Crash in Windows 7 64bit Guest => Fixed in 3.1.4

comment:4 Changed 4 years ago by frank

  • Status changed from assigned to closed
  • Resolution set to fixed

comment:5 Changed 4 years ago by gnordli

  • Status changed from closed to reopened
  • Resolution fixed deleted

This may be a regression.

I am running Vbox 3.2 Host: Windows 7 (64bit) Guest: Windows Server 2008 R2 (64bit).

The error in the event log is:

Faulting application name: VBoxService.exe, version: 3.2.0.0, time stamp: 0x4bf2d752 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x000007ff756a1000 Faulting process id: 0x284 Faulting application start time: 0x01cafb7d6f81ecf0 Faulting application path: C:\Windows\system32\VBoxService.exe Faulting module path: unknown Report Id: eb7bec29-6770-11df-9f73-080027c47339

Changed 4 years ago by gnordli

comment:6 Changed 4 years ago by gnordli

This appears to be directly tied to Page Fusion.

If I disable Page Fusion on the VM, then it the service fault disappears.

If enable Page Fusion then the service faults.

comment:7 Changed 4 years ago by frank

  • Priority changed from minor to major
  • Version changed from VirtualBox 3.1.2 to VirtualBox 3.2.0
  • Summary changed from Guest Additions Service Crash in Windows 7 64bit Guest => Fixed in 3.1.4 to Guest Additions Service Crash in Windows 7 64bit Guest => Page fusion

Thank you for these findings.

comment:8 Changed 4 years ago by gnordli

Just to clarify, the guest is Windows Server 2008 R2 (64bit) The host is Windows 7 64bit

comment:9 Changed 4 years ago by sandervl73

  • Summary changed from Guest Additions Service Crash in Windows 7 64bit Guest => Page fusion to Guest Additions Service Crash in Windows 7 64bit Guest => Page fusion -> fixed in SVN

Please create a new ticket in the future as this one is unrelated. Anyway, fixed for the upcoming maintenance release.

comment:10 Changed 4 years ago by frank

  • Status changed from reopened to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use