Share via

Windows 7 BSoD BCCode 19 BAD_POOL_HEADER

Anonymous
2014-01-25T18:52:28+00:00

Hello, so here is my problem.  I got a new computer, all custom built with parts by ASUS and NVIDA a few months ago, in December.  For the first while it worked perfectly, then after a few weeks or so I started getting occasional Blue Screens.  Once a couple days, but then it picked up.  I tried to find out why, getting Norton, McAfee, and Super Anti-Spyware.  I knew that some of these BSoD's were from malware, but nothing could pick it up, then I got Mawarebytes, and it got rid of it, but I was still getting Blue Screens.  I found that these usually had to do with memory, so I got and ran memtest x86+.  It found no errors after running, and had passes on my RAM.  Just yesterday my Solve PC Issues told me I needed a driver for my computer battery.  This fixed some, most of the memory errors, but I still got Blue Screens.  Blue Screens happen even when the computer is idle.  I can still start up my computer, and run Windows, so I can fix it from there.

I run Windows 7 64x

8 GB RAM

6 Core Processor

If you need anything else, I can post it.

But here is the windows recovery information.  If you need an Event Viewer event post, I can put whatever you need up.

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033

Additional information about the problem:

BCCode: 19

BCP1: 0000000000000020

BCP2: FFFFFA8007D06840

BCP3: FFFFFA8007D06950

BCP4: 0000000004110004

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

Files that help describe the problem:

C:\Windows\Minidump\012514-18782-01.dmp

C:\Users\Max\AppData\Local\Temp\WER-44647-0.sysdata.xml

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-02-06T21:40:11+00:00

    Yes, removal is fine. If you're still skeptical, set up a restore point before doing so - Windows 7 - START | type create | select "Create a Restore Point"

    Keep me updated.

    Regards,

    Patrick

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2014-02-06T05:00:18+00:00

    Not a problem, thanks for the dumps!

    We have various bug checks:

    BAD_POOL_HEADER (19)

    This indicates that a pool header is corrupt.4: kd> !pool fffffa8007d06840Pool page fffffa8007d06840 region is Unknown fffffa8007d06000 size:  160 previous size:    0  (Allocated)  Ntfx fffffa8007d06160 size:   40 previous size:  160  (Allocated)  NDCM fffffa8007d061a0 size:   b0 previous size:   40  (Allocated)  SAHC fffffa8007d06250 size:  150 previous size:   b0  (Allocated)  File (Protected) fffffa8007d063a0 size:   c0 previous size:  150  (Allocated)  FMsl fffffa8007d06460 size:  100 previous size:   c0  (Allocated)  MmCa fffffa8007d06560 size:   c0 previous size:  100  (Allocated)  FMsl fffffa8007d06620 size:  100 previous size:   c0  (Free)       MmCa fffffa8007d06720 size:   e0 previous size:  100  (Allocated)  SASC fffffa8007d06800 size:   40 previous size:   e0  (Allocated)  ReTa*fffffa8007d06840 size:  110 previous size:   40  (Free ) *MmCa        Pooltag MmCa : Mm control areas for mapped files, Binary : nt!mmThe pool block we're looking at within the page pool belongs to - Mm control areas for mapped files.

    *4: kd> !poolval fffffa8007d06840Pool page fffffa8007d06840 region is UnknownValidating Pool headers for pool page: fffffa8007d06840Pool page [ fffffa8007d06000 ] is __inVALID.Analyzing linked list...[ fffffa8007d06840 ]: invalid block size [ 0x11 ] should be [ 0x10 ]*PAGE_FAULT_IN_NONPAGED_AREA (50)

    This indicates that invalid system memory has been referenced.

    Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

    Another common cause is the installation of a faulty system service.

    Antivirus software can also trigger this error, as can a corrupted NTFS volume.

    NTFS_FILE_SYSTEM (24)

    This indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives.

    2: kd> .exr 0xfffff8800b7095a8ExceptionAddress: fffff8000306abe8 (nt!ExReinitializeResourceLite+0x0000000000000168)   ExceptionCode: c0000005 (Access violation)^^ The ExReinitializeResourceLite routine reinitializes an existing resource variable.

    With a single call to ExReinitializeResource, a driver writer can replace three calls: one to ExDeleteResourceLite, another to ExAllocatePool, and a third to ExInitializeResourceLite. As contention for a resource variable increases, memory is dynamically allocated and attached to the resource in order to track this contention. As an optimization, ExReinitializeResourceLite retains and zeros this previously allocated memory.

    -------------

    1. You have various troublesome Asus utilities installed such as Asus PC Probe, etc. Most if not all Asus software is bloatware and is known to cause issues. Please remove any and all installed Asus software ASAP.
    2. Remove and replace Norton with Microsoft Security Essentials for temporary troubleshooting purposes:

    Norton removal -https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;jsessionid=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&pvid=f-home

    MSE -  http://windows.microsoft.com/en-us/windows/security-essentials-download

    1. If you're still crashing after the above, please enable Driver Verifier:

    Driver Verifier:

    What is Driver Verifier?

    Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

    Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

    Before enabling Driver Verifier, it is recommended to create a System Restore Point:

    Vista - START | type rstrui - create a restore point

    Windows 7 - START | type create | select "Create a Restore Point"

    Windows 8 - http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html

    How to enable Driver Verifier:

    Start > type "verifier" without the quotes > Select the following options -

    1. Select - "Create custom settings (for code developers)"
    2. Select - "Select individual settings from a full list"
    3. Check the following boxes -
    • Special Pool
    • Pool Tracking
    • Force IRQL Checking
    • Deadlock Detection
    • Security Checks (Windows 7 & 8)
    • DDI compliance checking (Windows 8)
    • Miscellaneous Checks
    1. Select  - "Select driver names from a list"
    2. Click on the "Provider" tab. This will sort all of the drivers by the provider.
    3. Check EVERY box that is [B]NOT[/B] provided by Microsoft / Microsoft Corporation.
    4. Click on Finish.
    5. Restart.

    Important information regarding Driver Verifier:

    • If Driver Verifier finds a violation, the system will BSOD.
    • After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

    If this happens, do not panic, do the following:

    • Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
    • Once in Safe Mode - Start > Search > type "cmd" without the quotes.
    • To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.

    ・    Restart and boot into normal Windows.

    If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

    • Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
    • Once in Safe Mode - Start > type "system restore" without the quotes.
    • Choose the restore point you created earlier.

    How long should I keep Driver Verifier enabled for?

    It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

    My system BSOD'd, where can I find the crash dumps?

    They will be located in %systemroot%\Minidump

    Any other questions can most likely be answered by this article:

    http://support.microsoft.com/kb/244617

    Regards,

    Patrick

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-02-06T03:39:12+00:00

    Sorry it took so long for me to respond.  I can get into my computer, and here are the minidump files.  I may have had a second Bluescreen that day, but all other than this one are solved now, but this one is hard to deal with.

    Here are the minidumps.  (Using mediafire for now)

    http://www.mediafire.com/download/a6euzcxyvddlc5l/Minidumps%282%29.zip

    Was this answer helpful?

    0 comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  5. Anonymous
    2014-01-25T21:49:54+00:00

    Hi,

    In order to assist you, we will need the DMP files to analyze what exactly occurred at the time of the crash, etc.

    If you don't know where DMP files are located, here's how to get to them:

     1.    Navigate to the %systemroot%\Minidump folder.

     2.    Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

     3.    Upload the zip containing the DMP files to Skydrive or a hosting site of your choice and paste in your reply.

    If you are going to use Skydrive but don't know how to upload to it, please visit the following:

    http://www.wikihow.com/Use-SkyDrive

    Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete DMP files upon use.

    If your computer is not generating DMP files, please do the following:

    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.
    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

    1. Double check that the WERS is ENABLED:

    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

    If you cannot get into normal mode to do any of this, please do this via Safe Mode.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments