Discussions related to using VirtualBox on Linux hosts.
ericp56
Posts: 2 Joined: 15. Jul 2017, 21:55
Post
by ericp56 15. Jul 2017, 22:12
Host: Fedora 26
Guest: Windows 10
VB Version: 5.1.3 r116680.
I installed the latest VB non-dev build to fix the Win10 audio issues.
Is there a reference to what this fatal condition is?
Error in the log:
Code: Select all
01:17:56.556448 GIM: HyperV: Guest indicates a fatal condition! P0=0x10e P1=0x12 P2=0x0 P3=0x0 P4=0x0
01:17:57.558479 Display::handleDisplayResize: uScreenId=0 pvVRAM=00007f66b8000000 w=640 h=480 bpp=0 cbLine=0x140 flags=0x0
01:17:57.558575 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=640x480, Sending to async-handler
01:17:57.558614 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=640x480
01:17:57.558620 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=640x480
01:17:57.558627 GUI: UIFrameBufferPrivate::performResize: Size=640x480, Directly using source bitmap content
01:17:58.954363 AHCI#0: Reset the HBA
01:17:58.954883 AHCI#0: Port 0 reset
01:17:59.984067 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
01:18:12.166014 GIM: HyperV: Reset initiated through MSR
01:18:12.166071 Changing the VM state from 'RUNNING' to 'RESETTING'
01:18:12.168896 GIM: HyperV: Resetting MMIO2 regions and MSRs
01:18:12.168960 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
01:18:12.169226 Stopping the host clipboard service
and it follows the traditional guest logging, stopping the OS and restarting it...
Last edited by
socratis on 15. Jul 2017, 22:29, edited 1 time in total.
Reason: Enclosed the information in [code] tag for better readability
socratis
Site Moderator
Posts: 27329 Joined: 22. Oct 2010, 11:03Primary OS: Mac OS X otherVBox Version: PUELGuest OSses: Win(*>98), Linux*, OSX>10.5Location: Greece
Post
by socratis 15. Jul 2017, 22:30
Partial logs are not that helpful I'm afraid. Please ZIP and attach the full log. See the "Upload attachment" tab below the reply form.
Do NOT NOT reply with the "QUOTE" button, please use the "POST REPLY ", at the bottom of the form.any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
ericp56
Posts: 2 Joined: 15. Jul 2017, 21:55
Post
by ericp56 18. Jul 2017, 17:34
I've attached a VB log.
I captured a dump from the bluescreen and I got this from windbg
Code: Select all
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000012, Driver overflowed the provided DMA buffer.
I turned off 3D acceleration, and it seems to be working fine now. Before hand, it was 3D acceleration with 128M RAM (max was 256M, but I didn't try bumping it up).
Full dump is here:
Microsoft (R) Windows Debugger Version 10.0.15063.468 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\eric\Desktop\071717-4843-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 15063 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff801`d6c87000 PsLoadedModuleList = 0xfffff801`d6fd35e0
Debug session time: Mon Jul 17 13:34:16.982 2017 (UTC - 4:00)
System Uptime: 0 days 4:02:02.940
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10E, {12, 0, 0, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+175 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000012, Driver overflowed the provided DMA buffer.
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.15063.483 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: innotek GmbH
VIRTUAL_MACHINE: VirtualBox
SYSTEM_PRODUCT_NAME: VirtualBox
SYSTEM_VERSION: 1.2
BIOS_VENDOR: innotek GmbH
BIOS_VERSION: VirtualBox
BIOS_DATE: 12/01/2006
BASEBOARD_MANUFACTURER: Oracle Corporation
BASEBOARD_PRODUCT: VirtualBox
BASEBOARD_VERSION: 1.2
DUMP_TYPE: 2
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_P1: 12
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BUGCHECK_STR: 0x10e_12
CPU_COUNT: 2
CPU_MHZ: 946
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 8e
CPU_STEPPING: 9
CPU_MICROCODE: 6,8e,9,0 (F,M,S,R) SIG: 0'00000000 (cache) 0'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: MIMAS
ANALYSIS_SESSION_TIME: 07-17-2017 14:11:30.0184
ANALYSIS_VERSION: 10.0.15063.468 amd64fre
LAST_CONTROL_TRANSFER: from fffff8013b7b355e to fffff801d6df34c0
STACK_TEXT:
ffffbd80`04938218 fffff801`3b7b355e : 00000000`0000010e 00000000`00000012 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffbd80`04938220 fffff801`3cd0e17d : ffff930e`539a6000 ffffd309`3a72a3a0 ffff930e`539a6000 ffffcf67`b3c02dc8 : watchdog!WdLogEvent5_WdCriticalError+0xce
ffffbd80`04938260 fffff801`3cd1a365 : ffffd309`3a72a3a0 00000000`00000000 ffffd309`00000008 ffffbd80`04938330 : dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+0x175
ffffbd80`049382e0 fffff801`3cd1a454 : 00000000`00000000 fffff801`00000000 ffffd309`3a72a3a0 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::MemoryTransferInternal+0x35d
ffffbd80`049384a0 fffff801`3cd29eed : 00000000`00000000 ffff930e`541c2000 ffffd309`348625c0 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::MemoryTransfer+0xb8
ffffbd80`04938540 fffff801`3cd1b14c : ffff930e`541c2000 00000000`00000000 ffffd309`2fc22108 00000000`00000000 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0xccd
ffffbd80`049386c0 fffff801`3cd1b207 : 00000000`0000000c ffff930e`541c2000 ffff930e`539a6c68 ffff930e`539a6000 : dxgmms1!VIDMM_GLOBAL::EvictAllAllocationInList+0x78
ffffbd80`04938710 fffff801`3cd1f5e9 : 00000000`0000000c ffffbd80`04938841 ffff930e`541c2000 ffff930e`539a6000 : dxgmms1!VIDMM_GLOBAL::EvictAllReclaimedAllocation+0x5f
ffffbd80`04938750 fffff801`3cd159bb : ffff930e`51eff000 ffffd309`2fb81fd0 00000000`00000000 ffff930e`541a76c0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x15f9
ffffbd80`04938890 fffff801`3cd306d5 : ffff930e`54238010 00000000`0000000f ffff930e`00000000 ffff930e`00000008 : dxgmms1!VidSchiSubmitRenderCommand+0x1eb
ffffbd80`04938b80 fffff801`3cd3060b : ffff930e`51eff000 00000000`00000080 fffff801`3cd30570 ffff930e`5081e000 : dxgmms1!VidSchiRun_PriorityTable+0xb5
ffffbd80`04938bd0 fffff801`d6d63ac7 : ffffbd80`03e35180 fffff801`d6df88c7 00000000`00c26389 ffff930e`537dc080 : dxgmms1!VidSchiWorkerThread+0x9b
ffffbd80`04938c10 fffff801`d6df8946 : ffffbd80`03e35180 ffff930e`537dc080 fffff801`d6d63a80 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffbd80`04938c60 00000000`00000000 : ffffbd80`04939000 ffffbd80`04933000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: fe2bd9b1f8a69c00c0e1edff2a8f60f129fdd7f8
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e89fec67ec872113afaea8657ac142ff6320bb20
THREAD_SHA1_HASH_MOD: ae698b0730373b17d02b5b4a50374bd8307c259e
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+175
fffff801`3cd0e17d 4601a4ab38060000 add dword ptr [rbx+r13*4+638h],r12d
FAULT_INSTR_CODE: aba40146
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+175
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 59dd31ce
IMAGE_VERSION: 10.0.15063.137
BUCKET_ID_FUNC_OFFSET: 175
FAILURE_BUCKET_ID: 0x10e_12_dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration
BUCKET_ID: 0x10e_12_dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration
PRIMARY_PROBLEM_CLASS: 0x10e_12_dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration
TARGET_TIME: 2017-07-17T17:34:16.000Z
OSBUILD: 15063
OSSERVICEPACK: 483
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-07-07 02:06:35
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.15063.483
ANALYSIS_SESSION_ELAPSED_TIME: 46e
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x10e_12_dxgmms1!vidmm_global::completebuildpagingbufferiteration
FAILURE_ID_HASH: {08959385-451d-5bd3-3b0d-29b7688a0eac}
Followup: MachineOwner
---------
Attachments
Mimas-2017-07-17-13-37-07.zip (31.32 KiB) Downloaded 5 times
Last edited by
mpack on 18. Jul 2017, 18:19, edited 1 time in total.
Reason: Add code brackets for readability.
Martin
Volunteer
Posts: 2561 Joined: 30. May 2007, 18:05Primary OS: Fedora otherVBox Version: PUELGuest OSses: XP, Win7, Win10, Linux, OS/2
Post
by Martin 18. Jul 2017, 18:04
(another of these new Core i7 which gets "matched" to a Pentium N...)