Bluescreen I Od Razu Reset.

[ZwieRZakwawa]

Witam mamy problem z kompem kolegi podczas różnych gier(głównie tych nowych) wyskakuje bluescreen na ułamek sekundy że nie da się nic z niego odczytać bo od razu następuje reset.

konfiguracja kompa to:

E8400 podkręcony do 400x9 -3600MHz

napięcie na auto

płyta główna: asus P5E3 na x38 wersja biosu 1502 napięcie na northbridge 1.5V

pamięc DDR3 2x2Gb OCZ XMP pracują na: 1333MHz @ 7-7-7-20 1T napięcie 1.9V

Grafa: EVGA GF8800GTS512 nie kręcony.

zasilacz: Be-quiet 550W

dźwięk: SB X-FI gamer

dyski 2x250 GB w RAID 0 i 160GB SATA

sprzęt kupiony w ŚP ZNAK'u

oddawany kilkakrotnie na serwis

testowany primem i orthosem przez 24h i nic.

system Winows XP profesional SP3(32bit)

 

Prosił bym o pomoc bo sami już nie wiemy co to może być.

poniżej zamieszczam loga z windows debbuging tools:

 

Loading Dump File [C:\WINDOWS\Minidump\Mini071409-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 3) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

Debug session time: Tue Jul 14 05:58:37.718 2009 (GMT+2)

System Uptime: 0 days 13:43:44.437

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

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

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

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

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 24, {1902fe, a448b48c, a448b188, b7c848e5}

 

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

*** ***

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

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

*** ***

*** ***

*** 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 : Ntfs.sys ( Ntfs+308e5 )

 

Followup: MachineOwner

Edytowane 19 Lipca 2009 przez ZwieRZakwawa

[ULLISSES]

Przeczytaj przyklejony temat i wyciągnij wnioski...

[ZwieRZakwawa]

Wybacz, ale czytałem przyklejony temat i właśnie z niego pobrałem ten program win debbugger, ale jak widać w załączonym logu jest tam coś dziwnego (chodzi mi o to: ***** Kernel symbols are WRONG. Please fix symbols to do analysis.) a nie mogę rozkminić co z tego wynika, w google też szukałem kodów tych błędów ale nic nie ma dlatego proszę o pomoc.

[ULLISSES]

Szkoda, że nie czytałeś reszty tematu lub właściwego tematu. Tam jest opisane, że trzeba wyłączyć restart po BSOD i odczytać treść komunikatu z błędem. Jest też opisane o sprawdzeniu temperatur, wyczyszczeniu z kurzu, sprawdzeniu pamięci oraz sprawdzeniu kompa na innym zasilaczu.

 

Jeśli prime nie wali błędami, to albo wina grafiki (uszkodzona, przegrzewa się, kiepskie sterowniki), dysku, albo wtyczki zasilania do dysku/taśmy danych lub płyty głównej. Co zmieniałeś ostatnio w kompie? Nowe sterowniki? Nowy system? Nowy sprzęt? Jakieś nowe aplikacje? Np Deamon Tools, Nero Drive Image i inne wirtualne napędy.

 

Na początek sprawdź na innym zasilaczu. (napisane w przyklejonym temacie)

Zmień sterowniki do grafiki na inne. (j.w.)

Sprawdź na innej grafice lub tą grafikę u kumpla (j.w.)

[ZwieRZakwawa]

generalnie w kompie nie było nic zmieniane od nowości pamiętam tylko ze na początku były jakieś problemy z ramami kilkakrotnie były wymieniane. procka raczej wykluczam bo siedzi na nim ninja czyściutka, jak nowa no dobra ale zrobię tak jak radzisz zasilacz i grafę podepnę od siebie. Aha i w którym temacie jest napisane jak wyłączyć reset po BSODzie? bo szukałem tu: http://forum.purepc.pl/Microsoft-Windows-f...ia-t100972.html i nie mogę znaleźć. z góry dzięki.

Edytowane 19 Lipca 2009 przez ZwieRZakwawa

[pietro54]

Na 80% przegrzewa się procesor

a na 20% nie wyrabia zasilacz.

Myślę że tu się zawiera problem.