Bsod ..Atikmag.sys
Chtěl bych se jen zeptat, je to teda cca už půl roku co mi začalo pc padat a házet bsodky jednu za druhou, vždy se mi to podařilo nějak vyřešit, většinou za to mohlo nastavení ramek, protože základka si je nastavuje díky nějaké funkci, to se mi podařilo zakázat a přenastavit je do továrních hodnot, ale teď poslední dobou mam každý den jednu Bsodku s parametrem atikmag.sys viz. foto
, mám takové podezření na grafiku, je už starší asi 3 roky (Ati HD 5750), a je to v podstatě jediný komponent, který jsem zanechal při sestavení nového pc, už jsem zkoušel kompletně zdemolovat drivery, a nahrát je znova od továrních z CD, po nejnovější vždy se stejným výsledkem. Jediné co mě na tom zaráží je že se mi ty smrti dějí jen při jedné jediné věci a max 1x denně a to když si chci zahrát Heroes of Newerth, hned při 1. hře Mordá restartuji pc, a mohu hrát třeba celý den, vypnu pc, za pár hodin zapnu a stane se mi to znovu.
Ještě zkusím Goldmemory jestli zase není v čudu nějaká ram, ale jak říkám, problémy jsem měl i před touhle sestavou , kdyby jste někdo věděl nějakou dobrou radu, budu šťastný, jen abych nemusel kupovat novou grafiku.. i když bych jí už asi potřeboval.
Sestava
MB Asus M4N98TD EVO
AMD Phenom II X4 3,00 GHz
2x 4GB Geil Value Plus CL7
Ati HD5750
2x 320 GB HDD Samsung
Fortron HEXA 500W
, mám takové podezření na grafiku, je už starší asi 3 roky (Ati HD 5750), a je to v podstatě jediný komponent, který jsem zanechal při sestavení nového pc, už jsem zkoušel kompletně zdemolovat drivery, a nahrát je znova od továrních z CD, po nejnovější vždy se stejným výsledkem. Jediné co mě na tom zaráží je že se mi ty smrti dějí jen při jedné jediné věci a max 1x denně a to když si chci zahrát Heroes of Newerth, hned při 1. hře Mordá restartuji pc, a mohu hrát třeba celý den, vypnu pc, za pár hodin zapnu a stane se mi to znovu.
Ještě zkusím Goldmemory jestli zase není v čudu nějaká ram, ale jak říkám, problémy jsem měl i před touhle sestavou , kdyby jste někdo věděl nějakou dobrou radu, budu šťastný, jen abych nemusel kupovat novou grafiku.. i když bych jí už asi potřeboval.
Sestava
MB Asus M4N98TD EVO
AMD Phenom II X4 3,00 GHz
2x 4GB Geil Value Plus CL7
Ati HD5750
2x 320 GB HDD Samsung
Fortron HEXA 500W
Chceš ten soubor z C:/win/minidump a příslušné datum nebo to nějak vypsat.
Jestli vypsat tak nevím jak.Pokud nemyslíš z prohlížeče událostí, to potom vím.
A hra je 100% orig... za 1. je zdarma k hraní,ale s omezeným přístupem, a za 2. já jí mam ještě z dob kdy zdarma nebyla pěkně zaplacenou.
Jestli vypsat tak nevím jak.Pokud nemyslíš z prohlížeče událostí, to potom vím.
A hra je 100% orig... za 1. je zdarma k hraní,ale s omezeným přístupem, a za 2. já jí mam ještě z dob kdy zdarma nebyla pěkně zaplacenou.
Tak jsem si to zjistil , ale přijde mi ten dump dlouhý..
[SPOILER]Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\031912-19702-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\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 Vista Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e55670
Debug session time: Mon Mar 19 19:44:47.260 2012 (GMT+1)
System Uptime: 0 days 7:23:09.170
*********************************************************************
* 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\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 User Symbols
Loading unloaded module list
.....................................
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8007e4b4e0, fffff88003b788f0, 0, 2}
***** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!DXGADAPTER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
Probably caused by : atikmpag.sys ( atikmpag+78f0 )
Followup: MachineOwner
---------
1: kd> g
^ No runnable debuggees error in 'g'
1: kd> g
^ No runnable debuggees error in 'g'
1: kd> .restart /f
Loading Dump File [C:\Windows\Minidump\031912-19702-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\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 Vista Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e55670
Debug session time: Mon Mar 19 19:44:47.260 2012 (GMT+1)
System Uptime: 0 days 7:23:09.170
*********************************************************************
* 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\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 User Symbols
Loading unloaded module list
.....................................
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8007e4b4e0, fffff88003b788f0, 0, 2}
***** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!DXGADAPTER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
Probably caused by : atikmpag.sys ( atikmpag+78f0 )
Followup: MachineOwner
---------
[/SPOILER]
Doufám že je to ono:)
[SPOILER]Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\031912-19702-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
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\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 Vista Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e55670
Debug session time: Mon Mar 19 19:44:47.260 2012 (GMT+1)
System Uptime: 0 days 7:23:09.170
*********************************************************************
* 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
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\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 User Symbols
Loading unloaded module list
.....................................
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8007e4b4e0, fffff88003b788f0, 0, 2}
***** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!DXGADAPTER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
Probably caused by : atikmpag.sys ( atikmpag+78f0 )
Followup: MachineOwner
---------
1: kd> g
^ No runnable debuggees error in 'g'
1: kd> g
^ No runnable debuggees error in 'g'
1: kd> .restart /f
Loading Dump File [C:\Windows\Minidump\031912-19702-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
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\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 Vista Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e55670
Debug session time: Mon Mar 19 19:44:47.260 2012 (GMT+1)
System Uptime: 0 days 7:23:09.170
*********************************************************************
* 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
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\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 User Symbols
Loading unloaded module list
.....................................
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8007e4b4e0, fffff88003b788f0, 0, 2}
***** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!DXGADAPTER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
Probably caused by : atikmpag.sys ( atikmpag+78f0 )
Followup: MachineOwner
---------
[/SPOILER]
Doufám že je to ono:)
Bylo myšleno zabalit obsah složky C:\Windows\Minidump a vložit ji do přílohy. Né se pokoušet o debug.
Dobře chybička se vloudila, to se omlouvám tak tady je to v RARu, jsou tam bohužel jen 3 to je od reinstalace systému .
Pc jsem předevčírem čistil kompresůrem, minulý týden jsem koukal i na pastu jestli není vytvrdlá, byla tak jsem tam stříknul trochu Revoltechu, ale pořád stejné, jak říkám grafika je stará a nikdy sem jí nešetřil , teď teda už jo , měl jsem jí dlouho trošku taktlou, vše sem vrátil na referenčky, a taky nic, jedinýco mě na tom zaráží že se mi to zatim stává jen u Heroes of Newerth , BF3 jede na high detaily úplně v pohodě.
Zkusil bych jí jinde ,ale není kde , v práci by asi nebyli rádi kdybych přišel do kanceláře a rozebral jim tam compa :D ,
Mno nic našetřím si na novou Atinku ...
Má cenu kupovat 6950 twin frozr , nebo už bude jistější tam rovnou hodit 7850 ?
Zkusil bych jí jinde ,ale není kde , v práci by asi nebyli rádi kdybych přišel do kanceláře a rozebral jim tam compa :D ,
Mno nic našetřím si na novou Atinku ...
Má cenu kupovat 6950 twin frozr , nebo už bude jistější tam rovnou hodit 7850 ?
jen vystrel do tmy, rozebrani celeho PC a vycisteni vsech kontaktu a samozrejme i od prachu / vcetne zdroje, nejen vyfoukat, ale stetecek a trpelivost /?
ono chyby ovladacu maj kolikrat spojitost s RAM / jen je vytahnout ze slotu, vycistit kontakty na ram tak i ve slotu, isopropyl+uterka s mikrovlaknem /, a to same udelat s GPU...
edited: asi blbost, ale predpokladam, ze nemas zaply shadowing BIOSu VGA do RAM / nekoukal jsem se na moznosti BIOSu tve desky /
ono chyby ovladacu maj kolikrat spojitost s RAM / jen je vytahnout ze slotu, vycistit kontakty na ram tak i ve slotu, isopropyl+uterka s mikrovlaknem /, a to same udelat s GPU...
edited: asi blbost, ale predpokladam, ze nemas zaply shadowing BIOSu VGA do RAM / nekoukal jsem se na moznosti BIOSu tve desky /
