Bsod Google Chrome

Witam od pewnego czasu występuje u mnie Blue screen podczas korzystania z Google chrome. Najczęściej dzieje się to przy oglądaniu filmików. Wysyłam raport i proszę o pomoc

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 3) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

Debug session time: Fri Jun 24 18:12:20.109 2011 (GMT+2)

System Uptime: 0 days 3:36:00.849

*********************************************************************

* 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 watchdog.sys, Win32 error 0n2

*** ERROR: Module load completed but symbols could not be loaded for watchdog.sys

Unable to load image nv4_disp.dll, Win32 error 0n2

*** WARNING: Unable to verify timestamp for nv4_disp.dll

*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 1000008E, {e0000001, f7963925, b6ed68b8, 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 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 : nv4_disp.dll ( nv4_disp+1dda7c )


Followup: MachineOwner

kryniooo ,

Proszę poprawić pisownię w tytule tematu. W celu edycji swojego posta proszę skorzystać z przycisku Edytuj przy poście otwierającym temat.

Zignorowanie zalecenia będzie skutkowało usunięciem tematu do Kosza.

Na początek spróbuj przeinstalować sterownik od karty graficznej.

Dobrze chociaż szczerze mówiąc wątpię żeby to coś dało wczoraj formatowałem dysk nie z powodu tych błędów tylko oczyszczenia komputera ze śmieci. Błąd występował także przed formatowaniem z tymi samymi sterownikami.

Może wtyczka adobe flash powoduje wysypywanie się Chrome. Spróbuj zainstalować jakąś starszą wersję.

A sprawdzałeś czy na stronie producenta karty graficznej nie ma nowszych sterowników? Oglądając filmiki na innej przeglądarce też pojawia się BSOD?

Nie ma nowszych sterowników. Nie korzystam z innych przeglądarek.

Nie besztać za odgrzebywanie. Bo ważne. :smiley:

Ogólnie problem z BSOD watchdog na kartach NVIDII ( NV4 ) w:

  • filmach flash (youtube oraz inne tube takie jak dailymotion)

  • media player classic

  • GoogleEarth

  • wszędzie gdzie wykorzystana jest technologia DXVA (ta co odciąża naszego pentjuma podczas oglądania filmów - akceleracja wideo)

Rozwiązaniem było zainstalowanie starszej wersji sterowników w wersji 266.58 ( każde następne były już uwalone)

Obecnie (przedwczoraj) nvidia wypuściła wersję 285.27BETA

W informacjach (w PDF) dotyczącej tej wersji

http://us.download.nvidia.com/Windows/285.27/285.27-WinXP-Desktop-Release-Notes.pdf

na jedenastej stronie możemy wyczytać:_Adobe Flash–Blue-screen crash occurs when playing Adobe flash content at HD resolutions and then switching to full-screen mode._Sterownik beta do pobrania tutaj (85MB):

http://www.nvidia.com/object/winxp-285.27-beta-driver.html

Sterownik beta do pobrania tutaj, wersja PL (126MB):

http://www.nvidia.pl/object/winxp-285.27-beta-driver-pl.html