bad_pool_header

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

Code:

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

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

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

Code:

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.

Yes, do it.

Code:

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.

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.