Bsod Wanarp.sys ( Wanarp+57fb )

[kamilo23]

Microsoft ® Windows Debugger Version 6.10.0003.233 X86

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini020609-01.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 2) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20

Debug session time: Fri Feb 6 12:46:35.750 2009 (GMT+1)

System Uptime: 1 days 17:53:16.330

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

* 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 wanarp.sys, Win32 error 0n2

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

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

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 100000D1, {f7acff75, 2, 0, f7acff75}

 

ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.

ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,214600,41108004

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

 

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

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

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

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

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

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

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

*** ***

*** ***

*** 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 : wanarp.sys ( wanarp+57fb )

 

Followup: MachineOwner

---------

 

kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: f7acff75, memory referenced

Arg2: 00000002, IRQL

Arg3: 00000000, value 0 = read operation, 1 = write operation

Arg4: f7acff75, address which referenced memory

 

Debugging Details:

------------------

 

ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.

ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,214600,41108004

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

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

 

MODULE_NAME: wanarp

 

FAULTING_MODULE: 804d7000 nt

 

DEBUG_FLR_IMAGE_TIMESTAMP: 41107c89

 

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

f7acff75

 

CURRENT_IRQL: 2

 

FAULTING_IP:

+fffffffff7acff75

f7acff75 ?? ???

 

CUSTOMER_CRASH_COUNT: 1

 

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

 

BUGCHECK_STR: 0xD1

 

LAST_CONTROL_TRANSFER: from ecd9f7fb to f7acff75

 

FAILED_INSTRUCTION_ADDRESS:

+fffffffff7acff75

f7acff75 ?? ???

 

STACK_TEXT:

WARNING: Frame IP not in any known module. Following frames may be wrong.

80550374 ecd9f7fb 823f5968 80550384 82361798 0xf7acff75

80550390 f72a2c1c 0cabb1e5 823f5968 00000000 wanarp+0x57fb

805503b4 ec27bb69 82a07130 823f5968 00000000 NDIS+0x15c1c

805503d4 f72a2c1c 82e66930 013f5968 00000000 psched+0x8b69

805503f8 f728ff95 82b98318 823f5968 00000000 NDIS+0x15c1c

80550420 ec27bf31 82d281b8 823f5968 82a07130 NDIS+0x2f95

8055045c f72a5424 82e66930 823f5968 00000002 psched+0x8f31

80550490 ecd9f404 82b84cf8 00000000 00000001 NDIS+0x18424

805504ac ecd9f707 82ad33e8 82352910 829eca20 wanarp+0x5404

805504f0 eb18670a 82ad33e8 80550530 00000001 wanarp+0x5707

80550520 eb1864ad 82d1a668 b2f51054 823f5968 tcpip+0x370a

8055066c eb187546 eb1c44b8 00000000 82303440 tcpip+0x34ad

805506b8 eb19d850 02d6a7d8 eb1833dd 00000000 tcpip+0x4546

805506d8 eb19da87 00000002 00000002 00000000 tcpip+0x1a850

80550754 eb1833ec eb1cb8e0 00000000 80550880 tcpip+0x1aa87

80550764 804dcaad eb1cb8f0 eb1cb8e0 905c5060 tcpip+0x3ec

80550880 804dc928 80559580 80559320 ffdff000 nt+0x5aad

805508ac 804dc179 80559980 00000000 00934314 nt+0x5928

805508b0 80559980 00000000 00934314 00000000 nt+0x5179

805508b4 00000000 00934314 00000000 80559320 nt+0x82980

 

 

STACK_COMMAND: kb

 

FOLLOWUP_IP:

wanarp+57fb

ecd9f7fb ?? ???

 

SYMBOL_STACK_INDEX: 1

 

SYMBOL_NAME: wanarp+57fb

 

FOLLOWUP_NAME: MachineOwner

 

IMAGE_NAME: wanarp.sys

 

BUCKET_ID: WRONG_SYMBOLS

 

Followup: MachineOwner

---------

Instalka windowsa ma ponad rok, ostatnio mam taki bsod, nie moge znalezc jednoznacznej odpowiedzi od czego sie tak dzieje. Jesli chodzi o sprzet to wlozylem kosc ramu 512 bo ilez mozna jechac na 256 :P , kosc jest sprawna testowana rowniez w sp2000 ale zaraz przejade ja memtestem.

 

Co do tego błedu ?

 

edit

 

Pamieci przetestowane po 40 minutach program wykazał 0 błedów.

Edytowane 6 Lutego 2009 przez kamilo23