Details
-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
Description
ROS version: Affects current master be5c889cdf73080228f6f41c8bbb2fdac4dfb31c and last 0.4.14 release 10d0e9b24aa32b93da3e0916c54b43040f18e0c3
Context:
VirtualMachine under VersiĆ³n 6.1.46 r158378 (Qt5.15.10) and the attached version of the driver.
VM with 3441MB of RAM and VBOXVGA controller with 64 MB, one screen, no 3D accel.
Host: Debian 12 with Linux 6.4.15-2-liquorix-amd64 x86_64 kernel / Dell Optiplex 3010
Description of the bug:
The bug reported in https://forums.virtualbox.org/viewtopic.php?f=2&t=109196#p535394 and apparently fixed under 6.1.45r156947, 7.0.9r156960, 7.0.97r156981, is still affecting us under ReactOS.
How it must behave:
It behaves well under XP and XP64bits in same configurations. Loads without bugcheck.
Workaround for now: Still the https://download.virtualbox.org/virtualbox/6.1.34/VBoxGuestAdditions_6.1.34.iso do work for newer versions of the interface. But it's not a solution.
It is affected in a similar way to CORE-19100 and CORE-18915, but now we know this is "our bad".
Debuglog shows the next thing:
VBox-GA-Video2.log
(ntoskrnl/mm/ARM3/sysldr.c:169) Loading: \SystemRoot\System32\win32k.sys at F6438000 with 350 pages |
(ntoskrnl/mm/ARM3/sysldr.c:169) Loading: \SystemRoot\System32\ftfd.dll at F62E4000 with 154 pages |
KdSystemDebugControl is unimplemented!
|
KdSystemDebugControl is unimplemented!
|
(dll/win32/kernel32/client/loader.c:386) LoadLibraryExW(\??\C:\ReactOS\system32\csrss.exe) failing with status c000000f |
(win32ss/reactx/ntddraw/ddraw.c:57) Warning: trying loading xp/2003/windows7/reactos dxg.sys |
(ntoskrnl/mm/ARM3/sysldr.c:169) Loading: \SystemRoot\System32\drivers\dxg.sys at F62C3000 with 11 pages |
(ntoskrnl/mm/ARM3/sysldr.c:169) Loading: \SystemRoot\System32\drivers\dxgthk.sys at F62BC000 with 7 pages |
(win32ss/reactx/ntddraw/ddraw.c:112) DirectX interface is activated |
(win32ss/user/ntuser/display.c:98) err: Didn't find 'InstalledDisplayDrivers', status = 0xc0000034 |
(win32ss/user/ntuser/display.c:182) err: No usable display driver was found. |
|
*** Fatal System Error: 0x000000b4 |
(0xC0000001,0x00000000,0x00000000,0x00050000) |
|
|
Entered debugger on embedded INT3 at 0x0008:0x805A1E94. |
|
kdb:> bt
|
Eip:
|
<ntoskrnl.exe:1a1e94 (sdk/lib/rtl/i386/debug_asm.S:56 (RtlpBreakWithStatusInstruction))> |
Frames:
|
<ntoskrnl.exe:96bc1 (ntoskrnl/ke/bug.c:1070 (KeBugCheckWithTf))> |
<ntoskrnl.exe:9712b (ntoskrnl/ke/bug.c:1417 (KeBugCheckEx))> |
<win32k.sys:7445b (win32ss/user/ntuser/ntuser.c:136 (UserInitialize))> |
<win32k.sys:74755 (win32ss/user/ntuser/ntuser.c:206 (NtUserInitialize))> |
<ntoskrnl.exe:3fe5 (:0 (KiSystemCallTrampoline))> |
<ntoskrnl.exe:164395 (ntoskrnl/ke/i386/traphdlr.c:1840 (KiSystemServiceHandler))> |
<ntoskrnl.exe:3e2f (:0 (KiFastCallEntry))> |
<ntdll.dll:f47d>
|
<csrsrv.dll:67aa>
|
<csrsrv.dll:483f>
|
<csrsrv.dll:4fb5>
|
<csrss.exe:10a2>
|
<csrss.exe:148c>
|
|
Attachments
Issue Links
- duplicates
-
CORE-19224 VBox guest additions cause a BSOD 0xB4 bugcheck, part II
- Resolved