Custom Query (16363 matches)
Results (385 - 387 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10002 | duplicate | HostMemoryLow (Halted when Increase VM-RAM to 2 GB) | ||
| Description |
When I define 2 GB RAM , VBox halted & show error message with topic : hostmemorylow My RAM is 6 GB and enough but show HostMemoryLow. |
|||
| #10136 | obsolete | HostMemoryLow | ||
| Description |
Hi When my RAM is 1 GB all things is OK but When I increase RAM to 2 GB my system halted & Show HostMemoryLow error. My Computer info : CPU : Core i5 RAM : 6 GB OS : Windows 7 x64 My Vbox Machine : RAM : 2 GB OS : Windows 7 x86 |
|||
| #11097 | fixed | Blue Screen on win7 while installing guest from .iso | ||
| Description |
host: Guest: Linux windbg: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\102112-84536-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols\cache*http://msdl.microsoft.com/download/symbols;c:\symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02c12000 PsLoadedModuleList = 0xfffff800`02e56670
Debug session time: Sun Oct 21 15:24:46.301 2012 (UTC + 2:00)
System Uptime: 0 days 0:24:17.693
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff8800562d000, 2, 1, fffff880099269fa}
Unable to load image \??\C:\Program Files\Oracle\VirtualBox\VMMR0.r0, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VMMR0.r0
*** ERROR: Module load completed but symbols could not be loaded for VMMR0.r0
Probably caused by : VMMR0.r0 ( VMMR0+5a9fa )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8800562d000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880099269fa, address which referenced memory
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'VMMR0' and 'VMMR0.r0' overlap
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec0100
fffff8800562d000
CURRENT_IRQL: 2
FAULTING_IP:
VMMR0+5a9fa
fffff880`099269fa f348a5 rep movs qword ptr [rdi],qword ptr [rsi]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: VirtualBox.exe
TRAP_FRAME: fffff8800562c370 -- (.trap 0xfffff8800562c370)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800562c699 rbx=0000000000000000 rcx=00000000000000d4
rdx=0000000000001000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880099269fa rsp=fffff8800562c508 rbp=0000000005000060
r8=0000000000001000 r9=0000000000001000 r10=0000000000001000
r11=fffff88003d2f000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
VMMR0+0x5a9fa:
fffff880`099269fa f348a5 rep movs qword ptr [rdi],qword ptr [rsi]
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c90769 to fffff80002c911c0
STACK_TEXT:
fffff880`0562c228 fffff800`02c90769 : 00000000`0000000a fffff880`0562d000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0562c230 fffff800`02c8f3e0 : 00000000`00000000 fffffa80`04fb62a0 fffff880`0562c4e0 00000000`00000020 : nt!KiBugCheckDispatch+0x69
fffff880`0562c370 fffff880`099269fa : fffff880`0990da53 00000000`00000000 fffff880`098f7bc9 fffff880`03d2f000 : nt!KiPageFault+0x260
fffff880`0562c508 fffff880`0990da53 : 00000000`00000000 fffff880`098f7bc9 fffff880`03d2f000 00000000`00000000 : VMMR0+0x5a9fa
fffff880`0562c510 00000000`00000000 : fffff880`098f7bc9 fffff880`03d2f000 00000000`00000000 00000000`00000000 : VMMR0+0x41a53
STACK_COMMAND: kb
FOLLOWUP_IP:
VMMR0+5a9fa
fffff880`099269fa f348a5 rep movs qword ptr [rdi],qword ptr [rsi]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: VMMR0+5a9fa
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: VMMR0
IMAGE_NAME: VMMR0.r0
DEBUG_FLR_IMAGE_TIMESTAMP: 504a14c5
FAILURE_BUCKET_ID: X64_0xD1_VMMR0+5a9fa
BUCKET_ID: X64_0xD1_VMMR0+5a9fa
Followup: MachineOwner
---------
|
|||

