Witam, dzisiaj chciałem zainstalować stery do karty graficznej ATI bo niedawno miałem formata a tu nagle przy instalacji wyskakuje niebieski ekran i pisze Krytyczny błąd systemu i po kilku sekundach laptop się wyłancza. Mam win XP, prosze o pomoc!
sterowniki pod ten system?
nie rozumię cię zabardzo, wszytko opisałęm w pierwszym poscie
Może niewłaściwe sterowniki.Podaj typ lapka.
A dasz rade spisać w te kilka sekund zanim sie resetuje komp, kod błędu z blue screena?
Jak za szybko sie resetuje to kliknij prawym myszy na mój komputer > właściwości > zaawansowane > ustawienia (przy uruchamianie i odzyskiwanie) i tam odznacz automatycznie uruchom ponownie. Jak spiszesz kod błędu to łatwiej będzie Ci pomóc, albo nawet sam znajdziesz rozwiązanie jak wklepiesz kod w google.
Możesz też innym sposobem odczytać logi BSOD, za pomocą programu Windbg ale nie wiem na ile jesteś obyty więc nie opisuje tego sposobu.
Powodzenia.
Zrób zdjęcie ekranu.
no to tak:
Proces systemowy Windows SybSystem skończył(lub zakończył, nie jestem pewien jak to było) się niespodziewanie ze stanem 0xc0000005 (0x7c9101b3 0x00ccde88).
System zostanie zamknięty.
Wyszukiwarka nic mi ciekawego nie znalazła o tym błędzie. Spróbuj odczytać jaki plik powoduje błąd tak jak ten gość z filmiku.
Ok mam, co powiecie na to?
Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © 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) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c720
Debug session time: Sat Nov 21 08:50:00.843 2009 (GMT+1)
System Uptime: 0 days 0:19:27.541
*********************************************************************
* 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
…
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {80000004, 806eaad1, a3cfb130, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for pci.sys
*** ERROR: Module load completed but symbols could not be loaded for pci.sys
*** WARNING: Unable to verify timestamp for VIDEOPRT.SYS
*** ERROR: Module load completed but symbols could not be loaded for VIDEOPRT.SYS
*** WARNING: Unable to verify timestamp for igxpmp32.sys
*** ERROR: Module load completed but symbols could not be loaded for igxpmp32.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.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 : pci.sys ( pci+ae0 )
Followup: MachineOwner
0: 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: 80000004, The exception code that was not handled
Arg2: 806eaad1, The address that the exception occurred at
Arg3: a3cfb130, 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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+ *
*********************************************************************
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: pci
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 41107d31
EXCEPTION_CODE: (HRESULT) 0x80000004 (2147483652) - Taki interfejs nie jest obs ugiwany.
FAULTING_IP:
hal+8ad1
806eaad1 c20800 ret 8
TRAP_FRAME: a3cfb130 – (.trap 0xffffffffa3cfb130)
ErrCode = 00000000
eax=80001090 ebx=00000090 ecx=00000090 edx=00000cf8 esi=806ef3a0 edi=a3cfb22c
eip=806eaad1 esp=a3cfb1a4 ebp=a3cfb1b4 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
hal+0x8ad1:
806eaad1 c20800 ret 8
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 806e7f0d to 806eaad1
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a3cfb1b4 806e7f0d 806ef3a0 a3cfb1d4 a3cfb300 hal+0x8ad1
a3cfb1e8 806e8335 a3cfb200 00000002 a3cfb300 hal+0x5f0d
a3cfb208 806e914b a3cfb22c 00000002 a3cfb300 hal+0x6335
a3cfb298 b9f67ae0 00000000 00000000 00000002 hal+0x714b
a3cfb2bc b9f67b74 8a259af8 00000002 a3cfb300 pci+0xae0
a3cfb2dc b9f67fcc 8a284f08 a3cfb300 00000090 pci+0xb74
a3cfb404 b9f6acbd 8a284f08 a3cfb48c 00000090 pci+0xfcc
a3cfb428 b9f6734d 8a284f08 00000000 a3cfb48c pci+0x3cbd
a3cfb448 b8bc50d2 8a284f08 00000000 a3cfb48c pci+0x34d
a3cfb464 b8be5a11 89833878 00000004 00000000 VIDEOPRT+0x10d2
a3cfb498 b8bf938d 89833878 000000ea 00000000 igxpmp32+0xda11
a3cfb4e8 b8bc521b 89833878 000000ea 89731000 igxpmp32+0x2138d
a3cfb50c b8bd1b06 a3cfb5a4 00000000 89613f38 VIDEOPRT+0x121b
a3cfb5cc 804ef199 892d3040 89821838 00000000 VIDEOPRT+0xdb06
a3cfb60c bf93d438 892d3040 0023002c 00000000 nt+0x18199
a3cfb634 bf961701 00000000 a3cfb68c bf805bd5 win32k+0x13d438
a3cfb654 bf805b7e e2167690 00000000 00000000 win32k+0x161701
a3cfb68c bf864bba e12eb5e8 e13b3cb0 00000000 win32k+0x5b7e
a3cfb6d4 bf8649d2 bf805b89 a3cfb77c e12eb5e8 win32k+0x64bba
a3cfb788 bf864c07 e12eb5e8 e13b3cb0 00000000 win32k+0x649d2
a3cfb7bc bf809e6d e12eb5e8 e13b3cb0 00000000 win32k+0x64c07
a3cfb850 805413fc e12eb5d8 bf9a6e20 e220f378 win32k+0x9e6d
a3cfb884 7c90e514 badb0d00 026cf2d0 bf83833b nt+0x6a3fc
a3cfb888 badb0d00 026cf2d0 bf83833b 03e55d58 0x7c90e514
a3cfb88c 026cf2d0 bf83833b 03e55d58 00000000 0xbadb0d00
a3cfb890 bf83833b 03e55d58 00000000 00000001 0x26cf2d0
a3cfb894 03e55d58 00000000 00000001 a3cfb920 win32k+0x3833b
a3cfb898 00000000 00000001 a3cfb920 a3cfb8bc 0x3e55d58
STACK_COMMAND: kb
FOLLOWUP_IP:
pci+ae0
b9f67ae0 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: pci+ae0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: pci.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner