I have a new bad_pool_caller error that keeps causing BSOD.
Type: Posts; User: xsilicon9
I have a new bad_pool_caller error that keeps causing BSOD.
Thanks. Windows 10 has way too many BSOD over minor things.
I'm getting another BSOD error.Bad_Pool_Caller. Seemed to be caused by tcpip.sys,ntoskrnl.exe,ndis.sys. Information attached.
I uninstalled ESET smart security a few months ago. I use Bitdefender now. I guess I need to manually delete those leftover eset files.
I'm getting random BSOD errors from three different files every few days or so. fwpkclnt.sys/ntoskrnl.exe/tcpip.sys
They seem to happen at random times.
Okay, I will continue if the problem comes back. it just happened yesterday. But I entered safe mode and ran malwarebytes and roguekiller. They found a bunch of malware that bitdefender missed....
Now I have another problem. Do I need to start a new thread? I'm getting ntoskrnl.exe BSOD and high cpu usage for DWM.exe.
So far so good. Looks like that was the problem. Thanks
This BSOD error seems to happen randomly every few weeks or so.