Witam,pröbowalam dzisiaj wlaczyc komputer ale niestety kilku minutach komputer samoczynnie sie restartowal,powtörzylo sie to 6 razy a za siudmym razem zdazylam tylko odhaczyc samoczynne restartowanie i znowu byl reset.Po godzinie wlaczylam znowu komputer i juz wszystko bylo w porzadku,kolega poradzil mi aby zrobic Debugging Tools for Windows i oto co mi sie w skröcie ukazalo.
Z tego co sie zorientowalam w necie to ta prisma to chyba jakis sterownik od USB Sticka ktörego uzywam do polaczenia sie z Internetem,nie rozumiem tylko dlaczego teraz cos sie dzieje,nigdy nie mialam takich problemöw.
wirusa nie ma poniewaz chlopcy na forum bezpieczenstwa sprawdzili mi logi i bylo czysto,nie sadze röwniez aby komputer sie przegrzewal,od czego?Wszystko co mam na kompie jest ograniczone do minimum a wiec watpie aby to bylo przyczyna :((
Skoki energii i brakuje mocy dla procka i się wyłacza, prawdopodobnie system chłodzący i w min. zasilacz do wymiany. Ja akurat miałem to samo i musiałem wymienić płyt główną i zasilacz :o Najlepiej idź do serwisu zapytać się co ci powiedzą
Tutaj podaje caly WinDlbg,moze to wam pomoze i bedziecie mogli mi pomöc
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) 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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Tue Mar 25 13:33:05.906 2008 (GMT+1)
System Uptime: 0 days 0:00:43.484
*********************************************************************
* 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
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, 80042000, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for PRISMA02.sys
*** ERROR: Module load completed but symbols could not be loaded for PRISMA02.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 : PRISMA02.sys ( PRISMA02+175d6 )
Followup: MachineOwner
---------
Najpierw sprawdź napięcia i temperatury, nawet w bios-ie. Jeżeli wszystko jest OK, to spróbuj odłączyć problemowy sprzęt i zobaczyć co się dzieje z systemem. Ewentualnie, przed startem Windy wciśnij F8 i wybierz ostatnią znaną dobrą konfigurację. Być może coś namieszałeś i o tym nie wiesz. Jeżeli nie działa to spróbuj tryb awaryjny. Tam usuń sprzęt, który robi problemy. Uruchom ponownie i zainstaluj go na nowo.