This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Multiple PCs frozen right after update.

Over the last couple weeks, since we received the Core Agent update to 2.19.8 on 10/4, we've had multiple older machines freeze completely.  Screen freezes, no keyboard or mouse, NIC unresponsive.  We have to do a hard shut down to bring them down and back up.  Not positive that this update is the culprit, but on the computers that have been freezing 2 to 3 times a day, we uninstalled Sophos and they've been behaving for a couple days now. 

Models affected:  HP xw4400, HP xw4600, Z400.  All have been running Win10 21H1 with last update back in September.  "Newer" computers (e.g. Z420, Z4 G4) have not had this problem.  Event logs show nothing out of the ordinary around the time of crash.  

Just curious if anybody else has run into this in the last week.    



This thread was automatically locked due to age.
  • Hi Jtorres

    Thanks for your checking!

    it is the first PC nothing relate to Broadcom Netxtreme in this case.

  • We are having the same issue with HP 6000 Pro SFF with Intel Nics. About 48 computers with the issue since October.

  • Same here.  HP 6000 Pro SFF as well.  I have one person that it specifically freezes at roughly 11AM and 2PM every single day and moved with her to a different computer (same model).  I have others that it hasn't happened to a single time yet.  I have verified if the Real Time file scanning is disabled, the issue stops occurring.  Anyone have any fixes for this yet?

  • Instead of turning off real-time scanning, it would be interesting to know if excluding the C drive has the same outcome with realtime scanning enabled.  E.g The drive C:

    If that helps, then that would at least prove there is a workaround with an exclusion, even if the next step is something like:

    C:\windows\

    or

    C:\users\

    or

    C:\programdata\

    The trailing backslash is required to mean the directory.

  • I added an exception for C:\Windows\System32\Drivers but didn't know about the trailing backslash so I just added that and will wait and see what happens (It didn't help without the trailing \ for obvious reasons).  Then I will back it up a level to System32 then windows and so on I think.

  • Trying something a little different and I haven't had a crash on the computer for 24 hours, when it typically has been happening twice a day.  Previously, I had this test computer running for over a week with network debugging hoping to catch something.  It was just running idle, headless, and not being used the whole time and never crashed.  As soon as I started using it as an RDP client, it began crashing frequently.  I notice that it never crashes at night when not in use.  I currently have all peripherals unplugged and am remoting into it from another computer.  I'm then remoting from there into my work computer so that I'm using all the same software and services all day like I've been doing previously when it was crashing, except there is no direct input from mouse/keyboard.  It's a long shot, but more and more computers are crashing and it's getting ridiculous. 

  • Still happened around 2pm with the drivers folder exception so I went ahead and switched it to C:\.  We'll see how it goes.

  • We have narrowed it down.

    Disabling Endpoint Defense by renaming the .sys file corrects the lockup problem but the HitmanPro and A-V settings are irrelevant

  • After doing an exception for the entire c:\ it still froze...

  • when I read the Exceptions you have to use C:\**

    double star for all folders and files