BSOD related to memory management (even after changed RAM)

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack Center - Microsoft Windows

A 0XC1 BSOD may be caused by a few factors like a failing driver that is passing bad data to the memory, or a failing physical RAM stick or a failing DIMM slot (which is a motherboard component). As you have replaced the memory lately, let us check for any failing driver at first.

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to 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. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
____________________________________________________________________________
BSOD ANALYSIS:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C1, {fffff9802882eff0, fffff9802882effc, 93c014, 24}

Probably caused by : memory_corruption ( nt!MmFreeSpecialPool+383 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffff9802882eff0, address trying to free
Arg2: fffff9802882effc, address where bits are corrupted
Arg3: 000000000093c014, (reserved)
Arg4: 0000000000000024, caller is freeing an address where bytes after the end of the allocation have been overwritten

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


BUGCHECK_STR:  0xC1_24

SPECIAL_POOL_CORRUPTION_TYPE:  24

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LOCK_ADDRESS:  fffff80002cd1400 -- (!locks fffff80002cd1400)

Resource @ nt!PiEngineLock (0xfffff80002cd1400)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff80002cd1400
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff80002bd4843 to fffff80002acd740

STACK_TEXT:  
fffff880`0795b8e8 fffff800`02bd4843 : 00000000`000000c1 fffff980`2882eff0 fffff980`2882effc 00000000`0093c014 : nt!KeBugCheckEx
fffff880`0795b8f0 fffff800`02c00390 : fffff800`02a5d000 00000000`54426d43 ffffffff`fffffd64 00000000`00000008 : nt!MmFreeSpecialPool+0x383
fffff880`0795ba20 fffff800`02f0b327 : 00000000`00000001 00000000`00000001 fffffa80`052cc390 00000000`00000006 : nt!ExDeferredFreePool+0xf4d
fffff880`0795bad0 fffff800`02f13456 : 00000000`00000000 fffff880`0795bc01 fffff880`0795bb98 00000000`00000000 : nt!PiQueryDeviceRelations+0x227
fffff880`0795bb30 fffff800`02d6f1b0 : fffff8a0`025b1cf0 fffff800`00000044 fffff880`0795bc01 fffff800`02d6f0b0 : nt!PiControlQueryDeviceRelations+0xf6
fffff880`0795bb90 fffff800`02acc993 : fffffa80`05223b60 00000000`013ae278 fffff880`0795bc60 00000000`00440088 : nt!NtPlugPlayControl+0x100
fffff880`0795bbe0 00000000`77660daa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`013ae208 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77660daa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MmFreeSpecialPool+383
fffff800`02bd4843 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MmFreeSpecialPool+383

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xC1_24_VRF_nt!MmFreeSpecialPool+383

BUCKET_ID:  X64_0xC1_24_VRF_nt!MmFreeSpecialPool+383

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