BSOD Memory_Management

Code:

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8800c98d5b8, The pool entry we were looking for within the page.
Arg3: fffff8800c98da78, The next pool entry.
Arg4: 000000000d4c49b0, (reserved)

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

So you need to enable Driver Verifier to monitor the drivers at this stage.

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.

Driver verifier detects memory corruption.

Code:

BugCheck C1, {fffff980102f2fe0, fffff980102f2274, 910018, 32}

Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 )

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

Code:

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff980102f2fe0, address trying to free
Arg2: fffff980102f2274, address where one bit is corrupted
Arg3: 0000000000910018, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error

No guilty party is revealed, nothing in the raw stacks, too.

So it may not be a driver caused BSOD. Let us look at the RAM now. 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.

Let us know how it goes. It would be the best reporting if you can take a camera snap of the memtest86+ screen before closing it and upload the picture here.

It is a memory error, as the dumps are reporting.

Driver verifier is not finding any driver causing it.

Memtest is not causing any memory failure.

So, another possibility is .... mismatch RAM.

Your 10 GB RAM consists of two sticks; one 8 GB and one 2 GB.

Code:

  Physical Memory Array Handle  000bh
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   0dh - SODIMM
  Device Set                    [None]
  Device Locator                ChannelA-DIMM0
  Bank Locator                  BANK 0
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1600MHz
  Manufacturer                  8502

Code:

  Physical Memory Array Handle  000bh
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          2048MB
  Form Factor                   0dh - SODIMM
  Device Set                    [None]
  Device Locator                ChannelB-DIMM0
  Bank Locator                  BANK 2
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1600MHz
  Manufacturer                  Hynix/Hyundai

As those sticks are from different manufacturer, there remains a chance that they may not work properly with each other. RAM should be bought in a KIT, a couple or more sticks tested to work together.

Remove either one, see how the computer is running with the remaining one.

You are welcome, Paul. Let us know for any further issue.