TechSpot

BSOD - PAGE_FAULT_IN_NONPAGED_AREA (50) AND 1000007e

By danny6514
Jun 8, 2008
  1. Attached two memory dumps..
    Please help...BSOD nearly everyday...multiple times...

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {bd2afbbc, 0, abe3953e, 0}

    Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+dc )

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

    1: kd> !analyze -v
    *******************************************************************************
    * *
    * 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: bd2afbbc, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: abe3953e, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 00000000, (reserved)

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from 82155868
    Unable to read MiSystemVaType memory at 82135420
    bd2afbbc

    FAULTING_IP:
    +ffffffffabe3953e
    abe3953e ?? ???

    MM_INTERNAL_CODE: 0

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

    BUGCHECK_STR: 0x50

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    TRAP_FRAME: 85f61b6c -- (.trap 0xffffffff85f61b6c)
    ErrCode = 00000000
    eax=00000000 ebx=bc14c3ec ecx=bd2afb98 edx=00000000 esi=bc14c418 edi=bc14c3d8
    eip=abe3953e esp=85f61be0 ebp=bd317ec0 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    abe3953e ?? ???
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 82078bb4 to 820c3155

    STACK_TEXT:
    85f61b54 82078bb4 00000000 bd2afbbc 00000000 nt!MmAccessFault+0x10a
    85f61b54 abe3953e 00000000 bd2afbbc 00000000 nt!KiTrap0E+0xdc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    85f61bdc 00000000 a3693618 81a26f48 a3693618 0xabe3953e


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiTrap0E+dc
    82078bb4 85c0 test eax,eax

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!KiTrap0E+dc

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 47918b12

    FAILURE_BUCKET_ID: 0x50_VRF_nt!KiTrap0E+dc

    BUCKET_ID: 0x50_VRF_nt!KiTrap0E+dc

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

    =========================================================================================================================================

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007E, {c0000005, 0, 8038cb48, 8038c844}

    *** WARNING: Unable to verify timestamp for iastorv.sys
    *** ERROR: Module load completed but symbols could not be loaded for iastorv.sys
    Probably caused by : CLASSPNP.SYS ( CLASSPNP!ClassCompleteRequest+11 )

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

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

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    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: 00000000, The address that the exception occurred at
    Arg3: 8038cb48, Exception Record Address
    Arg4: 8038c844, Context Record Address

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


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

    FAULTING_IP:
    +0
    00000000 ?? ???

    EXCEPTION_RECORD: 8038cb48 -- (.exr 0xffffffff8038cb48)
    ExceptionAddress: 00000000
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 00000008
    Parameter[1]: 00000000
    Attempt to execute non-executable address 00000000

    CONTEXT: 8038c844 -- (.cxr 0xffffffff8038c844)
    eax=878d99f4 ebx=867d3020 ecx=ffffe800 edx=85cc08c0 esi=878d9888 edi=878d99d3
    eip=00000000 esp=8038cc10 ebp=8038cc40 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    00000000 ?? ???
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

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

    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82147868
    Unable to read MiSystemVaType memory at 82127420
    00000000

    FAILED_INSTRUCTION_ADDRESS:
    +0
    00000000 ?? ???

    BUGCHECK_STR: 0x7E

    LAST_CONTROL_TRANSFER: from 8204a0e4 to 00000000

    STACK_TEXT:
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    8038cc0c 8204a0e4 867d3020 878d9888 00000000 0x0
    8038cc40 8b1b7773 8038cc74 8b1b7d4d 85cbda38 nt!IopfCompleteRequest+0x11d
    8038cc48 8b1b7d4d 85cbda38 878d9888 00000001 CLASSPNP!ClassCompleteRequest+0x11
    8038cc74 8204a0e4 00000000 87469008 00497870 CLASSPNP!TransferPktComplete+0x2b6
    8038ccac 82695e2d 86e67bf0 857c888c 857c833c nt!IopfCompleteRequest+0x11d
    8038ccc0 8269728f 857b10e8 86e67bf0 85962c48 iastorv+0x15e2d
    8038ccd4 826975d2 86e67bf0 8038ccfc 826a4abf iastorv+0x1728f
    8038cce0 826a4abf 857c888c 86e67bf0 85821708 iastorv+0x175d2
    8038ccfc 826a4c2e 85962c48 8038cd20 8269cd1a iastorv+0x24abf
    8038cd08 8269cd1a 857c833c 85962c48 85962d34 iastorv+0x24c2e
    8038cd20 82699566 85962c48 ffffffff 86c46c50 iastorv+0x1cd1a
    8038cd3c 826996f4 85821708 8038cd70 82694fb9 iastorv+0x19566
    8038cd48 82694fb9 85821708 85821714 00000000 iastorv+0x196f4
    8038cd70 8269513a 857496d0 8038cdc0 821e5a1c iastorv+0x14fb9
    8038cd7c 821e5a1c 857496d0 413e303d 00000000 iastorv+0x1513a
    8038cdc0 8203ea3e 8269512c 857496d0 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    FOLLOWUP_IP:
    CLASSPNP!ClassCompleteRequest+11
    8b1b7773 5d pop ebp

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: CLASSPNP!ClassCompleteRequest+11

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: CLASSPNP

    IMAGE_NAME: CLASSPNP.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP: 47918f70

    STACK_COMMAND: .cxr 0xffffffff8038c844 ; kb

    FAILURE_BUCKET_ID: 0x7E_NULL_IP_CLASSPNP!ClassCompleteRequest+11

    BUCKET_ID: 0x7E_NULL_IP_CLASSPNP!ClassCompleteRequest+11

    Followup: MachineOwner
    ---------
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Run MemTest on your RAM for a minimum of 7 passes. If you receive any errors you have faulty RAM that must be replaced. Run the test then on each stick to determine which one(s) is faulty.

    Run a full harddrive diagnostics on your harddrive. Your hardderive manufacturer will provide a free utility in order to do so.

    Run ChkDsk from your Run box.
     
  3. danny6514

    danny6514 TS Rookie Topic Starter

    I'll give memtest a try...
    The tool seagate provided...for the most part, did not work
    only "short generic" and "long generic" tests worked. Both passed.

    I also ran Chkdsk, also passed.
    Memory diagnostic from vista, passed.
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...