none
BSOD - 000.fcl ->Windows XP

    Question

  • Please help to diagnose/explain the dump file.

    ----------------------

    Loading Dump File [C:\Users\Joey\Desktop\000.fcl\Mini070610-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    WARNING: Whitespace at end of path element
    WARNING: Non-directory path: 'C:\Users\Joey\Desktop\000.fcl\Mini070610-01.dmp'
    Symbol search path is: symsrv*symsrv.dll*C:\Symbols*http://msdl.microsoft.com/download/symbols  ;C:\Users\Joey\Desktop\000.fcl\Mini070610-01.dmp
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 2600.xpsp_sp3_gdr.080814-1236
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
    Debug session time: Tue Jul  6 15:52:12.343 2010 (GMT+8)
    System Uptime: 0 days 0:06:21.890
    Loading Kernel Symbols
    ...............................................................
    .........................................................
    Loading User Symbols
    Loading unloaded module list
    .................
    Unable to load image 000.fcl, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for 000.fcl
    *** ERROR: Module load completed but symbols could not be loaded for 000.fcl
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, a428d069, a458cb74, 0}

    Probably caused by : 000.fcl ( 000+2069 )

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


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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: a428d069, The address that the exception occurred at
    Arg3: a458cb74, Trap Frame
    Arg4: 00000000

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP:
    000+2069
    a428d069 66833b10        cmp     word ptr [ebx],10h

    TRAP_FRAME:  a458cb74 -- (.trap 0xffffffffa458cb74)
    ErrCode = 00000000
    eax=a428d064 ebx=00000000 ecx=e17c48c8 edx=e17c48ce esi=e17c48c8 edi=80569788
    eip=a428d069 esp=a458cbe8 ebp=a458cc08 iopl=0         nv up ei ng nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
    000+0x2069:
    a428d069 66833b10        cmp     word ptr [ebx],10h       ds:0023:00000000=????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0x8E

    PROCESS_NAME:  P1W1MAX.exe

    LAST_CONTROL_TRANSFER:  from 805c05b1 to a428d069

    STACK_TEXT: 
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a458cc08 805c05b1 00000000 00000760 a458cce0 000+0x2069
    a458cd0c 80586e50 7c8106f5 00000000 00000000 nt!DbgkCreateThread+0xb3
    a458cd50 804ec6d9 00000000 7c8106f5 00000001 nt!PspUserThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    000+2069
    a428d069 66833b10        cmp     word ptr [ebx],10h

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  000+2069

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: 000

    IMAGE_NAME:  000.fcl

    DEBUG_FLR_IMAGE_TIMESTAMP:  48dcdf70

    FAILURE_BUCKET_ID:  0x8E_000+2069

    BUCKET_ID:  0x8E_000+2069

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

    Thursday, July 08, 2010 6:31 AM

Answers

  • Is there anyone there to lend me a helping hand on this?

    The file that caused the BSOD, is a CyberLink FCL driver (000.fcl ) depending on the make of your system (Acer, HP, etc.) and if you've installed any DVD or BluRay playing application (which would probably be PowerDVD V.9 or V.10) then that is the cause, and uninstalling that then checking and making sure that the driver is taken off startup, and deleted should take care of the issue. with some OEM makes, there is a variation of CyberLinks players installed with different names, and so the manufacturer of your system would make the difference if PowerDVD wasnt installed
    Dennis ,, Owner: HTML tutorial Please dont forget to mark any post(s) that helped as helpful or answered EMAIL ME:: PERSONAL EMAIL :: BUSINESS EMAIL
    • Marked as answer by Joey9168 Friday, July 09, 2010 3:44 AM
    Friday, July 09, 2010 12:01 AM

All replies

  • Is there anyone there to lend me a helping hand on this?
    Thursday, July 08, 2010 9:40 AM
  • See if this is relevant; http://support.microsoft.com/kb/903251

     

    Thursday, July 08, 2010 5:31 PM
  • Is there anyone there to lend me a helping hand on this?

    The file that caused the BSOD, is a CyberLink FCL driver (000.fcl ) depending on the make of your system (Acer, HP, etc.) and if you've installed any DVD or BluRay playing application (which would probably be PowerDVD V.9 or V.10) then that is the cause, and uninstalling that then checking and making sure that the driver is taken off startup, and deleted should take care of the issue. with some OEM makes, there is a variation of CyberLinks players installed with different names, and so the manufacturer of your system would make the difference if PowerDVD wasnt installed
    Dennis ,, Owner: HTML tutorial Please dont forget to mark any post(s) that helped as helpful or answered EMAIL ME:: PERSONAL EMAIL :: BUSINESS EMAIL
    • Marked as answer by Joey9168 Friday, July 09, 2010 3:44 AM
    Friday, July 09, 2010 12:01 AM