Symantec writes about it.Įndpoint Protection Client gets a Blue Screen Of Death (BSOD) BAD_POOL_CALLER (c2) or KERNEL_MODE_HEAP_CORRUPTION (13A) Symantec released an official support article TECH256643 on Octoconfirming the bug. The other solution is to block the buggy update for Symantec SEP. If you can stop the BSOD with a FW, then your system is up… IMHO. One suggestion from a user was to block communication with in the firewall.ĭid anyone try a temp FW block to ""? I'd think it would be way too much work to manually touch all your systems to roll them back/forward. It would Blue Screen before we could do anything so we had to safe mode and clean wipe.Īnother user suspects a connection with a faulty IPS Signature R61 and writes that the TECH256643 Signature R62 fixes this. A user describes how he got out of the situation by safe mode and uninstalling the update from the BSOD loop. Windows servers are also affected and are restarting randomly. So the problem occurs while deDas seems to affect all Windows versions – there are postings for Windows 7, Windows 8.1 and Windows 10. The BSOD occurs before they can do or verify anything. After a Symantec SEP update on October 14, 2019, a user got BlueScreens on his machines. Within the Symantec forum this thread, titled BSOD caused by SEP update? a user posted to a discussion at reddit. I didn't have time to post yesterday, hence the post. Judging by the tweet above, Symantec has already admitted the problem. This probably affects all Windows versions. There are BlueScreen issues with Symantec Endpoint Protection (Symantec SEP). Symantec acknowledges that the Endpoint Protection client is throwing bluescreens BAD_POOL_CALLER (c2) or KERNEL_MODE_HEAP_CORRUPTION (13A). But I had already noticed it via the following tweet from Woody Leonhard. informed me yesterday afternoon about the issue via mail (thanks for that).
0 kommentar(er)
