dyzio163 utworzono 26 lipca 2010 utworzono 26 lipca 2010 Witam. Ostatnio bardzo dziwny problem zaobserwowałem z moim kompem. Otóż CZASAMI po załączeniu systemu pojawia się bluescreen i komp się resetuje, tj. bios się wczytuję, pokazuję się "trwa uruchamianie systemu" a następnie wyświetla się okno logowania i po tych paru sekundach wyskakuje błąd. Nie zawsze on występuję, np. parę dni temu po wystąpieniu błędu, lekko trzasnąłem obudową i komputer się załączył. Błąd występuję zawsze po tym jak wyciągam obudowę żeby ją rozkręcić. Np. dzisiaj chciałem sprawdzić parę rzeczy w obudowie, następnie skręciłem ją, chcę uruchomić a tu bluescreen, wsunąłem obudowę trochę bardziej, przy okazji nią ruszając i komp się załączyłem. Wie ktoś jaka może być tego przyczyna? Ja osobiście podejrzewam, że coś musi nie łączyć - albo karta graficzna, albo kość ram.
HQ19 komentarz 26 lipca 2010 komentarz 26 lipca 2010 Podaj kod błędu, bo to, że wyskakuje BSOD to za wiele nie mówi. Przy okazji możesz podać konfigurację komputera.
dyzio163 komentarz 26 lipca 2010 Autor komentarz 26 lipca 2010 Komputer: Core 2 Duo, E4400 z Boxowym chłodzeniem Asus P5B Galaxy GF 7600 GS 256 ddr3 z chłodzeniem Zalmana Kingston HyperX 2x1GB 800 MHz Co do błędu, póki co nie sprawdzę, bo nie wyskakuje, jednak dzisiaj będę montował wentylatory w obudowie, więc spodziewam się że wyjdzie błąd, to postaram się cyknąć foto.
HQ19 komentarz 26 lipca 2010 komentarz 26 lipca 2010 Zasilacz podaj jeszcze jaki masz, no i jak będziesz miał photo to dodaj.
raazor90 komentarz 26 lipca 2010 komentarz 26 lipca 2010 Wykonaj analizę plików minidump: http://www.forumpc.pl/index.php?showtopic=16074
dyzio163 komentarz 27 lipca 2010 Autor komentarz 27 lipca 2010 [quote]******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {c0000005, 962cc3d6, 8c789f84, 8c789b60} *** WARNING: Unable to verify timestamp for Ntfs.sys *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys ***** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 : cpu.sys ( cpu+13d6 ) Followup: MachineOwner --------- [/quote] O to co mi pokazał ten program. A to mi pokazał gdy pobrałem symbole: [quote] Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Dyz\Desktop\072710-17206-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.x86fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0x82a55000 PsLoadedModuleList = 0x82b9d810 Debug session time: Tue Jul 27 10:34:39.864 2010 (GMT+2) System Uptime: 0 days 0:00:19.472 Loading Kernel Symbols ............................................................... ................................................................ ............ Loading User Symbols Loading unloaded module list ..... Unable to load image \??\C:\Program Files\Temporary\cpu.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for cpu.sys *** ERROR: Module load completed but symbols could not be loaded for cpu.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {c0000005, 962cc3d6, 8c789f84, 8c789b60} Probably caused by : cpu.sys ( cpu+13d6 ) Followup: MachineOwner --------- [/quote] Można już stwierdzić co jest przyczyną tych błędów?
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.