Windows 10x64 Guest Crashing VBox 5.1.4

[luckylouie]

Having an issue with a Windows 10 Guest Crashing. I have 4 macs in our design department running virtualbox with Windows 10 guests, 3 of which are stable, but the 4th one randomly crashes sometimes frequently, other times it will run for a week without a problem. I'm at a complete loss as to why this one VM is having so much trouble.

vbox.log.2 is showing the guru mediation error (Not sure what this actually means)

I looked up the memory settings (referenced in other posts relating to Guru Mediation errors) in the log and it appears OK to me, no oversubscription.

Code: Select all

Host RAM: 12288MB total, 9413MB available
RamSize           <integer> = 0x0000000100000000 (4 294 967 296, 4 GB)
VRamSize         <integer> = 0x0000000008000000 (134 217 728, 128 MB)

Could someone look at my logs and point me in the right direction to resolving this issue ?

Code: Select all

00:00:02.626201 Console: Machine state changed to 'Running'
00:00:02.633458 OpenGL: Set 3D content scale factor to (10000, 10000), multiplier 10000 (rc=VINF_SUCCESS)
00:00:02.633509 OpenGL: Set OpenGL scale policy on HiDPI displays (fUnscaledHiDPI=0)
00:00:02.659228 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={02326f63-bcb3-4481-96e0-30d1c2ee97f6} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0
00:00:02.659443 VMMDev: Guest Log: BIOS: VirtualBox 5.1.4

Code: Select all

00:01:34.234540 OpenGL Warning: cleaning gl error (0x502), ignoring.. (1 out of 5) ..
00:01:34.935831 OpenGL Warning: cleaning gl error (0x501), ignoring.. (2 out of 5) ..
00:01:35.115867 OpenGL Warning: cleaning gl error (0x501), ignoring.. (3 out of 5) ..
00:01:35.116059 OpenGL Warning: cleaning gl error (0x501), ignoring.. (4 out of 5) ..
00:01:35.225836 OpenGL Warning: cleaning gl error (0x501), ignoring.. (5 out of 5) ..
00:01:35.930376 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:01:35.930400 Console: Machine state changed to 'GuruMeditation'
00:01:35.930794 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:01:35.930794 !!
00:01:35.930794 !!                 Guru Meditation -5300 (VERR_IEM_INSTR_NOT_IMPLEMENTED)
00:01:35.930794 !!
00:01:35.930794 Guest CPUM (VCPU 0) state: 

Code: Select all

00:01:36.011520 VGA Sequencer (3C5): SR index 3C4:04
00:01:36.011526  SR00:03 SR01:00 SR02:0F SR03:00 SR04:0A
00:01:36.011559 !!
00:01:36.011559 !! {vgatext}
00:01:36.011560 !!
00:01:36.011565 Not in text mode!
00:01:36.011568 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:01:36.011631 emR3Debug: rc=VERR_IEM_INSTR_NOT_IMPLEMENTED
00:02:32.841320 GUI: Request to close active machine-window.
00:02:32.841366 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state GuruMeditation when checking if the guest entered the ACPI mode)}, preserve=false aResultDetail=0
00:02:34.241499 GUI: Request for close-action to power VM off.
00:02:34.241519 GUI: Passing request to power VM off from machine-logic to UI session.
00:02:34.241523 GUI: Powering VM down on UI session power off request...
00:02:34.242130 Console: Machine state changed to 'Stopping'
00:02:34.242719 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
00:02:34.242734 Display::handleDisplayResize: uScreenId=0 pvVRAM=000000011841f000 w=1437 h=1116 bpp=32 cbLine=0x1674 flags=0x1
00:02:34.242759 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1437x1116, Sending to async-handler
00:02:34.243253 Changing the VM state from 'GURU_MEDITATION' to 'POWERING_OFF'
00:02:34.243269 ****************** Guest state at power off for VCpu 1 ******************

I appreciate you taking the time to look.

Thank you.

[socratis]

First thing I would do is to update to 5.1.6. It fixes a lot of audio related issues.

Are the other 3 machines identical? Close maybe? If the upgrade doesn't fix it, I'd like to see a log from a working one and a log from the Guru one. Just that log, not everything under the radar. Because you included 4 logs of which only one had the Guru and a black large PNG. Makes it difficult to shift through too much information.

[luckylouie]

2 of the imacs are running the same version OSX, and are pretty similar.
I'll get it upgraded to the latest version of virtual box. I think I've upgraded vbox 4 times since this issue started, each time hoping the latest version was going to resolve the issue.
I'll ask the user then to let me know if/when it crashses again so I can acquire the relevant logs before they rotate out.

Thanks.

[RossC]

I am having a similar problem. It seems only to occur when running Dragon Natural Speaking. I run a Ubuntu 64 16.04 LTS as the host and Windows 10 32 bit as guest. My computer has 16 gigs of RAM and I have assigned 10 gigs of those to the Guest. Interestingly, Wijndows 10 is reporting only 3.5 gigs of RAM. I was concerned I might be running out of RAM while dictating.

Anyone know why Windows is not showing the full RAM I have allocated?? I think this is all related to my BSOD occurrence in Windows 10.

Thanks,
Ross

[socratis]

You are here:

Board index ‹ General ‹ VirtualBox on Mac OS X Hosts

I am having a similar problem ... I run a Ubuntu 64 16.04 LTS as the host

Do you see the inconsistency? You're in the wrong forum. Please select the "Linux Hosts" or the "Windows Guests" forum, search for a similar thread and post there. You have to be a little bit more thorough with what "error" you're having, otherwise I would have directed you to something similar. I.e. the OP had a GURU_MEDITATION. Do you have the same? I don't know.

If you can't find an existing thread, open a new one; no need to hijack someone else's irrelevant one. Before you do, please read the following: Minimum information needed for assistance.

PS. 32-bit guests can see a maximum of 3.5 GB of RAM. No more.