x-kom hosting

blue screen 0x00000050

grabekgliwice
utworzono
utworzono

Witam

Wyskakuje mi blue screen, użyłem programu Debugging Tools for Windows i wyskoczyła mi następująca treść

Microsoft ? Windows Debugger Version 6.10.0003.233 X86Copyright ? Microsoft Corporation. All rights reserved.Loading Dump File [C:\WINDOWS\Minidump\Mini121508-04.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol 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.exeWindows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatibleProduct: WinNt, suite: TerminalServer SingleUserTSMachine Name:Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700Debug session time: Mon Dec 15 19:55:03.828 2008 (GMT+1)System Uptime: 0 days 0:00:29.562********************************************************************** 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.exeLoading Kernel Symbols.......................................................................................................Loading User SymbolsLoading unloaded module list..********************************************************************************																			 **						Bugcheck Analysis									**																			 ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 1000008E, {c0000005, 8060bf25, ba977bb0, 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!_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 : ntoskrnl.exe ( nt+134f25 )Followup: MachineOwner---------

Miałem najnowsze sterowniki ze strony producenta - nic nie dało

Wgrałem sterowniki z płytki - nic nie dało

Prosze o pomoc

Psycholandia
komentarz
komentarz

Zainstaluj Service Pack 3.

grabekgliwice
komentarz
komentarz

kod błędu to 0x00000050(0XE33BODDP,0x00000000,0x8054AFCB,0x00000001)

dziwne ściągnełem service pack'a 3 z 2 różnych źródeł i 2 błędy ;/

grabekgliwice
komentarz
komentarz

może będzie dla Was podpowiedzią że przy instalowaniu windowsa tez mi sie restartowal (wszystkie partycje były sformatowane)

dar55
komentarz
komentarz

zassak memtest +86 nagraj na cd i zabootuj z niej kompa , jak bedziesz miał chociaż jeden ERROR , ram do kosza

grabekgliwice
komentarz
komentarz
zassak memtest +86 nagraj na cd i zabootuj z niej kompa , jak bedziesz miał chociaż jeden ERROR , ram do kosza

a moglbys opisac dokladniej jak to zrobic ?

dar55
komentarz
komentarz

zasysasz to http://www.memtest.org/download/2.10/memtest86+-2.10.iso.zip wypkowujesz JEDEN RAZ , nagrywasz jako obraz , i z nagranej płyty uruchamiasz kompa tak jakby system instalował

uruchomi ci się test i nie nie dotykaj przez 1-2 godziny

grabekgliwice
komentarz
komentarz

robi mi sie to juz 21 godzin i jeszcze nie skonczylo :)

dar55
komentarz
komentarz

i nie skończy :D bo jest w pętli

sprawdź czy nie ma ERROR

grabekgliwice
komentarz
komentarz

aktualnie mi wyswietla ze jest ponad 18 mln errors

moge juz przestac ? bo mam do przetestowania 1 kosc ramu a nie mam za bardzo czasu, a chyba juz te bledy udowodnily ze obie kosci mam zepsute

dar55
komentarz
komentarz

sprawdzasz jedną , wyskakuje pierwszy bład = przestajesz testować

testujesz drugą kośc - jeden błąd = przestajesz testować

Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!

Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.

×
×
  • Dodaj nową pozycję...

Powiadomienie o plikach cookie

Strona wykorzystuje pliki cookies w celu prawidłowego świadczenia usług i wygody użytkowników. Warunki przechowywania i dostępu do plików cookies możesz zmienić w ustawieniach przeglądarki.