Supportnet / Forum / WindowsXP

Hi an alle, ich habe seit geraumer zeit das problem das mein pc immer wieder abschmiert (nur beim filme gucken zocken usw.) ich hab mal die minidump ausgelesen kann damit aber überhaupnichts anfangen hoffe ihr könnt mir weiter helfen. Microsoft (R) Windows Debugger Version 6.9.0003.113 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini052008-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 \WINDOWS\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.exe Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible Product: WinNt Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0 Debug session time: Tue May 20 20:20:01.937 2008 (GMT+2) System Uptime: 0 days 0:32:46.664 *************************************************** ****************** * 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 \WINDOWS\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.exe Loading Kernel Symbols ......................................Unable to load image &#19968;&#34225;&#16392;, Win32 error 0n2 *** WARNING: Unable to verify timestamp for &#19968;&#34225;&#16392; Unable to add module at 00000000 Loading User Symbols Loading unloaded module list ............ ***************************************************** ************************* * * * Bugcheck Analysis * * * ****************************************************** ************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, bf801cc6, f7535c44, 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 *** *** *** ******************************************************* ****************** ******************************************************** ************* * 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 : ntoskrnl.exe ( nt+698f ) Followup: MachineOwner ---------

Hallo,

damit kann ich so zwar auch nicht allzuviel anfangen, es wären ein paar klare Angaben zum PC besser gewesen.

Hier könnte aber folgender Fehler vorliegen

http://www.jasik.de/shutdown/stop_fehler.htm#8E

Gruß

Helmut

danke ich forste mich grad durch deinen link

hab nochmal den blue screen abgetackert

STOP: 0*00000Dd1, (0*000155BD, 0*00000002, 0*00000001, 0*F77927E9)




usbuhci.sys - adress F77927E9 base at F778F000, datestamp 480254CE

DRIVER_IRQL_NOT_LESS_OR_EQUAL

• Blue Screen Meldung während msn videofonie
• Blue Screen - UNEXPECTED_KERNEL_MODE_TRAP
• web-cam erzeut blue-screen???
• blue screen bei vista " home premium "
• Blue Screen warum?