jozekst

powiem tak ze jakies pol roku temu mialem ten sam problem ale po reinstalce win XP ,bylo wszystko spoko... ... teraz zrobilem to samo tzn. reinstalka systemu,proby z innymi sterami(omegi ,catalysty), i dalej to samo, na poczatku tylko na jednej grze " METIN2" bo w nia gram( ma male wymagania), na innych grach nie resetowal sie tzn. NFS-MW,CARBON,COD2 itp. wszystko dobrze smiga, ale teraz juz na wwzystkich grach wywala. procek temp. ma w norm( stres~45`C) nieraz po kilku minutach w grze ,a nieraz po 2 godz., przy pracy biurowej nic sie nie resetuje, po reinstalce dalej to samo, zastanawiam sie czy zasilacz juz nie pada ale nie jest jakis stary, nie grzeje sie. dodam ze raporty z debugera sa rozne bede probowac z mocniejszym firmowym zasilaczem min.500W jezeli bedzie to samo podejzewam ze dzieje sie cos z karta graf. po experymentach napisze co i jak!

witam mam ten sam problem win XP,AMD 64 3500+,2x 1gb patriot 800mhz ddr2, zasilacz takeme 400w ,readon 9800PRO,ASROCK nFORCE3 , saggate 720.100 czy cos takiego 320GB raport z debug... Loading Dump File [C:\WINDOWS\Minidump\Mini033108-02.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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0 Debug session time: Mon Mar 31 19:23:29.531 2008 (GMT+2) System Uptime: 0 days 0:04:48.113 ********************************************************************* * 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 Loading unloaded module list ........... Unable to load image VIDEOPRT.SYS, Win32 error 0n2 *** WARNING: Unable to verify timestamp for VIDEOPRT.SYS *** ERROR: Module load completed but symbols could not be loaded for VIDEOPRT.SYS ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 10000050, {ffffffe8, 1, 80521dd1, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** 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 : VIDEOPRT.SYS ( VIDEOPRT+d9c9 ) Followup: MachineOwner --------- pomozcie bo niewiem czy zmieniac zasilacz czy grafe