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

Ciągłe restarty i zwisy - MB Jetway P4XFCU

27 Lip 2006 14:09 1485 6
  • Poziom 10  
    Mam płyte główną Jetway p4xfcu mam z nią problem związany z ciągłymi resetami i zwisami moja konfiguracja to:

    celeron 2.4 northwood
    zasilacz Enlight 350W
    karta graficzna radeon 9550 128/128
    dysk twardy samsung spinpoint 80GB
    2 kośći pamieci pierwasza blitz 256 /400mhz druga Twinmos 256/266mhz

    w programie Microsoft Debugging Tools wygenerował taki błąd




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


    Loading Dump File [C:\WINDOWS\Minidump\Mini072706-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) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
    Debug session time: Thu Jul 27 12:37:58.951 2006 (GMT+2)
    System Uptime: 0 days 2:46:55.522
    *********************************************************************
    * 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 User Symbols
    Loading unloaded module list
    ..............
    *** WARNING: Unable to verify timestamp for hal.dll
    *** ERROR: Module load completed but symbols could not be loaded for hal.dll
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {548b0067, 2, 1, 806f26e0}

    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.

    ***** 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 cmuda.sys
    *** ERROR: Module load completed but symbols could not be loaded for cmuda.sys
    Probably caused by : hardware ( cmuda+288c )

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

    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: 548b0067, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 806f26e0, 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.

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

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    548b0067

    CURRENT_IRQL: 2

    FAULTING_IP:
    hal+66e0
    806f26e0 2408 and al,8

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xA

    MISALIGNED_IP:
    hal+66e0
    806f26e0 2408 and al,8

    LAST_CONTROL_TRANSFER: from 00000000 to 806f26e0

    SYMBOL_ON_RAW_STACK: 1

    STACK_ADDR_RAW_STACK_SYMBOL: 17002000010004

    STACK_COMMAND: dds 8221A6F4-0x20 ; kb

    STACK_TEXT:
    8221a6d4 822a2b28
    8221a6d8 0000001e
    8221a6dc 00000002
    8221a6e0 806f26e0 hal+0x66e0
    8221a6e4 00000008
    8221a6e8 00010282
    8221a6ec 00000000
    8221a6f0 f7e0e88c cmuda+0x288c
    8221a6f4 00000000
    8221a6f8 0002000e
    8221a6fc 6d665346
    8221a700 81703e00
    8221a704 816dd7c0
    8221a708 0a060002
    8221a70c 63504354
    8221a710 98000197
    8221a714 00000001
    8221a718 82210000
    8221a71c 00040001
    8221a720 00000000
    8221a724 8221a724
    8221a728 8221a724
    8221a72c 821f19d8
    8221a730 00000000
    8221a734 00000000
    8221a738 0a140006
    8221a73c c3646641
    8221a740 0000afd8
    8221a744 00000000
    8221a748 00000000
    8221a74c 822182a8
    8221a750 821e6600


    FOLLOWUP_IP:
    cmuda+288c
    f7e0e88c ?? ???

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: hardware

    SYMBOL_NAME: cmuda+288c

    MODULE_NAME: hardware

    FAILURE_BUCKET_ID: IP_MISALIGNED

    BUCKET_ID: IP_MISALIGNED

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

    Prosił bym was o porady związane tym problemem
  • e-miernikie-mierniki
  • Spec od drukarek
    były od początku używania tego komputera? Jeśli tak, to ja podejrzewam nieprawidłową współpracę kości pamięci - są różnych firm, do tego jedna taktowana 400, a druga 266MHz. Polecałbym wyjąć jedną kość, włączyć komputer i popracować na nim jakiś czas...
  • e-miernikie-mierniki
  • Spec od komputerów
    Pamięć proszę przetestować Memtestem
    www.memtest86.com
    Proszę zmierzyć miernikiem napiecia z zasilacza.Temperatury są monitorowane ?
  • Poziom 10  
    Komputer mam stale monitorowany przez everesta i aide robią mi sie te restarty tylko na tej płyćie głównej bo miałem mobo MSI wcześniej i takie cyrki mi sie nierobiły tylko że poszła do serwisu z powodu USB i teraz sie męcze na tym Jetway podaje wartośći zasilacza

    Wartości napięć
    Napięcie rdzenia procesora 1.50 V
    +3.3 V 3.31 V
    +5 V 5.03 V
    +12 V 11.92 V
    -12 V -12.03 V
    +5 V podczas wstrzymania pracy 4.78 V
    VBAT baterii CMOS 3.28 V
  • Spec od komputerów
    Kolego,napięcia należy mierzyć tylko i wyłącznie MIERNIKIEM.Zrób test pamięci.
  • Poziom 10  
    wszystko wskazuje na pamiec bo w książce z tej płyty pisze ze obsługuje tylko pamieci 266 i 200 a ja mam 266 i 400 czy to coś może robić a miernik musze pożyczyć bo niemam
  • Spec od komputerów
    Trzeci raz namawiam cię abyś przetestował RAM Memtestem.Najpierw jedną kość a potem drugą,jak bedzie bez błędów to obie na raz.