Driver Troubles

Discussion in 'LnS English Forum' started by aneurism, Jun 27, 2005.

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

    aneurism Registered Member

    Joined:
    Jun 27, 2005
    Posts:
    10
    Location:
    Seattle, WA, USA
    Hi! I love this program. Runs like clockwork on my in-vehicle PC.

    Unfortunatley, on my laptop the driver seems to be causing a bluescreen hard failure and memory dump.

    Windows reports home and they say that your driver caused it.
    how do I find the core dump? Do I need too?

    Any ideas?

    Here is the system information;

    OS Name: Microsoft Windows XP Professional (Media Center)
    OS Version: 5.1.2600 Service Pack 2 Build 2600
    OS Manufacturer: Microsoft Corporation
    OS Configuration: Standalone Workstation
    OS Build Type: Multiprocessor Free

    System Manufacturer: Hewlett-Packard
    System Model: Pavilion zd8000 (PR315UA#ABA)
    System type: X86-based PC
    Processor(s): 2 Processor(s) Installed. (not really, it just thinks so)
    [01]: x86 Family 15 Model 4 Stepping 1 GenuineIntel ~
    3194 Mhz
    [02]: x86 Family 15 Model 4 Stepping 1 GenuineIntel ~
    3194 Mhz
    BIOS Version: HP - 6040000
    Windows Directory: C:\WINDOWS
    System Directory: C:\WINDOWS\system32
    Boot Device: \Device\HarddiskVolume1
    System Locale: en-us;English (United States)
    Input Locale: en-us;English (United States)
    Time Zone: (GMT-08:00) Pacific Time (US & Canada); Tijuana
    Total Physical Memory: 510 MB
    Available Physical Memory: 216 MB
    Virtual Memory: Max Size: 2,048 MB
    Virtual Memory: Available: 2,001 MB
    Virtual Memory: In Use: 47 MB
    NetWork Card(s): 3 NIC(s) Installed.
    [01]: Realtek RTL8139/810x Family Fast Ethernet NIC
    Connection Name: Local Area Connection
    Status: Media disconnected
    [02]: Broadcom 802.11b/g WLAN
    Connection Name: Wifi
    DHCP Enabled: Yes
    DHCP Server: 10.1.6.29
    IP address(es)
    [01]: 10.50.151.191
    [03]: 1394 Net Adapter
    Connection Name: 1394 Connection
    DHCP Enabled: Yes
    DHCP Server: N/A
    IP address(es)
     
  2. aneurism

    aneurism Registered Member

    Joined:
    Jun 27, 2005
    Posts:
    10
    Location:
    Seattle, WA, USA
    Maybe I should expand on my earlier post. After installing L&S, rebooting and all L&S doesn't think that I am online. I am connect via the broadcom 802.11b/g to a wifi gateway. Also not automatically selected. I did read through the faq's downloaded a couple of files that were sugested for somewhat similar problems. Manually selected the correct NIC and internet filtering starts to work. However on the welcome page the connected box is still unchecked. No application filtering though. No auto detect on internet capable program at startup either. Haven't tried manually adding any yet. Not long after I get the blue screen of death telling me of a hard failure and proceeds dump the memory after which it reboots.
     
  3. WSFuser

    WSFuser Registered Member

    Joined:
    Oct 7, 2004
    Posts:
    10,632
    im not sure what is causing ur problem but if windows created a dump file it should be located in %SystemRoot%\Minidump aka C:\Minidump
     
  4. aneurism

    aneurism Registered Member

    Joined:
    Jun 27, 2005
    Posts:
    10
    Location:
    Seattle, WA, USA
    Thanks for the reply WFSuser. Nope nothing there.

    Just thought to try something on the system that L&S is working on. What I did was disconnect from the internet with the Verizon Wireless Aircard and connect using an 802.11b Wifi Card. Guess what, yup you got it no connection detected nor did it automaticly detect and select the NIC. As for the blue screen I don't know. I certainly don't want to crash that system so I imedeately terminated my experiment. Does anyone know why L&S wouldn't work with a wifi connection?
     
  5. WSFuser

    WSFuser Registered Member

    Joined:
    Oct 7, 2004
    Posts:
    10,632
    wireless connection seem tricky in general, i tried searching the forum to help answer ur question and i found a post where a person couldnt use their wifi with nod32. neways maybe u could try running WinSock XP Fix
     
  6. aneurism

    aneurism Registered Member

    Joined:
    Jun 27, 2005
    Posts:
    10
    Location:
    Seattle, WA, USA
    Okay, I d/l'd and ran the fix. On reboot L&S showed an empty field in the Options/Network Interface. had to uninstall and reinstall L&S to restore it's registry entries and get it to see them again. No luck still thinks i'm not connected and no selection of the NIC.
     
  7. aneurism

    aneurism Registered Member

    Joined:
    Jun 27, 2005
    Posts:
    10
    Location:
    Seattle, WA, USA
    Okay I have found a solution for the wifi problem. LnS Support informed me that the reason that LnS didn't think it was connected and the NIC wasn't being selected is do to the Option/Advanced Option/Network interface autodetect, IP to exclude list was telling LnS to exclude anything that had an IP address starting with 10. and since my ip address at that time started with 10 then it was excluded. Excellent idea really. you can regulate traffic on the NIC to the internet exsclusively while leaving your internal network alone.

    As for the Application filtering I d\l\d the LnsRegPatch.exe and though it does seem to have stabalinzed the system, no more blue screens, LnS still isn't filtering applications. So any trojan horse that makes it in has free reign. :(
     
  8. aneurism

    aneurism Registered Member

    Joined:
    Jun 27, 2005
    Posts:
    10
    Location:
    Seattle, WA, USA
    I may have spoke to soon. No BSOD this time but what did happen was really wierd.

    The same errors that happened before the BSOD and Memory dump
    happened twice more. What's wierd is that this time no BSOD but had to cut
    power in order to reboot.
    After the first time voula! Aplication filtering starts working. after the second time it not only still worked but started catching things I haven't seen caught on my other system. :eek:
    For example:
    LSA Shell (Export Version)
    Application layer Gateway Service

    This time I had time to write things down before a reset, the LSA Shell was
    one of the programs that had an application error. Another was svchost.exe
    and winlogon.exe. There was also an alert telling me MCI command error
    handling winlogon

    All four alert window wanted to shut the respective apps down and contained
    this error message;

    The instruction at "0x7c8f3f5f" reffered memory at "0x7c8f3f5f" the memory
    can't be "written"

    Attached are text file containing what information I know how to extract
    from the dump files as well as the minidump file related to the crash and
    BSOD

    I would love to attach the memory dump file but I don't think anyone would appreciate a 510 meg file. So I will just attach the minidump file. I do have a debugger but short of the !analize -v and lvm commands I am lost right now. So if you need or would like me to extract any info from the big file just let me know and how to get it for you.

    It's nice that it seem to be working now but WTF?

    Any ideas?
     
  9. aneurism

    aneurism Registered Member

    Joined:
    Jun 27, 2005
    Posts:
    10
    Location:
    Seattle, WA, USA
    Oh yeah the files? I hope :rolleyes:
     
  10. aneurism

    aneurism Registered Member

    Joined:
    Jun 27, 2005
    Posts:
    10
    Location:
    Seattle, WA, USA
    Well i thought I had attache the files.. I will try one more time and if they aren't here would someone please tell me the proper way to do it? Seemed pretty straight forward.

    I see. they are too big. 109.8 for the output textfile of what I got from the debugger on the memory.dmp file. and only one file at a time.
     

    Attached Files:

  11. aneurism

    aneurism Registered Member

    Joined:
    Jun 27, 2005
    Posts:
    10
    Location:
    Seattle, WA, USA
    Here is the actuall minidump file. just remove the .log and put the . before dmp.

    I sure hope this will help. :oops:
     

    Attached Files:

Thread Status:
Not open for further replies.