1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

XP Crash - PAGE_FAULT_IN_NONPAGED_AREA

Discussion in 'Windows XP' started by Sashank, 2006/04/02.

  1. 2006/04/02
    Sashank

    Sashank Inactive Thread Starter

    Joined:
    2006/04/02
    Messages:
    1
    Likes Received:
    0
    Hi,

    My notebook is crashing repeatedly.
    I ran the debugwiz tool for the memory.dmp file created and got the following debuglog.txt.

    Any help would be highly appreciated.

    Thanks
    _____________________________________________________________

    Opened log file 'c:\debuglog.txt'

    Microsoft (R) Windows Debugger Version 6.6.0003.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\MEMORY.DMP]
    Kernel Complete Dump File: Full address space is available

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
    Unable to read NT module Base Name string at 00670020 - NTSTATUS 0xC0000147
    Missing image name, possible corrupt data.
    *** WARNING: Unable to verify timestamp for Unknown_Module_00650068
    *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00650068
    Debugger can not determine kernel base address
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_rtm.040803-2158
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
    Debug session time: Sat Apr 1 08:15:37.281 2006 (GMT+8)
    System Uptime: 0 days 13:17:46.865
    WARNING: Unable to reset page directories
    Unable to read NT module Base Name string at 00670020 - NTSTATUS 0xC0000147
    Missing image name, possible corrupt data.
    *** WARNING: Unable to verify timestamp for Unknown_Module_00650068
    *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00650068
    Debugger can not determine kernel base address
    Loading Kernel Symbols
    Unable to read NT module Base Name string at 00670020 - NTSTATUS 0xC0000147
    Missing image name, possible corrupt data.
    .Unable to read KLDR_DATA_TABLE_ENTRY at 00680074 - NTSTATUS 0xC0000147

    WARNING: .reload failed, module list may be incomplete
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {f7eb8780, 0, f76baf9d, 0}

    ***** Debugger could not find nt in module list, module list might be corrupt.

    Probably caused by : Unknown_Image

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

    kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: f7eb8780, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: f76baf9d, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 00000000, (reserved)

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

    ***** Debugger could not find nt in module list, module list might be corrupt.


    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    f7eb8780

    FAULTING_IP:
    +fffffffff76baf9d
    f76baf9d 0000 add [eax],al

    MM_INTERNAL_CODE: 0

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x50

    LAST_CONTROL_TRANSFER: from 00000000 to 804f8925

    STACK_TEXT:
    f7aa17a0 00000000 00000000 00000000 00000000 0x804f8925


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    +ffffffff804f8925
    804f8925 5d pop ebp

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME: Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    BUCKET_ID: CORRUPT_MODULELIST

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

    eax=ffdff13c ebx=00000000 ecx=00000000 edx=80540fed esi=c07bf5c0 edi=00000000
    eip=804f8925 esp=f7aa1788 ebp=f7aa17a0 iopl=0 nv up ei ng nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
    804f8925 5d pop ebp
    ChildEBP RetAddr Args to Child
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    f7aa17a0 00000000 00000000 00000000 00000000 0x804f8925
    start end module name
    00650068 00d400d4 Unknown_Module_00650068 Unknown_Module_00650068 unavailable (FFFFFFFE)
    Closing open log file c:\debuglog.txt
     
  2. 2006/04/02
    charlesvar

    charlesvar Inactive Alumni

    Joined:
    2002/02/18
    Messages:
    7,024
    Likes Received:
    0

  3. to hide this advert.

  4. 2006/04/02
    cpc2004

    cpc2004 Inactive

    Joined:
    2005/07/08
    Messages:
    366
    Likes Received:
    0
    Hi,

    I find the following message at your debug.log. Probably the problem is related to bad paging space. Run chkdsk /r to perform hard disk health check.

    WARNING: Unable to reset page directories
    Unable to read NT module Base Name string at 00670020 - NTSTATUS 0xC0000147 <-- No paging space ??
    Missing image name, possible corrupt data.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.