VirtualBox

Ticket #14383 (closed defect: fixed)

Opened 7 years ago

Last modified 6 years ago

Windows 10 Host hang on VM-start and freezes PC.

Reported by: PanzerTeo Owned by:
Component: other Version: VirtualBox 5.0.0
Keywords: Cc:
Guest type: other Host type: Windows

Description

After the host machine Windows 10 upgrade I uninstalled VBox 4.3 and then reinstalled VBox 5.0 after a PC restart. When I installed VBox 5.0. I disabled the Windows driver signing check.

I do the following:

  1. I open Virtualbox VM Manager
  2. Start a virtual machine (doesn't matter if guest is 32 bit or 64 bit)
  3. System + Mouse + Sound laggs
  4. after a few seconds (the first time) the virtual machine exits itself with an vbox internal error message (at this time it continues lagging)
  5. then I click ok, the machine ends only after that everything is ok
  6. if I start a machine a second time and do not exit it within 10 seconds the whole pc freezes and I have to reset it.

I attached a few logfiles to this this ticket.

PS: I tried the latest test-build, (5.0.1 r101908), the error happens here too.

Hardware:

  • AMD FX 8320
  • ASRock Mainboard
  • AMD R9 290
  • Windows 10 Pro x64

Attachments

VBox Logs.zip Download (92.5 KB) - added by PanzerTeo 7 years ago.
VBox Logs (1x 32-bit, 3x 64-bit guest)
Screenshot 2015-08-04 00.07.32.png Download (24.3 KB) - added by Programming4life 7 years ago.
Memory error image
Vbox_r101957.txt Download (74.1 KB) - added by PanzerTeo 7 years ago.
VBox.log Download (63.9 KB) - added by Ponof 6 years ago.
VBoxStartup.log Download (383.9 KB) - added by Ponof 6 years ago.

Change History

Changed 7 years ago by PanzerTeo

VBox Logs (1x 32-bit, 3x 64-bit guest)

comment:1 Changed 7 years ago by PanzerTeo

the first message which appears is the same as here: #14370

Changed 7 years ago by Programming4life

Memory error image

comment:2 Changed 7 years ago by Programming4life

I've got this problem too. I tried to start the vm 3 times the third time I got this message after the vbox give me a critical error. Hopefully the image I've attached helps with solving this problem.

Hardware: Cpu: AMD FX-8350 Mobo: Gigabyte-990FXA-UD3 Gpu: R9 280 x2 OS: Windows Pro x64

Last edited 7 years ago by Programming4life (previous) (diff)

comment:3 Changed 7 years ago by Programming4life

@PanzerTeo I've solved this problem for my self at least. You can try this too. Originally I had upgraded to windows 10 from windows 8.1 and was having this lag problem. Then I ended up doing a clean install of windows 10 and tested vbox and it works now. So it looks like the prolem is caused when you upgrade to windows 10 from another windows version.

comment:4 Changed 7 years ago by PanzerTeo

@Programming4life: I completely reinstalled Windows 10 and installed the VirtualBox Build 5.0.1 r101957. now the VM starts but after round about 1-3 Minutes the whole PC freezes. Without running VirtualBox the PC didn't crashes.

Changed 7 years ago by PanzerTeo

comment:5 Changed 7 years ago by frank

Could you retry with VBox 5.0.2?

comment:6 Changed 7 years ago by PanzerTeo

5.0.2 works for me, thanks!

comment:7 Changed 7 years ago by frank

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

Thanks for the feedback!

comment:8 Changed 6 years ago by ClasG

I've upgraded my processor from an FX-6100 to FX-8370 and are experiencing the same problems on v.5.0.16 since. The OS was upgraded from 8.1 (prior to processor upgrade) to Windows 10, but V-Box crashed (froze) and wrecked my system disk. I reinstalled Windows 10 from scratch (system wouldn't even repair or reset), but the problem persists. Because of my first crash causing the re-install I'm hesitant to try to many times.

Could this fix have been lost between versions? What are the minimum info I have to submit to file a ticket, or re-open this one?

Regards

Changed 6 years ago by Ponof

Changed 6 years ago by Ponof

comment:9 Changed 6 years ago by Ponof

  • Status changed from closed to reopened
  • Resolution fixed deleted

I've the same problem... I tried version 5.0.16 and version 5.0.2 same problem just after the vm is launch. Problem is repeatable.

Could you please give us instructions. I attached logs.

Regards,

Last edited 6 years ago by Ponof (previous) (diff)

comment:10 Changed 6 years ago by frank

Ponof, your VBox.log file contains only garbage. The VBoxStartup.log file is from VBox 5.0.2. Please attach VBox.log and VBoxHardening.log from VBox 5.0.16.

comment:11 Changed 6 years ago by frank

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

Please reopen when you can provide the requested information.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use