Selbstgebautes PC stürtzt ab mit Bluescreen NICHT GELÖST!

AW: Selbstgebautes PC stürtzt ab mit Bluescreen NICHT GELÖST!

Mobo und Cpu kann ich gleich ausschliessen da ich es in den Reparatur geschickt habe.
Und es gab keine Fehler
 
AW: Selbstgebautes PC stürtzt ab mit Bluescreen NICHT GELÖST!

Wenns weder Brett von CPU ist, bleibt nur noch RAM übrig.
Hast du mal eine andere Maus/Tastatur ausprobiert?
 
AW: Selbstgebautes PC stürtzt ab mit Bluescreen NICHT GELÖST!

Was bedeutet durchnessen bei Netzteil genau und was bringt das? Wie kann ich das machen?
 
AW: Selbstgebautes PC stürtzt ab mit Bluescreen NICHT GELÖST!

Welches Netzteil würdet ihr mir empfehlen? Es muss sehr leise unter last sein und muss genug stark sein mein ganzes System anzufeuern.
 
AW: Selbstgebautes PC stürtzt ab mit Bluescreen NICHT GELÖST!

Es lag nicht am NT
ich hab es mal mit Whocrashed ausgewertet:
Crash dump file: C:\Windows\memory.dmp
Date/time: 16.10.2011 10:42:21 GMT
Uptime: 00:25:21
Machine:
Bug check name: CLOCK_WATCHDOG_TIMEOUT
Bug check code: 0x101
Bug check parm 1: 0x19
Bug check parm 2: 0x0
Bug check parm 3: 0xFFFFF88002F65180
Bug check parm 4: 0x2
Probably caused by: [FONT=Segoe UI, Arial]Unknown[/FONT]
Driver description: http://www.google.com/search?q=
Driver product: http://www.google.com/search?q=
Driver company: http://www.google.com/search?q=
OS build: Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Architecture: x86 (32 bit)
CPU count: 8
Page size: 4096

Bug check description:
This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

Comments:
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .

Könnt ir mir sagen was da falsch ist
 
AW: Selbstgebautes PC stürtzt ab mit Bluescreen NICHT GELÖST!

Hast du all das gemacht was ich dir mal gepostet habe?

Hübie schrieb:
Hallo GTAPLAYER.

Du scheinst ja echt verzweifelt zu sein. Ich denke aber nicht das wir es hier mit einem hardware-Problem zu tun haben.
  1. Lade doch mal bitte ein oder zwei der letzten *.dmp-Datei(en) hoch (C:\Windows\Minidump\*.dmp)
  2. Hast du den Intel Watchdog Treiber installiert? (Hier)
  3. Welchen Grafikkarten-Treiber verwendest du? Empfehlen kann ich den 275.33 (WHQL)
  4. Welchen Chipsatztreiber hast du installiert? (Dieser ist aktuell)
  5. Welche Programme laufen im Hintergrund?
  6. Hast du ALLE Windows-Updates installiert (ca. 300 Updates sollten das sein)?
  7. Wie sieht es im Hardware-Manager aus? Irgendwelche Treiber die nicht installiert sind?
  8. Starte mal msinfo32 und schau unter Komponenten->Problemgeräte ob da was verdächtiges ist.
  9. Hast du nach dem BIOS-Update ein reset gemacht und danach "load optimized defaults" ausgeführt? Wenn nicht beides nachholen!
Zum Vergrößern anklicken....
Zum Vergrößern anklicken....
 
AW: Selbstgebautes PC stürtzt ab mit Bluescreen NICHT GELÖST!

Ich habe es mit debuging tool analysiert:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
WARNING: Whitespace at end of path element
WARNING: Whitespace at end of path element
Symbol search path is: SRV"c:\symbols"http://msdl.microsoft.com/download/symbols

Executable search path is: C:\Windows\System32

*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`0309fe90
Debug session time: Sun Oct 16 20:38:46.820 2011 (UTC + 2:00)
System Uptime: 0 days 0:38:54.695
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
......
The context is partially valid. Only x86 user-mode context is available.
The wow64exts extension must be loaded to access 32-bit state.
.load wow64exts will do this if you haven't loaded it already.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {19, 0, fffff88003117180, 6}
***** 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 : ntkrnlmp.exe
Followup: MachineOwner
---------
16.0: kd:x86> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003117180, The PRCB address of the hung processor.
Arg4: 0000000000000006, 0.
Debugging Details:
------------------
***** 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 ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80002e5a000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 0x0

STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
16.0: kd:x86> lmvm nt
start end module name
fffff800`02e5a000 fffff800`03444000 nt (export symbols) ntkrnlmp.exe
Loaded symbol image file: ntkrnlmp.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Sat Nov 20 10:30:02 2010 (4CE7951A)
CheckSum: 0055CE0C
ImageSize: 005EA000
File version: 6.1.7601.17514
Product version: 6.1.7601.17514
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 6.1.7601.17514
FileVersion: 6.1.7601.17514 (win7sp1_rtm.101119-1850)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.
16.0: kd:x86> lmvm nt
start end module name
fffff800`02e5a000 fffff800`03444000 nt (export symbols) ntkrnlmp.exe
Loaded symbol image file: ntkrnlmp.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Sat Nov 20 10:30:02 2010 (4CE7951A)
CheckSum: 0055CE0C
ImageSize: 005EA000
File version: 6.1.7601.17514
Product version: 6.1.7601.17514
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 6.1.7601.17514
FileVersion: 6.1.7601.17514 (win7sp1_rtm.101119-1850)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.
16.0: kd:x86> g
^ No runnable debuggees error in 'g'
16.0: kd:x86> gn
^ No runnable debuggees error in 'gn'
16.0: kd:x86> gh
^ No runnable debuggees error in 'gh'
 
AW: Selbstgebautes PC stürtzt ab mit Bluescreen NICHT GELÖST!

Wenn du dir dein log anschauen würdest wäre dir aufgefallen, dass dein symbols-path flasch ist ;) Noch mal das ganze. Meine Fragen sind damit aber auch nicht beantwortet. Also bitte Punkt für Punkt abchecken und beantworten, sonst können wir dir keinen support bieten.

LG Hübie
 
AW: Selbstgebautes PC stürtzt ab mit Bluescreen NICHT GELÖST!

Ich habe alle deine schritte befolgt und sogar Netzteil und Graka prüfen lassen und die graka hatte probleme aber der NT hatte erfolg.
ich bekam ein ersatz GTX 470 aber nun weiss ich dass es nicht an der Graka liegt weil der Problem weiterhin besteht.
Brauchst du den Minidump noch weil ich hab schon ausgewertet und ober gepostet.
Update ist sehr unregemässig ich habe dann win neu installiert und update deaktiviert.
Kannst du mir sagen wo eventuell eine Seite gibt wo alle updates downloaden kann. Das warten nervt
Was kann ich symbols-paths machen??
Intel Watchdog Treiber Link ist nicht aktiv
Danke vorraus
 
Zuletzt bearbeitet:
AW: Selbstgebautes PC stürtzt ab mit Bluescreen NICHT GELÖST!

Wie du den Symbol Path korrekt einstellst kannst du in dem Link in meiner Signatur nachlesen (mit der Methode werden nur die benötigten Symbole heruntergeladen - eine Internetverbindung ist während des Debuggens notwendig).

Dann auf Files -> Symbol File Path und in das kleine Fenster folgenden Befehl eingeben (paste&copy):

"SRV*C:\symbols*http://msdl.microsoft.com/download/symbols" (ohne "")
Zum Vergrößern anklicken....
 
AW: Selbstgebautes PC stürtzt ab mit Bluescreen NICHT GELÖST!

sorry wenn ich so dumm frage aber ich finde den Link nicht kannst du mir ihn hier posten
 
Du musst dich einloggen oder registrieren, um hier zu antworten.

Ähnliche Themen

C
PC crasht willkürlich
Antworten
3
Aufrufe
1K
Cody1805
C
H
Bluescreens wiederkehrend
Antworten
4
Aufrufe
1K
hunterseyes
H
D
Zufällige Bluescreens
Antworten
0
Aufrufe
1K
drsommer1
D
S
Bluescreen beim Spielen
Antworten
13
Aufrufe
4K
Mitchpuken
M
T
DirectX Error und anschließender Bluescreen (Win7)
Antworten
7
Aufrufe
1K
Thanatously
T
Oben Unten
Zurück