Wątek zamknięty

Temperatura procesora - przyczyną restartów PC?

 
ampa
Młodszy user systemu

Liczba postów: 152
Post: #21

RE: Temperatura procesora - przyczyną restartów PC?


Pamięci testowałem 5 godz i było w porządku...o dziwo zmusiłem je do pracy jako 1600 dopiero jak w biosie ustawiłem XMP inaczej nie chciały współpracować i były problemy jak ręcznie ustawiałem timingi i napięcia,więc wróciłem do ustawień fabrycznych i włączyłem XMP i wszelkie problemy zniknęły a było to prawie z rok temu.W podglądzie zdarzeń który wyczyściłem niepotrzebnie jedyny błąd to kopiowania woluminów w tle czy jakoś tam.
Jedyny minidump jaki mam bo chyba skasowałem jakoś poprzednie:
Kod:
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C: \Windows\Minidump\050211-17908-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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product:  WinNt, suite:  TerminalServer SingleUserTS
Kernel base = 0x83417000 PsLoadedModuleList = 0x83561850
Debug session time:  Mon May  2 18: 59: 46.587 2011 (GMT+2)
System Uptime:  0 days 0: 00: 05.210
*********************************************************************
* 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
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 8719e024, 0, 0}

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

*********************************************************************
* 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+                                    *
*********************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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 :  hardware

Followup:  MachineOwner
Z pomiarami będzie gorzej,o ile zasilacz mi sprawdzał kolega co się na tym zna to nie mam miernika aby samemu sprawdzić.Co w biosie odnośnie procka mogę sprawdzić...jakieś ustawienia? czy też zresetować.Jakim programem monitorować? Dodam że do crysis 2 wszystko działało bez problemów więc czyżby jednak gra.Pograłem w crysisa z pół godz.w ostatnim rozdziale miałem 2 zwiechy (niezależnie od czasu gry) a teraz wcale temp.grafa-63,procek 62,57,61,59 więc chyba nie za wysokie.

---------

Płyta:ASRock Z68 Extreme4 Gen3:Intel Core i7-2600K:Grafa Asus GF GTX 970 STRIX:G.Skill 4x4GB 1600MHz:X-Fi Xtreme Gamer:Zasilacz Be Quiet Power Zone 650W
(Ten post był ostatnio modyfikowany: 03.05.2011 19:27 przez ampa.)

03.05.2011 18:35

Znajdź wszystkie posty użytkownika
Wątek zamknięty

Podobne wątki
Wątek: Autor Odpowiedzi: Wyświetleń: Ostatni post
Czy to jest optymalna temperatura komputera? zorro223 4 1.826 21.08.2016 21:04
Ostatni post: thermalfake
skoki wydajności i pracy procesora GhostofAmon 0 1.398 31.05.2016 21:42
Ostatni post: GhostofAmon
Temperatura CPU - czy jest w normie? Rukahs 1 1.579 25.05.2016 19:46
Ostatni post: LadyInBlue
Rozwiązany Duże zużycie procesora Shoyu 1 2.660 03.03.2016 19:09
Ostatni post: Shoyu
Rozwiązany ThinkCentre M52 zmiana procesora alwaysbad 1 1.205 16.11.2015 21:15
Ostatni post: thermalfake
Jak pozbyć się pasty z pinów procesora. mateusz28011 1 2.319 13.10.2015 23:44
Ostatni post: thermalfake
« Starszy wątek | Nowszy wątek »

Temat został oceniony na 0 w skali 1-5 gwiazdek.
Zebrano 0 głosów.