x-kom hosting

Problem z włanczaniem Filmów lub gry

izumi19
utworzono
utworzono

Witam :) Problem polega na tym ze od niedawna kiedy chce włonczyć jakis film np. pzrez Winampa Czy Media Player lub Real Player komputer sie resetuje pojawia sie przez chwilke niebieskie okno z tekstem na calym ekrane ale to pzrez sekunde i reset komputera to samo ejst przy wlanczaniu gry:( Jeśli ktoś wie obc to prosze napisać Dzięki z Gory :* :)

[lucas]
komentarz
komentarz

Zainstaluj Debugging Tools

Po instalacji dopalamy programik;) Start--->>> Wszystkie programy---->>>Debugging Tools for Windows (x86)----->>>>WinDbg

Klikamy na File, potem Open Crash Dump Wskazujemy lokalizację c:\Windows\minidump

Pliki wewnątrz tego folderu mają unikalną nazwę, np. Mini111208-01.dmp 11- miesiąc 12- dzień 08 rok 2008. Wskaż ten plik,z datą kiedy wyskoczył Ci Blue Screen;) klikamy na Otwórz.

Uwaga: Jeśli pojawi się okno o Zapisaniu naszego Miejsca pracy (Save Workspace) wybierasz NO.

jeśli wszystko dobrze zrobiłaś, powinno pojawić się okienko z tekstem, wklej go tutaj;)

izumi19
komentarz
komentarz
Microsoft ? Windows Debugger Version 6.9.0003.113 X86Copyright ? Microsoft Corporation. All rights reserved.Loading Dump File [C:\WINDOWS\Minidump\Mini080408-01.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 SingleUserTS PersonalKernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700Debug session time: Mon Aug  4 22:53:22.187 2008 (GMT+2)System Uptime: 0 days 11:55:07.921********************************************************************** 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 1000000A, {16, 1c, 0, 805021de}***** Kernel symbols are WRONG. Please fix symbols to do analysis.*** WARNING: Unable to verify timestamp for atkosdmini.dll*** ERROR: Module load completed but symbols could not be loaded for atkosdmini.dll*** WARNING: Unable to verify timestamp for atkdisp.dll*** ERROR: Module load completed but symbols could not be loaded for atkdisp.dll*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sys*** WARNING: Unable to verify timestamp for dxg.sys*** ERROR: Module load completed but symbols could not be loaded for dxg.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									  ******																   ********************************************************************************************************************************************************																   ******																   ******	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 : atkosdmini.dll ( atkosdmini+1370 )Followup: MachineOwner---------

//logi wstawiamy w tagi code

//vocativus

Mateusz J.
komentarz
komentarz

Probably caused by : atkosdmini.dll ( atkosdmini+1370 )

Rozwiązanie

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.