Memory_Management BSOD and random hang ups

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Hipposly, Jun 25, 2011.

  1. Hipposly

    Hipposly New Member

    Joined:
    Jun 25, 2011
    Messages:
    4
    Likes Received:
    0
    I have an Acer X1700 PC 4gb Ram Intel Pentium Dual CPU E222o @2.40ghz
    I've been experiencing BSODs and hang ups. I just swapped out the video card thought that was the problem
    But i guess not. I installed the Radeon HD 5450 I've attached a copy of the dmp file Thanks fpr looking
     

    Attached Files:

  2. yowanvista

    yowanvista Well-Known Member

    Joined:
    Apr 10, 2011
    Messages:
    82
    Likes Received:
    0
    A Hardware fault is the cause, seems to be defective RAM
    Test your RAM RAM - Test with Memtest86+ - Windows 7 Forums

    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: 82e4bc23, The address that the exception occurred at
    Arg3: 807866dc, 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: 
    nt!CmpDelayDerefKeyControlBlock+53
    82e4bc23 01803dd68cd4    add     dword ptr [eax-2B7329C3h],eax
    
    TRAP_FRAME:  807866dc -- (.trap 0xffffffff807866dc)
    ErrCode = 00000002
    eax=82d79080 ebx=82d79080 ecx=00000048 edx=00000000 esi=8be5eb48 edi=853c9d48
    eip=82e4bc23 esp=80786750 ebp=80786758 iopl=0         ov up ei ng nz ac pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210a96
    nt!CmpDelayDerefKeyControlBlock+0x53:
    82e4bc23 01803dd68cd4    add     dword ptr [eax-2B7329C3h],eax ds:0023:576466bd=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x8E
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    MISALIGNED_IP: 
    nt!CmpDelayDerefKeyControlBlock+53
    82e4bc23 01803dd68cd4    add     dword ptr [eax-2B7329C3h],eax
    
    LAST_CONTROL_TRANSFER:  from 82e6f8c7 to 82e4bc23
    
    STACK_TEXT:  
    80786758 82e6f8c7 853f7448 8ce04750 00000000 nt!CmpDelayDerefKeyControlBlock+0x53
    807867ac 82e33a98 8ce04768 8ce04768 8ce04750 nt!CmpDeleteKeyObject+0x3db
    807867c4 82c7b080 00000000 853c9d48 8ce04750 nt!ObpRemoveObjectRoutine+0x59
    807867d8 82c7aff0 8ce04768 82e57c5c 8be01cb0 nt!ObfDereferenceObjectWithTag+0x88
    807867e0 82e57c5c 8be01cb0 853c9d48 0000006c nt!ObfDereferenceObject+0xd
    80786824 82e59442 8be01cb0 8be030d8 853c9020 nt!ObpCloseHandleTableEntry+0x21d
    80786854 82e595ba 853c9020 00000000 807868f8 nt!ObpCloseHandle+0x7f
    80786870 82c5541a 8000006c 8078693c 82c52d6d nt!NtClose+0x4e
    80786870 82c52d6d 8000006c 8078693c 82c52d6d nt!KiFastCallEntry+0x12a
    807868ec 82db6765 8000006c 80786b28 00000000 nt!ZwClose+0x11
    8078693c 82db63f2 80786b28 80000128 00000001 nt!PnpIsAnyDeviceInstanceEnabled+0xaf
    807869b4 82db53c8 80000128 00000000 80786aec nt!PnpPrepareDriverLoading+0x61
    80786b9c 82fc383b 00000001 00000000 80786bd4 nt!IopLoadDriver+0x478
    80786be8 82fbf863 8080f918 8080a598 00000000 nt!IopInitializeSystemDrivers+0x163
    80786c6c 82fc4e60 0080a598 853c90b8 853c9d48 nt!IoInitSystem+0x6de
    80786d48 82d9d48e 80786d90 82e209df 8080a598 nt!Phase1InitializationDiscard+0xced
    80786d50 82e209df 8080a598 acad3261 00000000 nt!Phase1Initialization+0xd
    80786d90 82cd2219 82d9d481 8080a598 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!CmpDelayDerefKeyControlBlock+53
    82e4bc23 01803dd68cd4    add     dword ptr [eax-2B7329C3h],eax
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!CmpDelayDerefKeyControlBlock+53
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: hardware
    
    FAILURE_BUCKET_ID:  IP_MISALIGNED
    
    BUCKET_ID:  IP_MISALIGNED
    
    Followup: MachineOwner
    ---------
    
    
     
  3. Hipposly

    Hipposly New Member

    Joined:
    Jun 25, 2011
    Messages:
    4
    Likes Received:
    0
    Thank you for your help
    One of the Memory ports went bad making the system fail
     

Share This Page

Loading...