Foren
Neue Beiträge
Foren durchsuchen
Aktuelles
Neue Beiträge
Profilnachrichten
Neueste Aktivitäten
Mitglieder
Zurzeit aktive Besucher
Profilnachrichten
Profilnachrichten suchen
Login
Registrieren
Aktuelles
Suche
Suche
Nur Titel durchsuchen
Von:
Neue Beiträge
Foren durchsuchen
Menü
Login
Registrieren
App installieren
Installieren
Foren
Acer Forum
Acer Treiber
Grafiktreiber (ATI/AMD) & Hybrid (ATI/AMD + Intel) & Realtek Audio Treiber + HDMI >>> Support & Disk
JavaScript ist deaktiviert. Für eine bessere Darstellung aktiviere bitte JavaScript in deinem Browser, bevor du fortfährst.
Du verwendest einen veralteten Browser. Es ist möglich, dass diese oder andere Websites nicht korrekt angezeigt werden.
Du solltest ein Upgrade durchführen oder einen
alternativen Browser
verwenden.
Auf Thema antworten
Beitrag
<blockquote data-quote="El_SchNoReLLi" data-source="post: 296729" data-attributes="member: 7495"><p><strong>AW: Grafiktreiber (ATI/AMD) & Hybrid (ATI/AMD + Intel) & Realtek Audio Treiber + HDMI >>> Support & Diskussion</strong></p><p></p><p></p><p> </p><p>zum Thema Dumpfile: </p><p> </p><p>[CODE] </p><p>Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64</p><p>Copyright (c) Microsoft Corporation. All rights reserved.</p><p> </p><p> </p><p>Loading Dump File [C:\Users\elschnorelli\Desktop\040611-80215-01.dmp]</p><p>Mini Kernel Dump File: Only registers and stack trace are available</p><p> </p><p>Symbol search path is: *** Invalid ***</p><p>****************************************************************************</p><p>* Symbol loading may be unreliable without a symbol search path. *</p><p>* Use .symfix to have the debugger choose a symbol path. *</p><p>* After setting your symbol path, use .reload to refresh symbol locations. *</p><p>****************************************************************************</p><p>Executable search path is: </p><p>*********************************************************************</p><p>* Symbols can not be loaded because symbol path is not initialized. *</p><p>* *</p><p>* The Symbol Path can be set by: *</p><p>* using the _NT_SYMBOL_PATH environment variable. *</p><p>* using the -y <symbol_path> argument when starting the debugger. *</p><p>* using .sympath and .sympath+ *</p><p>*********************************************************************</p><p>Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2</p><p>*** WARNING: Unable to verify timestamp for ntoskrnl.exe</p><p>*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe</p><p>Windows 7 Kernel Version 7600 MP (4 procs) Free x64</p><p>Product: WinNt, suite: TerminalServer SingleUserTS</p><p>Built by: 7600.16695.amd64fre.win7_gdr.101026-1503</p><p>Machine Name:</p><p>Kernel base = 0xfffff800`0305e000 PsLoadedModuleList = 0xfffff800`0329be50</p><p>Debug session time: Wed Apr 6 23:26:12.841 2011 (UTC + 2:00)</p><p>System Uptime: 0 days 0:05:35.386</p><p>*********************************************************************</p><p>* Symbols can not be loaded because symbol path is not initialized. *</p><p>* *</p><p>* The Symbol Path can be set by: *</p><p>* using the _NT_SYMBOL_PATH environment variable. *</p><p>* using the -y <symbol_path> argument when starting the debugger. *</p><p>* using .sympath and .sympath+ *</p><p>*********************************************************************</p><p>Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2</p><p>*** WARNING: Unable to verify timestamp for ntoskrnl.exe</p><p>*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe</p><p>Loading Kernel Symbols</p><p>...............................................................</p><p>................................................................</p><p>...........................</p><p>Loading User Symbols</p><p>Loading unloaded module list</p><p>.........</p><p>Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2</p><p>*** WARNING: Unable to verify timestamp for dxgkrnl.sys</p><p>*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys</p><p>*******************************************************************************</p><p>* *</p><p>* Bugcheck Analysis *</p><p>* *</p><p>*******************************************************************************</p><p> </p><p>Use !analyze -v to get detailed debugging information.</p><p> </p><p>BugCheck 116, {fffffa800845a010, fffff8800814740c, 0, 2}</p><p> </p><p>Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2</p><p>*** WARNING: Unable to verify timestamp for atikmpag.sys</p><p>*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys</p><p>***** Kernel symbols are WRONG. Please fix symbols to do analysis.</p><p> </p><p>*************************************************************************</p><p>*** ***</p><p>*** ***</p><p>*** Your debugger is not using the correct symbols ***</p><p>*** ***</p><p>*** In order for this command to work properly, your symbol path ***</p><p>*** must point to .pdb files that have full type information. ***</p><p>*** ***</p><p>*** Certain .pdb files (such as the public OS symbols) do not ***</p><p>*** contain the required information. Contact the group that ***</p><p>*** provided you with these symbols if you need this command to ***</p><p>*** work. ***</p><p>*** ***</p><p>*** Type referenced: nt!_KPRCB ***</p><p>*** ***</p><p>*************************************************************************</p><p>*************************************************************************</p><p>*** ***</p><p>*** ***</p><p>*** Your debugger is not using the correct symbols ***</p><p>*** ***</p><p>*** In order for this command to work properly, your symbol path ***</p><p>*** must point to .pdb files that have full type information. ***</p><p>*** ***</p><p>*** Certain .pdb files (such as the public OS symbols) do not ***</p><p>*** contain the required information. Contact the group that ***</p><p>*** provided you with these symbols if you need this command to ***</p><p>*** work. ***</p><p>*** ***</p><p>*** Type referenced: nt!KPRCB ***</p><p>*** ***</p><p>*************************************************************************</p><p>*************************************************************************</p><p>*** ***</p><p>*** ***</p><p>*** Your debugger is not using the correct symbols ***</p><p>*** ***</p><p>*** In order for this command to work properly, your symbol path ***</p><p>*** must point to .pdb files that have full type information. ***</p><p>*** ***</p><p>*** Certain .pdb files (such as the public OS symbols) do not ***</p><p>*** contain the required information. Contact the group that ***</p><p>*** provided you with these symbols if you need this command to ***</p><p>*** work. ***</p><p>*** ***</p><p>*** Type referenced: nt!_KPRCB ***</p><p>*** ***</p><p>*************************************************************************</p><p>*************************************************************************</p><p>*** ***</p><p>*** ***</p><p>*** Your debugger is not using the correct symbols ***</p><p>*** ***</p><p>*** In order for this command to work properly, your symbol path ***</p><p>*** must point to .pdb files that have full type information. ***</p><p>*** ***</p><p>*** Certain .pdb files (such as the public OS symbols) do not ***</p><p>*** contain the required information. Contact the group that ***</p><p>*** provided you with these symbols if you need this command to ***</p><p>*** work. ***</p><p>*** ***</p><p>*** Type referenced: nt!KPRCB ***</p><p>*** ***</p><p>*************************************************************************</p><p>*************************************************************************</p><p>*** ***</p><p>*** ***</p><p>*** Your debugger is not using the correct symbols ***</p><p>*** ***</p><p>*** In order for this command to work properly, your symbol path ***</p><p>*** must point to .pdb files that have full type information. ***</p><p>*** ***</p><p>*** Certain .pdb files (such as the public OS symbols) do not ***</p><p>*** contain the required information. Contact the group that ***</p><p>*** provided you with these symbols if you need this command to ***</p><p>*** work. ***</p><p>*** ***</p><p>*** Type referenced: nt!_KPRCB ***</p><p>*** ***</p><p>*************************************************************************</p><p>*************************************************************************</p><p>*** ***</p><p>*** ***</p><p>*** Your debugger is not using the correct symbols ***</p><p>*** ***</p><p>*** In order for this command to work properly, your symbol path ***</p><p>*** must point to .pdb files that have full type information. ***</p><p>*** ***</p><p>*** Certain .pdb files (such as the public OS symbols) do not ***</p><p>*** contain the required information. Contact the group that ***</p><p>*** provided you with these symbols if you need this command to ***</p><p>*** work. ***</p><p>*** ***</p><p>*** Type referenced: nt!_KPRCB ***</p><p>*** ***</p><p>*************************************************************************</p><p>*************************************************************************</p><p>*** ***</p><p>*** ***</p><p>*** Your debugger is not using the correct symbols ***</p><p>*** ***</p><p>*** In order for this command to work properly, your symbol path ***</p><p>*** must point to .pdb files that have full type information. ***</p><p>*** ***</p><p>*** Certain .pdb files (such as the public OS symbols) do not ***</p><p>*** contain the required information. Contact the group that ***</p><p>*** provided you with these symbols if you need this command to ***</p><p>*** work. ***</p><p>*** ***</p><p>*** Type referenced: nt!_KPRCB ***</p><p>*** ***</p><p>*************************************************************************</p><p>*************************************************************************</p><p>*** ***</p><p>*** ***</p><p>*** Your debugger is not using the correct symbols ***</p><p>*** ***</p><p>*** In order for this command to work properly, your symbol path ***</p><p>*** must point to .pdb files that have full type information. ***</p><p>*** ***</p><p>*** Certain .pdb files (such as the public OS symbols) do not ***</p><p>*** contain the required information. Contact the group that ***</p><p>*** provided you with these symbols if you need this command to ***</p><p>*** work. ***</p><p>*** ***</p><p>*** Type referenced: nt!_KPRCB ***</p><p>*** ***</p><p>*************************************************************************</p><p>Probably caused by : atikmpag.sys ( atikmpag+740c )</p><p> </p><p>Followup: MachineOwner</p><p>---------</p><p>[/CODE]</p></blockquote><p></p>
[QUOTE="El_SchNoReLLi, post: 296729, member: 7495"] [b]AW: Grafiktreiber (ATI/AMD) & Hybrid (ATI/AMD + Intel) & Realtek Audio Treiber + HDMI >>> Support & Diskussion[/b] zum Thema Dumpfile: [CODE] Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\elschnorelli\Desktop\040611-80215-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 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Machine Name: Kernel base = 0xfffff800`0305e000 PsLoadedModuleList = 0xfffff800`0329be50 Debug session time: Wed Apr 6 23:26:12.841 2011 (UTC + 2:00) System Uptime: 0 days 0:05:35.386 ********************************************************************* * 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 ......... Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa800845a010, fffff8800814740c, 0, 2} Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* Probably caused by : atikmpag.sys ( atikmpag+740c ) Followup: MachineOwner --------- [/CODE] [/QUOTE]
Authentifizierung
Antworten
Foren
Acer Forum
Acer Treiber
Grafiktreiber (ATI/AMD) & Hybrid (ATI/AMD + Intel) & Realtek Audio Treiber + HDMI >>> Support & Disk
Oben