Windows 10: Help, cant get past bad_pool_caller and kernal_mode_heap_corruption errors

So I was recently trying to see if my drivers for my cpu were correct for reference I have a ryzen 5 2600 so I went to there website and downloaded what looked like some sort of driver thing called StoreMI. basically, I had uninstalled Ryzen Master to see if this StoreMI was anybetter for my system as my cpu seemed to be running kinda slow recently. Long story short, My pc gave me the blue screen with the error code bad_pool_caller. I went into safe mode to delete the file I had just downloaded and also undeleted ryzen master. still getting an error code switching from bad_pool_caller and ke

:)

 

Bad_pool_caller

Hi Donald,

BAD_POOL_CALLER is a blue screen error that happens whenever your PC encounters something that it can't process. This error will make your computer crash to prevent further damage to your system. For us to be able to isolate the problem, kindly answer the
following questions:

• Did you make any changes to your computer prior to the issue?
• Does the problem persist after restarting your computer?
• Have you taken any troubleshooting steps so far?

We recommend that you check this
article and follow the steps provided on how to troubleshoot blue screen errors in Windows 10.

Keep us posted and we'll be willing to assist you further.

 

Kernal_Mode_Heap_Corruption

Hi there,

Getting a Windows 10 Bluescreen - Kernal_Mode_Heap_Corruption

Minidump link below.

minidump.zip

Any help would be much appreciated.

 

Bad_Pool_Caller


I have read quite a few "Bad_Pool_Caller" posts and none that I've read have been any help. It really is getting frustrating; as many as three times in a day. I've tried safe mode, but couldn't figure anything from that. In fact as I write here I'm expecting a crash. Jeez this really is a backward step. I don't remember windows 3 crashing like this with no explanation as to what is causing the crash. I have a Dell Studio 1747 laptop (six years old now). I installed a 240GB SSD drive a week or so ago. I can't remember if I had these BSOD's with the old drive. I've attached the suggested system file from previous posts. I notice ads to repair this problem, but hesitate to try them; any suggestions on that.

Thanks, Allan