[Problem] Blue Screen/BIOS

[MultiHawoK]

Witam !

 

Gdy ładuje się gra Arctic Combat i jest 2/10 lub 3/10 to pojawia się blue screen.

Mam prośbę o to aby podać mi link do aktualizacji BIOSA AMI.

Grę reinstalowałem chyba z 3 razy , zainstalowałem najnowsze sterowniki do karty graficznej ,temperatura kompa 39 stopni.

Procesor :CPU #0 AMD Athlon? 64 X2 Dual Core Processor 3600+, 2005 MHz.

 

Proszę o pomoc

 

Podam jeszcze dokładniejszy opis:

Podpis problemu:
Nazwa zdarzenia problemu: BlueScreen
Wersja systemu operacyjnego: 6.1.7600.2.0.0.256.1
Identyfikator ustawień regionalnych: 1045

Dodatkowe informacje o problemie:
BCCode: 1000008e
BCP1: C0000005
BCP2: 909E7AEF
BCP3: A3BE0B50
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

[gepard]

po 1 nie jestesmy magikami zeby ci biosa znalesc bez pelnej nazwy plyty glownej

po 2 BCCode: 1000008e wskazuje ze to cos z ekranem/grafika/ badz cos za to odpowiedzialne

po 3 poczytaj jak zdebugowac bluescreena w google i zrob tak jak pisza a moze pomoze

[MultiHawoK]

Po 1 sprawdzam everestem nie ma nazwy

Po 2 grafika ekran działaja bez zarzutu nawet na bf3

Po 3 Już się robi

 

Debugowałem ,mam wynik:

 

Microsoft ? Windows Debugger Version 6.11.0001.404 X86

Copyright ? Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Windows\Minidump\123012-42057-01.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 argument when starting the debugger. *

* using .sympath and .sympath+ *

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

Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntkrnlpa.exe

*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe

Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.17118.x86fre.win7_gdr.120830-0334

Machine Name:

Kernel base = 0x82c4c000 PsLoadedModuleList = 0x82d94810

Debug session time: Sun Dec 30 15:10:45.845 2012 (GMT+1)

System Uptime: 0 days 0:08:05.108

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

* 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntkrnlpa.exe

*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

.....

Unable to load image \SystemRoot\System32\Drivers\ousbehci.sys, Win32 error 0n2

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

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 1000008E, {c0000005, 92600aef, a5863b50, 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 ***

*** ***

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

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

*** ***

*** ***

*** 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 : ousbehci.sys ( ousbehci+aef )

 

Followup: MachineOwner

---------

 

 

 

A co do płyty głównej to sprawdzałem everestem i raczej nic nie wyszło...

ID płyty głównej 64-0100-000001-00101111-111209-ATHLON64$A7388800_A7388AMS V8.4 111209
Nazwa płyty głównej Nieznane

[MultiHawoK]

Odpowie ktoś?

 

//kolejny post pod sobą możesz napisać za 24h, używaj opcji edytuj

[Mr0zi0]

Nowego BIOSa zainstaluj mi to pomogło