Crashes under Windows 2003 SP1

Discussion in 'LnS English Forum' started by Kran, Sep 19, 2005.

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

    Kran Guest

    Hi all,

    I have tested LnS 2.05p2 (base install) under w2003-SP1 and here are some results:
    - do not seem to crash with base 2.05sp2 version, standard settings (no advanced option such as DLL, stateful TCP, etc.)
    - seem to crash when using an advanced option (DLL, stateful TCP, etc.)

    With the supplementary patches for lnsfn(1).sys:
    - crashes (bsod) are VERY frequent with these latest patches. Cannot almost use the computer.

    - I am using also CfosSpeed; seem like the interaction between these 2 programs is unstable? (After having installed CfosSpeed, I had to reinstall everything from the start because LnS was crashing at every reboot. Then reinstalled everything from scratch carefully. Worked fine until I activated the advanced options. I reverted back to standard options but am still anxious about server crashes).

    Crash info:
    - Lnsfn1.sys : base BAE8469B at BAE77000 datestamp 413E0419

    Have you got some tips for W2K3 so that I can use it under this system without fear.

  2. Frederic

    Frederic LnS Developer

    Jan 9, 2003

    Probably the features causing this issue are:
    - watch thread injection
    - watch DNS Calls
    - the new ones from the new lnsfw1 beta driver activated with the registry

    Perhaps you have a processor with the Nx bit/DEP protection ?
    In that case you will find some related topics:

    Otherwise, could you send us ( a minidump file (these files are created in c:\windows\mnidump) and join us also the lnsfw1.sys file you were using when you got the BSOD.


  3. zoes

    zoes Registered Member

    Jun 10, 2005
    I use windows 2003 server too。
    My experience is if you open the follow features,the BSOD is occure.
    - watch DNS Calls
    - DLLs detect.

    Only one of this is opened,the BSOD must occure.
  4. Stelios

    Stelios Guest

    I'm experiencing the same problems with win2k3 sp1 and cause of this , i have to use outpost firewall .

    After reading some threads , i'm gonna try again but this time i will disable "thread injection" and the DNS thing.
  5. kaishaku

    kaishaku Registered Member

    Jan 19, 2006
    You need to disable DEP in Windows 2003 SP1 if you want
    your machine to run applications like it used to. Otherwise,
    you will find many apps crash, especially those written by
    kick*ss programmers.

    Disable DEP in Windows 2003 SP1 and beyond by editing
    the boot.ini file as follows:

    C:\>notepad boot.ini
    Change the /NoExecute line to:

    Your machine will now act more like it used to.

    If you have no such line then you have not installed a
    DEP-capable version of Windows or I suppose your processor
    does not support DEP.

    I have not tried LnS, but I have lost two Win2k3 installs
    due to Kerio 2.1.5, so now I am trying to be very certain
    my next firewall supports Win2k3.
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.