ByczY
(ByczY)
26 Lipiec 2008 13:44
#1
Witam. Mam problem tak jak w temacie Podczas pracy komputer resetuje się. Chwilę przed resetem otrzymuje BS którego nawet nie można zdążyć przeczytać. Wiem że pierwsze co mi napiszecie to wina zasilacza Zasilacz ma bodajże rok i 2 miesiące, jest to Amacrox Warrior 450 PNF. Czy w tak szybkim czasie zasilacz może się uszkodzić/zepsuć ?
To TEN zasilacz, nawet od tego samego sprzedawcy.
adam749
(adam749)
26 Lipiec 2008 13:45
#2
PPM na mój komp > zaawansowane > uruchamianie i odzyskiwanie --> ustawienia > odznacz automatycznie uruchom ponownie > ok
I teraz spisz co to za BSOD. (może być nr błędu lub jakiś plik który wywołał ten błąd).
Zasiłka spox.
Scorpio
(Emilmlo)
26 Lipiec 2008 14:31
#3
adam749:
Zasiłka spox.
Ale na wszelki wypadek sprawdził bym napięcia miernikiem w spoczynku i pod obciążeniem
viewtopic.php?f=7&t=9809
viewtopic.php?t=64002
Sprawdził bym też pamięć ram memtestem na błędy
viewtopic.php?f=7&t=50125
Zobacz jakie są temperatury podzespołów.
Tobi
(Tobi)
26 Lipiec 2008 15:02
#4
Może i szybciej, zwykle sprzęt pada przy 3 pierwszych m-c użytkowania.
Są zapisane w minidumpach
http://forum.purepc.pl/temat/FAQ/8/Debu … try1167930
SEBA65310
(Seba65310)
26 Lipiec 2008 15:14
#5
ja mam pdobny problem jak włączam Viste ,pokazuje mi się logo VISTY ,a następnie BS , dopiero po restarcie kompa działa normalnie i tak cały czas. i pisze tak w raportach :
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1045
Files that help describe the problem (some files may no longer be available)
Mini071608-01.dmp
sysdata.xml
Version.txt
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.
Extra information about the problem
BCCode: a
BCP1: 00000000
BCP2: 0000001B
BCP3: 00000000
BCP4: 81EFDCBA
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1
ByczY
(ByczY)
26 Lipiec 2008 16:29
#6
Sprawdzałem - 0 errors.
W dniu 26.07.2008 , o godzinie 18:22 został dopisany post przez ByczY
Temp raczej dobre. Na procesorze mam Karakorum a na grafice standardowe ZALMANA .
W dniu 26.07.2008 , o godzinie 18:29 został dopisany post przez ByczY
Microsoft ® Windows Debugger Version 6.9.0003.113 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 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 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700 Debug session time: Sat Jul 26 15:52:16.562 2008 (GMT+2) System Uptime: 0 days 0:02:44.261 ********************************************************************* * 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 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 psched.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for psched.sys *** ERROR: Module load completed but symbols could not be loaded for psched.sys Unable to load image NDIS.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for NDIS.sys *** ERROR: Module load completed but symbols could not be loaded for NDIS.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 100000D1, {c0bbc0de, 2, 0, b352d258} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** WARNING: Unable to verify timestamp for cfosspeed.sys *** ERROR: Module load completed but symbols could not be loaded for cfosspeed.sys ************************************************************************* *** *** *** *** *** 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 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : cfosspeed.sys ( cfosspeed+278dd ) Followup: MachineOwner ---------
Tobi
(Tobi)
26 Lipiec 2008 18:07
#7
cfosspeed wykasuj dokładnie ten program.
ByczY
(ByczY)
26 Lipiec 2008 19:27
#8
Heheh zauważyłem ;p tylko zastanawia mnie dlaczego? Zawsze działał bez zarzutów, a teraz nagle jakieś błędy sypie.
adam749
(adam749)
26 Lipiec 2008 19:28
#9
Może z jakiegoś powodu się posypał? Jak Ci na nim zależy to go przeinstaluj, a jak nie zależy to go wywal i nie instaluj.
SEBA65310
(Seba65310)
26 Lipiec 2008 20:12
#10
u mnie wyskakuje przy otwieraniu minidumpa komunikat :
Mini072608-01
You don’t have permission to open this file .
Contact the file owner or an administrator to obtain permission .
Jestem administratorem systemu!