Latest F-Secure BSOD on Windows 11 24H2

Zorglubxx
Zorglubxx Posts: 2 New Member
in Device Protection

I have been running the Ziggo-branded version of F-Secure for years without issues. Suddenly around April 9th my computer started getting BSOD with error BAD_POOL_CALLER 0xC2. It just wouldn't stay up for more than an hour. Looking into the memory dump file I could see that the error was often in tcpip.sys and ndis.sys drivers so I started uninstalling things that accessed the network like VPN etc. When I finally uninstalled F-Secure the reboots stopped and computer has been stable again.

So something to do with latest Windows Update + F-Secure around that date. Any ideas? I'm scared to re-install again.

Like Awesome

Answers

  • Ukko
    Ukko Posts: 3,817 Superuser

    Hello,

    I think they will advise you to contact Ziggo support since you are using a branded solution.

    This can actually help - because their Support are most likely certified to accept diagnostic data from you, for example, such as fsdiag; And then somehow continue to investigate the problem even if with F-Secure directly.

    But, just because sounds that such a BSOD can be related with some F-Secure Browsing Protection or whatever things - I do not recall any recent mentions of something like this. Thus, maybe an attempt to install most recent build of Ziggo's branded solution is the only way to check if you still can to reproduce it. And if so - then to contact Ziggo's Support with some created diagnostic files (I am not sure how with branded solution, but mainly you can find it in F-Secure Settings : Support tab : Run 'Support Tool' - it should generate .zip file) with some dumps (if any).

    Thanks!

    Like Awesome
  • Jasper1900
    Jasper1900 Posts: 2 New Member
    edited April 17

    I have had exactly the same problem on two different PC's, but with the KPN branded version.
    Both on Windows 10 and Windows 11.

    Windows boots fine, I can even login. But after about 2-5 minutes BSOD.
    When I disconnect the ethernet cable the computer keeps running fine.

    I managed to solve the problem by reinstalling the latest network drivers for my on-board ethernet controller.

    But I'm pretty sure the root cause is F-secure that corrupts the network stack.

    Like Awesome
  • Zorglubxx
    Zorglubxx Posts: 2 New Member

    Sounds indeed like the same problem. I did look if Intel had newer drivers for mine, but no. Which brand is yours?

    Like Awesome
  • Jasper1900
    Jasper1900 Posts: 2 New Member

    One PC had a Realtek NIC the other is an Intel I219-V on a MSI motherboard.
    I downloaded and installed the Intel drivers from the MSI support site, these are pretty old (2021 ), but it still solved the problem.
    So I think the version doesn't really matter, I think just reinstalling the same drivers will also solve the problem.
    If you're really looking for newer drivers you can probably download them from the Intel website.

    1Like Awesome

Categories