kerio 2.1.5 fwdrv.sys BSOD ?

Discussion in 'other firewalls' started by Mucus, Dec 11, 2007.

Thread Status:
Not open for further replies.
  1. Mucus

    Mucus Registered Member

    Joined:
    Dec 11, 2007
    Posts:
    2
    So, everyone here know about kerio 2.1.5 fwdrv.sys BSOD...
    For some reason it suddently started happening to me. No apparent reason (not that I know of), might BSOD when computer just idling. I've read all around Internet, but haven't found a cure. This seemed a best place to ask, anyone know medicine for the cursed fwdrv.sys?
    BSOD happens every 4 days or something. No perfectdisk, never had.
    Hopefully this isn't forgotten thread :)
     
  2. Jarmo P

    Jarmo P Registered Member

    Joined:
    Aug 27, 2005
    Posts:
    1,188
    Re: How to Optimize Security in Kerio 2.1.5 -Learning Thread 3

    I have not heard kerio 2.1.5 causing a blue screen of death.
    It had some problem with fdisr or perfectdisk I think, but I have never used those programs.

    A new thread would be more likely appropriate though so someone knowledgeable could see your problem by just reading the header.
     
  3. Mapson

    Mapson Registered Member

    Joined:
    Dec 29, 2005
    Posts:
    54
    In the registry change all values for "MaxBufferSize" under keys "CurrentControlSet\Services\fwdrv" to at least 8000
     
  4. Allen L.

    Allen L. Registered Member

    Joined:
    Sep 1, 2004
    Posts:
    335
    Location:
    -Close-
    I've seen that it is preferred to set at 16000 or even a bit higher.
     
  5. Mucus

    Mucus Registered Member

    Joined:
    Dec 11, 2007
    Posts:
    2
    thanks. I try that "MaxBufferSize" change. Kerio 2.1.5 is the best firewall I've seen, would be shame if I had to change firewall.

    Jarmo P: Try google "kerio 2.1.5 fwdrv.sys bsod" you find many others.
    If the MaxBufferSize doesn't help, I post a new thread. ( I just found this by google and didn't check out the whole forum )

    Edit: Someone made it new thread...
     
Thread Status:
Not open for further replies.