hm po reinstalacji systemu XP zaczął wyskakiwać BSOD przy włączaniu jakiejkolwiek gierki lub filmu na necie
po wyskoczeniu owego ekranu śmierci ukazuje się kod:
stop: 0x0000008E (0xC00000005, 0xBFA89ACD, 0xB5D362E8, 0x00000000)
-- Dzisiaj, 15:20 --
a i czy ponowna instalacja Windows-a coś da??
BSOD 0x0000008E przy uruchamianiu gier
-
xxxkrecik01
- Posty: 87
- Rejestracja: 08 paź 2009, 15:15
BSOD 0x0000008E przy uruchamianiu gier
Ostatnio zmieniony 08 paź 2009, 15:28 przez me@djohnsc, łącznie zmieniany 3 razy.
Powód: zmieniłem tytuł, poprawiłem pisownię
Powód: zmieniłem tytuł, poprawiłem pisownię
Krecik
-
djkamil09061991
- Posty: 8250
- Rejestracja: 18 lut 2009, 11:54
- Lokalizacja: Wrocław
- Kontaktowanie:
BSOD prz uruchamianiu jakiejkolwiek gry
W menu start->uruchom->wpisz->cmd
Wpisz:
chkdsk /F /R
i pozwól, aby system sprawdził dysk przy następnym uruchomieniu systemu.
Wpisz:
chkdsk /F /R
i pozwól, aby system sprawdził dysk przy następnym uruchomieniu systemu.
Mój kanał YouTube - Dostępne tylko dla zarejestrowanych użytkowników
Przyjmuje skiny Cs Go: Dostępne tylko dla zarejestrowanych użytkowników
Przyjmuje skiny Cs Go: Dostępne tylko dla zarejestrowanych użytkowników
-
me@djohnsc
- Posty: 1225
- Rejestracja: 22 lis 2008, 19:28
- Lokalizacja: Śląsk
BSOD 0x0000008E przy uruchamianiu gier
Kod 0x0000008E -> Błędy systemu Windows (kody BSOD)
Aby dowiedzieć się, jaki sterownik powoduje błąd odczytaj plik DMP -> Bluescreen (BSOD) - szukanie przyczyny powstawania. Czytanie plików DMP i podaj go na forum
Aby dowiedzieć się, jaki sterownik powoduje błąd odczytaj plik DMP -> Bluescreen (BSOD) - szukanie przyczyny powstawania. Czytanie plików DMP i podaj go na forum
-
xxxkrecik01
- Posty: 87
- Rejestracja: 08 paź 2009, 15:15
BSOD 0x0000008E przy uruchamianiu gier
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini100809-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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a6a0
Debug session time: Thu Oct 8 09:08:41.125 2009 (GMT+2)
System Uptime: 0 days 0:11:10.718
*********************************************************************
* 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 ati3duag.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati3duag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll
*** WARNING: Unable to verify timestamp for ati2dvag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati2dvag.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bfa89acd, b5d362e8, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** 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 <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 : ati3duag.dll ( ati3duag+55acd )
Followup: MachineOwner
---------
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: bfa89acd, The address that the exception occurred at
Arg3: b5d362e8, 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 <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.
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 3f627fb6
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo
FAULTING_IP:
ati3duag+55acd
bfa89acd 8b7008 mov esi,dword ptr [eax+8]
TRAP_FRAME: b5d362e8 -- (.trap 0xffffffffb5d362e8)
ErrCode = 00000000
eax=00000001 ebx=00000005 ecx=00000000 edx=00000005 esi=e188c010 edi=b5d36684
eip=bfa89acd esp=b5d3635c ebp=b5d366d0 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
ati3duag+0x55acd:
bfa89acd 8b7008 mov esi,dword ptr [eax+8] ds:0023:00000009=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from bf9dcd22 to bfa89acd
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b5d366d0 bf9dcd22 e1882080 00000285 00000001 ati3duag+0x55acd
b5d366fc bf9f418e bfa1e5a0 b5d36718 00000001 ati2dvag+0x7d22
b5d3698c bf9f4ea8 00000001 00000000 00000000 ati2dvag+0x1f18e
b5d369a8 bf9f5071 e1882080 00000000 e1564224 ati2dvag+0x1fea8
b5d369c8 bf9f50c3 e1882080 00000000 bf960ccf ati2dvag+0x20071
b5d36a10 bf93ea32 e1882080 00000000 e1564224 ati2dvag+0x200c3
b5d36a3c bf89fdbb e187c008 00000000 00000000 win32k+0x13ea32
b5d36a70 bf8a09cc e158ef38 e119e100 e106fce0 win32k+0x9fdbb
b5d36be8 bf8a730f b5d36cb0 e170b6e0 00000001 win32k+0xa09cc
b5d36cdc bf8a9574 b5d36cb0 e187c008 00000000 win32k+0xa730f
b5d36d20 bf8a9467 023fa778 001af600 00000000 win32k+0xa9574
b5d36d48 804de7ec 023fa778 001af600 00000000 win32k+0xa9467
b5d36d64 7c90e514 badb0d00 023fa754 b6944d98 nt+0x77ec
b5d36d68 badb0d00 023fa754 b6944d98 b6944dcc 0x7c90e514
b5d36d6c 023fa754 b6944d98 b6944dcc 00000000 0xbadb0d00
b5d36d70 b6944d98 b6944dcc 00000000 00000000 0x23fa754
b5d36d74 b6944dcc 00000000 00000000 00000000 0xb6944d98
b5d36d78 00000000 00000000 00000000 00000000 0xb6944dcc
STACK_COMMAND: kb
FOLLOWUP_IP:
ati3duag+55acd
bfa89acd 8b7008 mov esi,dword ptr [eax+8]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ati3duag+55acd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ati3duag
IMAGE_NAME: ati3duag.dll
BUCKET_ID: WRONG_SYMBOLS
-- Dzisiaj, 10:04 --
rozumiecie coś z tego??
Ostatnio zmieniony 09 paź 2009, 14:50 przez me@djohnsc, łącznie zmieniany 1 raz.
Powód: dodałem znacznik code
Powód: dodałem znacznik code
Krecik
-
seba86mu
- Posty: 9744
- Rejestracja: 13 lis 2008, 18:07
- Lokalizacja: Sosnowiec
BSOD 0x0000008E przy uruchamianiu gier
Raport wskazuje na problem ze sterownikiem ekranu.
Pobierz program Everest Ultimate Edition.
Otwórz program -> Komputer -> Podsumowanie -> spisz informacje z pozycji:
-> Nazwa płyty głównej
-> Mikroukład płyty głównej
-> Ekran (karta wideo)
Pobierz program Everest Ultimate Edition.
Otwórz program -> Komputer -> Podsumowanie -> spisz informacje z pozycji:
-> Nazwa płyty głównej
-> Mikroukład płyty głównej
-> Ekran (karta wideo)
-
xxxkrecik01
- Posty: 87
- Rejestracja: 08 paź 2009, 15:15
BSOD 0x0000008E przy uruchamianiu gier
nazwa płyty głównej: asrock p4i65g- płyta była wymieniana bo wcześniejsza poszła z dymem
mikro układ płyty głównej: Intel Springdale-G i865g
ekran: Radeon 9200 series secondary (128 MB)
mikro układ płyty głównej: Intel Springdale-G i865g
ekran: Radeon 9200 series secondary (128 MB)
Krecik
-
seba86mu
- Posty: 9744
- Rejestracja: 13 lis 2008, 18:07
- Lokalizacja: Sosnowiec
BSOD 0x0000008E przy uruchamianiu gier
xxxkrecik01, odinstaluj obecny sterownik karty graficznej:
Start -> Panel sterowania -> Dodaj lub Usuń programy -> ATI DISPLAY DRIVER /usuń/
Po zakończeniu deinstalacji uruchom ponownie komputer.
Teraz zainstaluj sterownik do karty graficznej ATI Catalyst 5.8.
Po zakończeniu instalacji uruchom ponownie komputer.
Na końcu zainstaluj najnowsze biblioteki DirectX 9.0c (Instrukcja instalacji bibliotek DirectX 9.0c).
Start -> Panel sterowania -> Dodaj lub Usuń programy -> ATI DISPLAY DRIVER /usuń/
Po zakończeniu deinstalacji uruchom ponownie komputer.
Teraz zainstaluj sterownik do karty graficznej ATI Catalyst 5.8.
Po zakończeniu instalacji uruchom ponownie komputer.
Na końcu zainstaluj najnowsze biblioteki DirectX 9.0c (Instrukcja instalacji bibliotek DirectX 9.0c).
-
xxxkrecik01
- Posty: 87
- Rejestracja: 08 paź 2009, 15:15
-
seba86mu
- Posty: 9744
- Rejestracja: 13 lis 2008, 18:07
- Lokalizacja: Sosnowiec
BSOD 0x0000008E przy uruchamianiu gier
Więc na razie możesz pobrać sam sterownik ATI Catalyst 5.8, a DirectX na razie odpuścimy.
-
xxxkrecik01
- Posty: 87
- Rejestracja: 08 paź 2009, 15:15
-
- Reklama
Kto jest online
Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 190 gości
