Pc Abstürze- Bluescreens

Ich versteh nicht viel von Hardware deshalb ist mir der Satz jetzt eher Spanisch

Bitte um Erklärung

Ich hab den einen Link gefolgt und WIndebug installiert und die Speicherpfade für die dump dateien festgelegt, jetzt muss ich nur abwarten bis die kiste wieder abstürzt damit der Fehlerbericht erstellt wird den ich dann mit Windebug öffnen und analysieren kann?

Ich kann die Dump dateien nicht mit windebug öffnen da ich nicht die berechtigung habe , obwohl ich als administrator eingetragen bin.
Die Txt dateien finde ich nicht, da ich nichtmal die dateipfade nachvollziehen kann (da sie nicht existieren) -.-

so aus der minidump des letzen absturzes der 2 minuten her ist entnehme ich:


Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini090509-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: "SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;
Executable search path is:
Unable to load image \SystemRoot\system32\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 Longhorn Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff800`01a64000 PsLoadedModuleList = 0xfffff800`01c29db0
Debug session time: Sat Sep 5 20:37:45.189 2009 (GMT+2)
System Uptime: 0 days 0:16:46.832
Unable to load image \SystemRoot\system32\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
*

• *
• Bugcheck Analysis *
• *

*

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1000ff, 2, 0, fffffa6000e6fe21}

* Kernel symbols are WRONG. Please fix symbols to do analysis.

Unable to load image \SystemRoot\System32\drivers\tcpip.sys, Win32 error 2
* WARNING: Unable to verify timestamp for tcpip.sys
* ERROR: Module load completed but symbols could not be loaded for tcpip.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 *
* *
*
Unable to load image \SystemRoot\System32\drivers\fwpkclnt.sys, Win32 error 2
* WARNING: Unable to verify timestamp for fwpkclnt.sys
* ERROR: Module load completed but symbols could not be loaded for fwpkclnt.sys
Unable to load image \SystemRoot\system32\drivers\volsnap.sys, Win32 error 2
* WARNING: Unable to verify timestamp for volsnap.sys
* ERROR: Module load completed but symbols could not be loaded for volsnap.sys
* WARNING: Unable to verify timestamp for hal.dll
* ERROR: Module load completed but symbols could not be loaded for hal.dll
Unable to load image \SystemRoot\system32\mcupdate_GenuineIntel.dll, Win32 error 2
* WARNING: Unable to verify timestamp for mcupdate_GenuineIntel.dll
* ERROR: Module load completed but symbols could not be loaded for mcupdate_GenuineIntel.dll
Probably caused by : tcpip.sys ( tcpip+6de21 )

Followup: MachineOwner