Bluescreen podczas ogladania filmow

przez **sonar** » 03 Sie 2008, 10:53

Witam.
Mam pewien problem... Otoz, kiedy chce ogladnac jakis film to odrazu wywala mi po 2,3 sekundach bluescreena. nawet nie moge zobaczyc co on tam zlego zrobil bo system odrazu robi restart. przeinstalowywalem odtwarzacze, kodeki... co mam zrobic zeby moc znow ogladac filmy?

przez **Palacio** » 03 Sie 2008, 10:56

z WMP też tak się dzieje :?:

przez **huber2t** » 03 Sie 2008, 11:05

Usuń wszystkie kodeki i odtwarzacze wideo, przeczyść po nich system ccleanerem

Zainstaluj k lite codec pack full

a po tym:

Pokaz na forum log z tego: http://www.forumpc.pl/index.php?showtopic=16074

przez **sonar** » 03 Sie 2008, 12:57

ok. dzieki za rade, zrobilem wszystko tak jak tam pisalo i taki wyskoczyl mi komunikat:

Kod: Zaznacz wszystko: Microsoft (R) Windows Debugger Version 6.9.0003.113 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini080308-05.dmp] 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 <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.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: Sun Aug 3 12:09:08.296 2008 (GMT+2) System Uptime: 0 days 1:31:30.019 ********************************************************************* * 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.exe Loading Kernel Symbols .................................................................................................................................. Loading User Symbols Loading 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 ---------

przez **huber2t** » 03 Sie 2008, 13:24

Jeśli to przeczytasz to rozwiązesz swój problem:
http://www.searchengines.pl/Restart-kom ... 02929.html
http://www.searchengines.pl/index.php?s ... ntry455581

przez **Dawid255151** » 03 Sie 2008, 22:23

huber2t napisał(a):Jeśli to przeczytasz to rozwiązesz swój problem:
http://www.searchengines.pl/Restart-kom ... 02929.html
http://www.searchengines.pl/index.php?s ... ntry455581

huber2t zamiast pokazywać linki co można zrobić lepiej przejść do rzeczy konkretnych

1.Przetestuj dysk tym programikiem HD TUNE
2.Przetestuj pamięci Memtest
3.jaki masz komputer tzn podzespoły i najważniejsze jaki zasilacz.

przez **huber2t** » 04 Sie 2008, 05:43

Dawid heh, przejrzyj te linki, Picasso jest najlepszym specjalistą w dziedzinie komputerów i po co ja mam przepisywac to co ona napisałą, to jest bez sensu.

Ale widze że ty nie zajrzałeś bo rozwiązaniem tego prawopodobnie jest sterownik ASUSa, a dokładnie Enhanced Display Driver Helper Service w ASUS Other Devices. Odinstalowanie sposobem przedstawionym na tamtym forum i zainstalowanie oryginalnych sterowników nVidii rozwiązało problem z filmami.

Przynajmniej na razie nie widzę problemów. Mam nadzieję, że mój temat pomoże komuś jeszcze. Nie instalujcie sterowników ASUSa do kart graficznych, jeśli nie jesteście pewni, że są w porządku. Lepiej ściągnąć oryginały ze stron.

Nawet jeśli kolega by twoje polecenia zrobił to nie dało by skutku

przez **Dawid255151** » 04 Sie 2008, 09:49

Nawet jeśli kolega by twoje polecenia zrobił to nie dało by skutku

Tu nie chodzi o skutek! tu chodzi o wykluczenie podzespołów

przez **huber2t** » 04 Sie 2008, 10:03

Rozwiązanie problemu już podałem więc po co inne wykluczać

przez **Dawid255151** » 04 Sie 2008, 10:50

Z własnego doświadczenia wiem że jak bluscrenny to najlepiej pamięci testować ;-)

Ale nic może i masz racje.

Bluescreen podczas ogladania filmow

Bluescreen podczas ogladania filmow

Kto jest na forum