Krzeslo

Witam, niedawno wymienilem w komputerze plyte glowna, ram i procesor. Natomiast dyski twarde, grafika i zasilacz zostaly te same. Od tego czasu dziwne rzeczy dzieja sie z moim komputerem. Czasami zlapie freeza i nic nie moge zrobic, czasami sie zwiesi na chwile i wychodzi BSD przy czym po takim BSD zawsze jest jakis problem przy ponownym wlaczeniu komputera. Za pierwszym razem dostalem komunikat zeby wlozyc USB do flashowania biosu :| Nastepnym razem ustawienia biosu sie zresetowaly po BSD [obecnie najczesciej to wlasnie sie dzieje po trafieniu mnie BSD] Zainstalowalem nowe sterowniki do grafiki, sprawdzalem czy dyski nie robia bledow, temperatura na procku oscyluje w granicach 36 stopni, na grafice tez sie nic nie grzeje, flashowalem bios do najnowszej wersji i ciagle problem sie powtarza. Resetowalem bios przez wyjecie baterii - co prawda nie wiem czy nie za krotko byla wyjeta no ale to chyba nie musi trwac kilku minut ? Ustawialem na sztywno napiecie na RAMie i dalej problem nierowiazany. Sprzet to: Płyta głowna: MSI 870 G-45 Procesor: Athlon II x3 455 RAM: Geil 2gb PC3-10660 CL=7-7-7-24 [mam wlozona jedna kosc bo jak wloze 2 na dual channel to komputer sie nie wlacza - raczej wina zasilacza, tylko 400w] Grafika: Radeon X1950 pro Generalnie kiepsko sie na tym znam i bylbym wdzieczny gdyby ktos mogl mi podpowiedziec, na co moze wskazywac ten raport. Z gory dzieki za pomoc ! A oto i raport z .dmp Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\070311-47205-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 0n2 *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Machine Name: Kernel base = 0xfffff800`02c1f000 PsLoadedModuleList = 0xfffff800`02e64650 Debug session time: Sun Jul 3 22:26:42.086 2011 (UTC + 2:00) System Uptime: 0 days 1:59:48.616 ********************************************************************* * 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 *** 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, fffff9600021349b, fffff88006f201f0, 0} Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys ***** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 : win32k.sys ( win32k+20349b ) Followup: MachineOwner ---------