locked
NK Kernel Debug Check Error RRS feed

  • Question

  • Hi    I am using Windows CE 5.0 to build a simple platform.    The OS Builds and downloads to the device with EBOOT.BIN

    I am getting an error once CE starts up, see the Debug Output Below.   The error log lines say DEBUG CHECK FAILED ... in KMSIC.C.  I assume KMISC.C is a protected operating system file so I dont have the source.    It seems like the OS is trying to start the file system but it is failing.   The OS hangs after the last line of this log.

    Can anyone help me try and decipher what is going on???

    Thanks

    Ken

    Loaded symbols for 'C:\WINCE500\PBWORKSPACES\ICOPDEMO\RELDIR\VORTEX86DX_50F_X86_DEBUG\COREDLL.DLL'

    4294767388 PID:3fdf002 TID:3fdf1de 0x83fdf030: Did not find emulation code for x86... using floating point hardware.

    4294767398 PID:43fa55c6 TID:43fa5596 0x83fa53e8: >>> Loading module coredll.dll at address 0x03F60000-0x04000000 (RW data at 0x01FFE000-0x01FFF765)

    4294767411 PID:43fa55c6 TID:43fa5596 0x83fa53e8: >>> Loading module filesys.exe at address 0x04010000-0x0407C000

    Loaded symbols for 'C:\WINCE500\PBWORKSPACES\ICOPDEMO\RELDIR\VORTEX86DX_50F_X86_DEBUG\FILESYS.EXE'

    4294767425 PID:43fa55c6 TID:43fa5596 0x83fa53e8: CertMod.dll not found, using old OEM Trust Model

    4294767428 PID:43fa55c6 TID:43fa5596 0x83fa53e8: FileSystem Starting - starting with clean file system

    4294767429 PID:43fa55c6 TID:43fa5596 0x83fa53e8: FS: initializing ROM/RAM file system

    4294767430 PID:43fa55c6 TID:43fa5596 0x83fa53e8: SC_CreateAPIHandle: pvData == NULL

    4294767430 PID:43fa55c6 TID:43fa5596 0x83fa53e8: FS: Registering file system ROM, index 2, flags 0x00000031

    4294767431 PID:43fa55c6 TID:43fa5596 0x83fa53e8: FS: Mount complete (ROM, index 2, flags 0x00000031)

    4294767433 PID:43fa55c6 TID:43fa5596 0x83fa53e8: OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35

    4294767617 PID:43fa55c6 TID:43fa5596 0x83fa53e8: Succeeded on CheckFile

    4294767618 PID:43fa55c6 TID:43fa5596 0x83fa53e8: RestoreFile(0x43f8bcc2) called fDelete = TRUE

    4294768062 PID:43fa55c6 TID:43fa5596 0x83fa53e8: PCIReg(key: Drivers\BuiltIn\PCI\Instance\KITL, device: 0/8/0)

    4294768067 PID:43fa55c6 TID:43fa5596 0x83fa53e8: >>> Loading module fsdmgr.dll at address 0x03C90000-0x03CB3000 (RW data at 0x01FD0000-0x01FD0810)

    Loaded symbols for 'C:\WINCE500\PBWORKSPACES\ICOPDEMO\RELDIR\VORTEX86DX_50F_X86_DEBUG\FSDMGR.DLL'

    4294768078 PID:43fa55c6 TID:43fa5596 0x83fa53e8: FS: Registering file system StoreMgr, index 3, flags 0x00000001

    4294768080 PID:43fa55c6 TID:43fa5596 0x83fa53e8: InitSharedHeap: 42100000 10000 c

    4294768080 PID:43fa55c6 TID:43fa5596 0x83fa53e8:   InitSharedHeap: return 42100060

    4294768082 PID:43fa55c6 TID:43fa5596 0x83fa53e8: NK Kernel: DEBUGCHK failed in file D:\macallan\private\winceos\COREOS\nk\kernel\nknormal\..\kmisc.c at line 2759

    4294768102 PID:43fa55c6 TID:43fa5596 0x83fa53e8: NK Kernel: DEBUGCHK failed in file D:\macallan\private\winceos\COREOS\nk\kernel\nknormal\..\kmisc.c at line 2766

    4294768140 PID:43fa55c6 TID:43fa5596 0x83fa53e8: NK Kernel: DEBUGCHK failed in file D:\macallan\private\winceos\COREOS\nk\kernel\nknormal\..\kmisc.c at line 2768

    Thursday, October 11, 2012 4:07 PM

All replies

  • You should have it, if you installed the Private code.   The file was pre-built by Microsoft, so the path may look odd.   D:\macallan maps to your C:\WINCE500.   Also note the two dots in the path, which mean go up a directory (back to kernel).

    Bruce Eitman (eMVP)
    Senior Engineer
    Bruce.Eitman AT Eurotech DOT com
    My BLOG http://geekswithblogs.net/bruceeitman

    Eurotech Inc.
    www.Eurotech.com

    Thursday, October 11, 2012 5:36 PM
  • Bruce,

       Thanks for the reply.   There are only 3 files in the kernel directory.  Loader.c schedule.c watchdog.c.

    There is no file named kmisc.c!!

      The last thing I see in the debug log is the folowing line.

    FS: Registering file system StoreMgr, index 3, flags 0x00000001

      I am guessing that there may be a registry setting that is incorrect in the file system or disk driver. 

      If you have any other ideas i would appreciate it.

    Ken

    Thursday, October 11, 2012 5:52 PM