VirtualBox

Opened 8 years ago

Closed 8 years ago

#14928 closed defect (fixed)

Windows 7 x64 Virtualbox crash with latest test builds

Reported by: frg Owned by:
Component: other Version: VirtualBox 5.0.10
Keywords: Cc:
Guest type: Windows Host type: Windows

Description

The latest test builds have a tendency to suddenly crash the guest using Windows 7 x64 as a host.

I experienced the crash with the following revisions:

5.0.11 revision 104592 5.0.11 revision 104602 5.0.51 revision 104644

Logs are from the 5.0.51 build but it was more or less the same with the official test builds. Tried Windows 7 x64 and Windows 10 x86 and x64 guests. Windows 10 wouldn't even start correctly most of the time. Same problem on an older laptop using a Core2Duo.

5.0.11 revisions 104456 works like a champ.

Attachments (2)

crashlogs.zip (24.7 KB ) - added by frg 8 years ago.
crash104675.zip (25.3 KB ) - added by frg 8 years ago.

Download all attachments as: .zip

Change History (15)

by frg, 8 years ago

Attachment: crashlogs.zip added

comment:1 by johnlee, 8 years ago

Sounds like same (or similar) problem I reported in 'discuss the 5.0.10 release' forum, with latest test builds on win 7 64. 4456 is fine for me too.

fyi, Mon 1230 just tried latest test build 4675 - ok so far, my vms start ok. However cannot see in vm manager help contents any changes that seem to relate to this fault! Maybe frg can try this build? j

Last edited 8 years ago by johnlee (previous) (diff)

comment:2 by frg, 8 years ago

A little early but 104675 seems to have fixed it on both the laptop and desktop. Just close the Ticket. I will reopen it if it's not fixed.

FRG

comment:3 by Frank Mehnert, 8 years ago

Resolution: fixed
Status: newclosed

Thanks.

comment:4 by johnlee, 8 years ago

Looks as if it is fixed, but it'd be good to make the changes between builds clear - this would encourage people to provide feedback. Why no mention of this problem and its fix in the 'help'?

comment:5 by frg, 8 years ago

Resolution: fixed
Status: closedreopened

Spoke too soon 104675 did go south also yesterday evening after 1 1/2h of heavy use. Back to 104456 for now.

by frg, 8 years ago

Attachment: crash104675.zip added

comment:6 by sunlover, 8 years ago

Without a crash dump it is difficult to fix this. See Windows section of https://www.virtualbox.org/wiki/Core_dump for details. Thanks.

comment:7 by Mihai Hanor, 8 years ago

WER is not able to create a memory dump because it's not able to attach to the hardened process (the 2nd child process).

comment:8 by Frank Mehnert, 8 years ago

IIRC there are 3 processes, attaching to one process is possible. Still reproducible with 5.0.12?

comment:9 by Mihai Hanor, 8 years ago

If the hardened process crashes, WER attempts to attach to it and fails. Attaching to another process makes sense?

comment:10 by frg, 8 years ago

I just installed 5.0.12. Should know over the weekend. 104721 might have fixed it already. Was stable on the laptop the last two days.

comment:11 by johnlee, 8 years ago

I'm running 5.0.12 - think it is ok. What was the problem? j

comment:12 by frg, 8 years ago

5.0.12 running stable for 2 days now. I think you can close the ticket again. This time hopefully for good.

Thanks FRG

comment:13 by Frank Mehnert, 8 years ago

Resolution: fixed
Status: reopenedclosed

Thanks!

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use