Czasem zawiesza mi się system i wyświetla Blue Screen

(St4szek) #1

Zastanawiam się czy w dobrym dziale piszę ( czy nie lepiej w problemach?! jeżeli konieczne proszę o przeniesienie tematu)

Mam pewien problem z laptopem… (ASUS C90 - C2D E6600, GF 8600 GT, 2GB, 160GB) mam wgraną vistę z płytki załączonej do kompletu. Jakiś czas temu zdarzyło mi się że po wgraniu Alkohola 120% system w ogóle nie chciał wystartować. Restartował się przed wczytaniem widoku logowania użytkowników. Poradziłem sobie robiąc formata. Zapytałem na forum powiedziano mi że to wina niekompatybilności programu z systemem Vista. Ale dzisiaj słuchając internetowego radia przez WinAmpa również komputer wyświetlił mi niebieski ekran i się zresetował. Po załadowaniu windy wyświetliło mi że komputer odzyskał sprawność po poważnym błędzie… w szczegółach było coś takiego:

Podpis problemu:

  Nazwa zdarzenia problemu:	BlueScreen

  Wersja systemu operacyjnego:	6.0.6001.2.1.0.768.3

  Identyfikator ustawień regionalnych:	1045


Dodatkowe informacje o problemie:

  BCCode:	a

  BCP1:	994114F4

  BCP2:	00000002

  BCP3:	00000001

  BCP4:	81D03874

  OS Version:	6_0_6001

  Service Pack:	1_0

  Product:	768_1


Pliki pomagające opisać problem:

  C:\Windows\Minidump\Mini070508-01.dmp

  C:\Users\XXX\AppData\Local\Temp\WER-69716-0.sysdata.xml

  C:\Users\XXX\AppData\Local\Temp\WERCB2A.tmp.version.txt


Przeczytaj nasze zasady zachowania poufności informacji:

  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0415

Potraficie to zdiagnozować? Bardzo bym Was prosił… aha jeszcze później mama mówiła że siedząc i buszując po internecie również zawiesił jej się komputer i zresetował… nie wiem jak to wyglądało dokładnie bo nie potrafiła mi tego do końca opisać… Powiedzcie jaka może być przyczyna takich zachowań się komputera? Z góry dziękuję. POZDRAWIAM

W dniu 06.07.2008 , o godzinie 0:25 został dopisany post przez st4szek

Zauważyłem że są podobne wątki… przepraszam za zaśmiecanie forum… Ale mimo wszystko proszę o jakąś pomoc…

(Cosik Ktosik) #2

Odczytaj co spowodowało błąd z pliku C:\Windows\Minidump\Mini070508-01.dmp

http://forum.purepc.pl/temat/FAQ/8/Debu … try1167930

Błąd Stop 0x0000000A, czyli zapewne IRQL_NOT_lESS_OR_EQUAL oznacza wadliwy sterownik. Odczytaj ten DMP i zaktualizuj sterownik, który poowduje błąd.

(St4szek) #3

Zrobiłem tak jak w tym poście. Pokazało mik coś takiego:

Microsoft (R) Windows Debugger Version 6.9.0003.113 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntkrnlpa.exe

*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe

Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0x81c0c000 PsLoadedModuleList = 0x81d23c70

Debug session time: Sat Jul 5 18:17:29.777 2008 (GMT+2)

System Uptime: 0 days 2:58:32.806

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

* 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntkrnlpa.exe

*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe

Loading Kernel Symbols

............................................................................................................................................................................

Loading User Symbols

Loading unloaded module list

.....................................

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck A, {a473a4f4, 2, 1, 81cc1874}


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

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

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

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

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

******

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

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

******

******

***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 : itecir.sys ( itecir+3f76 )


Followup: MachineOwner

---------
(Cosik Ktosik) #4

To jest chyba sterownik od IR (podczerwieni): http://www.runscanner.net/files/sys/ite … r.sys.aspx