BSOD przy włączeniu Media player!

[ixkuba (Ixjakub)]

Witam!

Korzystam z przeglądarki Mozilla Firefox 3 i na stronie np. http://www.itvp.pl/event/pekin/?page=live_player&video_id=38312&mode=2 chciałbym oglądać igrzyska olimpijskie .

Wszystko ładnie działało, lecz nagle zaczął się wyświetlać komunikat Can not create DirectShow Player.

(niepotrzebnie się rozpisuję )

Jako alternatywę zainstalowałem wtyczkę Media Player Connectivity i działało. Teraz, gdy klikam na odp. link włącza się WMP 11, ale po chwili mam BSOD (niebieski ekran śmierci): :?

http://wbv.pl/gallery.php?entry=images/dxm4iy4mvojzgyw3jctj.png

A po restarcie:

http://wbv.pl/gallery.php?entry=images/u4dmzoytviwijlmwnzdo.png

Proszę o pomoc

[cosik_ktosik]

Aby odczytać problem, którego dotyczy BSOD użyj tego: Klik

Raport daj na forum, albo znajdź linijkę Probably caused by. Zidentyfikuj sterownik robiący problemy i uaktualnij go.

[ixkuba (Ixjakub)]

Tutaj raport z programu:

Microsoft ® Windows Debugger Version 6.9.0003.113 X86 Copyright © 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 3) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0 Debug session time: Mon Aug 18 12:06:07.750 2008 (GMT+2) System Uptime: 0 days 0:23:42.358 ********************************************************************* * 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 Fastfat.SYS, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Fastfat.SYS *** ERROR: Module load completed but symbols could not be loaded for Fastfat.SYS ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 23, {e0100, b830d800, b830d4fc, 804ed684} ***** 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 eBoost.sys *** ERROR: Module load completed but symbols could not be loaded for eBoost.sys *** WARNING: Unable to verify timestamp for fltmgr.sys *** ERROR: Module load completed but symbols could not be loaded for fltmgr.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 *** *** *** ************************************************************************* ********************************************************************* * 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 : Fastfat.SYS ( Fastfat+5b22 ) Followup: MachineOwner ---------

[Olcia (Olixxx94)]

Z tego, co widzę, to problem sprawia plik Fastfat.sys , więc, patrz tu http://support.microsoft.com/kb/810091/pl

[ixkuba (Ixjakub)]

Heh!

Cytat z ww. strony:

Informacje zawarte w tym artykule dotyczą: • Microsoft Windows 2000 Professional Edition

A system posiadam Microsoft Windows XP SP3

Zresztą mam wszystkie partycje NTFS.

Jak włączam w IE stronę http://www.itvp.pl/event/pekin/?page=li … 312&mode=2 to mi ładnie odtwarza. Ciekawe…

[matusia]

może strona przeciążona i generuje błędy.

z tego co sie doczytałam to ten plik odpowiad za partycja na FAT:

http://komputery.katalogi.pl/Fastfat.sys-t46308.html

http://www.searchengines.pl/lofiversion … 63950.html

Jesteś pewien że twoje partycje są na ntfsie???

Sprawdź to tu:

PPM na Mój Komputer >> Zarządzaj >> Zarządzanie dyskami

[ixkuba (Ixjakub)]

Czy to dotyczy także pamięci pendrive?

Wszystkie trzy partycje to NTFS

[matusia]

Nie wiem czy tak może być… ale myśle że chodzi tylko o partycje systemową.

Z resztą nie ważne. Zostaw ten błąd. Poczytałam twój BSOD i znalazłam przyczne. Mianowicie chodzi o Irql Not Less Or Equal jest to ogólnie błąd sprzetu i w nim trzeba szukac problemu!

Zmieniałeś sprzęt ostatnio? jakaś GPU czy cokolwiek innego? Instalowałeś nowe sreowniki?

Wejdz w Menadżera Zarań. Czyli:

PPM na Mój Komputer>>Właściwości>>Sprzęt>>Menadżer Urządzeń.

Sprawdż czy nie masz jkichś znaków zapytania, wykrzykników,

Daj jeszcze raz tego drugiego screena z błedami które ci wyrzuciło bo ten co jest, jest nieczytelny. Daj w jakieś leprzej rozdzielczości. Najlepiej wklej tu:

http://imageshack.us/

i podaj linka.

[Olcia (Olixxx94)]

Czy to dotyczy także pamięci pendrive?

Dotyczy, jeśli system plików na penie to FAT.