Blue Screen

[Turek1233]

Witam, pojawia mi sie blue Screen ale nie wiem dlaczego. Wszedłem w narzędzia administracyjne i w system, znalazłem tam właśnie o tej godzinie i minucie błąd.

 

Nastąpił ponowny rozruch komputera po operacji wykrywania błędów. Wyniki tej operacji były następujące: 0x000000c2 (0x00000007, 0x00000cd4, 0x024c0001, 0x88a16978). Zrzut zapisano w: C:\WINDOWS\Minidump\Mini011308-02.dmp.

Czy może ktos mi pomóc dlaczego ta się dzieje ?

 

Edit:

A tak w ogóle Witam wszystkich bo to jest mój pierwszy post.

Edytowane 13 Stycznia 2008 przez Turek1233

[zax880]

Ja mialem taki blad o tych wartosciach co u ciebie jak mi kosc ramu padla (zawierala bledy), wiec jak masz wiecej niz 1 to pokombinuj i wyjmij ktoras, ewentualnie jakies sterowniki. A tak na marginesie to kiedy ci sie to dzieje?? Jak wlaczasz jakas konkretna aplikacje czy nie ma reguly i kiedy chce to sie wiesza?

 

Ps instalowales jakis nowy sprzet ostatnio?

Edytowane 13 Stycznia 2008 przez zax880

[Turek1233]

Ja mialem taki blad o tych wartosciach co u ciebie jak mi kosc ramu padla (zawierala bledy), wiec jak masz wiecej niz 1 to pokombinuj i wyjmij ktoras, ewentualnie jakies sterowniki. A tak na marginesie to kiedy ci sie to dzieje?? Jak wlaczasz jakas konkretna aplikacje czy nie ma reguly i kiedy chce to sie wiesza?

 

Ps instalowales jakis nowy sprzet ostatnio?

no własnie o to chodzi że nie ma reguły kiedy to nastąpi.

 

Tak instalowałem. Nową karte dźwiękową włożyłem i tez podejrzewam właśnie karte dźwiękową, ale nie jestem pewny.

[Kolobos]

Zrob ze zrzutem to:

http://forum.purepc.pl/index.php?showtopic=104416

Wynik wklej na forum.

[Turek1233]

Zrob ze zrzutem to:

http://forum.purepc.pl/index.php?showtopic=104416

Wynik wklej na forum.

Zrobiłem tak kazali.

Microsoft ® Windows Debugger Version 6.8.0004.0 X86

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini011208-01.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: Sat Jan 12 15:26:35.234 2008 (GMT+1)

System Uptime: 0 days 0:36:23.953

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

* 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 C2, {7, cd4, 24c0003, 8873eda8}

 

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

 

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

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

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

*** ERROR: Module load completed but symbols could not be loaded for portcls.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

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

*** ***

*** ***

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

*** ***

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

unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

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

*** ***

*** ***

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

*** ***

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

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

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

*** ***

*** ***

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

*** ***

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

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

*** ***

*** ***

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

*** ***

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

Cannot get _POOL_TRACKER_BIG_PAGES type size

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

*** ***

*** ***

*** 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 wdmaud.sys

*** ERROR: Module load completed but symbols could not be loaded for wdmaud.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 <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 : e10kx2k.sys ( e10kx2k+dd26 )

 

Followup: MachineOwner

---------

[zax880]

Probably caused by : e10kx2k.sys

O ile dobrze kojarze to ten plik jest wlasnie od karty dzwiekowej, wiec sprobuj zainstalowac nowe sterowniki lub chociazby w innej wersji.

[Turek1233]

Probably caused by : e10kx2k.sys

O ile dobrze kojarze to ten plik jest wlasnie od karty dzwiekowej, wiec sprobuj zainstalowac nowe sterowniki lub chociazby w innej wersji.

tylko skąd wziąć nowe sterowniki do Saund Blastera Audigi SB0090 - Wgrywałem sterowniki te co dali standardowo.

[zax880]

No chociazby ze strony creativa:

http://pl.europe.creative.com/support/downloads/