obracím se zde s problémem, který mě uvrhl do bludného kruhu problémů a errorů.
První část problému spočívá v ramce v současnosti mám kit 2x2Gb Kingston HyperX 4GB PC2-8500 CL7 240-Pin DIMM Kit (2 pcs.) označení kitu KHX8500AD2k2/4G píší záměrně celý název z toho důvodu že už si nevím rady s tím, že když přidám Kingston HyperX 4GB PC2-8500 CL5 240-Pin DIMM Kit (2 pcs.) označení kitu KHX8500D2K2/4G tak ram sice funguje, ale je na nižší frekvenci což je nejákých 557MHz oproti udávaným 1066MHz. Nevím jestli je to způsobeno tím že jsou zapojené v Dual-chanelu nebo je to způsobeno voltáží jelikož původní ram má na krytu 2.0V a nová má 2.3V po změně na 800MHz z původních 557 systém najede bez problému, ale po přehození na 1066 se BIOS ressetuje na původní hodnoty.
Základní desku mám Asus P5Q Pro bios je flashnutý na verzi 1613 a deska má podporu pro ram do 16GB s voltáží jsem si nehrál jelikož si nejsem jistý hodnotami ani frekvencemi které bych měl použít.
Jinak jsem ram projížděl memtestem z linuxového Live CD v případě nastavení 1066MHz vypisuje chyby domnívám se ovšem, že se nejedná o závadu modulů z toho důvodu že testem na jiném stroji projde bez problému a na mém stroji jsem zkoušel různé kombinace a pakliže jsou zapojeny zvlášť na automatickou frekvenci a voltáž tak chyby nehlásí.
Druhá část se týká CPU jedná se o Intel Core 2 Quad 9300 2.50GHz, přičemž po spuštění testu na OCCT asi po 5-ti minutách vypíše error na jádře jedna nevím jak moc to ovlivňuje aplikace jelikož stroj jako takový pracuje.
A ve třetí části bych se chtěl odkázat na Call of Duty 4 v tom duchu že tenhle problém si myslím že je spjatý s předchozíma dvěma. Konkrétněji hra zamrzne a s ní celý počítač nebo naskočí BSOD, vím že už tady na tohle téma jsou nějáké topicy, ale přecejenom nevím jestli je chyba softwaru nebo hardwaru tak se ptám. Na internetu odkazují na obsah souboru Minidump tákže jsem stáhl debuging tools v SDK od Windowsu a prikládám jej na konec topicu. Zvláštní je že při hraní Two Worlds 2 které je graficky náročnější můžu mít zapnutý PhysX a strojem to ani nehne nezamrzá vše běží jak má. Případný dotaz na to jestli se jedna o originál CoD4,, narovinu nejedná je to release R------D.
Veškeré drivery, což se týká základní desky, grafiky, DirectX jsou aktuální W7 je naupdatován po nejnovější aktualizace stroj je čerstvě po reinstalaci.
PS:Děkují za případné odpovědi přecejenom víc hlav víc ví.
------------------------------
Sestava:
Windows 7
Asus P5Q Pro
Asus Nvidia 260gtx
Intel Core 2 Quad 9300
Kingston HyperX 2x2GB CL7 1066MHz
výpis minidump:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\Windows\Minidump\012311-18080-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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02a17000 PsLoadedModuleList = 0xfffff800`02c54e50
Debug session time: Sun Jan 23 15:05:18.629 2011 (UTC + 1:00)
System Uptime: 0 days 0:00:09.299
*********************************************************************
* 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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** 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
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa800498c8f8, 0, 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!_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: nt!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.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: 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: 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_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: 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 ***
*** ***
*************************************************************************
Probably caused by : hardware
Followup: MachineOwner
---------
