LAG i reset

[TaFiK]

siema mam problem , podczas glupich czynnosci tak jak np zmiana karty w przegladarce czy cos innego komputer dostaje lag i po 5 sekundach sie resetuje . Jak sie ponownie wlaczy to wyskakuje ze system odzyskal sprawnosc po nieoczekiwanym zamknieciu i pisze cos tam: Podpis problemu:

Nazwa zdarzenia problemu: BlueScreen

Wersja systemu operacyjnego: 6.1.7601.2.1.0.256.48

Identyfikator ustawień regionalnych: 1045

Dodatkowe informacje o problemie:

BCCode: 124

BCP1: 0000000000000000

BCP2: FFFFFA80028408F8

BCP3: 0000000000000000

BCP4: 0000000000000000

OS Version: 6_1_7601

Service Pack: 1_0

Product: 256_1

Pliki pomagające opisać problem:

C:\Windows\Minidump\100713-14554-01.dmp

C:\Users\Easy\AppData\Local\Temp\WER-24070-0.sysdata.xml

Dodam ze zmienialem zasilacz - nie pomoglo . ram tez zmienialem tez nie pomoglo . Dysk testowalem hdtune 0 bledow. Temperatury w normie w stresie procek ma 55stopni a karta 75 na pasywnym chlodzeniu .

Tutaj zas z windbg o tym bsod:

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\100713-18267-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 x64

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0xfffff800`0285c000 PsLoadedModuleList = 0xfffff800`02aa1e90

Debug session time: Mon Oct 7 17:31:53.396 2013 (GMT+2)

System Uptime: 0 days 0:00:07.612

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

* 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, fffffa80028388f8, 0, 0}

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

*** ***

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

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

*** ***

*** ***

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

*** ***

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

Unable to load image PSHED.dll, Win32 error 0n2

*** WARNING: Unable to verify timestamp for PSHED.dll

*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll

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

*** ***

*** ***

*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***

*** ***

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

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

*** ***

*** ***

*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***

*** ***

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

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

*** ***

*** ***

*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***

*** ***

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

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

*** ***

*** ***

*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***

*** ***

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

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

*** ***

*** ***

*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***

*** ***

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

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

*** ***

*** ***

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

---------

[Haitz]

Podaj jaki jest kod błędu(taki na dole bluescreena)

[TaFiK]

No wlasnie nie wywala zadnego bsod a system wykrywa ze to jednak byl bluescreen .

 

Nie wiem czy to to akuratnie ale to z tego windbg

Kernel base = 0xfffff800`0285c000 PsLoadedModuleList = 0xfffff800`02aa1e90

[TaFiK]

i teraz mam rozkmine temperatura cpu w biosie wynosi 54stopnie :unsure: zas w hwmonitor 55stopni to mam w stresie pasta wczoraj wymieniona i cooler przeczyszczony

[Rocki star12]

w stresie to normalne temperaturki .

Wgl, podaj jakie posiadasz podzespoły, jbc. reinstal systemu może/powinien pomóc.

[TaFiK]

asus m4a78

phenom x4 9500

2gb ddr2

zasilacz qoltec wiem ze szajs ale na innym tez bylo to samo na, chieftecu tez

8500gt 1gb

[Rocki star12]

Wydaje mi się że jest to spowodowane w7. Nie dam sobie ręki uciąć ale wałkować tematu nie trzeba że 2gb na w7 to za mało.

A może to być wina zasilacza.. Może najlepiej jak byś sprawdził napięcia?

 

O/C jakoś tego phenoma robiłes?

[TaFiK]

bez oc , na 4gb ramu to samo

[Rocki star12]

Na twoim miejscu bym się z tym nie bawił tylko zreinstalował system, bo jeśli zależy Ci na czasie to najlepsze rozwiązanie.

Pliki na pen'a i tyle.

[TaFiK]

system praktycznie nowy z 4dni temu instalowany , no ale chyba innego wyjscia nie ma i trzeba od nowa zainstalowac

[BlackSkilll]

Wydaje mi się że jest to spowodowane w7. Nie dam sobie ręki uciąć ale wałkować tematu nie trzeba że 2gb na w7 to za mało.

A może to być wina zasilacza.. Może najlepiej jak byś sprawdził napięcia?

 

O/C jakoś tego phenoma robiłes?

 

 

2 gb ramu na w7 jest całkiem spoko miałem tak kiedyś. I w7 lepiej śmiga niż xp na 2gb ramu.

 

A propo problemu to reinstal systemu. Albo jakiś sterownik koliguje.

[TaFiK]

No i niestety ;/ z win7 przesiadlem sie na xp sp3 i odziwo zawiesza sie zadziej ale niestety dalej