Blue screen error: WlanBZXP.sys


(Omegab6) #1

Witam,

Znów mam blue screen z błędem (już mam dosyć tych błędów, za często te blue screeny).

Poniżej raport:

Microsoft ® Windows Debugger Version 6.6.0007.5

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C]

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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image ntoskrnl.exe, Win32 error 2

*** 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) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0

Debug session time: Sun Dec 21 11:21:48.953 2008 (GMT+1)

System Uptime: 0 days 0:09:42.625

*********************************************************************

* 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image ntoskrnl.exe, Win32 error 2

*** 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 WlanBZXP.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for WlanBZXP.sys

*** ERROR: Module load completed but symbols could not be loaded for WlanBZXP.sys

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {b91a3224, 0, b67ee6ba, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** 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 ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** 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 ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** 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 ***

*** ***

*************************************************************************

*** WARNING: Unable to verify timestamp for NDIS.sys

*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys

Probably caused by : WlanBZXP.sys ( WlanBZXP+3c6ba )

Followup: MachineOwner


Bardzo proszę o pomoc, z jakiego programu ten błęd.

Pozdrawiam,

Omegab5


(slawex1983) #2

Sprawdź pamięć programem memtest, goldememory. Uaktualnij Windows, zaktualizuj WSZYSTKIE sterowniki. Podaj wartości napięć (najlepiej jakbyś zmierzył miernikiem wtykając sondę + we wiązkę ATX, - w molexa) Jeżeli nie masz miernika, to podaj wartości z biosu.


(Omegab6) #3

Witam slawex1983,

Zrobiłem test pamięci jak mi doradziłeś i raport to:

Memry error detected! Copying between ab62ced and ab62cdb did not result in accurate copy.

MamTest has detected that your computer cannot accurtely store data in RAM.

You need to fix this.

I dalej nie wiem o co chodzi.

Co do napięcia to nie mam miernika, ale zobacze w BIOSie.


(Omegab6) #4

To był jeden error z MemTestu, skanowanie trwa, myślałem ze to już koniec.

c.d.n.


(slawex1983) #5

Wyjmij pamięć. Przeczyść dokładnie złącze krawędziowe i delikatnie gniazdo w płycie głównej. Sprawdź ustawienia pamięci w biosie. Przeprowadź test ponownie. Jeżeli błąd będzie się powtarzał, to pamięć do wymiany.


(Omegab6) #6

Test osiągnął ponad 200% i przerwałem go, ponieważ nie wiedziałem jak długo to będzie trwać. W tym czasie wykrył 5 errorów i wszystkie takie same:

Memry error detected! Copying between ab62ced and ab62cdb did not result in accurate copy.

MamTest has detected that your computer cannot accurtely store data in RAM.

You need to fix this.

Pamięć wyciągłem ale u mnie jest wszystko czyste, ponieważ sprzęt ma góra 1 rok a poniżej jego konfiguracja:

Intel® Core2 Duo CPU E4500 @ 2.20GHz

Gigabyte 945P-S3

2x1024 Good RAM

NVIDIA GeForce 8600 GTS

A tak w ogole to czemu sadzisz ze to pamiec RAM, ja zaczalem troche szukac tematu i doszukalem sie ze ten driver jest od LANu czy internetu a ja mam dokladnie Neostrade Livebox Sagem WiFi i dokladnie stad pochodzi ten driver.


(slawex1983) #7

Sterownik jest dobry. Livebox tworzy sieć LAN. Częste bluescreeny z reguły są wynikiem wadliwej pamięci.


(Omegab6) #8

a jakim dobrym programem mogę przetestować pamięć RAM, bo ten MemTest już nie chce testować.


(Cosik Ktosik) #9

Zapewne używasz Memtesta pod Windows.

Sprawdź pamięć programem Memtest86+.

Memtest86+ ściągasz, wypakowujesz jeżeli potrzeba, aby nagrać plik ISO. Nagrywasz go na płytę, w Nero opcja Nagraj obraz na dysk. Potem uruchamiasz na nowo komputer bootując go z płyty (w biosie ustaw: okno Advanced Bios Features->First Boot Device ustaw na CD/DVD).