singleuserts Go Windows Forum - 819382

264 Benutzer online
01. November 2024, 07:27:44

Windows Community

Seiten: [1] Nach unten

Neues Thema erstellen

	Antworten / Aufrufe	Themen mit dem Stichwort singleuserts
	14 Antworten 8176 Aufrufe	Vista x64 Problem :( Begonnen von zweipackk 01. März 2009, 17:29:48 Hallöchen Habe folgendes Problem mein OS Vista x64 stürzt öfters unerwartet ab, dabei ist es egal welche Anwendungen laufen oder nicht ist also kein Softwareproblem. Ich habe auch Prime95 24h laufen lassen können und es gab absolut keine Probleme oder Bluescreens. Auch Memtest86 fand keine Fehler. Ich bin wirklich am verzweifeln. Ich habe mir die dump file mal angeschaut und auch schon gegoogelt aber bezieht sich leider alles nur auf xp und hilft mir daher nicht weiter... Zu meinem System: Intel i7 DDR3 Ram Nanya 1333MHZ ATI HD 4870 In der Dump file steht problem caused by hardware, leider kann ich damit nicht viel anfangen vllt. könnt Ihr mehr herauslesen. Ich bin über jede Hilfe sehr dankbar. Danke schonmal im Voraus Jetzt die dmp. file: Microsoft (R) Windows Debugger Version 6.11.0001.402 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini030109-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 * WARNING: Unable to verify timestamp for ntoskrnl.exe * ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff800`01e4e000 PsLoadedModuleList = 0xfffff800`02013db0 Debug session time: Sun Mar 1 13:21:37.144 2009 (GMT+1) System Uptime: 0 days 1:31:08.101 ********************************************** ***************** * 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.exe Loading Kernel Symbols .................................................. ............. .................................................. .............. ............................. Loading User Symbols Loading unloaded module list ................... * WARNING: Unable to verify timestamp for hal.dll * ERROR: Module load completed but symbols could not be loaded for hal.dll ********************************************** *************************** * * * Bugcheck Analysis * * * ************************************************ ************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8008932030, be000000, 800400} * 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!_WHEA_ERROR_RECORD_HEADER * * * ********************************************** ******************* ********************************************** ******************* * * * * * 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!_WHEA_ERROR_RECORD_HEADER * * * ********************************************** ******************* Unable to load image \SystemRoot\system32\PSHED.dll, Win32 error 0n2 * WARNING: Unable to verify timestamp for PSHED.dll * ERROR: Module load completed but symbols could not be loaded for PSHED.dll ********************************************** ******************* * * * * * 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: pshed!_WHEA_ERROR_RECORD_HEADER * * * ********************************************** ******************* ********************************************** ******************* * * * * * 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR * * * ********************************************** ******************* ********************************************** ******************* * * * * * 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: pshed!_WHEA_ERROR_RECORD_HEADER * * * ********************************************** ******************* ********************************************** ******************* * * * * * 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: pshed!_WHEA_ERROR_RECORD_HEADER * * * ********************************************** ******************* ********************************************** ******************* * * * * * 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: pshed!_WHEA_ERROR_RECORD_HEADER * * * ********************************************** ******************* ********************************************** ******************* * * * * * 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 * * * ********************************************** ******************* ********************************************** ******************* * * * * * 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 * * * ********************************************** ******************* ********************************************** ******************* * * * * * 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 : hardware Followup: MachineOwner --------- probleme installiert kein zeigt x64 beta unable defekt not are org ntoskrnl 6002 546 completed pshed environ unable load image exe vista download stop gefunden office bluescreen module lautet personal systemfehler path symbols weitere Antworten anzeigen »»

Seiten: [1] Nach oben

0.027s 10q

© go-windows.de singleuserts Go Windows Forum - 819382