Alles klar, danke dir. Ich werd die Kabel alle überprüfen und mich nochmals melden falls ich weitere Schirmchen bekomme.
Bis dahin
Alles klar, danke dir. Ich werd die Kabel alle überprüfen und mich nochmals melden falls ich weitere Schirmchen bekomme.
Bis dahin
Gerade hatte ich wieder einen Bluescreen: Ich spielte Diablo, hörte nebenbei wieder Musik über YouTube.
Die Musik ging aus (nur chrome), ich wechselte von D3 auf chrome (alttab) und sah in dem YT tab das ladesymbol. Ich klickte einmal irgendwo hin bei Chrome, nach einigen Sekunden hieß es das chrome krine rückmeldung gäbe. Wieder einige Sekunden später war mein Rechner abgeschmiert.
WhoCrashed hat dazu leider keinen Report gefunden; auch stand in diesem BSOD auch nicht mehr "partmgr".
Auf C & D gab es keine Probleme.
Nachdem ich den Rechner nun neu aufgesetzt habe hatte ich leider wieder einen BSOD:
[Bilddatei] File-Upload.net - IMAG0366.jpg
Der Bluescreen ist dahingehend interessant, dass es das erste mal passiert das "partmgr.sys" dort steht.
Vielleicht habt ihr ja eine Idee dazu, oder soll ich die Programme (WhoCrashed, PPFScanner) nochmals durchlaufen lassen?
Edit: es lief im Hintergrund wieder Chrome mit einem YT Tab offen. (nur für das Protokoll)
MfG
Alles klar, dann werde ich das mal in Angriff nehmen.
Bis dahin
Ayay das kann es freilich sein.
Da muss ich dann mal den Rechner neu aufsetzen. Anzumerken hab ich hier nur noch das ich die Hardware so länger habe als die Software (vor allem den Keygen) und schon damals Probleme hatte. Mag freilich daran liegen das Windows nicht ganz sauber aufgesetzt wurde.
Nun, du schreibst "partitionieren"; damit meinst du nicht formatieren? Ich hab zwar gehört das man bei SSD Platten formatieren vermeiden sollte, hab aber nicht ganz nachvollziehen können was passiert wenn doch.
Soweit danke für deine Hilfe
Einige Datein (Bilder, Word etc.) sowie meine Spiele, Musik und Filme.
Programme laufen eigentlich alle über C.
Wonach hälst du auf D ausschau?
Meistens kommen die BSODs wenn ich auch Chrome offen habe und dort auch einen Tab bei Youtube. Das ist das wo ich am häufigsten Musik höre.
Seltener benutze ich auch VLC, dort dann MP3's. Wobei ich nun nicht zun 100% behaupten, dass Chrome zu dem Zeitpunkt nicht auch aktiv war.
Allerdings hatte ich diese Probleme auch bei Opera(+Youtube).
Nun, dort wurde schon wieder etwas gefunden:
File-Upload.net - TDSSKiller.2.8.16.0_01.10.2013_20.38.19_log.txt
die SSD:
HD Tune: OCZ-SOLID3 Health
ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 92 92 50 107577416 Ok
(05) Reallocated Sector Count 100 100 3 0 Ok
(09) Power On Hours Count 95 95 0 4591 Ok
(0C) Power Cycle Count 98 98 0 2426 Ok
(AB) (unknown attribute) 0 0 0 0 Ok
(AC) (unknown attribute) 0 0 0 0 Ok
(AE) (unknown attribute) 0 0 0 193 Ok
(B1) (unknown attribute) 0 0 0 6 Ok
(B5) (unknown attribute) 0 0 0 0 Ok
(B6) (unknown attribute) 0 0 0 0 Ok
(BB) (unknown attribute) 100 100 0 0 Ok
(C2) Temperature 128 129 0 8454272 Ok
(C3) Hardware ECC Recovered 120 120 0 107577416 Ok
(C4) Reallocated Event Count 100 100 3 0 Ok
(C9) TA Counter Detected 120 120 0 107577416 Ok
(CC) Soft ECC Correction 120 120 0 107577416 Ok
(E6) GMR Head Amplitude 100 100 0 100 Ok
(E7) Temperature 100 100 10 0 Ok
(E9) (unknown attribute) 0 0 0 4712 Ok
(EA) (unknown attribute) 0 0 0 2966 Ok
(F1) (unknown attribute) 0 0 0 2966 Ok
(F2) (unknown attribute) 0 0 0 7124 Ok
Power On Time : 4591
Health Status : Ok
Die normale HDD:
HD Tune: WDC WD20EARS-00MVWB0 Health
ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 200 200 51 0 Ok
(03) Spin Up Time 253 170 21 991 Ok
(04) Start/Stop Count 97 97 0 3135 Ok
(05) Reallocated Sector Count 200 200 140 0 Ok
(07) Seek Error Rate 200 200 0 0 Ok
(09) Power On Hours Count 91 91 0 6627 Ok
(0A) Spin Retry Count 100 100 0 0 Ok
(0B) Calibration Retry Count 100 100 0 0 Ok
(0C) Power Cycle Count 98 98 0 2416 Ok
(C0) Power Off Retract Count 198 198 0 2101 Ok
(C1) Load Cycle Count 138 138 0 188190 Ok
(C2) Temperature 118 101 0 32 Ok
(C4) Reallocated Event Count 200 200 0 0 Ok
(C5) Current Pending Sector 200 200 0 0 Ok
(C6) Offline Uncorrectable 200 200 0 0 Ok
(C7) Ultra DMA CRC Error Count 200 200 0 0 Ok
(C8) Write Error Rate 200 200 0 0 Ok
Power On Time : 6627
Health Status : Ok
4 Sachen wurden gefunden, hier die Logdatei:
Link gelöscht.
So, hier sind die Datein die der Scan nun hervorgebracht hat. Ich hoffe es sind die richtigen, denn als er abgeschlossen wurde war ich gerade nicht da.
Links gelöscht.
Edit:
Auch wenn das Problem derzeit unter Software läuft (und es wahrscheinlich auch ist) habe ich vergessen zu erwähnen das ich Windows auf einer SSD Platte habe. Nur damit das erwähnt und gegebenenfalls berücksichtig wird.
Gruß
Vielen dank für das verschieben des Themas.
Dies ist das Ergebniss des Programms WhoCrashed:
System Information (local)
--------------------------------------------------------------------------------
computer name: SMITH
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8555470848 total
VM: 2147352576, free: 1917272064
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 28.09.2013 09:25:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092813-16567-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009F7BB30, 0xFFFFFA8009F7BE10, 0xFFFFF80003984350)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 29.08.2013 14:12:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082913-16723-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A4E5B30, 0xFFFFFA800A4E5E10, 0xFFFFF8000398E350)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 18.10.2012 16:04:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101812-15646-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009709B30, 0xFFFFFA8009709E10, 0xFFFFF8000378A510)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 27.08.2012 20:24:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082812-14211-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009666950, 0xFFFFFA8009666C30, 0xFFFFF800037C9510)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 17.07.2012 19:03:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071712-14102-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009C37060, 0xFFFFFA8009C37340, 0xFFFFF8000379D510)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 15.03.2012 11:12:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031512-14336-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80097109E0, 0xFFFFFA8009710CC0, 0xFFFFF800035978B0)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 24.12.2011 13:31:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122411-13837-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006E78B30, 0xFFFFFA8006E78E10, 0xFFFFF800035D48B0)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 09.11.2011 16:54:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110911-13962-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006D77580, 0xFFFFFA8006D77860, 0xFFFFF800035D38B0)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
8 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Alles anzeigen
[Kann jemand das Zitat als Spoiler tarnen, damit es kleiner ist?
]
Ich hoffe das euch dies weiter bringt ![]()
Danke und bis später
Tag,
ich bekomme seit sehr langer Zeit (>1 Jahr) regelmäßig BSODs, welche recht zufällig sind.
Auffallend ist das in der Regel davor irgendetwas mit dem Sound passiert: Musik hört auf zu spielen oder Anwendungen bleiben stehen und der Sound ebenjener befindet sich in einer Endlosschleife.
Ich habe das von Schwabenpfeil nahegelegte Programm PPF benutzt und die Dateien hier hochgeladen:
Links gelöscht.
Vielleicht könnt ihr mir ja dabei helfen, denn langsam artet es leider ein wenig aus.
Grüße