Results 1 to 4 of 4

Thread: Blue screen after "netstat" command

  1. #1
    Join Date
    May 2008
    Posts
    976

    Blue screen after "netstat" command

    I have a big problem which is apparently unknown. When I open a command prompt and I type "netstat" and everything freezes for 2 seconds. After that I have a blue page with the following errors:

    0x0000008E (0xC0000005, 0x862BE0BD, 0xB99B6B58)

    The first error (0x0000008E) must be a hardware driver problem but I do not see why because I did not install any new hardware. The second error (0xC0000005) is rather vague. The third and fourth errors (0x862BE0BD, 0xB99B6B58) not found

    I did the analysis (Nod32, Ad-Aware, A-squared, Multi virus cleaner) but nothing unusual.

    My configuration:

    MSI K9N6PGM2
    AMD 64X2 4000+
    1GB Corsair PC2 6400C4 XSM2
    Twintech 8400GS 256 MB
    160 GB Seagate Baracuda HDD
    PSU "480W"

  2. #2
    Join Date
    May 2008
    Posts
    1,020

    Re: Blue screen after "netstat" command

    How is your network?
    Wifi / Ethernet?

    Do you use elements of your motherboard or you have a PCI card?
    You have installed the latest drivers for these?

  3. #3
    Join Date
    May 2008
    Posts
    976

    Re: Blue screen after "netstat" command

    I work in Wifi card with a D-Link DWL-G510 PCI

    have motherboard drivers and Wifi card was installed without problems as it seems to me

    I updated everything and now I have 2 messages that appear at the opening of Windows.

    AirGCFG.exe
    The procedure entry point apsGetinerfaceCount is found in the dynamic link library wlanapi.dll

    =====> I click ok and get it re-displays another:

    WZCSLDR2.exe
    the procedure entry point apsInitialize is found in the dynamic link library wlanapi.dll

    I try to type "netstat" and is always the same ...

  4. #4
    Join Date
    May 2008
    Posts
    1,020

    Re: Blue screen after "netstat" command

    So your card is a WIFI:

    1. problem of drivers
    2. problem of hardware

    uninstall everything properly, and reinstall your drivers (make sure you get the right version of drivers and that the model of the card is good (there are sometimes different version of cards)

    restart

    reinstall the drivers ...

Similar Threads

  1. Replies: 2
    Last Post: 06-02-2008, 07:58 PM
  2. Replies: 3
    Last Post: 18-01-2008, 10:10 PM
  3. Replies: 1
    Last Post: 24-12-2007, 08:41 PM
  4. Replies: 2
    Last Post: 07-12-2006, 05:56 PM
  5. Replies: 2
    Last Post: 16-03-2004, 07:32 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,514,895.04015 seconds with 17 queries