Strona 1 z 2 12 OstatniOstatni
Pokaż wyniki od 1 do 10 z 18
  1. #1
    Obserwator
    Dołączył
    June 08
    Postów
    12
    Siła Reputacji
    0


    Twoja ocena: Yes No

    błąd MICROSOFT WINDOWS

    witam Mam problem.
    Gdy włączam komputer po jakimś czasie ( 1-10 min)
    wyskakuje raport bledow MICROSOFT WINDOWS
    Gdy włączam jakaś grę restartuję mi się komputer:/

    tu macie link tego błędu


  2. #2
    Zaawansowany uczestnik
    Dołączył
    August 07
    Postów
    940
    Siła Reputacji
    0


    Twoja ocena: Yes No

    Po takim okienku nic konkretnego nie mozna wywnioskowac, oprocz tego, ze to blad programowy lub sprzetowy.
    Pokaz, co zawiera ten raport (niebieski link), co masz w folderze Windows/ Minidump i sprawdz czy nie ma bledow w logach (Panel sterowania/ Narzedzia administracyjne/ Podglad zdarzeń).
    Ale na poczatek skan dobrym antywirusem, antyspywarem oraz scandisk,chkdsk dysku twardego.

  3. #3
    Obserwator
    Dołączył
    June 08
    Postów
    12
    Siła Reputacji
    0


    Twoja ocena: Yes No

    zrobiłem format i dalej ten sam błąd o to screeny tego błędu




  4. #4
    Obserwator
    Dołączył
    June 08
    Postów
    12
    Siła Reputacji
    0


    Twoja ocena: Yes No

    WYSKOSZYLO MI JESZCZE COS TAKIEGO:

  5. #5
    Obserwator
    Dołączył
    June 08
    Postów
    12
    Siła Reputacji
    0


    Twoja ocena: Yes No

    to moze miec cos wspolnego z tym >>><<<

  6. #6
    Obserwator
    Dołączył
    January 08
    Postów
    355
    Siła Reputacji
    0


    Twoja ocena: Yes No

    Cytat Napisał ShelbyGT Zobacz post
    to moze miec cos wspolnego z tym >>><<<
    Na podstawie tamtej instrukcji, wyedytuj pliki minidump i podaj wyniki do postu.

  7. #7
    Obserwator
    Dołączył
    June 08
    Postów
    12
    Siła Reputacji
    0


    Twoja ocena: Yes No

    1 plik:

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


    Loading Dump File [Cocuments and SettingsPowerPulpitMini063008-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
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
    Debug session time: Mon Jun 30 13:23:42.132 2008 (GMT+2)
    System Uptime: 0 days 0:28:32.703
    ************************************************** *******************
    * 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
    ..............
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck F4, {3, 829d3da0, 829d3f14, 805fa7a8}

    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+ *
    ************************************************** *******************
    Probably caused by : csrss.exe

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

  8. #8
    Obserwator
    Dołączył
    June 08
    Postów
    12
    Siła Reputacji
    0


    Twoja ocena: Yes No

    2 plik:

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


    Loading Dump File [Cocuments and SettingsPowerPulpitMini063008-02.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
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
    Debug session time: Mon Jun 30 13:37:38.947 2008 (GMT+2)
    System Uptime: 0 days 0:07:16.524
    ************************************************** *******************
    * 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
    ............
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck C2, {7, cd4, 1, f36c73d4}

    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 Ntfs.sys
    *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
    *** WARNING: Unable to verify timestamp for sr.sys
    *** ERROR: Module load completed but symbols could not be loaded for sr.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 : sr.sys ( sr+7f70 )

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

  9. #9
    Obserwator
    Dołączył
    June 08
    Postów
    12
    Siła Reputacji
    0


    Twoja ocena: Yes No

    to 3 i 4 bo sie nie zmiescilo >><<

  10. #10
    Obserwator
    Dołączył
    January 08
    Postów
    355
    Siła Reputacji
    0


    Twoja ocena: Yes No

    Tych pozostałych, niestety nie podejrze (mam poblokowany komputer w biurze). Z tego co na razie widzę - obstawiam pamięć ram. Przetestuj, tylko przynajmniej parę godzin (chyba, że błędy bedą wcześniej) :
    http://www.memtest.org/
    Nie będzie błędów, to dla pewności test Orthos`em :
    http://sp2004.fre3.com/
    Dopisz z pozostałych debugów - sygnatury BugCheck, oraz Probably caused by .
    Po za tym, to nie są prawidłowo debugowane pliki *dmp, bo w instrukcji są braki. Uruchom WinDbg >> File >> Symbol File Path >> i wpisz/wklej :
    Kod:
    SRV*c:symbole*http://msdl.microsoft.com/download/symbols
    BTW
    Jeżeli się pomyliłem, to dopisz konfigurację sprzętu (dokładną), przeczyść komputer z kurzu (powyciągaj podzespoły), sprawdż temperatury.

Informacje o temacie

Users Browsing this Thread

Aktualnie 1 użytkownik(ów) przegląda ten temat. (0 zarejestrowany(ch) oraz 1 gości)

Podobne wątki

  1. laptop lenovo 3000 n100 Windows Vista na Windows xp
    By radosliv in forum Systemy Operacyjne
    Odpowiedzi: 2
    Ostatni post / autor: 27-12-07, 13:41
  2. błąd MICROSOFT WINDOWS
    By mozdzierz in forum HARDWARE
    Odpowiedzi: 4
    Ostatni post / autor: 27-12-06, 19:30
  3. Zakupy w Microsoft
    By Kundelek in forum PIENIĄDZE, POLITYKA, WŁADZA
    Odpowiedzi: 5
    Ostatni post / autor: 16-09-06, 09:24
  4. Windows XP. Neostrada dla różnych kont w Windows.
    By tomasz rakoczy in forum OPROGRAMOWANIE
    Odpowiedzi: 5
    Ostatni post / autor: 06-05-06, 16:43
  5. Reklama Microsoft w polskiej TV
    By konkordpl in forum INNE TEMATY
    Odpowiedzi: 4
    Ostatni post / autor: 01-11-04, 10:22

Zakładki

Zakładki

Uprawnienia

  • Nie możesz zakładać nowych tematów
  • Nie możesz pisać wiadomości
  • Nie możesz dodawać załączników
  • Nie możesz edytować swoich postów
  •  

Jak czytać DI?

Powered by  
ATMAN EcoSerwer