Win7 kloppt mir nur noch Bluescreens rein, bitte um Hilfe!
- Ersteller Sibst
- Erstellt am
G
ghostadmin
Guest
Wie willste den den EPS Stecker falsch drauf bekommen?
drdealgood
PC-Selbstbauer(in)
Falsch rum mein ich doch gar nicht 
Hab aber schon mal gesehen, dass der sich "leicht" gelöst und somit keinen richtigen Kontakt mehr hatte 
Hab aber schon mal gesehen, dass der sich "leicht" gelöst und somit keinen richtigen Kontakt mehr hatte
TE
TE
Sibst
Komplett-PC-Käufer(in)
Das die Hardware nicht miteinander kompatibel ist glaube ich nicht.
Habe den PC in nem Hardwareforum zusammenstellen lassen.
Da geh ich dann mal stark davon aus dass die Leute nen Plan davon haben was sie verzapfen^^
Die Riegel sitzen aber auch fest drin! ^^
Am Ram kanns doch nicht liegen, so viele Programme haben ausgesagt dass alles okay ist.
Habe den PC in nem Hardwareforum zusammenstellen lassen.
Da geh ich dann mal stark davon aus dass die Leute nen Plan davon haben was sie verzapfen^^
Die Riegel sitzen aber auch fest drin! ^^
Am Ram kanns doch nicht liegen, so viele Programme haben ausgesagt dass alles okay ist.
simpel1970
Lötkolbengott/-göttin
Läuft es denn bis jetzt?
.gif "sm_=) =)")
simpel1970
Lötkolbengott/-göttin
Ok. Dann schau ma mal.
TE
TE
Sibst
Komplett-PC-Käufer(in)
Hatte schon wieder nen Bluescreen... Diesesmal bei Counterstrike Source
Hier die Minidumpdateien: (Sind 2 Stück)
Minidump.rar
Hier die Minidumpdateien: (Sind 2 Stück)
Minidump.rar
G
ghostadmin
Guest
Wieso stellst du nicht einfach nen Bild des BSODs rein? Damit kann man meist mehr anfangen.^^
TE
TE
Sibst
Komplett-PC-Käufer(in)
Geht leider nicht. Win 7 will mein Handy nicht erkennen und kann deshalb die BluescreenPics nicht hier reinstellen, sonst hätt ichs längst gemacht.
Kann euch aber die Daten davon hier reinposten, müsst mir nur sagen was ich davon aufschreiben soll.
Kann euch aber die Daten davon hier reinposten, müsst mir nur sagen was ich davon aufschreiben soll.
Zuletzt bearbeitet:
simpel1970
Lötkolbengott/-göttin
Werte die Minidumps ganz einfach selbst aus: Klick!
Einfacher (aber nicht so ausführlich) geht es z.B. mit dem Programm Bluescreenview.
(Man hat damit zumindest die Stopfehlercodes).
Einfacher (aber nicht so ausführlich) geht es z.B. mit dem Programm Bluescreenview.
(Man hat damit zumindest die Stopfehlercodes).
TE
TE
Sibst
Komplett-PC-Käufer(in)
Ok, den Debugger habe ich jetzt benutzt. Habe den Bericht, soll ich den einfach mal hier reinkopieren?
Ist aber recht viel...
Ist aber recht viel...
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\XXX\Desktop\080910-23446-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 Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e4de50
Debug session time: Mon Aug 9 12:43:25.909 2010 (GMT+2)
System Uptime: 0 days 2:11:07.657
*********************************************************************
* 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
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffffffffffe8, 0, fffff880041aaa2a, 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 ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.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 : dxgmms1.sys ( dxgmms1+37a2a )
Followup: MachineOwner
---------
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\XXX\Desktop\080910-23446-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 Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e4de50
Debug session time: Mon Aug 9 12:43:25.909 2010 (GMT+2)
System Uptime: 0 days 2:11:07.657
*********************************************************************
* 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
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffffffffffe8, 0, fffff880041aaa2a, 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 ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.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 : dxgmms1.sys ( dxgmms1+37a2a )
Followup: MachineOwner
---------
Zuletzt bearbeitet:
simpel1970
Lötkolbengott/-göttin
Das kannst du ja mit einem Spoiler reinkopieren
Zuerst [ Spoiler] schreiben, dann den Text einfügen und mit [ /Spoiler] abschließen.
Die Leerzeichen innerhalb der [] Klammer weg lassen.
text
Zuerst [ Spoiler] schreiben, dann den Text einfügen und mit [ /Spoiler] abschließen.
Die Leerzeichen innerhalb der [] Klammer weg lassen.
simpel1970
Lötkolbengott/-göttin
Hinterlege noch den Symbolpfad (wie in der Anleitung erläutert).
Stopfehler: 0x50
Absturzursache: dxgmms1.sys
Poste das Ergebnis noch einmal, wenn der Symbolpfad hinterlegt wurde.
Versuche es noch mit der RAM-Spannung auf 1,66V.
Edit:
Hilft das auch nichts, zusätzlich (zu 1,66V) die Timings der RAM auf 8-8-8-24; Command Rate 2T, Frequenz fest auf 666mhz (1333mhz) einstellen. Hört sich zwar komisch an, probiere es aber.
Zuletzt bearbeitet:
simpel1970
Lötkolbengott/-göttin
Diesen hier:
TE
TE
Sibst
Komplett-PC-Käufer(in)
So da haben wirs für 2 .dmp
1: kd> .reload
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\XXX\Desktop\080910-23446-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e4de50
Debug session time: Mon Aug 9 12:43:25.909 2010 (GMT+2)
System Uptime: 0 days 2:11:07.657
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffffffffffe8, 0, fffff880041aaa2a, 0}
Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::Free+e6 )
Followup: MachineOwner
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\XXX\Desktop\080910-23446-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e4de50
Debug session time: Mon Aug 9 12:43:25.909 2010 (GMT+2)
System Uptime: 0 days 2:11:07.657
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffffffffffe8, 0, fffff880041aaa2a, 0}
Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::Free+e6 )
Followup: MachineOwner
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\XXX\Desktop\081010-17643-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
*** 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 Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c4a000 PsLoadedModuleList = 0xfffff800`02e87e50
Debug session time: Tue Aug 10 01:12:12.698 2010 (GMT+2)
System Uptime: 0 days 10:11:01.072
*********************************************************************
* 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
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff88004c277fb, fffff8800938f7f0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 : atikmdag.sys ( atikmdag+38b7fb )
Followup: MachineOwner
---------
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\XXX\Desktop\081010-17643-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
*** 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 Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c4a000 PsLoadedModuleList = 0xfffff800`02e87e50
Debug session time: Tue Aug 10 01:12:12.698 2010 (GMT+2)
System Uptime: 0 days 10:11:01.072
*********************************************************************
* 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
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff88004c277fb, fffff8800938f7f0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 : atikmdag.sys ( atikmdag+38b7fb )
Followup: MachineOwner
---------
1: kd> .reload
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
simpel1970
Lötkolbengott/-göttin
Wieso stimmt den der Symbolpfad bei der zweiten Auswertung schon wieder nicht? Hattest du die vor dem Anlegen des Symbolpfades gemacht?
Beim ersten Text ist soweit alles richtig, nur musst du noch !analyze -v (unten in der Kommandozeile) eingeben, damit die Auswertung auch gemacht wird.
Ich will dich aber nicht unnötig nerven, die beiden verschiedenen Bluescreens lassen auch ohne Auswertung ein Problem mit dem Speichermanagement vermuten. Dies kann durch den RAM oder auch durch die Grafikkarte (VRam) verursacht werden.
Probiere bitte zunächst die RAM-Spannung mit 1,66V aus.
Kommen die Bluescreens immer noch die oben genannten Einstellungen testen:
Beim ersten Text ist soweit alles richtig, nur musst du noch !analyze -v (unten in der Kommandozeile) eingeben, damit die Auswertung auch gemacht wird.
Ich will dich aber nicht unnötig nerven, die beiden verschiedenen Bluescreens lassen auch ohne Auswertung ein Problem mit dem Speichermanagement vermuten. Dies kann durch den RAM oder auch durch die Grafikkarte (VRam) verursacht werden.
Probiere bitte zunächst die RAM-Spannung mit 1,66V aus.
Kommen die Bluescreens immer noch die oben genannten Einstellungen testen:
TE
TE
Sibst
Komplett-PC-Käufer(in)
So, alles im Bios eingestellt und hier nochmal die Debug-Infos:
Komisch, die Zweite kann er nicht auslesen...
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\XXX\Desktop\080910-23446-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e4de50
Debug session time: Mon Aug 9 12:43:25.909 2010 (GMT+2)
System Uptime: 0 days 2:11:07.657
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffffffffffe8, 0, fffff880041aaa2a, 0}
Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::Free+e6 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffffffffffe8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880041aaa2a, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb80e0
ffffffffffffffe8
FAULTING_IP:
dxgmms1!VIDMM_LINEAR_POOL::Free+e6
fffff880`041aaa2a 488b4608 mov rax,qword ptr [rsi+8]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: Crysis64.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800a08f370 -- (.trap 0xfffff8800a08f370)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffffffe0 rbx=0000000000000000 rcx=fffffa8005941010
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880041aaa2a rsp=fffff8800a08f500 rbp=fffff8a0031cfb40
r8=fffff8800a08f560 r9=fffff8800a08f568 r10=fffff8a00989c040
r11=fffffa8005941050 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
dxgmms1!VIDMM_LINEAR_POOL::Free+0xe6:
fffff880`041aaa2a 488b4608 mov rax,qword ptr [rsi+8] ds:0404:00000000`00000008=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002d00e54 to fffff80002c80600
STACK_TEXT:
fffff880`0a08f208 fffff800`02d00e54 : 00000000`00000050 ffffffff`ffffffe8 00000000`00000000 fffff880`0a08f370 : nt!KeBugCheckEx
fffff880`0a08f210 fffff800`02c7e6ee : 00000000`00000000 fffff8a0`031cfb60 ffffffff`ffffff00 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x42877
fffff880`0a08f370 fffff880`041aaa2a : fffff8a0`031cfb60 fffff880`04178ee3 fffffa80`05a36010 fffff8a0`03b97d90 : nt!KiPageFault+0x16e
fffff880`0a08f500 fffff880`041a85eb : fffffa80`05a43000 00000000`0ab94000 ffffffff`ffffffe0 fffff8a0`0a807610 : dxgmms1!VIDMM_LINEAR_POOL::Free+0xe6
fffff880`0a08f550 fffff880`041a854a : fffffa80`00000000 fffffa80`0626c520 fffffa80`059fed20 fffff880`0a08f628 : dxgmms1!VIDMM_PROCESS_HEAP::FreeSmallAllocation+0x8b
fffff880`0a08f580 fffff880`04193b5a : fffff880`0a08f5a8 fffff8a0`0c988f80 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0x13a
fffff880`0a08f5b0 fffff880`0418e523 : fffffa80`067e44c0 00000000`00000000 fffff8a0`0c811e50 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x112
fffff880`0a08f660 fffff880`04174ecc : fffffa80`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0a08f730 fffff880`040b6c10 : 00000000`00000000 fffff8a0`03435000 fffff8a0`03435000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0a08f760 fffff880`040c967c : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`00000799 : dxgkrnl!DXGDEVICE:
estroyAllocations+0x248
fffff880`0a08f850 fffff880`040ae815 : 00000000`fffffeda fffff8a0`01dfc4e0 fffff8a0`03435000 fffffa80`05a30000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
fffff880`0a08f8c0 fffff880`040ecca6 : 00000000`00000000 fffffa80`05a30000 fffff8a0`01dfc4e0 fffff8a0`01dfc560 : dxgkrnl!DXGADAPTER:estroyDevice+0x1c9
fffff880`0a08f8f0 fffff880`040ec63c : fffff900`c25afce0 00000000`00000000 00000000`00000001 fffff900`c25afce0 : dxgkrnl!DXGPROCESS:estroy+0xba
fffff880`0a08f9a0 fffff960`00104aa4 : 00000000`00000da0 fffff900`c25afce0 00000000`00000000 fffff900`c25afce0 : dxgkrnl!DxgkProcessCallout+0x268
fffff880`0a08fa30 fffff960`001041a7 : fffffa80`05d10a00 00000000`00000001 fffffa80`06b2f860 00000000`38246f90 : win32k!GdiProcessCallout+0x244
fffff880`0a08fab0 fffff800`02f66881 : fffffa80`05d10a60 00000000`00000000 00000000`00000000 fffffa80`06b2f860 : win32k!W32pProcessCallout+0x6b
fffff880`0a08fae0 fffff800`02f3e6eb : 00000000`c000004b 00000000`00000001 fffffa80`0626c500 00000000`00000000 : nt!PspExitThread+0x561
fffff880`0a08fba0 fffff800`02c7f853 : fffffa80`0626c520 00000000`c000004b 00000000`00000001 fffffa80`06b2f860 : nt!NtTerminateProcess+0x25b
fffff880`0a08fc20 00000000`774d001a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0012d428 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774d001a
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_LINEAR_POOL::Free+e6
fffff880`041aaa2a 488b4608 mov rax,qword ptr [rsi+8]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgmms1!VIDMM_LINEAR_POOL::Free+e6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
FAILURE_BUCKET_ID: X64_0x50_dxgmms1!VIDMM_LINEAR_POOL::Free+e6
BUCKET_ID: X64_0x50_dxgmms1!VIDMM_LINEAR_POOL::Free+e6
Followup: MachineOwner
---------
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\XXX\Desktop\080910-23446-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e4de50
Debug session time: Mon Aug 9 12:43:25.909 2010 (GMT+2)
System Uptime: 0 days 2:11:07.657
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffffffffffe8, 0, fffff880041aaa2a, 0}
Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::Free+e6 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffffffffffe8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880041aaa2a, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb80e0
ffffffffffffffe8
FAULTING_IP:
dxgmms1!VIDMM_LINEAR_POOL::Free+e6
fffff880`041aaa2a 488b4608 mov rax,qword ptr [rsi+8]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: Crysis64.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800a08f370 -- (.trap 0xfffff8800a08f370)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffffffe0 rbx=0000000000000000 rcx=fffffa8005941010
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880041aaa2a rsp=fffff8800a08f500 rbp=fffff8a0031cfb40
r8=fffff8800a08f560 r9=fffff8800a08f568 r10=fffff8a00989c040
r11=fffffa8005941050 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
dxgmms1!VIDMM_LINEAR_POOL::Free+0xe6:
fffff880`041aaa2a 488b4608 mov rax,qword ptr [rsi+8] ds:0404:00000000`00000008=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002d00e54 to fffff80002c80600
STACK_TEXT:
fffff880`0a08f208 fffff800`02d00e54 : 00000000`00000050 ffffffff`ffffffe8 00000000`00000000 fffff880`0a08f370 : nt!KeBugCheckEx
fffff880`0a08f210 fffff800`02c7e6ee : 00000000`00000000 fffff8a0`031cfb60 ffffffff`ffffff00 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x42877
fffff880`0a08f370 fffff880`041aaa2a : fffff8a0`031cfb60 fffff880`04178ee3 fffffa80`05a36010 fffff8a0`03b97d90 : nt!KiPageFault+0x16e
fffff880`0a08f500 fffff880`041a85eb : fffffa80`05a43000 00000000`0ab94000 ffffffff`ffffffe0 fffff8a0`0a807610 : dxgmms1!VIDMM_LINEAR_POOL::Free+0xe6
fffff880`0a08f550 fffff880`041a854a : fffffa80`00000000 fffffa80`0626c520 fffffa80`059fed20 fffff880`0a08f628 : dxgmms1!VIDMM_PROCESS_HEAP::FreeSmallAllocation+0x8b
fffff880`0a08f580 fffff880`04193b5a : fffff880`0a08f5a8 fffff8a0`0c988f80 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0x13a
fffff880`0a08f5b0 fffff880`0418e523 : fffffa80`067e44c0 00000000`00000000 fffff8a0`0c811e50 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x112
fffff880`0a08f660 fffff880`04174ecc : fffffa80`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0a08f730 fffff880`040b6c10 : 00000000`00000000 fffff8a0`03435000 fffff8a0`03435000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0a08f760 fffff880`040c967c : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`00000799 : dxgkrnl!DXGDEVICE:
estroyAllocations+0x248fffff880`0a08f850 fffff880`040ae815 : 00000000`fffffeda fffff8a0`01dfc4e0 fffff8a0`03435000 fffffa80`05a30000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
fffff880`0a08f8c0 fffff880`040ecca6 : 00000000`00000000 fffffa80`05a30000 fffff8a0`01dfc4e0 fffff8a0`01dfc560 : dxgkrnl!DXGADAPTER:
estroyDevice+0x1c9fffff880`0a08f8f0 fffff880`040ec63c : fffff900`c25afce0 00000000`00000000 00000000`00000001 fffff900`c25afce0 : dxgkrnl!DXGPROCESS:
estroy+0xbafffff880`0a08f9a0 fffff960`00104aa4 : 00000000`00000da0 fffff900`c25afce0 00000000`00000000 fffff900`c25afce0 : dxgkrnl!DxgkProcessCallout+0x268
fffff880`0a08fa30 fffff960`001041a7 : fffffa80`05d10a00 00000000`00000001 fffffa80`06b2f860 00000000`38246f90 : win32k!GdiProcessCallout+0x244
fffff880`0a08fab0 fffff800`02f66881 : fffffa80`05d10a60 00000000`00000000 00000000`00000000 fffffa80`06b2f860 : win32k!W32pProcessCallout+0x6b
fffff880`0a08fae0 fffff800`02f3e6eb : 00000000`c000004b 00000000`00000001 fffffa80`0626c500 00000000`00000000 : nt!PspExitThread+0x561
fffff880`0a08fba0 fffff800`02c7f853 : fffffa80`0626c520 00000000`c000004b 00000000`00000001 fffffa80`06b2f860 : nt!NtTerminateProcess+0x25b
fffff880`0a08fc20 00000000`774d001a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0012d428 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774d001a
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_LINEAR_POOL::Free+e6
fffff880`041aaa2a 488b4608 mov rax,qword ptr [rsi+8]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgmms1!VIDMM_LINEAR_POOL::Free+e6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
FAILURE_BUCKET_ID: X64_0x50_dxgmms1!VIDMM_LINEAR_POOL::Free+e6
BUCKET_ID: X64_0x50_dxgmms1!VIDMM_LINEAR_POOL::Free+e6
Followup: MachineOwner
---------
Komisch, die Zweite kann er nicht auslesen...
drdealgood
PC-Selbstbauer(in)
Hmm, also ich würds erst mal mit runtertakten der Speicher auf 1200 oder 1066 MHz probieren, halt nur mal um zu schauen obs dann den "Blauen" nicht mehr gibt
