Mem_mang, Bad_pool_header, pfn_list etc BSODs

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 7 64bits
       #1

    Mem_mang, Bad_pool_header, pfn_list etc BSODs


    Guys please help me, i am recieving several BSODs from the very first day i assembled this PC and installed win7. All my hardware is 4 months old now.

    More often i recieve Memory_managment BSOD, in july i started my research on this and got to this forum. So, i collected my dmp files for the month of july and now reporting to you guys. I tried to comprehend these dmp files using WINDBG but i am unable to comprehend them or to pinpoint the problem.

    Please help me on this issue......

    I am new to this forum please let me know what more information is needed, I have read the method and followed it but still plz correct me if there are still errors.
      My Computer


  2. Posts : 4,517
    Windows 7 Home Premium 64bit
       #2

    I beleive this is a hardware error. Might possibly be a bad RAM module.

    Have you tried checking the Pc with only 1 of the RAM sticks installed?

    This is fairly easy to check. If I were you I would try to rule it out, until someone is able to analze your dump file:

    Pull one stick of RAM out, and test with just 1 module and see how it goes. Then, pull it and replace with other one. Test again.

    i understand the hardware is only a few months old, but it doesnt rule out the possibility you were sent a bad part. It can and does happen occasionally, unfortunatly.

    Also, double check that timings, speed and especially voltage aere set correctly in the bios.
      My Computer


  3. Posts : 9
    Windows 7 64bits
    Thread Starter
       #3

    I have checked the ram with windows diagnostic utility results are fine. also can explain a bit moree about these timings, speed etc....
      My Computer


  4. Posts : 3,300
    Win7 Home Premium 64x
       #4

    The timings for ram can be manually adjusted to change the way the system uses the ram. in the BIOS, you can set it to Auto to make the RAM run at default settings.

    The best test even if the Diagnostics didn't show anything is to run it with each individual sticks and see if any issues are seen. You could have a bad stick and it is only showing errors during normal use.


    For tech info:
    Timing has to do with clock cycles between accessing the info on RAM. Tight timing is low numbers like 5-5-5-15. (or 4-4-4-18) It is a little complex, but generally, lower numbers = better performance.
    Memory timings - Wikipedia, the free encyclopedia
      My Computer


  5. Posts : 3,300
    Win7 Home Premium 64x
       #5

    A good tool for finding this info is CPU-Z CPUID - System & hardware benchmark, monitoring, reporting


    If you are not overclocking your system or have never changed any settings in the BIOS you should be fine.
      My Computer


  6. Posts : 9
    Windows 7 64bits
    Thread Starter
       #6

    If I feed exactly the same setting as i find on the corsair website for my model, will it do the job. Also should i check the sticks individually with memtest as well, or windows tool is ok?

    I have attached my current CPU-ID Profile. Accordinf to corsair site my model data is:
    TW3X4G1600C9D
    Speed Rating
    PC3-12800
    Tested Speed
    1600Mhz
    Size
    4GB Kit (2 x 2GB)
    Tested Latency
    9-9-9-24
    Tested Voltage
    1.8
    Performance Profile
    XMP
    SPD Speed
    1333Mhz
    SPD Latency
    9-9-9-24
    Package
    240pin DIMM

    Alaso attached todays two minidumps, one memory_management ant other PFN_LIST_CORRUPT.
    Last edited by ovaisaijaz; 03 Aug 2010 at 13:25.
      My Computer


  7. Posts : 3,300
    Win7 Home Premium 64x
       #7

    Memtest wouldn't hurt. It might catch something Windows missed. I think the suggested process is to run memtest for a few passes as well.

    It is also important to check them individually. If you can run just one stick for a while, use it as normal daily use to see if you get the same issues.

    It might also not be the RAM itself. the RAM slots can have issues as well. There is a lot going on between all these system parts. try the one stick at a time in each slot

    Ex:

    Try Stick 1 in Slot A
    Try Stick 1 in Slot B
    Try Stick 2 in Slot A
    Try Stick 2 in Slot B
      My Computer


  8. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #8

    Hello ! Welcome to SF !

    Most of them a pointing to Memory Management there are lot of crashes with Svchost.exe with SysMain possibly caused by McAfee. I would recommend to uninstall McAfee completely and use Removal Tool How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)

    I would recommend http://www.microsoft.com/security_essentials/

    Uninstall the LogMeIn and you could reinstall it later seems like one of the LogMeIn driver has cause some trouble to the System.
    Code:
    LogMeIn Kernel Information Provider
    Run Hardware Diagnostic: Hardware Diagnostic !! « Captain Debugger

    Bugcheck:

    Code:
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Fri Jul 30 11:03:22.745 2010 (GMT+6)
    System Uptime: 0 days 0:04:42.181
    BUGCHECK_STR:  0x1a_41790
    PROCESS_NAME:  svchost.exe
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Wed Jul 14 16:58:22.497 2010 (GMT+5)
    System Uptime: 0 days 0:01:29.559
    BUGCHECK_STR:  0x1a_41790
    PROCESS_NAME:  svchost.exe
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Thu Jul 15 02:29:21.126 2010 (GMT+6)
    System Uptime: 0 days 1:09:05.562
    Loading Kernel Symbols
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  svchost.exe
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Mon Jul 19 19:30:40.697 2010 (GMT+5)
    System Uptime: 0 days 1:05:18.133
    BUGCHECK_STR:  0x19_22
    PROCESS_NAME:  EFLC.exe
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Tue Jul 20 19:27:01.841 2010 (GMT+6)
    System Uptime: 0 days 2:24:04.277
    BUGCHECK_STR:  0x1a_41790
    PROCESS_NAME:  dwm.exe
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Wed Jul 21 02:13:40.885 2010 (GMT+6)
    System Uptime: 0 days 0:08:14.321
    BUGCHECK_STR:  0x1a_41790
    PROCESS_NAME:  WerFault.exe
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Wed Jul 21 02:36:34.952 2010 (GMT+5)
    System Uptime: 0 days 0:22:02.013
    BUGCHECK_STR:  0x1a_41790
    PROCESS_NAME:  mcshield.exe
    Hope this helps,
    Captain
      My Computer


  9. Posts : 9
    Windows 7 64bits
    Thread Starter
       #9

    plz refer to previous post, some more data from my side
      My Computer


  10. Posts : 9
    Windows 7 64bits
    Thread Starter
       #10

    Thanks alot Captian Jack. I worked as u advices its almost 12hrs and i dnt have a BSOD yet. Hope it will do the trick.

    Thanks again. :)
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:20.
Find Us