XP crashes on VM 4.0.4

Discussions related to using VirtualBox on Windows hosts.

XP crashes on VM 4.0.4

Postby elserpiente » 21. Feb 2011, 14:30

Hi,
I have XP as guest os on win7(64) host system. Every time after sequence of actions I experience rebooting of VM with subsequently freeze of booting XP. This sequence of actions is permanent. Here is log journal. Timestamp 00:01:19.780 is the last row of successful loading of xp, then goes
00:02:11.304 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={09eed313-cd56-4d06-bd56-fac0f716b5dd} aComponent={Display} aText={Could not take a screenshot (VERR_TRY_AGAIN)}, preserve=false
which causes issue I guess. Any ideas? THanks

ps: my VM ver is 4.0.4 buil 70112, guest tool and Extension Pack are updated as well.
Attachments
XP2-2011-02-21-13-23-17.log
(54.59 KiB) Downloaded 12 times
Last edited by elserpiente on 22. Feb 2011, 14:09, edited 1 time in total.
elserpiente
 
Posts: 4
Joined: 21. Feb 2011, 13:25
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: xp

Re: XP crashes on VM 4.0.4 (ERROR [COM]: aRC=VBOX_E_IPRT_ERROR)

Postby elserpiente » 22. Feb 2011, 14:09

Rolled back to VM 4.0.2, but issue is still present. Looked at windows logs and find out maybe it's Qt related issue:

-
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-02-22T11:16:49.000000000Z" />
<EventRecordID>25369</EventRecordID>
<Channel>Application</Channel>
<Computer>snake-laptop2</Computer>
<Security />
</System>
- <EventData>
<Data>VirtualBox.exe</Data>
<Data>4.0.2.0</Data>
<Data>4d35ba7e</Data>
<Data>QtCoreVBox4.dll</Data>
<Data>4.4.3.0</Data>
<Data>49d69ee1</Data>
<Data>80000001</Data>
<Data>00000000001b1971</Data>
<Data>1038</Data>
<Data>01cbd2803eb2f3bd</Data>
<Data>C:\PROGRA~1\Oracle\VIRTUA~1\VirtualBox.exe</Data>
<Data>C:\PROGRA~1\Oracle\VIRTUA~1\QtCoreVBox4.dll</Data>
<Data>3dbd20b7-3e75-11e0-a3e3-87339887f4f2</Data>
</EventData>
</Event>
elserpiente
 
Posts: 4
Joined: 21. Feb 2011, 13:25
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: xp

Re: XP crashes on VM 4.0.4

Postby elserpiente » 22. Feb 2011, 21:07

Minidump when one of craches happened
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\windows\minidump\Mini022211-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Inaccessible path: 'c:\windows\i386'
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Feb 22 18:48:53.901 2011 (UTC + 2:00)
System Uptime: 0 days 0:04:26.181
Loading Kernel Symbols
...............................................................
...........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1902fe, b265977c, b2659478, 8056f16a}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanup+2273 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 001902fe
Arg2: b265977c
Arg3: b2659478
Arg4: 8056f16a

Debugging Details:
------------------


EXCEPTION_RECORD: b265977c -- (.exr 0xffffffffb265977c)
ExceptionAddress: 8056f16a (nt!FsRtlNotifyFilterReportChange+0x0000008c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000000
Attempt to read from address 00000000

CONTEXT: b2659478 -- (.cxr 0xffffffffb2659478)
eax=b2659858 ebx=000a2452 ecx=e215fef0 edx=00000000 esi=8a2bb748 edi=e238b287
eip=8056f16a esp=b2659844 ebp=b26598bc iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!FsRtlNotifyFilterReportChange+0x8c:
8056f16a 66833a00 cmp word ptr [edx],0 ds:0023:00000000=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: NULL_DEREFERENCE

PROCESS_NAME: svchost.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 00000000

READ_ADDRESS: 00000000

FOLLOWUP_IP:
Ntfs!NtfsCommonCleanup+2273
b9e58aca 895dfc mov dword ptr [ebp-4],ebx

FAULTING_IP:
nt!FsRtlNotifyFilterReportChange+8c
8056f16a 66833a00 cmp word ptr [edx],0

BUGCHECK_STR: 0x24

LAST_CONTROL_TRANSFER: from b9e58aca to 8056f16a

STACK_TEXT:
b26598bc b9e58aca 8a2bb748 8a303400 e215fef0 nt!FsRtlNotifyFilterReportChange+0x8c
b2659ae8 b9e52d4d b2659b04 89f7ce70 8a100948 Ntfs!NtfsCommonCleanup+0x2273
b2659c60 804ef19f 8a303020 89f7ce70 89f7ce70 Ntfs!NtfsFsdCleanup+0xcf
b2659c70 80583979 8a100930 00000038 8a2d2560 nt!IopfCallDriver+0x31
b2659ca0 805bca4e 89fb9b10 8a303020 00120196 nt!IopCloseFile+0x26b
b2659cd4 805bc377 89fb9b10 00000001 8a2d2560 nt!ObpDecrementHandleCount+0xd8
b2659cfc 805bc415 e1d4b398 8a100948 00000d74 nt!ObpCloseHandleTableEntry+0x14d
b2659d44 805bc54d 00000d74 00000001 00000000 nt!ObpCloseHandle+0x87
b2659d58 8054167c 00000d74 025efc04 7c90e514 nt!NtClose+0x1d
b2659d58 7c90e514 00000d74 025efc04 7c90e514 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
025efc04 00000000 00000000 00000000 00000000 0x7c90e514


SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: Ntfs!NtfsCommonCleanup+2273

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48025be5

STACK_COMMAND: .cxr 0xffffffffb2659478 ; kb

FAILURE_BUCKET_ID: 0x24_Ntfs!NtfsCommonCleanup+2273

BUCKET_ID: 0x24_Ntfs!NtfsCommonCleanup+2273

Followup: MachineOwner
---------
elserpiente
 
Posts: 4
Joined: 21. Feb 2011, 13:25
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: xp

Re: XP crashes on VM 4.0.4

Postby elserpiente » 22. Feb 2011, 21:08

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\windows\minidump\Mini022211-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Inaccessible path: 'c:\windows\i386'
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Feb 22 18:43:06.443 2011 (UTC + 2:00)
System Uptime: 0 days 0:03:10.820
Loading Kernel Symbols
...............................................................
...........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, e2cd5658, e2cd57e0, c310607}

Probably caused by : win32k.sys ( win32k!HeavyFreePool+bb )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: e2cd5658, The pool entry we were looking for within the page.
Arg3: e2cd57e0, The next pool entry.
Arg4: 0c310607, (reserved)

Debugging Details:
------------------


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: e2cd5658

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

PROCESS_NAME: bds.exe

LAST_CONTROL_TRANSFER: from 8054b583 to 804f9f43

STACK_TEXT:
b2876780 8054b583 00000019 00000020 e2cd5658 nt!KeBugCheckEx+0x1b
b28767d0 bf802a90 e2cd5660 00000000 b28767ec nt!ExFreePoolWithTag+0x2a3
b28767e0 bf800bd3 e2cd5660 b28767fc bf805768 win32k!HeavyFreePool+0xbb
b28767ec bf805768 8a0e2e58 e2cd5660 b2876850 win32k!ExFreeToPagedLookasideList+0x1e
b28767fc bf809584 e2cd5660 00000005 27050d17 win32k!FreeObject+0x25
b2876850 bf8096a3 00000000 00000000 b2876874 win32k!SURFACE::bDeleteSurface+0x14b
b2876860 bf81386d 00000000 00000000 e2cd5660 win32k!SURFREF::bDeleteSurface+0x12
b2876874 bf813946 27050d17 0012f940 b2876894 win32k!bDeleteSurface+0x20
b2876888 8054167c 27050d17 0012f954 7c90e514 win32k!NtGdiDeleteObjectApp+0x74
b2876888 7c90e514 27050d17 0012f954 7c90e514 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f954 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!HeavyFreePool+bb
bf802a90 5d pop ebp

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: win32k!HeavyFreePool+bb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d1dd63f

FAILURE_BUCKET_ID: 0x19_20_win32k!HeavyFreePool+bb

BUCKET_ID: 0x19_20_win32k!HeavyFreePool+bb

Followup: MachineOwner
---------
elserpiente
 
Posts: 4
Joined: 21. Feb 2011, 13:25
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: xp

Re: XP crashes on VM 4.0.4

Postby mapsonyllaer » 23. Feb 2011, 18:58

Same here, Host is Windows 7, Guest is Windows XP, VBox is 4.0.2, using SATA disks. The VM has been running fine and is still running fine on a Windows Server 2008 R2 host.
mapsonyllaer
 
Posts: 3
Joined: 1. Nov 2008, 01:38

Re: XP crashes on VM 4.0.4

Postby mutface » 1. Mar 2011, 15:28

Since upgrading to 4.0.4 from 3.xxx - XP occasionally shuts down by itself with no rhyme or reason. Sorry cannot give more details.

Running Opensuse 11.3 x86_64 as host.
mutface
 
Posts: 6
Joined: 10. Jun 2010, 15:33
Primary OS: Linux other
VBox Version: OSE Fedora
Guest OSses: CENTOS

Re: XP crashes on VM 4.0.4

Postby ajw1970 » 14. Mar 2011, 19:13

Same for me. Windows 7 32 bit. Solid State hard drive. Guest is XP Pro 32 bit.

"The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019"

Microsoft has this to add (for what it's worth):

"Microsoft is unable to determine the exact cause of this error. However, this problem was most likely caused by an error in your computer’s random access memory (RAM). RAM is the main internal storage area the computer uses to run programs and store data."

"During the crash analysis, we noticed the basic input/output system (BIOS) version on this computer does not match the specifications for the central processing unit (CPU), also known as a processor, that is installed on your computer. This can occur when a newer processor is installed on an older system board or older BIOS. Using a BIOS that does not support the installed processor can result in Windows system crashes. Contact your computer manufacturer or motherboard manufacturer for an updated version of BIOS for your computer's processor."
ajw1970
 
Posts: 5
Joined: 8. Feb 2011, 20:42
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: WinXP

Re: XP crashes on VM 4.0.4

Postby daveuk3 » 14. Mar 2011, 22:44

Hi,

I'm having the same issues, but its not only occurring on a guest of XP but also Vista and Server 2003, i can get it to crash just trying to enter the setting for the guest O/S. I have tried a downgrade of VM software but the same, I don't fancy having to create all the VM's again :roll: .

Any Ideas
daveuk3
 
Posts: 1
Joined: 14. Mar 2011, 22:37
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: All

Re: XP crashes on VM 4.0.4

Postby mvniekerk » 16. Mar 2011, 17:16

Host: Ubuntu 10.10 (64bit)
Guest: Windows XP

Same happens - XP BSOD on start-up. Tried running the install CD and doing a repair install on the partition - BSOD on setup's first restart, BSOD ever since.
Please refer my to debug instructions that I can help somehow.
mvniekerk
 
Posts: 3
Joined: 1. Apr 2008, 18:57


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 53 guests