tarzou6900

RE...moi, je pense que il y a une erreur car mon fichier dump ne ressemble pas a ceux que j'ai vu sur le net... je vous mets a tout hazard 2-3 fichiers dump en lien... merci beaucoup, www.ixiweb.be/dump/ tarzou6900

Bonjour, je vous écris car j'ai un écran bleu 2 - 3 fois par jour sur mon nnouveau pc... j'ai des fichier 'minidump' qui pourrait peut etre mettre quelqu'un sur la piste... j'ai lu beaucoup de choses sur ces erreurs et il semble que cela peut etre la memoire ou l'alimentation..mais.??? j'ai suivi les instructions de 'Nicolas Coolman' trouvées ici sur le forum.. mais sans succès.. (je n'ai pas tout testé ( ) j'ai issu le résultat du fichier minidump lu avec winDBG, peut etre que quelqu'un pourrait m'aider a ce sujet: j'ai windows xp PRO, l'alimentation est une coolermaster 400W le processeur, INTEL CORE 2 QUAD Q6600 mémoire 2x 2G DDR2 PC8500 carte mère ASUS P5Q carte graphique: ASUSTEK EN9800GT (mem 1G) Loading Dump File [C:\WINDOWS\Minidump\Mini070609-03.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 2 *** 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 3) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug session time: Mon Jul 6 23:40:51.184 2009 (GMT+2) System Uptime: 0 days 3:44:14.165 ********************************************************************* * 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 2 *** 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 unloaded module list ............. Loading User Symbols Unable to load image win32k.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 10000050, {bf1ac574, 0, bf804e05, 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 *** *** *** ************************************************************************* Probably caused by : win32k.sys ( win32k+4e05 ) Followup: MachineOwner merci beaucoup pour votre aide... tarzou6900