Hardware Boot Error Rev 25642

[James Tabor]

Hi!
Look at the cmd line options! It did display the debug printout for the devices.

Cool, Kick A$$, Rosxor! Alex!
James

(ntoskrnl/kd/kdio.c:193) -----------------------------------------------------
(ntoskrnl/kd/kdio.c:194) ReactOS 0.4-SVN (Build 20070126-r25642)
(ntoskrnl/kd/kdio.c:195) Command Line: DEBUGPORT=COM1  NOGUIBOOT  SOS
(ntoskrnl/kd/kdio.c:199) ARC Paths: multi(0)disk(0)rdisk(0)partition(1) \ 
multi(0)disk(0)rdisk(0)partition(1) \ReactOS\
(ntoskrnl/ke/i386/cpu.c:514) Not handling AMD caches yet
Used memory 1015744Kb
(ntoskrnl/se/semgr.c:36) FIXME: SeAccessCheck has been HACKED to always grant access!
(ntoskrnl/se/semgr.c:37) FIXME: Please fix all the code that doesn't get proper
rights!
(ntoskrnl/ke/i386/kiinit.c:43) Large Page support detected but not yet taken advantage
of!
WARNING:  HaliQuerySystemInformation at hal/halx86/generic/sysinfo.c:26 is UNIMPLEMENTED!
(ntoskrnl/ke/i386/patpge.c:62) Advanced Memory features detected but not yet taken
advantage of.
(ntoskrnl/ke/i386/mtrr.c:24) Your machine supports MTRR but ReactOS doesn't yet.
(ntoskrnl/io/iomgr/driver.c:908) Driver 'buslogic.sys' load failed, status
(c0000001)
(ntoskrnl/io/iomgr/file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1
(ntoskrnl/ldr/loader.c:259) Could not open module file:
\SystemRoot\system32\drivers\mpu401.sys 
(Status 0xc0000034)
(ntoskrnl/ldr/loader.c:259) Could not open module file:
\SystemRoot\system32\drivers\sndblst.sys 
(Status 0xc0000034)
(ntoskrnl/io/iomgr/file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 10001
(ntoskrnl/io/iomgr/file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1
(ntoskrnl/vdm/vdmmain.c:42) VME detected but not yet supported
(lib/fslib/vfatlib/vfatlib.c:215) VfatChkdsk() unimplemented!
(ntoskrnl/io/iomgr/file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1f01ff
(ntoskrnl/io/iomgr/file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1f01ff
(ntoskrnl/io/iomgr/file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1f01ff
(ntoskrnl/io/iomgr/file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1f01ff

*** Fatal System Error: 0x0000001e
                        (0x80000003,0x81022F94,0x00000000,0x00000000)

<ntoskrnl.exe:2891 (ntoskrnl/ke/bug.c:1078 (KeBugCheckEx))>
<ntoskrnl.exe:86b66 (ntoskrnl/ke/i386/exp.c:995 (KiDispatchException))>
<ntoskrnl.exe:8913b (ntoskrnl/ke/i386/trap.s:681 (CommonDispatchException))>
<81022F95>

[Alex Ionescu]

James Tabor wrote:
>   Hi!
>  Look at the cmd line options! It did display the debug printout for the devices.
>  
>  Cool, Kick A$$, Rosxor! Alex!
>  James
>   
Hi James,

Let's do a bit of bugcheck debugging. First of all, always take note of
the first parameter when hitting a 0x0000001E. In thise case, it's
0x80000003. In case you don't know, this is STATUS_BREAKPOINT, which
means the code hit an int3. Usually this means an assertion, not an
actual bug.

The next step is to see where this int3 came from. We have the answer
from two places: first, the stack frame, which shows 81022F95, and the
actual 2nd paramter, which shows 81022F94. The off-by-one difference is
caused by the fact the stack shows the line *after* the int3.

Now all we need to do is run "raddr2line module 81022f94". I don't know
what driver is loaded at 0x81022F94, and it actually looks like dynamic
code, but this should put you on the right road.

>   *** Fatal System Error: 0x0000001e
>                          (0x80000003,0x81022F94,0x00000000,0x00000000)
>  
>  <ntoskrnl.exe:2891 (ntoskrnl/ke/bug.c:1078 (KeBugCheckEx))>
>  <ntoskrnl.exe:86b66 (ntoskrnl/ke/i386/exp.c:995 (KiDispatchException))>
>  <ntoskrnl.exe:8913b (ntoskrnl/ke/i386/trap.s:681 (CommonDispatchException))>
>  <81022F95>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>   

-- 
Best regards,
Alex Ionescu
Project Lead, TinyKRNL
Kernel-Mode Software Design Engineer, ReactOS