Witam od jakiegoś czasu tj. kilka miesięcy mam pewien problem z ww. zjawiskiem.
Niestety, jest to tak uciążliwe, że komputer resetuje mi się kilka razy dziennie!
Z jakieś 2 miesiące temu miałem ten sam problem, lecz pewnego razu wyskoczył blue screen i komputer nie chciał się włączyć za każdym razem wyskakiwał blue screen i na tym się kończyło
komputer oddałem do serwisu został zresetowany bios i wgrano na nowo windowsa.
Niestety, na nowo pojawia się ten sam problem.Nie wiem, co mam robić?
Przeglądając internet zobaczyłem, że jest możliwość sprawdzenia problemu w folderze
C:\WINDOWS\Minidump
Lecz niestety jest to dla mnie "czarna magia"
Jeśli byłby ktoś na tyle miły aby mi pomóc będę wdzięczny. Mam tych błędów w tym folderze kilkanaście zapisanych.
Jest tutaj jakaś osoba, która pomoże mi wyjaśnić co jest nie tak z moim komputerem?
Na początek wkleję ostatni raport:
( Dodam także, że te raporty, które są zapisane na dysku różnią się się od siebie, więc pewnie problem nie dotyczy jednej rzeczy)
Loading Dump File [C:\WINDOWS\Minidump\Mini070112-09.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) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Jul 1 20:19:36.171 2012 (GMT+2)
System Uptime: 0 days 0:25:50.850
*********************************************************************
* 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
...........
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8053a933, a4ef59e8, 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : win32k.sys ( win32k+370c5 )
Followup: MachineOwner
---------
Blue Screen win32k.sys Windows XP
-
DrAudis
- Posty: 3
- Rejestracja: 02 lip 2012, 01:35
Blue Screen win32k.sys Windows XP
Ostatnio zmieniony 02 lip 2012, 11:56 przez seba86mu, łącznie zmieniany 1 raz.
Powód: Korekta tytułu.
Powód: Korekta tytułu.
-
seba86mu
- Posty: 9744
- Rejestracja: 13 lis 2008, 18:07
- Lokalizacja: Sosnowiec
Blue Screen znowu mam z tym problem!
Jaką posiadasz płytę główną i kartę graficzną ?
Sprawdzisz to programem => CPU-Z => zakładka Mainboard => zakładka Grpahics => pozycja Name
Podaj odczyty temperatur oraz wartości napięć z programu => Dostępne tylko dla zarejestrowanych użytkowników (screen okna programu)
Odczyt wartości napięć podaj również z BIOS-u z sekcji PC Health Status lub Hardware Monitor.
Do BIOS-u wejdziesz naciskając klawisz Delete podczas uruchamiania komputera.
Pokaż log z programu Autoruns => Optymalizacja autostartu z wykorzystaniem narzędzia Autoruns
Sprawdzisz to programem => CPU-Z => zakładka Mainboard => zakładka Grpahics => pozycja Name
Podaj odczyty temperatur oraz wartości napięć z programu => Dostępne tylko dla zarejestrowanych użytkowników (screen okna programu)
Odczyt wartości napięć podaj również z BIOS-u z sekcji PC Health Status lub Hardware Monitor.
Do BIOS-u wejdziesz naciskając klawisz Delete podczas uruchamiania komputera.
Pokaż log z programu Autoruns => Optymalizacja autostartu z wykorzystaniem narzędzia Autoruns
-
DrAudis
- Posty: 3
- Rejestracja: 02 lip 2012, 01:35
Blue Screen znowu mam z tym problem!
To w takim razie od początku :
Gigabyte technology Co.,Ltd. model M55S-S3
NVIDIA GeForce 9600 GT
Dostępne tylko dla zarejestrowanych użytkowników
Z biosu tej zakładki mam tylko to:
DDR2 1.8v
+3.3v
+12v
Current system temperature 25 C
Current CPU temperature 45 C
Current CPU Fan Speed 3590 RPM
I ostatnie: (mam nadzieje że dobrze zrobiłem)
Dostępne tylko dla zarejestrowanych użytkowników
Gigabyte technology Co.,Ltd. model M55S-S3
NVIDIA GeForce 9600 GT
Dostępne tylko dla zarejestrowanych użytkowników
Z biosu tej zakładki mam tylko to:
DDR2 1.8v
+3.3v
+12v
Current system temperature 25 C
Current CPU temperature 45 C
Current CPU Fan Speed 3590 RPM
I ostatnie: (mam nadzieje że dobrze zrobiłem)
Dostępne tylko dla zarejestrowanych użytkowników
-
XMan
- Posty: 13385
- Rejestracja: 30 lis 2008, 00:40
Blue Screen znowu mam z tym problem!
Jakiego masz antywirusa oraz inne programy zabezpieczające komputer, firewall itp. itd ?
Ile masz RAM-u ?
Sprawdź jeszcze pamięć:
Instrukcja obsługi programu Memtest86+ - Sprawdzanie pamięci RAM
Czym dłużej tym lepiej.
Jeżeli masz kilka to możesz jeszcze wcześniej sprawdzić oddzielnie tzn. najpierw na jednej a później na drugiej.
Ile masz RAM-u ?
Sprawdź jeszcze pamięć:
Instrukcja obsługi programu Memtest86+ - Sprawdzanie pamięci RAM
Czym dłużej tym lepiej.
Jeżeli masz kilka to możesz jeszcze wcześniej sprawdzić oddzielnie tzn. najpierw na jednej a później na drugiej.
-
seba86mu
- Posty: 9744
- Rejestracja: 13 lis 2008, 18:07
- Lokalizacja: Sosnowiec
Blue Screen znowu mam z tym problem!
Zaktualizuj sterowniki:
=> Chipset => Dostępne tylko dla zarejestrowanych użytkowników
=> Karta graficzna => Dostępne tylko dla zarejestrowanych użytkowników
Temperatury są w porządku.
W Autoruns odznacz:
Zakładka Logon:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
=> Adobe ARM
=> GrooveMonitor
=> InCD
=> KiesTrayAgent
=> LGODDFU
=> NeroFilterCheck
=> QuickTime Task
=> RemoteControl
=> SkyTel
=> SunJavaUpdateSched
=> SweetIM
=> Sweetpacks Communicator
=> TkBellExe
C:\Documents and Settings\x\Menu Start\Programy\Autostart
=> Tworzenie wycinków ekranu i uruchamianie programu OneNote 2007.lnk
HKCU\Software\Microsoft\Windows\CurrentVersion\Run
=> AlcoholAutomount
=> AlSrvN
=> DAEMON Tools Lite
=> KiesHelper
=> KiesPDLR
Zakładka Explorer:
HKCU\SOFTWARE\Microsoft\Internet Explorer\Desktop\Components
=> 0
Zakładka Internet Explorer:
=> Odznacz wszystko
Zakładka Scheduled Tasks:
=> Odznacz wszystko
Zakładka Services:
=> InCDsrv Helper
=> JavaQuickStarterService
=> Microsoft Office Groove Audit Service
=> MozillaMaintenance
=> nvUpdatusService
=> odserv
=> ose
=> SkypeUpdate
=> StarWindServiceAE
=> UleadBurningHelper
=> WMPNetworkSvc
Zakładka Drivers:
Wszystko co na żółto, czyli:
=> ALSysIO
=> Changer
=> i2omgmt
=> lbrtfdc
=> PCIDump
=> PDCOMP
=> PDFRAME
=> PDRELI
=> PDRFRAME
=> WDICA
Uruchom ponownie komputer.
=> Chipset => Dostępne tylko dla zarejestrowanych użytkowników
=> Karta graficzna => Dostępne tylko dla zarejestrowanych użytkowników
Temperatury są w porządku.
W Autoruns odznacz:
Zakładka Logon:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
=> Adobe ARM
=> GrooveMonitor
=> InCD
=> KiesTrayAgent
=> LGODDFU
=> NeroFilterCheck
=> QuickTime Task
=> RemoteControl
=> SkyTel
=> SunJavaUpdateSched
=> SweetIM
=> Sweetpacks Communicator
=> TkBellExe
C:\Documents and Settings\x\Menu Start\Programy\Autostart
=> Tworzenie wycinków ekranu i uruchamianie programu OneNote 2007.lnk
HKCU\Software\Microsoft\Windows\CurrentVersion\Run
=> AlcoholAutomount
=> AlSrvN
=> DAEMON Tools Lite
=> KiesHelper
=> KiesPDLR
Zakładka Explorer:
HKCU\SOFTWARE\Microsoft\Internet Explorer\Desktop\Components
=> 0
Zakładka Internet Explorer:
=> Odznacz wszystko
Zakładka Scheduled Tasks:
=> Odznacz wszystko
Zakładka Services:
=> InCDsrv Helper
=> JavaQuickStarterService
=> Microsoft Office Groove Audit Service
=> MozillaMaintenance
=> nvUpdatusService
=> odserv
=> ose
=> SkypeUpdate
=> StarWindServiceAE
=> UleadBurningHelper
=> WMPNetworkSvc
Zakładka Drivers:
Wszystko co na żółto, czyli:
=> ALSysIO
=> Changer
=> i2omgmt
=> lbrtfdc
=> PCIDump
=> PDCOMP
=> PDFRAME
=> PDRELI
=> PDRFRAME
=> WDICA
Uruchom ponownie komputer.
-
DrAudis
- Posty: 3
- Rejestracja: 02 lip 2012, 01:35
Blue Screen znowu mam z tym problem!
Zrobiłem tak jak mi kazałeś zobaczymy co z tego wyjdzie
Myślałem że to pomogło ale jednak nie.
Znowu mi się zrestartował
Napiszę tylko że grałem w League of Legends i dopóki tylko to robiłem było ok lecz gdy włączyłem stream komputer mi się zrestartował. Dodam jescze że to jest bardzo częste że komputer się restartuje kiedy ma do wykonania kilka czynności.
Np jeśli w coś tylko gram, słucham muzyki, oglądam filmy, przeglądam internet. To jest wszystko ok ale gdy chciałbym połączyć przynajmniej te 2 rzzeczy przypuścmy granie i słuchanie muzyki komputer zrestartuje się
NIe wiem może te wskazówki coś wam pomogą bo ja już naprawdę nie wiem co jest źle.
Oto raport sprzed chwili:
Loading Dump File [C:\WINDOWS\Minidump\Mini070212-05.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) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Jul 2 19:18:55.625 2012 (GMT+2)
System Uptime: 0 days 7:57:40.369
*********************************************************************
* 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
.....................
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8053a933, a601b9e8, 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : win32k.sys ( win32k+370c5 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8053a933, The address that the exception occurred at
Arg3: a601b9e8, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: win32k
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4fb259c6
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo
FAULTING_IP:
nt+63933
8053a933 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
TRAP_FRAME: a601b9e8 -- (.trap 0xffffffffa601b9e8)
ErrCode = 00000000
eax=8509f000 ebx=0471e470 ecx=1ffbec00 edx=00000000 esi=051a4000 edi=04824070
eip=8053a933 esp=a601ba5c ebp=a601ba64 iopl=0 nv up ei pl nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212
nt+0x63933:
8053a933 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope
CUSTOMER_CRASH_COUNT: 5
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from bf8370c5 to 8053a933
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a601ba64 bf8370c5 0471e470 0509e400 80000c00 nt+0x63933
a601ba88 bf836c0c 0000015d a601bcec e42d3d40 win32k+0x370c5
a601bc9c bf809c61 e42d3d50 00000000 00000000 win32k+0x36c0c
a601bd30 8054168c e42d3d40 e23c57f8 e1100760 win32k+0x9c61
a601bd64 7c90e514 badb0d00 0012f350 00000000 nt+0x6a68c
a601bd68 badb0d00 0012f350 00000000 00000000 0x7c90e514
a601bd6c 0012f350 00000000 00000000 00000000 0xbadb0d00
a601bd70 00000000 00000000 00000000 00000000 0x12f350
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k+370c5
bf8370c5 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: win32k+370c5
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: win32k.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Myślałem że to pomogło ale jednak nie.
Znowu mi się zrestartował
Napiszę tylko że grałem w League of Legends i dopóki tylko to robiłem było ok lecz gdy włączyłem stream komputer mi się zrestartował. Dodam jescze że to jest bardzo częste że komputer się restartuje kiedy ma do wykonania kilka czynności.
Np jeśli w coś tylko gram, słucham muzyki, oglądam filmy, przeglądam internet. To jest wszystko ok ale gdy chciałbym połączyć przynajmniej te 2 rzzeczy przypuścmy granie i słuchanie muzyki komputer zrestartuje się
NIe wiem może te wskazówki coś wam pomogą bo ja już naprawdę nie wiem co jest źle.
Oto raport sprzed chwili:
Loading Dump File [C:\WINDOWS\Minidump\Mini070212-05.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) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Jul 2 19:18:55.625 2012 (GMT+2)
System Uptime: 0 days 7:57:40.369
*********************************************************************
* 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
.....................
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8053a933, a601b9e8, 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : win32k.sys ( win32k+370c5 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8053a933, The address that the exception occurred at
Arg3: a601b9e8, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: win32k
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4fb259c6
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo
FAULTING_IP:
nt+63933
8053a933 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
TRAP_FRAME: a601b9e8 -- (.trap 0xffffffffa601b9e8)
ErrCode = 00000000
eax=8509f000 ebx=0471e470 ecx=1ffbec00 edx=00000000 esi=051a4000 edi=04824070
eip=8053a933 esp=a601ba5c ebp=a601ba64 iopl=0 nv up ei pl nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212
nt+0x63933:
8053a933 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope
CUSTOMER_CRASH_COUNT: 5
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from bf8370c5 to 8053a933
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a601ba64 bf8370c5 0471e470 0509e400 80000c00 nt+0x63933
a601ba88 bf836c0c 0000015d a601bcec e42d3d40 win32k+0x370c5
a601bc9c bf809c61 e42d3d50 00000000 00000000 win32k+0x36c0c
a601bd30 8054168c e42d3d40 e23c57f8 e1100760 win32k+0x9c61
a601bd64 7c90e514 badb0d00 0012f350 00000000 nt+0x6a68c
a601bd68 badb0d00 0012f350 00000000 00000000 0x7c90e514
a601bd6c 0012f350 00000000 00000000 00000000 0xbadb0d00
a601bd70 00000000 00000000 00000000 00000000 0x12f350
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k+370c5
bf8370c5 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: win32k+370c5
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: win32k.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
-
seba86mu
- Posty: 9744
- Rejestracja: 13 lis 2008, 18:07
- Lokalizacja: Sosnowiec
Blue Screen win32k.sys Windows XP
Odinstaluj sterownik karty graficznej poprzez Dodaj lub usuń programy w Panelu sterowania:
=> NVIDIA Display Driver
Nie uruchamiaj ponownie komputera.
Teraz odinstaluj kartę graficzną z Menadżera Urządzeń z sekcji:
+ Karta graficzna
Uruchom ponownie komputer i zainstaluj ten sterownik:
=> Dostępne tylko dla zarejestrowanych użytkowników
Następnie biblioteki DirectX:
=> Dostępne tylko dla zarejestrowanych użytkowników
Jaki posiadasz zasilacz ? (producent, model)
Dane te odczytasz z naklejki na zasilaczu.
Przewód dodatkowego zasilania podłączony masz do karty ?
=> NVIDIA Display Driver
Nie uruchamiaj ponownie komputera.
Teraz odinstaluj kartę graficzną z Menadżera Urządzeń z sekcji:
+ Karta graficzna
Uruchom ponownie komputer i zainstaluj ten sterownik:
=> Dostępne tylko dla zarejestrowanych użytkowników
Następnie biblioteki DirectX:
=> Dostępne tylko dla zarejestrowanych użytkowników
Jaki posiadasz zasilacz ? (producent, model)
Dane te odczytasz z naklejki na zasilaczu.
Przewód dodatkowego zasilania podłączony masz do karty ?
-
- Reklama
Kto jest online
Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 196 gości
