Częsty samoczynny restart systemu!


(Sandra19a) #1

Witam , od 3 dni mam problem z komputerem - dzisiaj w szczególności - otóż robi mi się restart i pojawia niebieski ekran który pokazuje

Driver_IRQL_NOT_LESS_OR_EQUAL . System dziś restartuje się prawie co chwile i zupełnie nie wiem czemu . Nic nowego nie instalowałam ani

nie zmieniałam . Mam windowsa XP z SP2 .

Raport błędów pokazuje komunikat :

BCCode : 100000d1 BCP1 : 00000004 BCP2 : 00000002 BCP3 : 00000001

BCP4 : 893EC3A0 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

i

C:\DOCUME~1\Kosmitka\USTAWI~1\Temp\WER23d0.dir00\Mini022709-01.dmp

C:\DOCUME~1\Kosmitka\USTAWI~1\Temp\WER23d0.dir00\sysdata.xml .

Pomóżcie bo nie mogę nic zrobić na kompie !!

Jaka jest tego przyczyna ?

Pozdrawiam


(me@djohnsc) #2

Tutaj znajdziesz rozwiązanie co do tego bluescreena => Błędy systemu Windows (kody BSOD)

Przeczytaj też Bluescreen (BSOD) - szukanie przyczyny powstawania


(Sandra19a) #3
HD Tune: SAMSUNG SP1213N Health


ID Current Worst ThresholdData Status   

(01) Raw Read Error Rate 100 100 51 0 Ok       

(03) Spin Up Time 61 1 0 6592 Ok       

(04) Start/Stop Count 97 97 0 4024 Ok       

(05) Reallocated Sector Count 253 253 10 0 Ok       

(07) Seek Error Rate 253 253 51 0 Ok       

(08) Seek Time Performance 253 253 0 0 Ok       

(09) Power On Hours Count 98 98 0 1437421 Ok       

(0A) Spin Retry Count 253 253 49 0 Ok       

(0C) Power Cycle Count 98 98 0 2026 Ok       

(C2) Temperature 139 76 0 33 Ok       

(C3) Hardware ECC Recovered 100 100 0 129336176 Ok       

(C4) Reallocated Event Count 253 253 0 0 Ok       

(C5) Current Pending Sector 253 253 10 0 Ok       

(C6) Offline Uncorrectable 253 253 10 0 Ok       

(C7) Ultra DMA CRC Error Count 100 92 51 510 Ok       

(C8) Write Error Rate 100 100 51 0 Ok       

(C9) TA Counter Detected 100 100 51 0 Ok       


Power On Time : 1437421

Health Status : Ok

Zrobiłam odczyt dysku programem HD TUNE , pomożecie zinterpretować ??

-- Dodane 27.02.2009 (Pt) 19:55 --

Sprawdzić jeszcze programem WinDbg - Microsoft Debugging Tools ?


(Olixxx94) #4

odczytaj ten plik i raport z Microsoft Debugging Tools wrzuć na wklej.org i daj linka na forum.


(Cosik Ktosik) #5

Wymień taśmę ATA (szeroka)


(Sandra19a) #6
Microsoft (R) Windows Debugger Version 6.11.0001.402 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 2) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553420

Debug session time: Fri Feb 27 20:30:53.234 2009 (GMT+1)

System Uptime: 0 days 1:07:56.840

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

* 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

..........

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck 100000D1, {4, 2, 1, 893c03a0}


***** 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 : Unknown_Image ( ANALYSIS_INCONCLUSIVE )


Followup: MachineOwner

---------

(Cosik Ktosik) #7

Błąd 0x000000D1: http://www.hotfix.pl/articles.php?article_id=11

Sterownik albo ten nieszczęsny kabel

Z tego DMP nic więcej nie wynika. Potrzebne inne.


(Sandra19a) #8

Uhh, to mam nadzieje że zmiana kabelka pomoże :slight_smile: