Random BSOD , memory management, page fault in nonpaged area, bad pool header?

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by jgro, Aug 24, 2010.

  1. jgro

    jgro New Member

    Joined:
    Aug 24, 2010
    Messages:
    8
    Likes Received:
    0
    View attachment sfdiag dumps.zip
    Hello I started a custom build about last December. Within two days of the first power up I started having problems. The system would just freeze up and the speakers would emit a dull tone. Did some research and discovered that it was most likely a RAM problem. I missed my return window so I was faced with possibly dropping another $100 and getting new ram, but the wife wouldnt allow that so I tested the crap out of my current ram and kept getting the same result... no problems found. Ok a few months go by and I get some more free time so I start working on it again. I would have probably a 10% chance of a smooth boot and error free time using the computer. When I would shut down at night and go back in the morning to play around I would get blue screen after blue screen. I orginally had it set up with home premium 64 but was having a couple problems with some of my older programs and thought maybe the 64 portion maybe causing the blue screen problem, so I installed the 32 bit version. After installing all ms updates (with multiple reboots) and an antivirus I still didnt have any problems so I made a restore point. Shut down computer and turn on again the following morning and BSOD once again. Im at my wits end. I want to take a sledge to my beauty but I know my wife will kill for wasting almost a grand on it. please help.

    Problem:
    BSOD - Memory management, page fault... nonpaged, bad pool header
    occasionally during safe mode as well

    Recently I have tried:
    Clean install of home premium 64
    Clean install of home premium 32
    registry cleaners
    memory testing - result = no problems
    memory swapping - still BSOD
    turning off XMP - had a good session immediately after i switched it off, on next boot up windows failed to start and I had to run windows startup repair about 4 times.
    trying different antivirus - first MS security essentials, then Norton Security suite from comcast
    various other suggestions from these forums over the past few months

    My Build:
    Intel Core i5-750 Lynnfield 2.66GHz LGA 1156 95W Quad-Core Processor BX80605I5750

    Western Digital Caviar Black WD6401AALS 640GB 7200 RPM SATA 3.0Gb/s 3.5" Internal Hard Drive -Bare Drive

    G.SKILL 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Dual Channel Kit Desktop Memory Model F3-10666CL8D-4GBHK

    ASUS P7P55D PRO LGA 1156 Intel P55 ATX Intel Motherboard

    MSI N260GTX-T2D896-OCv3 GeForce GTX 260 896MB 448-bit GDDR3 PCI Express 2.0 x16 HDCP Ready SLI Support Video Card

    I dont know what other info to give you all, but I hope you can help.

    Thanks!
     
    #1 jgro, Aug 24, 2010
    Last edited: Aug 24, 2010
  2. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Hi.

    Your main problem is with Norton/Symantec. Uninstall it in safe mode using the tool found here, then reboot and install MSE as a replacement:

    AV Uninstallers - Windows 7 Forums

    -------

    Be sure to also update this Realtek network driver:

    Code:
    Rt86win7 Rt86win7.sys Thu Feb 26 04:04:22 2009
    Type systeminfo the press enter in a command prompt to see which Realtek lan you have. Then search its number on the left side of this link for the latest software (driver) to install:

    Realtek

    If you have 8111, then don't search and simply use that linked page itself.
     
  3. jgro

    jgro New Member

    Joined:
    Aug 24, 2010
    Messages:
    8
    Likes Received:
    0
    View attachment secondset.zip

    Hello, did everything you said last night. Everything worked great until once again... the next day. here are the new dump files
     
  4. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Ouch haha, don't know how I missed it. Probably because it was very obvious Norton was causing issues so I didn't look too much after that for further issues.

    This guy is on the notorious list for crashing Windows 7. 2005 versions are great at doing that. The older, the worse. You have 2004:

    Code:
    ASACPI   ASACPI.sys   Thu Aug 12 22:52:52 2004
    To update this guy, visit your motherboard page at the following link. Download tab.
    Choose Windows 7. Then go to Utilities section. Download and install "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit".

    ASUSTeK Computer Inc. - Motherboards - P7P55D PRO

    -----

    Your video card driver would like to be updated:
    Code:
    nvlddmkm nvlddmkm.sys Thu May 14 16:32:27 2009 
    NVIDIA

    ------

    Enjoy.
     
  5. jgro

    jgro New Member

    Joined:
    Aug 24, 2010
    Messages:
    8
    Likes Received:
    0
  6. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Have you tested with memtest86 for a couple hours running it? Have you tried with one stick of ram? Swapping them? Your thirdest dumps point to the same memory problem, like :

    Code:
    READ_ADDRESS: GetPointerFromAddress: unable to read from 82984718
    Unable to read MiSystemVaType memory at 82964160
     ae267fb8 
    Code:
    082510-13509-01.dmp
    
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x4E (0x99, 0x6DF9D, 0x0, 0x6E09D)
    Error: PFN_LIST_CORRUPT
    
    
    
    082510-13088-01.dmp
    
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x1A (0x41790, 0xC080279C, 0xFFFF, 0x0)
    Error: MEMORY_MANAGEMENT
    
    
    
    082410-16411-01.dmp
    
    This was likely caused by the following module: idsvix86.sys
    Bugcheck code: 0x50 (0x8AA00000, 0x1, 0x90E5CB33, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    
    
    
    
    082310-31403-01.dmp
    
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x1A (0x41790, 0xC080207C, 0xFFFF, 0x0)
    Error: MEMORY_MANAGEMENT
    
    
    
    
    
    
    082310-23665-01.dmp
    
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x1A (0x41790, 0xC08020C2, 0xFFFF, 0x0)
    Error: MEMORY_MANAGEMENT
    
    
    
    
    
    082810-16005-01.dmp
    
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x50 (0xAE267FB8, 0x0, 0x8285A8D8, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    
    
    
    
    082710-19609-01.dmp
    
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x4E (0x99, 0x15EFA, 0x0, 0x15FFA)
    Error: PFN_LIST_CORRUPT
    
    
    
    082710-16598-01.dmp
    
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x1A (0x41790, 0xC0802074, 0xFFFF, 0x0)
    Error: MEMORY_MANAGEMENT
    
    
    
    
    082710-16582-01.dmp
    
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x1A (0x403, 0xC0097AF8, 0x17BFC867, 0xBFCBDFE0)
    Error: MEMORY_MANAGEMENT
    
    
    
    082610-19687-01.dmp
    
    This was likely caused by the following module: mpfilter.sys
    Bugcheck code: 0x1000008E (0xC0000005, 0x828334C4, 0x9DCD35B8, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    
    
    
    082610-17284-01.dmp
    
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x1A (0x41790, 0xC080204A, 0xFFFF, 0x0)
    Error: MEMORY_MANAGEMENT
    
    
    
    
    082610-17035-01.dmp
    
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x4E (0x99, 0x71A28, 0x0, 0x71B28)
    Error: PFN_LIST_CORRUPT
    
    
    
    082610-16192-01.dmp
    
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x50 (0xABA5804C, 0x1, 0x8292E067, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    
    
    
    
    082610-15990-01.dmp
    
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x50 (0xB3487584, 0x0, 0x8293D87B, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    
    
    
    082510-13556-01.dmp
    
    This was likely caused by the following module: ntkrnlpa.exe
    Bugcheck code: 0x1A (0x41790, 0xC080205E, 0xFFFF, 0x0)
    Error: MEMORY_MANAGEMENT
    
    
    
    
    amdxata.sys Tue May 19 20:57:35 2009 (AMD)
    What is this file doing in your system?
     
  7. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    It looks to me like it is possible that Norton/Symantec might have corrupted the file system on the hard drive. Or the hard drive is faulty. That's because all of your drivers are in excellent shape and autochk.exe was involved in one of the crashes.

    You can open an elevated command prompt. Type this command for each drive letter partition on the pc that is a hard drive letter:

    chkdsk /r C:

    Change C to the other letters when you run it for them. Let them all complete. Likely there will be some repairs made.

    ----------

    When that's all done, run this command:

    sfc /scannow

    This one won't take so long. It will replace any corrupt operating system files.

    -----------

    Test the memory modules overnight with Memtest86+ if the above hasn't seemed to alleviate issues.

    You're welcome to continue posting new crash dumps as they happen. Perhaps there will be new info to see. Good luck.
     
  8. jgro

    jgro New Member

    Joined:
    Aug 24, 2010
    Messages:
    8
    Likes Received:
    0
    Update- So i had about 2 weeks of good operation. When I was finished for the day I would just put the pc to sleep and would never have problems. Last night I accidentally clicked shutdown. This morning upon bootup I got a memory management error so when it restarted I threw in my memtest 86 disc and within 2 mins about 8% of a pass I have red on screen everywhere over 2000 errors! Where were these errors hiding the past 2 weeks? Why did a shutdown prompt these RAM problems? I have run memtest 86 before overnight with both sticks and one at a time with no negative results. Is this just a fluke or should I start shopping again for more sticks?
     
  9. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Just run the memtest several times again, and if it does show errors then either your sticks don't match well or one of them is broken.
     
  10. reghakr

    reghakr Excellent Member

    Joined:
    Jan 26, 2009
    Messages:
    14,220
    Likes Received:
    180
  11. zigzag3143

    zigzag3143 Honorable Member
    Microsoft MVP

    Joined:
    Jun 2, 2009
    Messages:
    812
    Likes Received:
    115

    As CC and RH have said re-run it and if this is a one up it wont repeat itself. You may have to run memtest on individual sticks and with known good ram on individual mobo slots

    Good luck

    Ken


    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.
     

Share This Page

Loading...