PC padá při spuštění určitých her
Dobrý den,
Potřeboval bych poradit.Při spuštění některých her se můj počítač restartuje (většinou BSOD).Naprosto v pořádku rozjedu nejnovější hry jako
FarCry 3,Assassins Creed 3,Dishonored,Fifa 13,Sleeping Dogs nebo třeba Battlefield 3.Většinu z těchto her hraji na vysoké nebo normální detaily.U těchto není naprosto žádný problém ani jedno seknutí za dobu hraní nebo něco podobného,ale po té jsou tu hry na, které má mé PC asi alergii jinak si to nedovedu vysvětlit.Jmenovitě Bordelands 2,Sains Row 3,Spec Ops: The Line a Prototype 2 o více hrách zatím nevím. Podotýkám,že by to nemělo mít nic společného s náročností her na můj PC, protože hry výše jmenované rozjedu a jsou mnohdy mnohem náročnější a novější. Jsem dá se říct velký laik, tak bych poprosil o velice do detailů rozpracované odpovědi ( jako pro debila) . děkuji
ještě uvádím parametry počítače:
HAL3000 Daemon
Microsoft Windows 7 Home Premium
Procesor: AMD FX-Series 4100 Quad-Core
RAM: 8GB
Model grafické karty: GeForce GT 430
Další část
************************************************** ***********************
*** ***
*** ***
*** 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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
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: fffff80003006000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`033c45b0 fffffa80`076768f8 : 00000000`00000001 00000000`00000000 fffffa80`08ce06a0 fffffa80`076768f8 : nt+0x4b094c
fffff880`033c45b8 00000000`00000001 : 00000000`00000000 fffffa80`08ce06a0 fffffa80`076768f8 00000000`00000000 : 0xfffffa80`076768f8
fffff880`033c45c0 00000000`00000000 : fffffa80`08ce06a0 fffffa80`076768f8 00000000`00000000 00000000`00000000 : 0x1
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
nebolo by lepsie pozret sa na to pomocou nirsoft bsod viewer ze jaka to bol bsod a v com nastala?
vseobecne: Otestuj si RAM pomocou goldmemory.cz (vypalit iso na CD ako obraz, nabootovat). Pripadne by som otestoval nejaky iny zdroj, nejaky slusnejsi. Ovladace skusit aktualne preinstalovat k zakl.doske zvukovke aj grafike, preistotu aj directx balik z microsoft.com