win32k.sys słynny niebieski ekran
Witam
Jeszcze nei dawno miałem problem z zalogowaniem do kompa (nie miałem hasła) a teraz drugi problem.
przy troche większym obciąźeniu systemu lub długiej bezczyności kompter pokazuje niebieski ekran a następnie sam się restartuje lub trzeba mu w tym pomóc.
nie instalowałem źadnych nowych kart graficznych ani innych rzeczy mam windows xp
oto log z DMP
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini022306–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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** 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 UP Free x86 compatible
Product: WinNt
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8054cb28
Debug session time: Thu Feb 23 12:23:06.811 2006 (GMT+1)
System Uptime: 0 days 2:18:09.398
*********************************************************************
* 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 2
*** 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 50, {d52b540d, 1, bf87637d, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Unable to load image win32k.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+7637d )
Followup: MachineOwner
–––––––––
[/u]
Jeszcze nei dawno miałem problem z zalogowaniem do kompa (nie miałem hasła) a teraz drugi problem.
przy troche większym obciąźeniu systemu lub długiej bezczyności kompter pokazuje niebieski ekran a następnie sam się restartuje lub trzeba mu w tym pomóc.
nie instalowałem źadnych nowych kart graficznych ani innych rzeczy mam windows xp
oto log z DMP
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini022306–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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** 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 UP Free x86 compatible
Product: WinNt
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8054cb28
Debug session time: Thu Feb 23 12:23:06.811 2006 (GMT+1)
System Uptime: 0 days 2:18:09.398
*********************************************************************
* 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 2
*** 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 50, {d52b540d, 1, bf87637d, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Unable to load image win32k.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+7637d )
Followup: MachineOwner
–––––––––
[/u]
Odpowiedzi: 3
Troszkę poszukałem w archiwum.kamaa:czemu tak uwaźasz??
damiancore:O ile się nie myle to win32k.sys jest spoowodowane problemem sprzetowym.
czemu tak uwaźasz??
O ile się nie myle to win32k.sys jest spoowodowane problemem sprzetowym. Np. przegrzewającym sie procesorem, koścmi ramu itd...
Strona 1 / 1