Niebieski erkan podczas grania

toria00 · 2 Lipiec 2007 13:25

STOP : 0x0000008E (0xC000008E, 0x00AED230, 0xBAD572AB, 0x00000000 )

SeBoLaS · 2 Lipiec 2007 16:32

poczytaj i wklej minidumpa

http://www.searchengines.pl/phpbb203/in … opic=50339

toria00 · 2 Lipiec 2007 18:56

Nie wiem czy tu jest jakas naza pliku zaczaczam error

KLIK zaraz wrzuce minidumpa

EDIT

Nie wstawiaj tak dużych obrazków bezpośrednio na forum.

Obraz zastąpiono linkiem.

Sdar

chaker.zbw · 2 Lipiec 2007 19:01

To może być sterownik od karty graficznej albo antywirus alb efekt podkręcania kompa.

Spróbuj przywrócić domyślne ustawienia BIOS, zreinstaluj stery od grafiki, usuń antywira (jeżeli masz).

tori00 · 3 Lipiec 2007 09:10

Zrobilem wszystko nie dizla

psychozje · 3 Lipiec 2007 09:37

Postępuj wedle tego i wklej log który ci się wyświetli .

toria00 · 3 Lipiec 2007 11:34

Microsoft ® Windows Debugger Version 6.7.0005.0

Loading Dump File [C]

Kernel Complete Dump File: Full address space is 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:

**************************************************************************

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

**************************************************************************

*********************************************************************

* 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 read PsLoadedModuleList

**************************************************************************

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

**************************************************************************

KdDebuggerData.KernBase < SystemRangeStart

Windows XP Kernel Version 2600 UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x00000000 PsLoadedModuleList = 0x805535a0

Debug session time: Tue Jul 3 13:29:00.906 2007 (GMT+2)

System Uptime: 0 days 2:29:15.469

**************************************************************************

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

**************************************************************************

*********************************************************************

* 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 read PsLoadedModuleList

**************************************************************************

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

**************************************************************************

KdDebuggerData.KernBase < SystemRangeStart

Loading Kernel Symbols

Unable to read PsLoadedModuleList

GetContextState failed, 0x80004002

CS descriptor lookup failed

GetContextState failed, 0x80004002

Unable to get program counter

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {c0000090, 55c742, a8d937b0, 0}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to read selector for PCR for processor 0

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner

GetContextState failed, 0x80004002

SeBoLaS · 3 Lipiec 2007 12:02

to wygląda na uszkodzoną pamięć ram lub jakiegoś podzespołu na kompie,tylko jednego miałeś minidumpa??sprawdź jak są inne to wkeli

Złączono Posta : 03.07.2007 (Wto) 14:04

sprawdz tym pamięć RAM

http://dobreprogramy.pl/index.php?dz=2&id=340&t=47