TaFiK utworzono 7 października 2013 utworzono 7 października 2013 (edytowane) Siema mam problem , otoz przy przegladaniu internetu najczesciej podczas przelaczenia pomiedzy kartami komputer mi sie zawiesza i resetuje . Jak sie uruchomi juz to wyskakuje okienko ze system odzyskal sprawnosc po nieoczekiwanym zamknieciu i pisze to ;) 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 No i niestety system wykrywa ze byl bsod ale ja zadnego bluescreena nie widzialem :D i nie zbyt moge odczytac co bylo powodem resetu Dodam ze wymienialem zasilacz , ram i dalej to samo . Temperatury w biosie to 54stopnie na CPU . A w hwmonitor 55stopni przy 100%obciazeniu cpu . Dysk skanowalem hdtune i nie wykrylo zadnych bledow . phenom x4 9500 asus m4a78 2gb ram ddr2 8500gt 1gb zasilacz quoltec 520w / bylo na innym sprawdzane i to samo
Filo1 komentarz 7 października 2013 komentarz 7 października 2013 podaj konfigurację z uwzględnieniem zasilacza <marka,moc> i wykonaj to http://www.forumpc.pl/tutorials/article/79-debugging-tools-for-windows-i-pliki-minidump/
TaFiK komentarz 7 października 2013 Autor komentarz 7 października 2013 sorki ale nie umiem spoilera robic :D Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\100713-14133-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`02863000 PsLoadedModuleList = 0xfffff800`02aa8e90 Debug session time: Mon Oct 7 20:43:33.818 2013 (GMT+2) System Uptime: 0 days 0:00:08.034 ********************************************************************* * 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, fffffa80028668f8, 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 ---------
Filo1 komentarz 7 października 2013 komentarz 7 października 2013 Probably caused by : hardware Podaj swoją konfigurację komputera
Gość komentarz 7 października 2013 komentarz 7 października 2013 / bylo na innym sprawdzane i to samo jakim?
TaFiK komentarz 7 października 2013 Autor komentarz 7 października 2013 tracer 400w i chieftec gps 450
Gość komentarz 7 października 2013 komentarz 7 października 2013 http://www.programosy.pl/program,occt-perestroika.html wlacz na 20 minut
Gość komentarz 7 października 2013 komentarz 7 października 2013 No to wklej po zabawie 20 min na forum (tam gdzie przycisk on)
TaFiK komentarz 7 października 2013 Autor komentarz 7 października 2013 z ktorej zakladki CPU:OCCT czy CPU:LINPACK?
TaFiK komentarz 7 października 2013 Autor komentarz 7 października 2013 co najgorsze raz moge i nawet pol dnia siedziec na necie i nic , a raz 15min i lag . troche mnie zdziwilo napiecie na lini 12 bo az 15.22v
Gość komentarz 7 października 2013 komentarz 7 października 2013 Załatw miernik i pomierz napiecia na zasilaczu .Być może program oszukuje ..........
Filo1 komentarz 7 października 2013 komentarz 7 października 2013 program na pewno oszukuje .. nie ufa się wskazaniom programu, jedynie V Core zazwyczaj dobrze pokazuje reszta napięć zazwyczaj wyssana z palca
TaFiK komentarz 7 października 2013 Autor komentarz 7 października 2013 (edytowane) w hwmonitor znowu jest 15.312v a w biosie 11.864v , a znowu miernika nie mam zbytnio skad wykminic :(
Filo1 komentarz 7 października 2013 komentarz 7 października 2013 Program HDTune screen z zakładki health oraz być może trzeba będzie przetestować RAM, czy próbowałeś z innymi pamięcami? jeżeli nie to spróbuj
TaFiK komentarz 7 października 2013 Autor komentarz 7 października 2013 tak probowalem na innych to samo
TaFiK komentarz 9 października 2013 Autor komentarz 9 października 2013 Wymieniony. Wczoraj zainstalowalem XP i odziwo wszystko pieknie ladnie dzialalo az do teraz niestety znowu lag i reset .
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.