Blue screen z kmixer.sys


(Allenvego) #1

dostałem taki crush dump

Microsoft (R) Windows Debugger Version 6.6.0007.5

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 2

*** 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

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420

Debug session time: Thu Mar 15 11:47:02.296 2007 (GMT+1)

System Uptime: 0 days 4:22:25.855

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

* 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 2

*** 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 100000D1, {0, 2, 0, 0}


ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.

ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,213F80,42250FF9

***** Kernel symbols are WRONG. Please fix symbols to do analysis.


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


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

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

*** WARNING: Unable to verify timestamp for kmixer.sys

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

*** WARNING: Unable to verify timestamp for ks.sys

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

*** WARNING: Unable to verify timestamp for sysaudio.sys

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

Probably caused by : kmixer.sys ( kmixer+264e )


Followup: MachineOwner

---------

(popula) #2

To wygląda na problem powodowany sterownikiem audio. Najlepiej przeinstaluj nowymi do swojej karty dźwiękowej.


(Allenvego) #3

własni niedawno ściągnąłem z netu stery do zintegrowanej karty na mojej pł gł ..... co moge jeszcze zrobić ??


(popula) #4

Przeczytaj to


(Allenvego) #5

odistalowałem stery tak jak było napisane w tym poradniku , późnej zainstalowałem nowe ściągnięte z neta i dzisiaj znów był blue screen tym razem taki

Microsoft (R) Windows Debugger Version 6.6.0007.5

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 2

*** 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

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620

Debug session time: Fri Mar 16 16:25:49.593 2007 (GMT+1)

System Uptime: 0 days 1:36:25.163

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

* 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 2

*** 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 win32k.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for win32k.sys

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

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck 1000008E, {c0000005, e1b1f9d2, b0c33780, 0}


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


Probably caused by : win32k.sys ( win32k+144e6 )


Followup: MachineOwner

---------

(popula) #6

A mozesz przytoczyć tekst z bluescreen'a? Chodzi szczególnie o kod błędu, o nim można zidentyfikować co jest powodem. Teraz raport wskazuje na win32k.sys. Czytałem w wypowiedziach innych użytkowników, że powodowały takie błędy problemy z kośćmi RAM'u. Powinieneś je solidnie przetestować memtestem


(Allenvego) #7

a jak mam niby przytoczyć ten tekst z blue screena , jest tylko chwile i raczej sie zdaża niespodziewanie więc nawet nie mam czasu na analize co tam pisze , a w tym logu tego nie ma ?? a tak btw zrobiłem test memtestem do poziomu 125% i było 0 błędów ....


(popula) #8

Aby odczytać tekst z bluescreen'a musisz wyłączyć automatyczne uruchamianie. Klikasz:

1.Moj komputer.

2.Właściwości.

3.Zakladka- Zaawansowane.

  1. Ustawienia w polu "uruchamianie i odzyskiwanie"- odznacz ptaszek

"automatycznie uruchom ponownie".

Przy następnym bluescreenie zapisz co jest tam napisane. Będzie, co powoduje błąd i jego kod.

Złączono Posta : 17.03.2007 (Sob) 12:33

Zmienne wskazania błędów przez Debugger najczęściej wskazują na problemy sprzętowe. Jeżeli jednak chcesz, to możesz za pomocą Konsoli odzyskiwania, podmienić plik win32k,sys wpisując komendy:

copy win32k.sys C:\WINDOWS\system32\win32k.sys

copy win32k.sys C:\WINDOWS\system32\dllcache\win32k.sys

exit

Przypomnij sobie, co zmieniałeś w systemie, przed pojawieniem sie pierwszego bluescreena'a. Może w tym kryć się powód problemu. Pozdrawiam.