I rebuilt my computer and still getting the same error. RAM related?

[Kickflapper]

I rebuilt my computer recently and I continue to get a "bad_caller_pool" error and occasional crashes. I had been getting errors prior to changing CPU, motherboard, GPU, and clean reinstall of windows 10. The parts that I kept were the power supply (older 750w coolermaster 80>), SSD (newer samsung 850 evo) and RAM which is a older Crucial 2 x 8 1600hz set. This error seems to occur when I'm multi-tasking and using the internet. I am updated and have current drivers. Has anyone had this problem and does this relate to my RAM? Any help is always appreciated. Thank you

[ddrkreature]

Here is what I found about the blue screen message:

 

Spoiler

BAD_POOL_CALLER is a stop error message that is caused because of problems with the memory management.

There is a list of more than thirty such causes that can give you this error message. If the stop error is consistent every time the system is rebooted, the following method will be effective in solving the problem:
* The hardware and RAM should be checked initially.
* Boot the system once again using the OS setup CD, or use a boot setup that has a GUI like BartPE.
* With RunScanner it is possible to use a memory test tool.
* Select a single account
* If all the accounts open then the system registry hive might be the problem.
* Locate the hive damaged and rename it, do not delete it.
* Create another hive from the backup or from the restore point.
* Initially uses the latest one and keep checking the restore points that come later.
* Avoiding harvesting any replacement hives from the hard drive booted Windows.
* After which compare the hives for differences.

This is one of the ways of fixing BAD_POOL_CALLER errors. Another method is to reinstall the OS but occasionally shows a disk read error or an error on the same lines. Switching the computer off for a minute or more and then switching it on can solve it since the error is only a slight glitch in the system operation.
The BAD_POOL_CALLER is seen for the first time after installing a hardware or software it is recommended that the computer be restarted. If it doesn’t solve the problem, the installation of the hardware or software should be checked for corrections. If the problem persists the installed hardware and software should be disabled, and the BIOS memory options like caching or shadowing should be disabled too. 
The safe mode can be used as well to remove or stop components.
To enable the safe mode just press F8 when the machine is being restarted and select it from the Advance Startup options and correct the problem. The installation of the graphics card is another reason the BAD_POOL_CALLER error shows up. A simple reinstallation of the driver can solve the problem. 
Microsoft has also acknowledged that the BAD_POOL_CALLER Stop 0xC2 error pops up when trying to print a document that contains a corrupt font.
A hot fix is available at www.support.microsoft.com

 

http://www.fixya.com/support/t17266430-bad_caller_pool_windows_7

Hope it helps a little bit for you

[Mark77]

Sounds software-related to me (see above), but maybe try pulling one stick of RAM, and running that way for a while.  On a single 8gb stick.  And then swap the single stick for the other one.  See if anything's different. 

[porina]

I'd try a hardware stress test initially. Do some passes of memtest then let prime95 stew on it for a bit. 

[xwrench3]

seems like there is a windows self test for ram memory. i did it a while back on my old computer parts prior to my own major rebuild. i bought new ram though. ddr2 was not going to work where ddr4 was needed. i am sure someone on this forum knows how to get you into the windows self check test. i know it is SOMETHING LIKE chkdsk, scannow,  or msconfig. it might even be one of those. i was following orders. you have to open the command prompt to use them. and i would not recommend just running those without knowing what they do.