Netzwerkproblem - ethernet adapter spinnt, blauer bildschrim

Dieses Thema Netzwerkproblem - ethernet adapter spinnt, blauer bildschrim im Forum "Windows XP Forum" wurde erstellt von Peggy1990, 14. Nov. 2005.

Thema: Netzwerkproblem - ethernet adapter spinnt, blauer bildschrim ich hab vor kurzem alle aktuellen treiber für meine netzwerkkarte eingerichtet, da die nicht installiert waren und...

  1. ich hab vor kurzem alle aktuellen treiber für meine netzwerkkarte eingerichtet, da die nicht installiert waren und ich somit mein dsl modem über usb installieren musste. seitdem hab ich mein dsl modem jetzt über lan installiert. auf dem desktop gehe ich mit einer dfü-verknüpfung ins netz. da kommt dann netzwerkverbindung wird registriert und dann wird auch schon der bildschirm blau! :cry: ich muss dann immer paar ma meinen VIA Rhine III Fast Ethernet Adapter neu installieren. erst nach mehrmaligen versuchen geht das internet dann wieder. aber wenn ich meinen pc dann ausschalte und wieder an mache, kommt das gleiche problem wieder mit dem blauen bildschirm. was is denn da los??? helft mir bitte!!! hab win xp und das sp2 drauf.

    hier en bild von dem blauen bildschrim

    [​IMG]
     
  2. Du könntest versuchen, das Speicherabbild durch WinDbg zu jagen und analysieren zu lassen. Evtl. stehen dort ja hilfreiche Informationen drin.
    Debugging Tools: http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
    Das Speicherabbild sollte sich wahrscheinlich unter C:\Windows\Minidump finden lassen. Ansonsten mal danach suchen. Also nach *.dmp. Nicht vergessen in den Suchoptionen anzugeben, dass du versteckte Orte durchsuchen lassen möchtest.

    Nachdem das Speicherabbild von WinDbg geöffnet wurde, kannst du es mit
    Code:
    !analyze -v
    detailliert untersuchen lassen.
     
  3. hab das jetz runtergeladen. is ja leider in englisch, meine englischkenntnisse sind nicht so gut. was muss ich jetz machen? kannst du mir bitte die einzelnen schritte erklären??
     
  4. Du startest WinDbg und wählst dort unter File -> Open Crash Dump. Dann musst du den Pfad zum Speicherabbild finden, wie du den Pfad findest, habe ich dir ja bereits beschrieben.
    Was du nach dem Öffnen machen sollst, habe ich ebenfalls bereits beschrieben.
     
  5. die datei die ich geprüft hab is vom 14.11
    da zeigt es mir jetz das an


    Microsoft (R) Windows Debugger Version 6.5.0003.7
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini111405-06.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 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 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
    Debug session time: Mon Nov 14 14:16:08.781 2005 (GMT+1)
    System Uptime: 0 days 0:01:05.482
    *********************************************************************
    * 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 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 unloaded module list
    ............
    Loading User Symbols
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, ff88c043, b183542b, 0}

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

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

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: ff88c043, The address that the exception occurred at
    Arg3: b183542b, Trap Frame
    Arg4: 00000000

    Debugging Details:
    ------------------

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

    MODULE_NAME: nt

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher in 0x%08lx. Der Vorgang %s konnte nicht auf dem Speicher durchgef hrt werden.

    FAULTING_IP:
    +ffffffffff88c043
    ff88c043 006d00 add [ebp],ch

    TRAP_FRAME: b183542b -- (.trap ffffffffb183542b)
    ErrCode = 00000002
    eax=700900ff ebx=3ae030b2 ecx=ae229081 edx=917ed881 esi=ae229081 edi=917ed8ff
    eip=ff88c043 esp=b183549f ebp=19c124ff iopl=0 nv up ei ng nz na pe cy
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010283
    ff88c043 006d00 add [ebp],ch ss:0010:19c124ff=??
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 6

    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

    BUGCHECK_STR: 0x8E

    LAST_CONTROL_TRANSFER: from 00000000 to ff88c043

    UNALIGNED_STACK_POINTER: b183549f

    STACK_TEXT:
    19c124ff 00000000 00000000 00000000 00000000 0xff88c043


    STACK_COMMAND: .bugcheck ; kb

    FOLLOWUP_NAME: MachineOwner

    BUCKET_ID: WRONG_SYMBOLS

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

    die datei die ich jetz anzeige is vom 26.10


    Microsoft (R) Windows Debugger Version 6.5.0003.7
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini102605-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 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 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
    Debug session time: Wed Oct 26 16:13:37.062 2005 (GMT+1)
    System Uptime: 0 days 1:47:03.763
    *********************************************************************
    * 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 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 unloaded module list
    ...............
    Loading User Symbols
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {14, 2, 1, 804e2407}

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

    Unable to load image wanarp.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for wanarp.sys
    *** ERROR: Module load completed but symbols could not be loaded for wanarp.sys
    *** WARNING: Unable to verify timestamp for kl1.sys
    *** ERROR: Module load completed but symbols could not be loaded for kl1.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 ***
    *** ***
    *************************************************************************
    Probably caused by : wanarp.sys ( wanarp+52ff )

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

    1: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 00000014, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 804e2407, address which referenced memory

    Debugging Details:
    ------------------

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

    MODULE_NAME: wanarp

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107c89

    WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    00000014

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt+b407
    804e2407 f00fba2900 lock bts dword ptr [ecx],0x0

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xA

    LAST_CONTROL_TRANSFER: from f7f7b2ff to 804e2407

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    b1f16b0c f7f7b2ff 0cabb1e5 81a189c0 81be34e0 nt+0xb407
    b1f16b38 81e4bff1 0cabb1e5 81a189c0 81be34e0 wanarp+0x52ff
    b1f16b6c 81e4c2b2 02000000 81483450 81e4fa17 0x81e4bff1
    b1f16bdc 81305ba8 81377200 81304008 00000001 0x81e4c2b2
    b1f16c0c f8949853 817e7ef0 81119868 f89499df 0x81305ba8
    b1f16c40 804e13d9 81eadf18 800520ec 80700410 kl1+0x853
    b1f16c64 80580fb1 81eadf18 812e6540 81ca86d8 nt+0xa3d9
    b1f16d00 8058709e 00000cac 00000000 00000000 nt+0xa9fb1
    b1f16d34 804dd99f 00000cac 00000000 00000000 nt+0xb009e
    b1f16d64 7c91eb94 badb0d00 0765f878 00000000 nt+0x699f
    b1f16d68 badb0d00 0765f878 00000000 00000000 0x7c91eb94
    b1f16d6c 0765f878 00000000 00000000 00000000 0xbadb0d00
    b1f16d70 00000000 00000000 00000000 00000000 0x765f878


    FOLLOWUP_IP:
    wanarp+52ff
    f7f7b2ff ??

    SYMBOL_STACK_INDEX: 1

    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: wanarp+52ff

    IMAGE_NAME: wanarp.sys

    STACK_COMMAND: kb

    BUCKET_ID: WRONG_SYMBOLS

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

    und was is jetz damit?
     
Die Seite wird geladen...

Netzwerkproblem - ethernet adapter spinnt, blauer bildschrim - Ähnliche Themen

Forum Datum
netzwerkproblem mit avm bluefritz und onboard gigabit ethernet Windows XP Forum 2. März 2005
Netzwerkprobleme Win10 Windows 10 Forum 21. Mai 2016
Netzwerkprobleme Windows 7 Forum 8. Juni 2015
Netzwerkproblem /Dringend Windows 7 Forum 10. Feb. 2015
netzwerkproblem - kein zugriff vom laptop auf pc Firewalls & Virenscanner 24. Apr. 2011