Poważny błąd ale jaki?


(Kkza) #1

Podczas gry windows sam się resetuje. Nie przy każdej gdzie tylko tej jednej akurat. Oczywiście jest restart i wyskakuje okienko ze System windows odzyskał sprawnośc po poważnym błędzie oraz jest podana sygnatura błędu.

BCCode : 1000008e BCP1 : C0000005 BCP2 : BFB76001 BCP3 : 971F38DC

BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 768_1

To jest właśnie to :?

Jeszcze weszłam w panel sterowania i tam w narzędzia administracyjne sprawdziłam podgląd zdarzeń i mam błąd System error w kategorii mam cyferkę 102 a obok w zdarzeniu jest 1003. Nie wiem czy to ma jakieś znaczenie


(Tomu250) #2

nie nie ma nic powaznego- jak chcesz grac w ta gre bez problemu- zainstaluj sterowniki do plyty glownej :stuck_out_tongue:


(Asterisk) #3

To znaczy jakiej ?

Podaj tez konfigurację kompa.


(Kkza) #4

Gra to Splitner Cell

a konfiguracja to

1 GB ramu karta grafiki RADEON X1600 procesor Intel Core2 CPU 6300 @ 1,86 GHz

Dodam ze jest to nowy komputer i wszystkie stey powinny chyba być zainstalowane :roll:


(ak6) #5

Chyba to trochę mało.

Sorawdź tempereaturę karty graficznej podczas lub zaraz po graniu


(Kkza) #6

To się dzieje nawet zaraz po uruchomieniu kompa :roll: a stery od karty są na 100% zainstalowane sprawdziłam.


(De Niro) #7

:arrow: włącz BSOD'a Win+Pause Break-> Zaawansowane-> Uruchamianie i odzyskiwanie, Automatycznie uruchom ponownie odznacz

:arrow: Debugger Windows


(Kkza) #8

Zaznaczyłam to co podałeś ale na tej stronie co podałes jest napisane ze winą restartu są dwie konkretne aktualizację i powinno się je wywalic lecz ja ich nie mogę odistalowac :? Poprostu nie mam takiej opcji usuń :roll:


(De Niro) #9

podaj ten LOG

Edit:

Debugger nie pokazuje poprawek tylko sterowniki oraz aplikacje.


(Kkza) #10
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 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 (Service Pack 2) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700

Debug session time: Thu Oct 5 20:38:41.937 2006 (GMT+2)

System Uptime: 0 days 0:05:32.638

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

* 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 unloaded module list

..............

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck 1000000A, {35, 2, 1, 806e4a16}


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


*** WARNING: Unable to verify timestamp for hal.dll

*** ERROR: Module load completed but symbols could not be loaded for hal.dll

Unable to load image Ntfs.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for Ntfs.sys

*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys

*** WARNING: Unable to verify timestamp for aswMon2.SYS

*** ERROR: Module load completed but symbols could not be loaded for aswMon2.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***

******

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

Probably caused by : aswMon2.SYS ( aswMon2+83c )


Followup: MachineOwner

---------

Czy o to chodziło ?


(De Niro) #11

odisntaluj antywirusa Avasta to jest przyczyną restartów :slight_smile:


(Kkza) #12

Kurde w takim razie jaki antywirus mam dac ? :roll:

Złączono Posta : 07.10.2006 (Sob) 9:15

Avast odinstalowany jednak restar jest dalej :?

Złączono Posta : 07.10.2006 (Sob) 9:17

Załączam nowy kod

Microsoft (R) Windows Debugger Version 6.5.0003.7

Copyright (c) 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 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 (Service Pack 2) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700

Debug session time: Sat Oct 7 09:14:17.406 2006 (GMT+2)

System Uptime: 0 days 0:02:53.981

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

* 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 unloaded module list

...............

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck 1000008E, {c0000005, bfb76001, a20d48dc, 0}


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


Unable to load image ati3duag.dll, Win32 error 2

*** WARNING: Unable to verify timestamp for ati3duag.dll

*** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll

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

******

******

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

******

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

Probably caused by : ati3duag.dll ( ati3duag+f0001 )


Followup: MachineOwner

---------

(De Niro) #13

kolejny nowy błąd jest związany z kartą graficzną.

Zrób tak odisnatluj sterowniki następnie jeżeli masz Mobo na Chipsecie VIA to instalacja sterów to Chipsetu i dopiero instalacja sterowników od karty graficznej :wink:


(Kkza) #14

Ok zaraz zobaczę :wink:

Złączono Posta : 07.10.2006 (Sob) 13:20

Niestety dalej wyskakuje ten sam błąd i resetuje też :?

Złączono Posta : 07.10.2006 (Sob) 18:06

Już nie wiem co jest grane zaczyna resetować się i przy kolejnych grach :?