Samoczynny restart i BCCode : 100000be
po paru minutach pracy,laptop się samoczynnie restartuje.
po restarcie pokazuje błąd:
[code]BCCode : 100000be BCP1 : F6E5252F BCP2 : 0F666121 BCP3 : EC8909B0
BCP4 : 0000000A OSVer : 5_1_2600 SP : 2_0 Product : 256_1 [/code]
Windbg:
[code]Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini031708-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 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
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Mon Mar 17 11:48:37.546 2008 (GMT+1)
System Uptime: 0 days 0:15:23.118
*********************************************************************
* 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 4E, {8f, fffffeff, 272eb, 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : ntoskrnl.exe ( nt+21925 )
Followup: MachineOwner
---------[/code]
co robić?
Odpowiedzi: 3
i????
to co wygrzebałam:
Nazwa systemu operacyjnego Microsoft Windows XP Professional
Wersja 5.1.2600 Dodatek Service Pack 2 Kompilacja 2600
Producent systemu operacyjnego Microsoft Corporation
Nazwa systemu EMI-426164C274A
Producent systemu iQon.ie
Model systemu M660SE
Typ systemu Komputer z procesorem x86
Procesor x86 Family 6 Model 14 Stepping 8 GenuineIntel ~1662 Mhz
Wersja/data systemu BIOS Phoenix Technologies LTD 6.00, 2007-04-13
Wersja SMBIOS 2.4
Katalog systemu Windows C:\WINDOWS
Katalog systemowy C:\WINDOWS\system32
Urządzenie rozruchowe \Device\HarddiskVolume2
Ustawienia regionalne Polska
Warstwa abstrakcji sprzętu Wersja = "5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)"
Nazwa użytkownika EMI-426164C274A\emi
Strefa czasowa Środkowoeuropejski czas stand.
Całkowita pamięć fizyczna 1 024,00 MB
Dostępna pamięć fizyczna 625,79 MB
Całkowity rozmiar pamięci wirtualnej 2,00 GB
Dostępna pamięć wirtualna 1,96 GB
Obszar pliku strony 2,12 GB
Plik strony C:\pagefile.sys
problem mam od samego początku tzn.odkąd został zakupiony laptop na rynku wtórnym oraz przeinstalowaniu. nie wiem czy prędzej były takie problemy u poprzedniego właściciela (był ten sam win, ale w języku słowackim).
restart następuje w krótkim czasie po uruchomieniu, obojętnie czy uruchomiony jest net, czy winamp czy inne programy. Także nie robi mu różnicy, czy w tym czasie jest podłączony do zasilania stałego czy czerpie z baterii.
nie wiem co jeszcze
Napięcia i pamięć do sprawdzenia ( może w kolejności odwrotnej ).
Naprawdę tach trudno podać choćby model notebooka i okolicznosci , w których problem zaczął się pojawiać ? - Pytanie jest oczywiście retoryczne.
Strona 1 / 1