PFN_list_CORRUPT

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by venax, Jan 9, 2015.

  1. venax

    venax Well-Known Member

    Joined:
    Feb 15, 2012
    Messages:
    66
    Likes Received:
    0
    the ram are good , i did memtest for 6 hours , 0 errors , all my drivers are up to date . No OC running
     

    Attached Files:

  2. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,817
    Likes Received:
    1,563
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {99, 9328, 1, 7228}
    
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    
    Followup: MachineOwner
    
    Hi,
    the above bugcheck is usually caused by a failure to read correctly a page, due to failed or defective RAM (including main memory, Level 2 (L2) cache, or video memory), incompatible or mismatched memory hardware, device drivers, system service or harddrive errors.
    You also need to update.
    BiosVersion = F5
    BiosReleaseDate = 04/11/2011
    SystemManufacturer = Gigabyte Technology Co., Ltd.
    SystemProductName = Z68X-UD4-B3
    Latest Bios release stands at F10 and can be found here: (please ensure the download is correct for your machine:
    http://www.gigabyte.com/products/product-page.aspx?pid=3849#bios

    EtronHub3.sys Fri Jul 20 08:15:52 2012: Etron USB3 driver. A 2013 version is available on the support page:
    http://www.gigabyte.com/products/product-page.aspx?pid=3849#driver

    Please run the Intel driver update utility:
    http://www.intel.com/p/en_US/support/detect

    Rt64win7.sys Tue Aug 23 14:55:41 2011: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet
    http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

    xusb21.sys Thu Aug 13 23:10:17 2009: XBox USB wireless controller BSOD issues in Win7 with 2009 driver:
    Please either try to update or remove to test.

    Find command prompt in the start menu, right click on it, properties then run as admin. Type:
    sfc /scannow
    Press enter and await results. This will test for corruption in the os.

    Please run a chkdsk making sure you enable the options to search and repair corrupt sectors. This guide although for vista still works for 7:
    http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/

    Check your Vram with this app:
    http://mikelab.kiev.ua/index_en.php?page=PROGRAMS/vmt_en

    If after making the above changes you still get the bsod then you need to test your RAM.
    Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
    http://www.memtest.org/

    To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
    Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
    I know you already tested with Memtest86 but you need to run the test for at least 12hrs as some errors won't appear until at least that amount of time has passed, unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

    Post any new dump files.
     
  3. venax

    venax Well-Known Member

    Joined:
    Feb 15, 2012
    Messages:
    66
    Likes Received:
    0
    ok i reinstalled windows , updated bios to f10 , i have a new GPU as well . And i got this now , while playing a game . So it must be hardware problem ? or do you see any driver crashing in that ?
    i ll run memtest against , but as i said last time i did 7 hours with no errors ...
     

    Attached Files:

    #3 venax, Jan 12, 2015
    Last edited: Jan 12, 2015
  4. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,817
    Likes Received:
    1,563
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {99, 164c25, 2, 159024}
    
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    
    Followup: MachineOwner
    
    Hi,
    As I mention above and below Memtest86 needs to be run for at least 12hrs and sometimes even then it doesn't catch the issue. If you run Memtest86 and after 12hrs no errors are present try running your machine on one stick of RAM. If it bsod's take it out and put in another stick and try again. Keep doing this for how many sticks you have and/or you find a stick which doesn't bsod. Usually it's only one stick which has failed but try checking anyway. Remember to make a note of which stick it is and then test the others.
    Please run the Intel driver update utility:
    http://www.intel.com/p/en_US/support/detect

    Rt64win7.sys Tue Aug 23 14:55:41 2011: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet
    http://www.realtek.com.tw/downloads...d=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

    If after making the above changes you still get the bsod then you need to test your RAM.
    Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
    http://www.memtest.org/

    To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
    Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
    I know you already tested with Memtest86 but you need to run the test for at least 12hrs as some errors won't appear until at least that amount of time has passed, unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.
     
  5. venax

    venax Well-Known Member

    Joined:
    Feb 15, 2012
    Messages:
    66
    Likes Received:
    0
    ok MEMTEST for 21 hours no errors :/. I updated rt64win7 ,and intel updated me a chipset driver then after 3 days again BSOD . is it possible that the memory are faulty even if memtest doesn t register any error? but it s weird, after 21 hours i should get something ...
    Now i ll start one stick at the time ..
     

    Attached Files:

    #5 venax, Jan 15, 2015
    Last edited: Jan 15, 2015
  6. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,817
    Likes Received:
    1,563
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {7, 1b9fe5, 23d48, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+165e6 )
    
    Followup: MachineOwner
    
    Hi,
    yes it's entirely possible to run Memtest86, not get any errors and still have a bad stick. I've dealt with users with similar issues and it wasn't until the user started running on one stick that he discovered the bad RAM module.
    Checking on the call stack for this dump file (a call stack is a list of sub routines prior to the bsod) and I see a lot of NTFS related issues. Please run a chkdsk making sure you enable the options to search and repair corrupt sectors. This guide although for vista still works for 7:
    http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/

    Also please run this test for HDDs from Seagate (works on any drive)
    http://www.seagate.com/gb/en/support/downloads/item/seatools-win-master/

    If after testing everything passes ok but the bsod is still present then consider running the Driver verifier:
    http://www.reviversoft.com/blog/2013/09/using-driver-verifier-to-fix-a-blue-screen-of-death/
     

Share This Page

Loading...