bad_pool_header

[dcfc79]

Hi everyone, I would like to know if this BSOD is fixable. Its done the BSOD 3 or 4 times since yesterday, I didn't manage to catch what it said at the top of the screen until earlier today.

Are there any other details I need to provide just let me know.

Thanks for your help

 

[Arc]

BugCheck 4E, {2, 661, 11fdff, 1}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8d )

Followup: MachineOwner
---------

BugCheck 19, {3, fffff8a00ded27d0, fffff8a00ded27d0, fffff8a002ed27d0}

Probably caused by : Pool_Corruption ( nt!ExFreePool+76b )

Followup: Pool_corruption
---------

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[dcfc79]

Thanks for your help Arc, I did the memtest and no errors were found, tried the driver verifier until another BSOD happened again. The latest BSOD that happened was something like " Page fault in non-paged area ". Should I do another
DM Log Collector ?

 

[Arc]

Yes, do it.

 

[dcfc79]

Here's the Log Collector

 

[Arc]

fffff880`085e6618  fffff880`03e2fd01Unable to load image \SystemRoot\system32\DRIVERS\eamonm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for eamonm.sys
*** ERROR: Module load completed but symbols could not be loaded for eamonm.sys
 eamonm+0x1bd01

Uninstall ESET as a test basis. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

See how it goes. Let us know.

 

[dcfc79]

Hi, have posted another Log and also got rid of Eset, replaced with Mse and installed MBAM.

Thanks.

 

[Arc]

Its a clueless MEMORY_MANAGEMENT (0x1A) BSOD.

Test your RAM modules for possible errors, one more time.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Take a camera snap of the memtest86+ screen before you close it, and let us see that screen. We need to see it.

 

[dcfc79]

What does a clueless MEMORY_MANAGEMENT (0x1A) BSOD mean ?

Ah i should have taken a pic of the memtest when I first ran it.

 

[dcfc79]

Attached is the photo of the latest memtest I ran.

 

[Arc]

What does a clueless MEMORY_MANAGEMENT (0x1A) BSOD mean ?

Ah i should have taken a pic of the memtest when I first ran it.

MEMORY_MANAGEMENT (0x1A) is the code of the BSOD.
Clueless means it is not pointing to anything.

Attached is the photo of the latest memtest I ran.

15 passes is a confirmation that RAM is not causing the issue at all.

So let us give driver verifier another go.

 

[dcfc79]

I did the driver verifier and let it run.

The last BSOD mentioned IRQ_not_less_or_equal, might have been IRQL.

 

[Arc]

I did the driver verifier and let it run.

The last BSOD mentioned IRQ_not_less_or_equal, might have been IRQL.

Blue Screen of Death (BSOD) Posting Instructions

 

[dcfc79]

Done the test and attached it.

 

[Arc]

Driver verifier blames memory, too.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8002403690
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:
------------------

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

So it is not a driver issue. Either your RAM are mismatch with the board or it is something to do with the motherboard itself.

 

[dcfc79]

When you say mismatch do you mean the RAM isn't compatible with the board ?

Thanks

 

[Arc]

Yes, the probability may remain there.

 

[dcfc79]

Thanks, ill double check the ram is compatible with the motherboard.

 

[Arc]

Then one possibility remains ... the motherboard itself. And unfortunately we cannot test the motherboard.

 

[dcfc79]

Thanks, have checked and the ram is compatible with the board, Ill get another stick of ram and see if it helps.

This is the motherboard

and this is the memory