Witam. Przed chwilą zawiesil mi sie komputer(podczas grania w CS) i pojawil sie blue screen z jakimis napisami. Ostatnio komputer zawiesil mi sie ale nic nie wyskoczylo a czasem nawet sam sie resetuje. Czym to moze byc spowodowane?? Prosze o pomoc
Zasilacz masz niezły, więc o ile jest sprawny to albo coś się przegrzewa albo pamiątki dostały alzheimera…:mrgreen:
komputer kupowalem w serwisie komputerowym a oni zamawiaja chyba czesci wiec nie wiem…komputer jest nowy i nie wiem dlaczego sie zawiesza ;/ strasznie to przeszkadza
nie wiem dokladnie taki to bląd. bylo tak ze zawiesil sie komputer po chwili wyskoczyl blue screen i jakies napisy. Moge dac zawartosc pliku minidump
Złączono Posta : 16.02.2007 (Pią) 18:02
Microsoft (R) Windows Debugger Version 6.6.0007.5
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 2
*** 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 Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Fri Feb 16 16:32:35.750 2007 (GMT+1)
System Uptime: 0 days 2:25:27.329
*********************************************************************
* 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 2
*** 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 10000050, {cde00000, 0, cde00000, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** 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***
******
*************************************************************************
*** WARNING: Unable to verify timestamp for Senfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for Senfilt.sys
Probably caused by : Senfilt.sys ( Senfilt+2cc3f )
Followup: MachineOwnerPoszukaj nowych sterów do karty dźwiękowej i zainstaluj.
ale skad mam wiedziec jakiego beda dobre i ktore beda pasowac?
Złączono Posta : 17.02.2007 (Sob) 18:29
komputer znowu sie zawiesil i wyskoczyl blue screen. Pisalo zeby cos tam zainstalowac jakies nowe sterowniki chyba albo wymienic karte video. Na dole pisalo ze trwa zrzucanie pamieci fizycznej . ;/