Problem z grafiką - reset kompa


(Kormak) #1

Witam!

Od wczoraj mam następujący kłopot (nie instalowałem nic nowego, nie grzebałem w ustawieniach):

Przy próbie odpalenia nowszych gier (np. GTA San Andreas, King Kong etc.) czy jakichkolwiek plików wideo (avi, mp4) na ułamek sekundy ekran robi się niebieski (białe literki z tym co zdążyłem odcyfrować to słowa pojawiające się to "memory" i "BIOS") po czym system się resetuje.

Próbowałem reinstalacji karty graficznej (GE Force GT 8600), sterowników, Directxa - nie pomogło. Jeden ze znajomych powiedział, że pomóc może wyłączenie pod BIOSem opcji "video ram cacheable" i "bios ram cacheable": problem w tym, że ja takich opcji u siebie w BIOSie nie widzę. Mam nowego kompa, w starym kompie i starym biosie takie opcje kojarzę, w nowym menu nie widzę.


(eyeti) #2

Klikasz PPM Mój Komputer >>> Zaawansowane >>> Uruchamianie i Odzyskiwanie >>> Awaria Systemu i odznaczasz ,,Automatycznie Uruchom ponownie" i podaj kod błędu.


(Cosik Ktosik) #3

Aby odczytać problem, którego dotyczy BSOD użyj tego i odczytaj plik DMP: Klik. Daj następnie raport.


(Mlajtner) #4

kłopotem może być wysoka temp otoczenia ,a przez to przegrzewanie się procesora

...........

otwórz obudowę ,...

daj inny wiatrak...

...lub

czekaj na obniżenie temp zewnętrznej

-ale to też tylko jeden z możliwych powodów... #-o


(Kormak) #5

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {16, 1c, 0, 80502392}

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

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

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

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

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

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

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

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

*** ERROR: Module load completed but symbols could not be loaded for dxg.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 : atkosdmini.dll ( atkosdmini+1370 )

Followup: MachineOwner



(Cosik Ktosik) #6

Zrób to samo co w tym równoległym temacie: viewtopic.php?f=2&t=261738

PS Co to jakaś plaga?


(Kormak) #7

dzięki, sposób podany w linku pomógł, ale przy okazji po restarcie wyskoczyły następujące błędy:

error1jq6.jpg

oraz

error2rj2.jpg

Nie załadował mi się Avast antiwirus i po próbach włączenia właśnie ten pierwszy bląd sie pojawia. Sęk w tym, że nie mogę odinstalować, bo przy próbie ojawia się błąd...


(Cosik Ktosik) #8

Tu Masz ten plik: http://www.dll-files.com/dllindex/dll-f ... ml?msvcr71

Wrzuć go do katalogu windows\system32

Masz zainstalowany MS C runtime library? Jak nie to go zainstaluj.


(Kormak) #9

dzięki!