samoczynny reset laptopa

[radio79]

Co może być przyczyną resetowania mi się laptopa? Mam Toshibe L40-139. Przegrzewanie chyba to nie jest bo czasem resetuje się po 5 minutach. Nie jest to jakiś program którego aktualnie używam bo robi się to także gdy nic nie robię. Antywirus nic nie znajduje, Tune up tak samo.
Zaczęło się jak Windows zainstalował sobie jakiegoś updata, chyba w mniej więcej tym czasie.
Czy może po 4 latach te typy tak mają i trzeba kupić nowy?

[lemari]

Odczytywanie BSOD

[radio79]

Bardzo proszę o pomoc w rozszyfrowaniu problemu


Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini021311-02.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 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805540c0
Debug session time: Sun Feb 13 09:38:07.903 2011 (UTC + 0:00)
System Uptime: 0 days 0:11:13.429
*********************************************************************
* 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 1000008E, {c0000005, 8062eb7b, a9b50bb4, 0}

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

Probably caused by : ntoskrnl.exe ( nt+157b7b )

Followup: MachineOwner
---------

[xoceanfirex]

Być może wina procka, ew. zasilacza

[Gość: a]

5 minut to wystarczająco dużo czasu na przegrzanie. Temperatury trzeba zmierzyć.

[radio79]

czy ktoś wie o co chodzi w tym logu?

[m.gregor]

Sprawdz pamiecm memtest86+