BSOD memory_management on windows 7,

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by scandiskwindows, Nov 17, 2011.

  1. scandiskwindows

    scandiskwindows New Member

    Joined:
    Nov 17, 2011
    Messages:
    24
    Likes Received:
    0
    Hello Everyone:

    i sometimes have an BSOD in windows 7 home premium saying or doing reference to memory management and really is annoying, this happen radomly and well this is my system characteristics

    CPU AMD Athlon x2 64 2.3GHZ
    HDD 500GB
    Memory 3GB ram totals

    physical memory 2.87 GB
    VGA memory 128 MB

    Nvidia Chipset, Nforce
    Windows 7 home premium compilation 7601 with service pack 1 applied


    well that is the basic data of my computer, , i have tried the memory diagnostic of windows 7 but it seems that the memories are ok.

    any help is appreciated

    best regards
    Scandiskwindows
     
  2. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Hello and welcome to the forums.
    Please read the first post in this sticky thread here How to ask for help with a BSOD problem
    Do your best to accumulate the data required.
    Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
    Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
    Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
    Good luck
    Randy
     
  3. scandiskwindows

    scandiskwindows New Member

    Joined:
    Nov 17, 2011
    Messages:
    24
    Likes Received:
    0
    ok well i do not thinked the whole info were important but will collect the whole info with the tools mentioned.

    have to post all the tabs of CPUZ or just the two ones mentioned in the post?

    best regards
    scandiskwindows
     
    #3 scandiskwindows, Nov 17, 2011
    Last edited: Nov 17, 2011
  4. scandiskwindows

    scandiskwindows New Member

    Joined:
    Nov 17, 2011
    Messages:
    24
    Likes Received:
    0
    memory management problem , (files of report enclosed)

    hello:

    well of anyway i been having radomly blue screen of the death about memory management, just i been trying of search for solutions and ran the memory diagnostic tool of windows and everything looks fine,

    well there are the data needed and collected by the tools .

    the first file is the minidumps files of windows, are in zip format.

    the motherboard is a biostar, just as this computer is of a national brand so they have put the computer brand in the mainboard vendor but in reality is a biostar mainboard.



    now comes the screenshots of cpuz

    Captura1.PNG

    the second tab

    Captura 2.PNG

    third one

    Captura3.PNG

    four one
    Captura4.PNG
    the five of the first memory slot
    Captura5.PNG

    the second slot of memory used

    Captura5.2.PNG

    the six tab
    Captura6.PNG


    well now the report of CPUZ in HTML format

    well is compressed into a zip file

    and the rammon report in html format


    well i do not know if was needed to post all the screenshots of CPUZ but just followed admin or moderator instructions.

    well best regards

    Scandiskwindows
     

    Attached Files:

  5. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Re: memory management problem , (files of report enclosed)

    Let's start by removing McAfee. Uninstall normally by using the programs uninstaller if available in the programs directory, or use the programs and features applet in the control panel. Follow that up with running the vendor specific proprietary removal tool. Consider replacing with MSE Anti-Malware, Virus, Spyware Protection | Microsoft Security Essentials
    DUMP:
    Code:
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {bce37790, 0, 0, 834e2a5c}
    
    *** WARNING: Unable to verify timestamp for mfehidk.sys
    *** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
    Probably caused by : [COLOR=#b22222][U][B]mfehidk.sys[/B][/U][/COLOR] ( mfehidk+3ac73 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: bce37790, memory referenced
    Arg2: 00000000, IRQL
    Arg3: 00000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 834e2a5c, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 835ac848
    Unable to read MiSystemVaType memory at 8358be40
     bce37790 
    
    CURRENT_IRQL:  0
    
    FAULTING_IP: 
    nt!MiDeleteVirtualAddresses+194
    834e2a5c 8b06            mov     eax,dword ptr [esi]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  VegasMovieStud
    
    TRAP_FRAME:  bf0c3a2c -- (.trap 0xffffffffbf0c3a2c)
    ErrCode = 00000000
    eax=0204b1fc ebx=4b1fc867 ecx=00080000 edx=00000200 esi=bce37790 edi=c011b708
    eip=834e2a5c esp=bf0c3aa0 ebp=bf0c3b90 iopl=0         nv up ei ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
    nt!MiDeleteVirtualAddresses+0x194:
    834e2a5c 8b06            mov     eax,dword ptr [esi]  ds:0023:bce37790=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 834e2a5c to 834845db
    
    STACK_TEXT:  
    bf0c3a2c 834e2a5c badb0d00 00000200 00000000 nt!KiTrap0E+0x2cf
    bf0c3b90 834e32b4 23250002 23a39fff 8647d838 nt!MiDeleteVirtualAddresses+0x194
    bf0c3c60 834e2f69 8647d838 88e3c4e0 86606428 nt!MiRemoveMappedView+0x325
    bf0c3c88 8368a33f 86606428 00000000 ffffffff nt!MiRemoveVadAndView+0xe5
    bf0c3cec 836a8737 8647d838 23250000 00000000 nt!MiUnmapViewOfSection+0x265
    bf0c3d0c 8b43cc73 ffffffff 23250000 08c1faec nt!NtUnmapViewOfSection+0x55
    WARNING: Stack unwind information not available. Following frames may be wrong.
    bf0c3d24 834811fa ffffffff 23250000 08c1faf4 [B][U][COLOR=#b22222]mfehidk[/COLOR][/U][/B]+0x3ac73
    bf0c3d24 777b70b4 ffffffff 23250000 08c1faf4 nt!KiFastCallEntry+0x12a
    08c1faf4 00000000 00000000 00000000 00000000 0x777b70b4
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    mfehidk+3ac73
    8b43cc73 ??              ???
    
    SYMBOL_STACK_INDEX:  6
    
    SYMBOL_NAME:  [B][U][COLOR=#b22222]mfehidk[/COLOR][/U][/B]+3ac73
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: [COLOR=#b22222][U][B]mfehidk[/B][/U][/COLOR]
    
    IMAGE_NAME:  [B][U][COLOR=#b22222]mfehidk.sys[/COLOR][/U][/B]
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e3ae7c6
    
    FAILURE_BUCKET_ID:  0xA_[B][U][COLOR=#b22222]mfehidk[/COLOR][/U][/B]+3ac73
    
    BUCKET_ID:  0xA_[B][U][COLOR=#b22222]mfehidk[/COLOR][/U][/B]+3ac73
    
    Followup: MachineOwner
    If Blue Screens persist after the removal post back with latest .dmp files and we'll take a look at some older drivers that may need addressing.
     
  6. scandiskwindows

    scandiskwindows New Member

    Joined:
    Nov 17, 2011
    Messages:
    24
    Likes Received:
    0
    Re: memory management problem , (files of report enclosed)

    i were checking the management tools and seen some errors or warnings of mcafee, but this have been happening even before of have installed mcffee antivirus.

    of anyway on december ends the antivirus suscription. but is just rare.

    because even when this computer was under warranty get those errors but i ignored those because just were not relevants .

    well but isolating the problem or the antivirus issue what can be happening,

    best regards
    Scandiskwindows
     

Share This Page

Loading...