locked
WRK boot failure RRS feed

  • Question

  • hello, i build WRK as readme.
    but when i boot windows 2003 from wrk
    there is some thing wrong , i got a blue screen
    and it said "PROCESS1_INITIALIZATION_FAILED"

    what's matter with my wrk?
    Thursday, May 17, 2007 8:22 AM

Answers

  • I've spoken with a kernel architect here at MSFT, and we'd like you to make sure that you are in fact trying to boot the WRK within Windows Server 2003 SP1. Principally because the version number you gave us does not match either the WRK kernel or the shipped kernel in WS2003 SP1. With the WRK kernel it is 3800 and the shipped kernel it is 3796. You're getting an error because the kernel can't find an entry point into ntdll.dll.

     

     

     

    Monday, May 21, 2007 6:25 PM

All replies

  • Are you booting Windows Server 2003 SP1 or SP2? SP2 is not supported.
    Thursday, May 17, 2007 4:51 PM
  • thanks for your reply

    i find that my windows 2k3 is service pack 1, v.1023

     

     

    Friday, May 18, 2007 1:01 AM
  • i just debug the wrk, and get some error log as follow:

     

     

    *** Fatal System Error: 0x0000006b
                           (0xC000007A,0x00000008,0x00000000,0x00000000)

    Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    Connected to Windows Server 2003 3800 x86 compatible target, ptr64 FALSE
    Loading Kernel Symbols
    .............................................................................
    Loading User Symbols
    Loading unloaded module list
    ...
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 6B, {c000007a, 8, 0, 0}

    Probably caused by : wrkx86.exe ( nt!PspInitializeSystemDll+41 )

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

    nt!RtlpBreakWithStatusInstruction:
    8053fd94 cc               int     3

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

    PROCESS1_INITIALIZATION_FAILED (6b)
    Arguments:
    Arg1: c000007a, Indicates the NT status code that caused the failure.
    Arg2: 00000008, (reserved)
    Arg3: 00000000
    Arg4: 00000000

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


    DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

    BUGCHECK_STR:  0x6B

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 8050256f to 8053fd94

    STACK_TEXT: 
    f789a894 8050256f 00000003 00000000 0000006b nt!RtlpBreakWithStatusInstruction [C:\WRK\base\ntos\rtl\i386\debug2.asm @ 47]
    f789a8e0 8050300e 00000003 c000007a 00000000 nt!KiBugCheckDebugBreak+0x19 [c:\wrk\base\ntos\ke\bugcheck.c @ 252]
    f789ac78 80503417 0000006b c000007a 00000008 nt!KeBugCheck2+0x5a4 [c:\wrk\base\ntos\ke\bugcheck.c @ 860]
    f789ac98 806dc0f1 0000006b c000007a 00000008 nt!KeBugCheckEx+0x19 [c:\wrk\base\ntos\ke\bugcheck.c @ 146]
    f789acb8 806dc10a 806dc13f 80087000 f789ada0 nt!PspInitializeSystemDll+0x41 [c:\wrk\base\ntos\ps\psinit.c @ 890]
    f789acbc 806dc13f 80087000 f789ada0 806cb9d3 nt!PspInitPhase1+0xa [c:\wrk\base\ntos\ps\psinit.c @ 574]
    f789acc8 806cb9d3 00000001 80087000 00000000 nt!PsInitSystem+0x27 [c:\wrk\base\ntos\ps\psinit.c @ 180]
    f789ada0 805be95f 80087000 f789addc 8060ee02 nt!Phase1InitializationDiscard+0x757 [c:\wrk\base\ntos\init\initos.c @ 1604]
    f789adac 8060ee02 80087000 00000000 00000000 nt!Phase1Initialization+0xb [c:\wrk\base\ntos\init\initos.c @ 929]
    f789addc 80565192 805be954 80087000 00000000 nt!PspSystemThreadStartup+0x2e [c:\wrk\base\ntos\ps\create.c @ 2214]
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 [C:\WRK\base\ntos\ke\i386\threadbg.asm @ 78]


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!PspInitializeSystemDll+41 [c:\wrk\base\ntos\ps\psinit.c @ 890]
    806dc0f1 e89c00fcff       call    nt!KdUpdateDataBlock (8069c192)

    FAULTING_SOURCE_CODE: 
       886:     if ( !NT_SUCCESS (st)) {
       887:         KeBugCheckEx(PROCESS1_INITIALIZATION_FAILED,st,8,0,0);
       888:      }
       889:
    >  890:     KdUpdateDataBlock ();
       891:
       892:     return st;
       893: }
       894:
       895: NTSTATUS


    SYMBOL_STACK_INDEX:  4

    FOLLOWUP_NAME:  MachineOwner

    SYMBOL_NAME:  nt!PspInitializeSystemDll+41

    MODULE_NAME:  nt

    IMAGE_NAME:  wrkx86.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  464c5c31

    FAILURE_BUCKET_ID:  0x6B_nt!PspInitializeSystemDll+41

    BUCKET_ID:  0x6B_nt!PspInitializeSystemDll+41

    Followup: MachineOwner

    Friday, May 18, 2007 1:13 AM
  • I've forwarded this message onto a kernel archtect here at MSFT. Hopefully, we can get you an answer soon.
    Friday, May 18, 2007 5:12 PM
  • thanks a lot~

     

    Saturday, May 19, 2007 2:20 AM
  • I've spoken with a kernel architect here at MSFT, and we'd like you to make sure that you are in fact trying to boot the WRK within Windows Server 2003 SP1. Principally because the version number you gave us does not match either the WRK kernel or the shipped kernel in WS2003 SP1. With the WRK kernel it is 3800 and the shipped kernel it is 3796. You're getting an error because the kernel can't find an entry point into ntdll.dll.

     

     

     

    Monday, May 21, 2007 6:25 PM
  • ok,thanks

     

    now , my problem is gone by reinstall win2k3 sp1, maybe my first installtion

    is not proper version.

     

    Tuesday, May 22, 2007 1:01 AM