timson utworzono 7 maja 2013 utworzono 7 maja 2013 Witam! Mam następujący problem - w komputerze zainstalowane były 2 x 1 GB Patriot PDC22G6400LLK DDR2 800mHZ. Ostatnio dołożyłem jeszcze 2 kości tej samej pamięci zatem teraz mam 4 x 1 GB Patriot PDC22G6400LLK DDR2 800mHZ. I tu pojawia się problem. Przy 4 kościach tej pamięci występuje blue screen - nie od razu, komputer chwile chodzi. . Jak wyciągnę 1 kość to blue screen nie występuje. System: Win 7 Proffesional 64 bit Płyta główna P5B SE Pamięć: 4 x 1 GB Patriot PDC22G6400LLK DDR2 800mHZ Grafa: GeForce 8500 GT Zasilacz: Feel 450 W 1. Remapowanie pamięci włączone w Biosie 2. Każda kość sprawdzona memtestem - 0 błędów 3. Dysk sprawdzony HD TUNE - 0 błedów 3. Bios bez względu na wersje (najnowsza czy starsza) - nie rozwiązuje problemu 4. Sterowniki do karty graficznej czy też bez nich - nie rozwiązuje problemu. Moim domysłem jest to iż na płycie głównej dla pamięci nie moge ustawić wiekszego napiecia niż 1.8 lub 1.9 V, na kościach mam podane 2.2V. Logi z "dumpów": Microsoft (R) Windows Debugger Version 6.6.0003.5 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\050313-23437-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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 2 *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows Vista Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Kernel base = 0xfffff800`0261c000 PsLoadedModuleList = 0xfffff800`02859e50 Debug session time: Fri May 3 23:41:20.095 2013 (GMT+2) System Uptime: 0 days 0:16:37.025 ********************************************************************* * 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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 2 *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ................................................................................................................................................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff960001b8122, fffff880057b4be0, 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 *** *** *** ************************************************************************* Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+17f4ef ) Followup: MachineOwner --------- ORAZ DRUGI: Microsoft (R) Windows Debugger Version 6.6.0003.5 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\050313-23437-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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 2 *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows Vista Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Kernel base = 0xfffff800`0261c000 PsLoadedModuleList = 0xfffff800`02859e50 Debug session time: Fri May 3 23:41:20.095 2013 (GMT+2) System Uptime: 0 days 0:16:37.025 ********************************************************************* * 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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 2 *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ................................................................................................................................................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff960001b8122, fffff880057b4be0, 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 *** *** *** ************************************************************************* Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+17f4ef ) Followup: MachineOwner ---------
bartek86 komentarz 8 maja 2013 komentarz 8 maja 2013 (edytowane) na stonie Asua, znalażłme twoją płyty główną i tam można znaleźć liste pamięci, które prawidłowo będą pracowały na tej płycie, przejżałem ją 3 razy i nie widze tam żadnych pamięcu firmy Patriot nie wiem kto ci dobierał pamięci ale zrobił to źle, musisz je wymienić na takie które są kompatybilne
timson komentarz 8 maja 2013 Autor komentarz 8 maja 2013 To że nie ma na liście kompatybilnych pamięci moich patriotów nie oznacza ze nie są kompaatybilne. 2 kości przez kilka lat chodziły bezawaryjnie, na 3 też działą ok, problem jest przy czwartej. Gdzies widziałem kogoś kto w tej płycie ma takie same pamięci niemniej jednak kontakt z tą osobą jest niemożliwy.
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.