Euvarios
(Euvarios)
22 Styczeń 2016 15:11
#1
Zacznę od tego, że wczoraj dołożyłem znalezioną kość DDR2 1GB, teraz mam 3 GB i dodatkowy problem. Co jakiś czas gdy mocno używa się Ramu ( np. podczas grania ) ekran wariuje a następnie wywala mnie do Blue Screena. Tutaj treść pliku dump oraz kilka screenów pomocniczych. Dodam, że aktualizowałem już wszystko co tylko mogłem.
Microsoft ® Windows Debugger Version 6.11.0001.404 X86Copyright © Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\012216-19905-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol 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 0n2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeWindows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7601.18798.amd64fre.win7sp1_gdr.150316-1654Machine Name:Kernel base = 0xfffff80002e63000 PsLoadedModuleList = 0xfffff800
030a8890Debug session time: Fri Jan 22 14:54:34.816 2016 (GMT+1)System Uptime: 0 days 0:01:17.267********************************************************************** 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 0n2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeLoading Kernel Symbols…Loading User SymbolsLoading unloaded module list…******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 50, {fffff900d27a0e38, 0, fffff960000930fe, 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: nt!_KPRCB ****** ******************************************************************************* WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.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 ****** ************************************************************************************************************************************************** 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+ ******************************************************************************************************************************************** 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+ **********************************************************************Probably caused by : win32k.sys ( win32k+730fe )Followup: MachineOwner--------- Przydatne screeny:Macie pomysł co z tym zrobić? Może coś pozmieniać w Biosie?
Podaj jeszcze markę i moc zasilacza.
Euvarios
(Euvarios)
22 Styczeń 2016 15:41
#3
Qoltec SilentLine 425W, ale czy zasilacz może być problemem, jeżeli z 2GB działał od paru lat a teraz po dodaniu 1 GB nagle miałby się psuć?
Po 1 - może jest walnięta
Po 2 - jeżeli jest inna niż te co były to trzeba włożyć od najwolniejszej do najszybszej, inaczej będzie wywalać bo na magistrali będziesz miał taktowanie pierwszej (szybszej) a pozostałe nie będą wyrabiać.
Zamień miejscami i zobacz co będzie
W 1 slota włóż ą 2 GB
Euvarios
(Euvarios)
22 Styczeń 2016 15:45
#5
Czyli powinienem przestawić kości ?
@edit Dobra, przestawiłem kości. Zobaczymy co będzie…
Co do zasilacza to trudno powiedzieć czy w tym przypadku może winowajcą.Nie zmienia to faktu,że pochodzi on z czarnej listy i nigdy nie wiadomo kiedy spali komputer.Tak czy siak ja na Twoim miejscu wymieniłbym na firmowy.
Sprawdź pamięć programem Memtest.
Czarne listy, czary mary, okultyzm i mroczne sztuki odstaw na później.
Zacznij od programu memtest.