Hallo,
mein PC startet sich in letzter Zeit ziemlich oft neu, einfach, wenn ich irgendetwas mache, egal was.
Er fährt sich herunter, startet neu und hat dann den KernelFaultCheck in der Autostartliste drin.
Was kann man dagegen machen???
danke
Lukas
Moin,
hört sich so erstmal nach einem Bluescreen an.
Stelle in der „Systemsteuerung“ unter „System“ -> Erweitert -> „Starten & Wiederherstellen“ den Punkt „Debuginformationen speichern“ am besten auf „kleines Speicherabbild (64k)“.
Wenn deine Kiste wieder mal abstürzt, dann wird ein Dumpfile geschrieben.
Ab hier wird’s etwas komplizierter 
Das File liegt nachher im Windowsverzeichnis unter Minidump (nach Datum sortiert).
Lade dir von Microsoft die Debugtools runter (Symbols sind nicht unbedingt erforderlich)
Lade im Debugtool deinen Dump ein („Open Crash Dump File“ oder so)
Tippe „!analyze -v“, dann wird’s etwas detailierter.
Ggf poste mal, was ab dem „!analyze -v“ rauskommt.
Viele Grüße
Markus
Nehme dort doch einfach das Häckchen raus!
Systemeigenschaften - Registerkarte Erweitert - Starten und Wiederherstellen Einstellungen - Systemfehler: Autom. Neustart durchführen (Häckchen entfernen)
Dann siehst du, ob es ein BlueScreen ist!
Lade dir von Microsoft die Debugtools runter (Symbols sind
nicht unbedingt erforderlich)
Lade im Debugtool deinen Dump ein („Open Crash Dump File“ oder
so)Tippe „!analyze -v“, dann wird’s etwas detailierter.
Ggf poste mal, was ab dem „!analyze -v“ rauskommt.
hi, ich check hier gar nix mehr bitte um hilfe!!
Das ist das nach dem „!analyze -v“:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000060, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f7812d6e, address which referenced memory
***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
MODULE_NAME: usbehci
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 480254ce
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000060
CURRENT_IRQL: 2
FAULTING_IP:
usbehci+3d6e
f7812d6e ff7660 push dword ptr [esi+60h]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from f7813192 to f7812d6e
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
805572ec f7813192 8a0eb9dc 01f1f898 88f1f898 usbehci+0x3d6e
80557348 f7814f1d 8a0eb9dc 88f1f898 80557378 usbehci+0x4192
80557358 b9e9e4aa 8a0eb9dc 88f1f898 804e56ec usbehci+0x5f1d
80557378 b9e9f768 026c6f50 8a0eb0e0 88f1f720 USBPORT+0x84aa
805573a0 b9ea30a0 8a0eb028 50457270 804e56ec USBPORT+0x9768
805573d0 b9eb124b 8a0eb028 804e56ec 8a0eb028 USBPORT+0xd0a0
8055740c b9eb13c2 8a0eb028 00000001 80561f20 USBPORT+0x1b24b
80557428 804dcd12 8a0eb64c 6b755044 00000000 USBPORT+0x1b3c2
8055742c 8a0eb64c 6b755044 00000000 8a0eb0ec nt+0x5d12
80557430 6b755044 00000000 8a0eb0ec 80561f20 0x8a0eb64c
80557434 00000000 8a0eb0ec 80561f20 80561cc0 0x6b755044
STACK_COMMAND: kb
FOLLOWUP_IP:
usbehci+3d6e
f7812d6e ff7660 push dword ptr [esi+60h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: usbehci+3d6e
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: usbehci.sys
BUCKET_ID: WRONG_SYMBOLS
Moin,
na guck mal, damit kann man doch schon mal ein bischen was anfangen
Der Fehler (DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)) deutet schon mal recht sicher auf einen Treiberfehler hin.
Die Datei scheint die usbehci.sys zu sein (einziger Hinweis)
Guck dir mal folgende Seiten dazu an:
http://www.file.net/prozess/usbehci.sys.html
http://www.supportnet.de/fresh/2005/3/id1022825.asp
Ja, es kann natürlich auch HArdware kaputt sein, aber ich vermute, daß es eher am Treiber liegt.
Grüße
Markus