ATI Catalyst 6.6 + CPF + games = BSOD

I keep getting a BSOD whenever I try to run any full screen game with CPF running. Every BSOD points to different ati driver files (didn’t write them down unfortunately). This problem has not happened with the latest Sunbelt-Kerio PF 4.3.912.

Observances:

  • Running the latest ATI Catalyst 6.6 for IGP.
  • The problem was noticed on an AMD ATI Xpress 200 motherboard with the integrated graphics solution (X300).
  • If I turn off “Monitor process injections” and “Monitor DLL injections” it does not happen.
  • Adding component rules for the DLLs of the games tested makes no difference whatsoever.
  • The system has all latest driver updates and latest Windows updates.
  • From what I was able to read on the BSOD (before it rebooted) it seems like if it’s a new variation on the infinite-loop problem.

I am also running an ATI Express 200 mobo (non-IGP) with an ATI X1600XT. I have also installed the 6.6 Catalyst.

Typically I had updated my Catalysts overtop of the existing, but this time (I think because of something I had read) I had fully uninstalled the 6.5 Catalyst before installing 6.6.

If you didn’t uninstall 6.5 first, you might want to try a uninstall/reinstall. I don’t have exactly your hardware, but I haven’t had any BSOD issues with Catalyst 6.6 and CPF.

Some other thoughts…

I will also mention that CPF is the only Real-Time Comodo product I am using so far. I would like to use CAV as well, but have had a problem getting the Real-Time monitor to load. I have noticed that some posts about CAV are about a slowness… or long access on files when there is a CAV “conflict” with another antivirus or real-time scanner like antispyware. Are you using CAV?

The only “problem” I’ve had with some full screen games is that the firewall “training prompts” can get bried under the application window. Occassionally Alt-Tab or Ctrl-Esc will work but not always… I’m wondering if you’ve had the opportunity to train CPF for the game(s), or if the BSOD happens when trying to access the “training prompts”…

The machine is a Compaq Presario SR1620NX. Unfortunately, unless I reinstall the OS myself, if I uninstall the drivers it will automatically reinstall the factory drivers. Getting rid of the .inf files in the windows folder makes no difference. I’m currently studying how to prevent this from happening.
If it weren’t for the software licenses that come with it, I’d just as soon do a clean install of WinXP.

After having a few problems with the temps on this PC, I decided to take it apart yesterday. I put some Arctic Silver 5 on both the CPU and the northbridge and viola` the temps are down and I haven’t noticed any more BSODs with “Monitor process injections” and “Monitor DLL injections” enabled in CPF.

Blame it on being poorly built. Luckily it’s my dad’s PC.

In any case, to answer your question m0ng0d, no, it happened after a few seconds into the games. Strangely, the quickest game to give a BSOD was Heroes of Might and Magic 4 which is a 2D game. Even when trying the HoMM5 demo it took a bit longer before it BSODed. Any other games still took less than a minute into the game to BSOD.
The games were never tried in multi-player.

I have the impression that CPF is designed to be very tight in using CPU cycles and so puts a bit of extra stress on the system bus. That’s the only think I can figure out as far as cause of it facilitating BSODs. Actually, I have noticed that when accessing the NIC the temps on the northbridges of all the PCs where I have CPF installed goes up by 1-2 degrees C.
I must say though that CPF is the absolute FASTEST software firewall I’ve tried so far, and yes it may use just a tad bit more CPU but it’s well worth it and the system is generally snappier.

Maybe a developer can confirm my observation regarding how CPF is optimized.

Glad to here you squashed your problem… lets just hope it stays squashed. ;D