Random crashes with LnS 2.05p3

Discussion in 'LnS English Forum' started by chaosblade, Feb 17, 2006.

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

    chaosblade Registered Member

    Joined:
    Dec 30, 2005
    Posts:
    18
    Location:
    Israel
    Hi there,

    Lately, After using LnS for awhile (was 2.05p2) i started getting some crashes recently. Windows would suddenly go blue screen, with "STOP 0x00000005" or similar messages. Examining the minidumps created afterwards shows that the last calls made were to both to the lns .sys file, and the wanarp.dll driver.

    I tried upgrading to the p3 version available here on the forums, with no luck. I have not tried any other beta drivers for LnS or such, so im not sure if these might fix my issues. I'll be happy to test if newer builds\drivers are offered.

    Other interesting applications running at the time were cFosSpeed (traffic shaper) and Kaspersky AV 2006 beta.

    PS: LnS is the best firewall ive used, in terms of personal experience. Thanks alot for your dedication to it ;]
     
  2. tosbsas

    tosbsas Registered Member

    Joined:
    Feb 9, 2002
    Posts:
    789
    Location:
    Lima, Peru
    Have you enabled thread injection? Or check dns calls?

    And have you enabled wanarp in the protocol settings?

    Ruben
     
  3. chaosblade

    chaosblade Registered Member

    Joined:
    Dec 30, 2005
    Posts:
    18
    Location:
    Israel
    I dont believe so, I havent enabled them myself so if the defaults are off than thats how it is - At least for the beta features such as "Watch Thread Injection" and such.

    WANARP in the protocol settings? You'll need to clarify this im afraid ;]
    I havent messed with specific TCP\UDP protocol settings, more or less just adding TCP\UDP\ICMP rules to cater for my applications.
     
  4. tosbsas

    tosbsas Registered Member

    Joined:
    Feb 9, 2002
    Posts:
    789
    Location:
    Lima, Peru
    I think check dns calls is enabled by default

    Wanarp is:

    options - advanced -protocols - by default you can see there ntbt.sys and tcpip.sys. I had to add wanarp.sys by writing it in the field on top of new and press new - than activate filter and restart

    Ruben
     
  5. chaosblade

    chaosblade Registered Member

    Joined:
    Dec 30, 2005
    Posts:
    18
    Location:
    Israel
    Well, The connection\modem is recognized by windows as USB WAN ADSL Adapter, So i suppose i need it aswell.
     
  6. tosbsas

    tosbsas Registered Member

    Joined:
    Feb 9, 2002
    Posts:
    789
    Location:
    Lima, Peru
    try it :)-)
     
  7. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
    Hi,

    You said you examined the minidump, but what was the involved driver exactly: lnsfw1.sys or lnsfw.sys ?

    Could you send us on of the minidumps you got (at lnssupport@soft4ever.com) so we can investigate a little more.

    Thanks,

    Frederic
     
  8. chaosblade

    chaosblade Registered Member

    Joined:
    Dec 30, 2005
    Posts:
    18
    Location:
    Israel
    Sadly, The only minidump i have left is not the one i examined earlier, must have gotten deleted by me or some program i use. I've sent this one in hope it might tell you anything, but it seems too general this time.

    I'll be sure to post on if it happens again. I've removed WANARP.sys from the protocol list in order to mimic the old configuration.
     
  9. chaosblade

    chaosblade Registered Member

    Joined:
    Dec 30, 2005
    Posts:
    18
    Location:
    Israel
    Sorry for doublepost. Seemed appropriate with that older one.

    Anyway, Crashed about three more times, This time i saved the crashdumps, sending them over now.
     
Thread Status:
Not open for further replies.