Problem z HDD,Raw Read Error Rate - Failed


(Format Kp) #1

Kilka minut po załadowaniu się, system się zawiesza, po kolejnych kilku minutach wyskakuje Blue Screen, po resecie CHKSDK sprawdza pliki, indeksy i deskryptory zabezpieczeń, usuwa kilka błędów, a sytuacja się powtarza.

Nie dzieje się to przy każdym uruchomieniu, ale przy większości, w tej chwili akurat wszystko działa bez zarzutu ale problem oczywiście jest.

Dane błędów:

-Komunikat STOP: 0x000000F4(0x0000003, 3 zmiennie wartości)

-Minidump odczytany z Windows Debuggera(nieco niżej, żeby było przejrzyście)

-Screen z HDTune: http://img199.imageshack.us/i/screenshot021i.jpg/

jak widać - Raw Read Error Rate - Failed - nie mam pojęcia co to znaczy

-W obecnym momencie robie error scan w HDDTune na 50GB są 3 czerwone(uszkodzone) kratki ;/

skan idzie bardzo wolno(2.5mb/s) więc pewnie dopiero jutro dowiem się jak reszta dysku

Dane techniczne:

Dysk twrdy: SAMSUNG SP1603C (160GB)

Płyta główna: ASUS P5VD-MX

czynności te polecili mi na innym forum, niestety nie otrzymałem żadnej odpowiedzi, więc szukam pomocy także tutaj

-- Dodane 13.06.2009 (So) 22:17 --

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

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

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700

Debug session time: Fri Jun 12 22:46:23.359 2009 (GMT+2)

System Uptime: 0 days 1:19:21.105

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

* 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 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, 863ea7a0, 863ea914, 805d1140}

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

unable to get nt!KiCurrentEtwBufferOffset

unable to get nt!KiCurrentEtwBufferBase

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

*** ***

*** ***

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

*** ***

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

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

*** ***

*** ***

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

* using .sympath and .sympath+ *

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

Probably caused by : csrss.exe

Followup: MachineOwner


(troiP) #2

http://forum.dobreprogramy.pl/jak-usunac-csrss-exe-t121597.html tu masz problem z tym csrss.exe


(Hashi) #3

Dysk do wymiany.

Możesz jeszcze przejechać tym dla sprawdzenia:

http://www.disk-monitor.com/download.html

(DiskMonitorFree.exe)

Najlepiej byłoby dysk podpiąć pod inny komp.


(Format Kp) #4

W disk-monitor pokazuje health(98%) i że wszystko ok, więc niewiem już :expressionless:


(Hashi) #5

Dlatego najlepiej podpiąć dysk pod inny komputer. Sprawdź zakładkę SMART info. Możesz zapuścić skanowanie powierzchni dysku (Scan disk). Albo slave albo podepnij u znajomego pod inny komputer i zrób scan.


(Jjoasz) #6

dysk sie sypie, a dokladnie glowice lub silnik - ten blad oznacza brak mozliwosci odczytu powierzchni talezy

dodatkowo lub na skutek sypie badsectorami - masz ich 6 przeniesionych, 78 biezacych, blad na tasmie (w zasadzie pomijalny o ile sie nie zwieksza)

zgraj dane i odeslij na gwarancje (jesli posiada), bo najwyrazniej skonczyl sie zywot tego egzemplarza…