Jak w temacie. Dziwny problem… Obojętnie jaki film i czym go otworze, to sytuacja jest identyczna - reset. Jak to naprawić?
Jaki windows?
Jaki av?
XP HE SP2, avast.
alojzy , nie masz żadnych bluescreenów??
Masz jakieś kodeki zainstalowane??
Prawdopodobnie komp się resetuje bo w trakcie oglądania filmów wyskakuje ekran śmierci… Wjedź do c:\windows\minidump i sprawdź czy masz tam pliki…
Bluescreena nie ma, ale wlaśnie w minidumpie są 4 pliki (Mini030909-0x.dmp, x to liczby od 1 od 4). Kodeki k-lite i ffdshow.
DMP=występowanie bluescreenów.
Aby dowiedzieć się więcej, czego dotyczył bluescreen, odczytaj plik DMP. Zrób to wg tej instrukcji 
Czytanie plików DMP
Sprawdź rozwiązanie (także w linkach): kody błędów.
Jeżeli nie rozwiążesz problemu, to daj raport na forum. Wklej go na http://wklej.org a tu daj tylko link do niego.
Sprawdź teraz, czy są jakieś pliki DMP.
Ale żadnego BSODa nie było… :?
Bo znika, gdyż dochodzi do restartu. Plik DMP tylko wtedy powstaje.
Aby BSOD pozostał na ekranie, wejdź do panelu sterowania->system->zaawansowane->uruchamianie i odzyskiwanie->ustawienia->odznacz automatyczny restart po awarii. Napisz na forum, jaki kod błędu został wygenerowany oraz jaką podano przyczynę.
Ściągnąłem narzędzie MS do odczytywania *.dmp, jak tylko uda mi się coś odczytać, to dam tu znać.
– Dodane 14.03.2009 (So) 22:10 –
Microsoft (R) Windows Debugger Version 6.11.0001.404 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
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a6a0
Debug session time: Mon Mar 9 16:35:56.546 2009 (GMT+1)
System Uptime: 0 days 1:12:10.119
*********************************************************************
* 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
.........
Unable to load image cmuda.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cmuda.sys
*** ERROR: Module load completed but symbols could not be loaded for cmuda.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {0, 2, 0, f7a32780}
***** 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 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 : cmuda.sys ( cmuda+2b780 )
Followup: MachineOwner
---------Wygląda na to, że błąd wywałują drivery od karty muzycznej… Spróbuj odinstalować obecne drivery i zainstalować nowsze…
Tu masz opis bsodu, od którego podałeś plik .dmp:
Stop 0x0000000A lub IRQL_NOT_LESS_OR_EQUAL
Proces lub sterownik trybu jądra próbował uzyskać dostęp do obszaru pamięci bez
autoryzacji. Ten błąd Stop zazwyczaj powodowany jest przez uszkodzone lub niekompatybilne urządzenie albo oprogramowanie. Nazwa będącego sprawcą sterownika urządzenia często ukazuje się w komunikacie o błędzie Stop i może dostarczyć ważnych wskazówek do rozwiązania problemu.
Opis pochodzi ze strony którą podał cosik_ktosik
Sterowniki najnowsze, odinstalowanie i ponowne zainstalowanie nic nie dało. Mem test - 0 errors, pamięć czysta. Jakieś pomysły? :?
Zrób jeszcze tak:
Wejdź w start->uruchom->cmd, wciśnij enter albo kliknij ok.
W okno które się otworzyło wpisz chkdsk /f /r jeżeli pojawi się informacja, że wolumin nie może być sprawdzony i czy zaplanować skanowanie przy następnym uruchomieniu komputera daj t, wciśnij enter i uruchom ponownie komputer. Kiedy rozpocznie się sprawdzanie dysku zwróć uwagę, czy zostały znalezione jakieś błędy… Również pobierz program hdtune i poda na forum zawartość zakładki health…
Dysk jest sprawny.
Zrób jeszcze raz analizę DMP, ale wersję pełną: http://www.hotfix.pl/articles.php?article_id=17
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: cmuda
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4282f5d2
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000000
CURRENT_IRQL: 2
FAULTING_IP:
cmuda+2b780
f7a32780 660f6f00 movdqa xmm0,xmmword ptr [eax]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from f7aab05a to f7a32780
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f8951cb0 f7aab05a 2819d11f fffff800 81b15020 cmuda+0x2b780
00000000 00000000 00000000 00000000 00000000 cmuda+0xa405a
STACK_COMMAND: kb
FOLLOWUP_IP:
cmuda+2b780
f7a32780 660f6f00 movdqa xmm0,xmmword ptr [eax]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: cmuda+2b780
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: cmuda.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------