[ros-bugs] [Bug 4296] Occasional crashes in Vbox, 2nd stage

ReactOS.Bugzilla at www.reactos.org ReactOS.Bugzilla at www.reactos.org
Sun Mar 22 23:30:57 CET 2009


Haos <olaf_siejka at o2.pl> changed:

           What    |Removed                     |Added
           Platform|QEmu                        |VirtualBox

--- Comment #1 from Haos <olaf_siejka at o2.pl>  2009-03-22 23:30:56 CET ---
The crash happens when i start moving the mouse after booting to 2nd stage. If
i dont, crash doesnt happen. Keyboard doesnt seem to be affected, but even if i
pass some stages with keyboard and use mouse later on, crash still happens:

(lib\cmlib\hivewrt.c:26) FIXME: HvpWriteLog doesn't do anything atm

*** Fatal System Error: 0x0000000a

PuTTYEntered debugger on embedded INT3 at 0x0008:0x808c1f18.
kdb:> t
Command 't' is unknown.
kdb:> bt
<NTOSKRNL.EXE:c1f19 (lib\rtl\i386\debug_asm.S:42
<NTOSKRNL.EXE:6739 (ntoskrnl/ke/bug.c:1089 (KeBugCheckWithTf at 24))>
<NTOSKRNL.EXE:bc929 (ntoskrnl\ke\i386\trap.s:2048 (KiTrap14))>
<NTOSKRNL.EXE:bdb37 (ntoskrnl\ke\i386\trap.s:2653 (KiInterruptDispatch at 0))>
<NTOSKRNL.EXE:76291 (ntoskrnl/mm/i386/page.c:1096 (MmUpdatePageDir at 12))>
<NTOSKRNL.EXE:7ee3a (ntoskrnl/mm/mm.c:54 (@MiSyncForContextSwitch at 4))>
<NTOSKRNL.EXE:d3bc (ntoskrnl/ke/thrdschd.c:367 (@KiSwapThread at 8))>
<NTOSKRNL.EXE:113aa (ntoskrnl/ke/wait.c:813 (KeWaitForMultipleObjects at 32))>
<win32k.sys:71cc3 (subsystems/win32/win32k/ntuser/msgqueue.c:533
(co_MsqPeekHardwareMessage at 24))>
<win32k.sys:72d49 (subsystems/win32/win32k/ntuser/msgqueue.c:1340
(co_MsqFindMessage at 28))>
<win32k.sys:6dfa5 (subsystems/win32/win32k/ntuser/message.c:817
(@co_IntPeekMessage at 20))>
<win32k.sys:6e479 (subsystems/win32/win32k/ntuser/message.c:1076
(@co_IntWaitMessage at 12))>
<win32k.sys:6e4eb (subsystems/win32/win32k/ntuser/message.c:1187
(NtUserGetMessage at 16))>
<NTOSKRNL.EXE:ba510 (ntoskrnl\ke\i386\trap.s:244 (KiFastCallEntry))>

Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

More information about the Ros-bugs mailing list