Restart laptopa i niebieski ekran


(Maliszewska Aga) #1

Witam

Mam problem z laptopem siostry. Od jakiegoś czasu resetuje sie sam. Przed restartem pojawia sie niebieski ekran. Ponadto wydaje mi się, że laptop jest zbyt ciepły. Siostra mówi, że tam są dwa systemy Vista i XP. Laptop działa na xp, ja nie wiem gdzie ta vista może być, może trzeba ją odinstalować, ale jakoś nie wiem jak jak jest jedna partycja. Zrobiłam skanowanie awastem przed rozruchem i uzyskałam takie wyniki:

Plik C:\Users\Michal.BZIANGUL-322758\Ustawienia lokalne\Temporary Internet Files\Content.IE5\QRWNVG3W\jbantv[1].zip\telewizja.exe Błšd 42125 {Archiwum ZIP jest uszkodzone.}

Plik C:\Windows\Temp\set1ED9.tmp\Wise0015.bin Błąd 42146 {Archiwum instalatora jest uszkodzone.}

Plik C:\Windows\Temp\set814E.tmp\Wise0015.bin Błąd 42146 {Archiwum instalatora jest uszkodzone.}

Plik C:\Windows\Temp\setBBF8.tmp\Wise0015.bin Błąd 42146 {Archiwum instalatora jest uszkodzone.}

Plik C:\Windows\Temp\setD224.tmp\Wise0015.bin Błąd 42146 {Archiwum instalatora jest uszkodzone.}

Czy ktoś wie co to może oznaczać? Ja myślę, że najlepiej byłoby przeinstalować od nowa tego laptopa, ale troche mnie martwi to przegrzewanie się go. Może problemem jest np wentylator, nie wiem , proszę o pomoc


(Olixxx94) #2

Klawiszse "logo Win"+Pause/Break->Zaawansowane->Ustawienia w sekcji uruchamianie i odzyskiwanie-> odhacz Automatycznie uruchom ponownie. Podaj kod błędu i plik, który go powoduje, jeśli takowy jest wymieniony.


(Maliszewska Aga) #3

Klawiszse "logo Win"+Pause/Break a gdzie to jest, sory ale nie bardzo wiem


(deFco247) #4

Klawisz Windows masz pomiędzy Ctrl a Alt , a Pause Break w tych trzech klawiszach na prawo od F12. :slight_smile:


(Maliszewska Aga) #5

A czy sądzisz że przeinstalowanie laptopa rozwiąże problem?

-- Dodane 07.08.2009 (Pt) 21:53 --

Odhaczyłam "Automatycznie uruchom ponownie" ale gdzie ten kod błędu i plik który go powoduje???

-- Dodane 07.08.2009 (Pt) 23:17 --

Zainstalowałam program Debugging Tools i zrobiłam jak było we wskazówkach i wyszło mi coś takiego:

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 2) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a820

Debug session time: Thu May 21 22:09:22.156 2009 (GMT+2)

System Uptime: 0 days 0:55:08.699

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

* 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 7F, {0, 0, 0, 0}


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


*** WARNING: Unable to verify timestamp for PAC7302.SYS

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

******

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

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

******

******

***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 : PAC7302.SYS ( PAC7302+2a84c )


Followup: MachineOwner

Czy to o taki rodzaj błedu chodziło, prosze o pomoc


(Maliszewska Aga) #6

No tak ale ja nie wiem jak te błędy odczytać, nie znam sie za bardzo na tym, prosze o wskazówki, a może po prostu przeinstalować laptopa tylko nie wiem czy to rozwiąże problem...


(sla17) #7

Przeinstalowanie systemu operacyjnego (nie laptopa :!:slight_smile: powinno pomóc.

Jak jest używany laptop? Dywan/koc, kolana, stół? Ma dobrą wentylację? Czy wiatraczki są zasłonięte (u mnie na dole jest wiatrak zasysający chłodne powietrze co jest ważne).

Możesz spróbować F8 przy starcie i wybranie Ostatnia dobra konfiguracja czy coś w tym stylu (dawno na tym na XP nie korzystałem)


(Maliszewska Aga) #8

F8 nie pomogło nadal sie restartuje... beznadzieja