Elektroda.pl
Elektroda.pl
X
Proszę, dodaj wyjątek www.elektroda.pl do Adblock.
Dzięki temu, że oglądasz reklamy, wspierasz portal i użytkowników.

BSOD - czy to wina karty WiFi?

tepek 07 Kwi 2014 18:22 1566 6
  • #1 07 Kwi 2014 18:22
    tepek
    Poziom 12  

    Laptop nawiedzany jest co kilkadziesiat minut przez bluescreeny, ale tylko wtedy gdy jest podlaczony do miejskiej publicznej otwartej sieci wifi.
    Karta wifi zostala dopiero co zakupiona, model tp-link tl-wn722n.
    System operacyjny to windows xp pro sp3
    Oto analiza pliku dump.

    Spoiler:
    Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [D:\Mini040314-04.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805541c0
    Debug session time: Thu Apr 3 17:27:37.343 2014 (GMT+2)
    System Uptime: 0 days 3:02:40.948
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe




    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........
    Loading User Symbols
    Loading unloaded module list
    ..............
    Unable to load image athuw.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for athuw.sys
    *** ERROR: Module load completed but symbols could not be loaded for athuw.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007E, {c0000005, b13bb2f6, ba583a1c, ba583718}

    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : athuw.sys ( athuw+ce2f6 )

    Followup: MachineOwner
    ---------


    Na poczatku myslalem, ze to wina sterownika, poniewaz mialem juz taka karte wifi podlaczona do innego komputera tylko, ze w wersji 1.8, a ta nowa karta jest w wersji 1.9 i jako, ze juz wczesniej mialem na kazdym komputerze zainstalowane sterowniki z wersji 1.8 to nawet nie ruszalem sterownikow z 1.9. Niestety po przinstalowaniu sterownikow na wersje 1.9 nadal wystepuja bluescreeny.

    Czy jest mozliwe, ze karta wifi (albo jej sterownik) nie chce wspolpracowac z publiczna siecia i w efekcie wystepuja bsody?

    0 6
  • #2 07 Kwi 2014 18:25
    Kasek21
    Poziom 43  

    Pobierasz sterownik dla odpowiedniej wersji tej karty?
    http://www.tp-link.com/en/Article/?id=46

    0
  • #3 07 Kwi 2014 18:27
    tepek
    Poziom 12  

    Sterowniki bralem z plytki dolaczanej do karty.

    0
  • #4 07 Kwi 2014 18:35
    Kasek21
    Poziom 43  

    Pobierz najnowsze sterowniki ze strony producenta.

    0
  • #5 07 Kwi 2014 18:46
    tepek
    Poziom 12  

    Pobralem, ale to raczej ten sam sterownik (rozmiar jak i suma kontrolna md5 sa takie samie, jedynie inna jest data modyfikacji pliku).

    0
  • #6 07 Kwi 2014 19:02
    Kasek21
    Poziom 43  

    Na starszym sterowniku także występują problemy?

    Możesz sprawdzić kartę na innym komputerze?

    0
  • #7 16 Kwi 2014 19:31
    tepek
    Poziom 12  

    Sprawdzalem wszystkie sterowniki, podlaczalem tez druga karte wifi (ten sam model, ale wersja 1.8) i tez wystepowaly bsody.

    0