Hi,
I have VBOX 6.0.4 (Update from latest 5) installed on Windows 10 64bit.
I use a Windows 10 64bit guest with it.
After some hours, the guest freezes and vbox has to be killed in the task manager.
With vbox 5 I had no problems. The guest was running without any problems.
Please help.
Thank you
VBOX 6.0.4 on Windows 10 with Windows 10 guest freezes
-
- Posts: 10
- Joined: 23. Mar 2019, 09:55
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: VBOX 6.0.4 on Windows 10 with Windows 10 guest freezes
We need to see a complete VBox.log, from a complete VM run, where the problem occurs:
- Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
- With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
- Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 10
- Joined: 23. Mar 2019, 09:55
Re: VBOX 6.0.4 on Windows 10 with Windows 10 guest freezes
So finally it happened again.
The VM was not working and I killed it in the task manager.
Here is the log file.
The VM was not working and I killed it in the task manager.
Here is the log file.
- Attachments
-
- VM2-2019-03-26-09-06-51.zip
- (26.05 KiB) Downloaded 12 times
-
- Posts: 10
- Joined: 23. Mar 2019, 09:55
Re: VBOX 6.0.4 on Windows 10 with Windows 10 guest freezes
Happened again today, after only some minutes of work.....
- Attachments
-
- VM2-2019-03-27-14-46-56.zip
- (21.04 KiB) Downloaded 12 times
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: VBOX 6.0.4 on Windows 10 with Windows 10 guest freezes
The VirtualBox RDP server is not operational because the port is used, most probably by the native RDP server.00:00:03.719134 VRDE: Warning: failed to launch VRDE server (VERR_NET_ADDRESS_IN_USE): VirtualBox Remote Desktop Extension server can't bind to the port(s): 3389
This doesn't seem like a standard location or name, there's something funny about it, can you explain the name and location?00:00:03.929791 File system of 'C:\VM\vm\export-disk1.vdi' is ntfs
Shut down the VM. Go to the VM Settings » Display » Screen. Enable 2D and 3D acceleration. Increase the VRAM to the max 256 MB.00:00:04.009335 3DEnabled <integer> = 0x0000000000000000 (0) 00:00:04.009339 VRamSize <integer> = 0x0000000004000000 (67 108 864, 64 MB) 00:00:05.871705 GUI: 2D video acceleration is disabled
I don't see any input/output for your sound. This usually happens when you have a not-so-ordinary setup, such as an HDMI output. Is that the case?Yours: 00:00:04.883422 Audio: Initializing DirectSound audio driver 00:00:05.327447 HDA: Codec reset 00:00:05.327512 HDA: Reset Mine: 00:00:28.397552 HDA: Asynchronous I/O enabled 00:00:28.397605 Audio: Initializing DirectSound audio driver 00:00:29.139600 Audio: Found 2 devices for driver 'DSoundAudio' 00:00:29.139628 Audio: Device 'Primary Sound Driver': 00:00:29.139638 Audio: Usage = Output 00:00:29.139646 Audio: Flags = DEFAULT 00:00:29.139655 Audio: Input channels = 0 00:00:29.139663 Audio: Output channels = 2 00:00:29.139716 Audio: Device 'Primary Sound Capture Driver': 00:00:29.139725 Audio: Usage = Input 00:00:29.139733 Audio: Flags = NONE 00:00:29.139741 Audio: Input channels = 2 00:00:29.139750 Audio: Output channels = 0 00:00:29.139975 HDA: Codec reset 00:00:29.140001 HDA: Reset
I see you're doing a lot of manual resizing of the VM window. Don't. It's best if you set the resolution from within the guest, set it and forget it. Also 2150x1240 is rather big for a VM with a fake GPU, and no 2D/3D acceleration. See the advice before about the Display, and select a "standard" size resolution from within the guest.0:01:37.110154 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1733x1018 00:01:37.119834 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 1733x1018 if necessary 00:01:37.119896 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1733x1018 00:01:37.122720 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 1733x1018 if necessary 00:01:37.122794 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1733x1018 00:01:37.125206 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 1733x1018 if necessary 00:01:37.125262 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1733x1018 00:01:37.129799 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 1733x1018 if necessary 00:01:37.129850 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1733x1018 00:01:37.202983 GUI: UIMediumEnumerator: Medium-enumeration finished! 00:01:37.443308 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 2150x1240 if necessary 00:01:37.443370 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 2150x1240
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.