MEMORY MANAGEMENT / PFN LIST CORRUPT

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Jeremy Chia, May 23, 2012.

  1. Jeremy Chia

    Jeremy Chia New Member

    Joined:
    May 23, 2012
    Messages:
    10
    Likes Received:
    0
    Hi everybody,

    I'm currently encountering some BSODs (Memory_Management and PFN_List_Corrupt) a few that i can remember. My laptop has been plagued with BSODs since the day i bought it, sent in for 2 rounds of repairs but to no avail. My laptop specs are as follows:-

    ASUS N53Sv
    CPU - Intel i7-2630QM 2.0Ghz
    RAM - 4Gb + 4Gb(added after purchase)
    GPU - GeForce GT540M 2Gb
    OS - Windows 7 Premium 64 bit

    Additional information:-

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 17417


    Additional information about the problem:
    BCCode: 1e
    BCP1: FFFFFFFFC0000005
    BCP2: 0000000000000000
    BCP3: 0000000000000008
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1




    SF Diagnostic Tools, CPU-Z, RAMMon files as attached.

    Appreciate the help, thank you.
     

    Attached Files:

    #1 Jeremy Chia, May 23, 2012
    Last edited: May 23, 2012
  2. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Sorry the single dump file contained in your attachments contained nothing of any real information.
    Code:
    BugCheck 1E, {ffffffffc0000005, 0, 8, 0}
    
    Probably caused by :[COLOR=#ff0000][U][B] Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B][/U][/COLOR]
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000008, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    FAULTING_IP: 
    +0
    00000000`00000000 ??              ???
    EXCEPTION_PARAMETER1:  0000000000000008
    EXCEPTION_PARAMETER2:  0000000000000000
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032bc0e8
     0000000000000000 
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  chrome.exe
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  [COLOR=#ff0000][U][B]from 0000000000000000 to 0000000000000000[/B][/U][/COLOR]
    STACK_TEXT:  
    [COLOR=#ff0000][U][B]00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0[/B][/U][/COLOR]
    STACK_COMMAND:  kb
    SYMBOL_NAME:      [COLOR=#ff0000][B]ANALYSIS_INCONCLUSIVE[/B][/COLOR]    
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: [COLOR=#ff0000][U][B]Unknown_Module[/B][/U][/COLOR]
    IMAGE_NAME:  [COLOR=#ff0000][U][B]Unknown_Image[/B][/U][/COLOR]
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    BUCKET_ID:  [COLOR=#ff0000][U][B]INVALID_KERNEL_CONTEXT[/B][/U][/COLOR]
    I don't see any issues with drivers that are currently installed.
    Can you adjust the Command Rate for your memory from 1T to 2T (depends on what your BIOS will allow, some laptops are very restricted).
    Can you go here and install the latest BIOS update ASUS - Notebooks- ASUS N53SV (BIOS 215 2012.02.10 update)
    If Blue Screens persist attach any new ones here in your thread.
    Regards
    Randy
     
  3. Jeremy Chia

    Jeremy Chia New Member

    Joined:
    May 23, 2012
    Messages:
    10
    Likes Received:
    0
    Hi Randy,

    I've managed to update to the latest BIOS. I'm sorry, but i can't figure out how to adjust the Command Rate for my memory. I've tried poking around in the BIOS but to no avail.

    I'll be sure to upload new dumpfiles, should the BSODs persists.

    Cheers
     
  4. Jeremy Chia

    Jeremy Chia New Member

    Joined:
    May 23, 2012
    Messages:
    10
    Likes Received:
    0
    Hi everyone,

    Second round of dump files. Crashed twice the past 3 days.
     

    Attached Files:

  5. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    You've attached three dump files now. They are all unique
    Code:
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000008, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    Code:
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000008, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    Code:
    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: ffffe4b404adaba8, memory referenced.
    Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
    Arg3: ffffe4b404adaba8, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000007, (reserved)
    But all three agree on one thing;
    Code:
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    Normally this is where I would recommend running Driver Verifier. Unfortunately because under some rare circumstance the use of Driver Verifier can result in unexpected consequences you should probably only consider running it if you are relatively certain that you have the skill set to recover from a worse case scenario.
    Please do some research and make sure you know how to run DV (how to start it and what to check) start by reading this reference Driver Verifier Settings (read it carefully) and probably just as important if not more how to stop running it.
    Additionally you might want to perhaps first run a couple hardware test.
    Check your hard drive with the native Check Disk utility. Launch an elevated command prompt and type chkdsk C: /R
    Then check your system memory.
    Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.
    Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
    See this Guide to using Memtest 86+
     
  6. Jeremy Chia

    Jeremy Chia New Member

    Joined:
    May 23, 2012
    Messages:
    10
    Likes Received:
    0
    I'll be sure to try it out. Thanks !!!
     
  7. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Sure. Keep us posted.
    A second link regarding Driver Verifier which might also help. You can never have too much information.
    Driver Verifier - jcgriff2.com
     
  8. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Jeremy:
    Please avoid using the site's PM system to ask questions. We like to keep everything discussed, concerning a particular issue, available publicly whenever possible.
    To answer your question, yes most top tier HDD manufacturer's provide some type of proprietary hard disk diagnostic software which you can generally find on their website. These are normally used for diagnosing specific issues when pursuing warranty / RMA claims with the vendor. Determine which drive you have and check with the manufacturer. A list of some link locations can be obtained here Hard Drive Diagnostic Procedure
    And as I mentioned above the native Check Disk Utility can also be used to supplement and augment your testing of the drive. From and elevated command prompt type
    chkdsk C: /R
    let it run all five stages and see what it produces in the way of information.
    Regards
    Randy
     
  9. Jeremy Chia

    Jeremy Chia New Member

    Joined:
    May 23, 2012
    Messages:
    10
    Likes Received:
    0
    Hi Randy,

    Sorry bout that, i had no idea.

    Sadly before i had the time to do any of the testing that you advised, it decided to crash again. Once more i've uploaded my minidump files.

    Thanks, again.

    Cheers

    View attachment 052912-23649-01.rar
     
  10. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Another
    Code:
    [COLOR=#ff0000][U][B]BugCheck 1E[/B][/U][/COLOR], {ffffffffc0000005, fffff8800141c86a, 1, 10}
    [COLOR=#ff0000][U][B]Probably caused by : Unknown_Image [/B][/U][/COLOR]( Ntfs!NtfsFastIoCheckIfPossibleInternal+25e )
    [COLOR=#ff0000][U][B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B][/U][/COLOR]
    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.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8800141c86a, The address that the exception occurred at
    Arg3: 0000000000000001, Parameter 0 of the exception
    Arg4: 0000000000000010, Parameter 1 of the exception
    I would say your best bet is to go here ASUS - Notebooks- ASUS N53SV and make sure that every driver for all your hardware is the latest available.
    I see there is a BIOS revision update to v215 2012.02.10 from v214 10/8/2011 which may help.
    But pay particular attention to any updates for your Chipset, Video, Audio and Network (wireless and wired). Also double check under utilities and others for ATKACPI driver and hotkey-related utilities, Intel Management Engine Interface, Intel Rapid Storage Technology driver and Keyboard Device Filter Utility.
    You have one slightly older (pre-Windows 7 RTM) driver
    ASMMAP64.sys 7/2/2009 which looks like a
    , which I would think should be a bit more recent, but perhaps not.
     
  11. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Looking a little more deeply at the stack for the raw thread I see the following three third party drivers listed
    Code:
    fffff880`09704f08  fffff880`04d84d52Unable to load image [COLOR=#ff0000][U][B]igdkmd64.sys[/B][/U][/COLOR], Win32 error 0n2
    *** WARNING: Unable to verify timestamp for [COLOR=#ff0000][U][B]igdkmd64.sys[/B][/U][/COLOR]
    *** ERROR: Module load completed but symbols could not be loaded for [COLOR=#ff0000][U][B]igdkmd64.sys[/B][/U][/COLOR]
    [B][U][COLOR=#ff0000] igdkmd64[/COLOR][/U][/B]+0x342d52
    Intel Graphics driver 1/27/2011 Check here http://downloadcenter.intel.com/Default.aspx for a possible update
    Code:
    fffff880`09705878  fffff880`05a947f0Unable to load image[COLOR=#ff0000][U][B] athrx.sys[/B][/U][/COLOR], Win32 error 0n2
    *** WARNING: Unable to verify timestamp for [COLOR=#ff0000][U][B]athrx.sys[/B][/U][/COLOR]
    *** ERROR: Module load completed but symbols could not be loaded for [COLOR=#ff0000][U][B]athrx.sys[/B][/U][/COLOR]
     [COLOR=#ff0000][U][B]athrx[/B][/U][/COLOR]+0x2897f0
    Atheros Network Adapter 10/4/2011 determine the actual Model Name and Number of the device and check here ATHEROS drivers for Microsoft Windows (Atheros?????) for something more current
    Code:
    fffff880`097089a8  fffff880`0124208aUnable to load image [COLOR=#ff0000][U][B]iaStor.sys[/B][/U][/COLOR], Win32 error 0n2
    *** WARNING: Unable to verify timestamp for [COLOR=#ff0000][U][B]iaStor.sys[/B][/U][/COLOR]
    *** ERROR: Module load completed but symbols could not be loaded for [COLOR=#ff0000][U][B]iaStor.sys[/B][/U][/COLOR]
     [COLOR=#ff0000][U][B]iaStor[/B][/U][/COLOR]+0x3908a
    Intel Storage driver 11/6/2010 Check here and make sure you have the latest available http://downloadcenter.intel.com/Default.aspx
    Good Luck
    Randy
     

Share This Page

Loading...