[ros-dev] registry problem

[art yerkes]

On Sat, 18 Dec 2004 15:59:37 +0100
Hartmut Birr <hartmut.birr at gmx.de> wrote:

> Hi,
> 
> I've some problems with the registry on my smp machine. I start ctm and 
> cmd. Within cmd, I start  compiling of reactos. After a short time ros 
> does crash. It seems that are two problems. Look at the debug output. 
> 
> - Hartmut
> 
> ...
> RegistryHive is NULL (must not be NULL)
> Assertion KeyObject->RegistryHive != NULL failed at cm/regfile.c:265 for 
> CPU0
> Bug detected (code 0 param 0 0 0 0)
>   The bug code is undefined. Please use an existing code instead.
> 
> Frames:
> <ntoskrnl.exe: bf4a (ke/bug.c:220 (KeBugCheckEx))>
> <ntoskrnl.exe: bf6a (ke/bug.c:237 (KeBugCheck))>
> <ntoskrnl.exe: 1971b (cm/regfile.c:265 (CmiVerifyKeyObject))>
> <ntoskrnl.exe: 20a7f (cm/regobj.c:224 (CmiObjectParse))>
> <ntoskrnl.exe: 6456c (ob/object.c:162 (ObFindObject))>
> <ntoskrnl.exe: 178f5 (cm/ntfunc.c:960 (NtOpenKey))>
> <ntoskrnl.exe: 2164b (cm/rtlfunc.c:122 (RtlpGetRegistryHandle))>
> <ntoskrnl.exe: 21af0 (cm/rtlfunc.c:359 (RtlQueryRegistryValues))>
> <win32k.sys: 522e7 (objects/text.c:2848 (SubstituteFontFamilyKey))>
> <win32k.sys: 5225b (objects/text.c:2870 (SubstituteFontFamily))>
> <win32k.sys: 52051 (objects/text.c:2897 (TextIntRealizeFont))>
> <win32k.sys: 3daa5 (objects/dc.c:1861 (NtGdiSelectObject))>
> <win32k.sys: 3c4f9 (objects/dc.c:1259 (NtGdiSetDCState))>
> <win32k.sys: 29d96 (ntuser/windc.c:248 (DceReleaseDC))>
> <win32k.sys: 2a79d (ntuser/windc.c:659 (NtUserReleaseDC))>
> <win32k.sys: 25771 (ntuser/painting.c:810 (NtUserEndPaint))>
> <ntoskrnl.exe: 3b87 
> (D:\DOKUME~1\HB0875~1.NEW\LOKALE~1\Temp/ccyKaaaa.s:154 
> (KeUserModeCallback))>
> <user32.dll: eb47 (misc/win32k.c:340 (NtUserEndPaint))>
> <user32.dll: 370d3 (windows/paint.c:105 (EndPaint))>
> <win32csr.dll: 8477 (guiconsole.c:392 (GuiConsoleHandlePaint))>
> <win32csr.dll: 8e9e (guiconsole.c:750 (GuiConsoleWndProc))>
> <user32.dll: 1364b (windows/message.c:926 (IntCallWindowProcW))>
> <user32.dll: 138a9 (windows/message.c:1061 (DispatchMessageW))>
> <win32csr.dll: 91a1 (guiconsole.c:871 (GuiConsoleGuiThread))>
> <kernel32.dll: 25653 (thread/thread.c:80 (ThreadStartup))>
> <DEADBEEF>
> ...
> 
> ...
> (mm/npool.c:1643) Trying to allocate 858993464 bytes from nonpaged pool 
> - nothing suitable found, returning NULL
> Frames:
> <ntoskrnl.exe: 54afb (mm/pool.c:47 (EiAllocatePool))>
> <ntoskrnl.exe: 54b81 (mm/pool.c:102 (ExAllocatePool))>
> <ntoskrnl.exe: 20f67 (cm/regobj.c:541 (CmiAddKeyToList))>
> <ntoskrnl.exe: 2090d (cm/regobj.c:163 (CmiObjectParse))>
> <ntoskrnl.exe: 6456c (ob/object.c:162 (ObFindObject))>
> <ntoskrnl.exe: 178f5 (cm/ntfunc.c:960 (NtOpenKey))>
> <ntoskrnl.exe: 3b3b 
> (D:\DOKUME~1\HB0875~1.NEW\LOKALE~1\Temp/ccyKaaaa.s:154 
> (KeUserModeCallback))>
> <7C901E67>
> <7C909547>
> <7C9047EE>
> Page fault at high IRQL was 2
> KeBugCheckWithTf at ke/catch.c:173
> Page fault at high IRQL was 2
> Bug detected (code 1e param 0 0 0 0)
>   KMODE_EXCEPTION_NOT_HANDLED
> 
> Page Fault Exception: 14(0)
> Processor: 1 CS:EIP 8:80082d21 <ntoskrnl.exe: 82d21 
> (D:\DOKUME~1\HB0875~1.NEW\LOKALE~1\Temp/ccw9aaaa.s:396 (RtlUnwind))>
> cr2 cccccccc cr3 10f94000 Proc: 80f224c0 Pid: 37 <rdel.exe> Thrd: 
> 80ef31c8 Tid: 8f
> DS 10 ES 10 FS 30 GS 10
> EAX: 80f1fff0   EBX: 00000010   ECX: 0ccccccc
> EDX: 33333330   EBP: 9ef13c40   ESI: cccccccc   ESP: 9ef13bc4
> EDI: 00000000   EFLAGS: 00010206 kESP 9ef13bc4 kernel stack base 9ef11000
> Frames:
> <ntoskrnl.exe: 20f91 (cm/regobj.c:546 (CmiAddKeyToList))>
> <ntoskrnl.exe: 2090d (cm/regobj.c:163 (CmiObjectParse))>
> <ntoskrnl.exe: 6456c (ob/object.c:162 (ObFindObject))>
> <ntoskrnl.exe: 178f5 (cm/ntfunc.c:960 (NtOpenKey))>
> <ntoskrnl.exe: 3b3b 
> (D:\DOKUME~1\HB0875~1.NEW\LOKALE~1\Temp/ccyKaaaa.s:154 
> (KeUserModeCallback))>
> <7C901E67>
> <7C909547>
> <7C9047EE>
> <7C904EC3>
> <7C909997>
> <DEADBEEF>

Running BitchX's starting ascii graphic repetedly exposes this bug.
-- 
Here's a simple experiment. Stand on a train track between two locomotives
which are pushing on you with equal force in opposite directions. You will
exhibit no net motion. None the less, you may soon begin to notice that
something important is happening.
-- Robert Stirniman