Bluescreen Problem (1-2 täglich) ggf. SSD

evilfler

Enthusiast
Thread Starter
Mitglied seit
15.08.2010
Beiträge
183
Hallo zusammen,

ich habe seit ein paar Monaten eine SSD und nun fangen die Bluescreens an. Keine Ahnung, ob es wirklich daran liegt, aber ich poste mal am besten kurz was bei den Dumps rauskam (whocrashed).
Noch zu erwähnen ist vielleicht, dass ich aktuelle Treiber + Firmware für die SSD habe.


Code:
On Wed 30.05.2012 12:37:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053012-8221-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009880920, 0xFFFFFA8009880C00, 0xFFFFF8000238E510)
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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Mon 28.05.2012 15:01:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052812-8080-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A304060, 0xFFFFFA800A304340, 0xFFFFF800033CA510)
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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Fri 25.05.2012 15:36:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052512-8002-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8007AE5A30, 0xFFFFFA8007AE5D10, 0xFFFFF8000339C510)
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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Fri 25.05.2012 07:28:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052512-8034-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80080F38D0, 0xFFFFFA80080F3BB0, 0xFFFFF8000337E510)
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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Thu 24.05.2012 15:16:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052412-7924-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800766B970, 0xFFFFFA800766BC50, 0xFFFFF80003390510)
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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Tue 15.05.2012 08:25:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051512-8034-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80080D2060, 0xFFFFFA80080D2340, 0xFFFFF80003395510)
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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Mon 14.05.2012 15:53:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051412-8112-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800818CB30, 0xFFFFFA800818CE10, 0xFFFFF8000339B510)
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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Mon 14.05.2012 11:17:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051412-8034-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80075DD4B0, 0xFFFFFA80075DD790, 0xFFFFF80003396510)
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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


Windbg:

Code:
Debugging Details:
------------------


OVERLAPPED_MODULE:  dump_iaStor

PROCESS_OBJECT:  fffffa8009880920

IMAGE_NAME:  

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME:  

FAULTING_MODULE: 0000000000000000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xF4

PROCESS_NAME:  wininit.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002416882 to fffff8000208f1c0

STACK_TEXT:  
fffff880`0791fe38 fffff800`02416882 : 00000000`000000f4 00000000`00000003 fffffa80`09880920 fffffa80`09880c00 : nt!KeBugCheckEx
fffff880`0791fe40 fffff800`023c2e8b : ffffffff`ffffffff fffffa80`09f54a50 fffffa80`09880920 fffffa80`09880920 : nt!PspCatchCriticalBreak+0x92
fffff880`0791fe80 fffff800`02341f74 : ffffffff`ffffffff 00000000`00000001 fffffa80`09880920 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`0791fed0 fffff800`0208e453 : fffffa80`09880920 fffff800`c0000005 fffffa80`09f54a50 00000000`00f70880 : nt!NtTerminateProcess+0xf4
fffff880`0791ff50 fffff800`0208aa0f : fffff800`020d9eaf fffff880`07920a38 fffff880`07920790 fffff880`07920ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`079200e8 fffff800`020d9eaf : fffff880`07920a38 fffff880`07920790 fffff880`07920ae0 00000000`77c19c12 : nt!KiIdleLoop+0x15f
fffff880`079200f0 fffff800`0208e842 : fffff880`07920a38 00000000`00000000 fffff880`07920ae0 00000000`00f710e8 : nt! ?? ::FNODOBFM::`string'+0x48e34
fffff880`07920900 fffff800`0208d3ba : 00000000`00000001 00000000`00f70f98 00000000`77c08f01 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`07920ae0 00000000`77c19ac6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00f70fa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c19ac6


FOLLOWUP_NAME:  MachineOwner

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  X64_0xF4_IMAGE__

BUCKET_ID:  X64_0xF4_IMAGE__

Followup: MachineOwner


Für eine paar Ideen und Hilfe wäre ich euch sehr dankbar.



Gruß
evilfler
 
Zuletzt bearbeitet:
Wenn Du diese Anzeige nicht sehen willst, registriere Dich und/oder logge Dich ein.
Bitte poste einmal die Smartwerte Deiner SSD (z. B. mit AIDA: AIDA64 | PC Benchmark | System Diagnostics | Network Inventory . oder Crystal Disk Info: Crystal Dew World) - ohne diese Info ist das Ganze leider reines "Kaffeesud" lesen. Falls hier keine Fehler erkennbar sind würde ich als nächsten Schritt den Arbeitsspeicher testen (z. B. mit MEMTEST). Kann aber auch sein, dass nur die ntoskrnl.exe Datei aus welchem Grund auch immer defekt ist.

l. G.
 
Zuletzt bearbeitet:
Hallo,

erstmal danke für die Hilfe. Den Memtest habe ich schon gemacht. Dabei gab es keinerlei Fehler/Probleme.

Crystal Disk Info sagt folgendes:

Code:
----------------------------------------------------------------------------
CrystalDiskInfo 4.6.2 (C) 2008-2012 hiyohiyo
                                Crystal Dew World : http://crystalmark.info/
----------------------------------------------------------------------------

    OS : Windows 7 Professional SP1 [6.1 Build 7601] (x64)
  Date : 2012/05/30 20:59:28

-- Controller Map ----------------------------------------------------------
 + Intel(R) Desktop/Workstation/Server Express Chipset SATA AHCI Controller [ATA]
   - OCZ-VERTEX3
   - ST3500410SV

-- Disk List ---------------------------------------------------------------
 (1) OCZ-VERTEX3 : 60.0 GB [0/0/0, pd1] - sf
 (2) ST3500410SV : 500.1 GB [1/0/1, pd1]

----------------------------------------------------------------------------
 (1) OCZ-VERTEX3
----------------------------------------------------------------------------
           Model : OCZ-VERTEX3
        Firmware : 2.22
   Serial Number : OCZ-E09AP3O6O0TSK839
       Disk Size : 60.0 GB (8.4/60.0/60.0)
     Buffer Size : Unbekannt
     Queue Depth : 32
    # of Sectors : 117231408
   Rotation Rate : ---- (SSD)
       Interface : Serial ATA
   Major Version : ATA8-ACS
   Minor Version : ACS-2 Revision 3
   Transfer Mode : SATA/600
  Power On Hours : 2541 Std.
  Power On Count : 44 mal
      Host Reads : 1343 GB
     Host Writes : 665 GB
     Temparature : 30 C (86 F)
   Health Status : Gut (100 %)
        Features : S.M.A.R.T., APM, 48bit LBA, NCQ, TRIM
       APM Level : 00FEh [ON]
       AAM Level : ----

-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr Raw Values (7) Attribute Name
01 105 105 _50 00000000A2EF84 Lesefehlerrate (roh)
05 100 100 __3 00000000000000 Ausrangierte Blöcke
09 __0 __0 __0 2C9052000009ED Eingeschaltete Stunden
0C 100 100 __0 0000000000002C Anzahl der Einschaltungen
AB __0 __0 __0 00000000000000 Programmfehler
AC __0 __0 __0 00000000000000 Löschfehler
AE __0 __0 __0 0000000000000D Unerwarteter Stromausfall
B1 __0 __0 __0 00000000000001 Abnutzungsbereichsdelta
B5 __0 __0 __0 00000000000000 Programmfehler
B6 __0 __0 __0 00000000000000 Löschfehler
BB 100 100 __0 00000000000000 Gemeldete unkorrigierbare Fehler
C2 _30 _30 __0 00001E001E001E Temperatur
C3 120 120 __0 00000000A2EF84 ECC On-the-fly Anzahl
C4 100 100 __3 00000000000000 Wiederzuweisungsereignisse
C9 120 120 __0 00000000A2EF84 Unkorrigierbare Software Lesefehler
CC 120 120 __0 00000000A2EF84 Software ECC Korrektur
E6 100 100 __0 00000000000064 Status der Lebensdauerkurve
E7 100 100 _10 00000000000000 SSD verbleibende Lebensdauer
E9 __0 __0 __0 000000000002C8 Verkäuferspezifisch
EA __0 __0 __0 00000000000299 Verkäuferspezifisch
F1 __0 __0 __0 00000000000299 Lebenszeit-Schreibvorgänge vom Host
F2 __0 __0 __0 0000000000053F Lebenszeit-Lesevorgänge vom Host

-- IDENTIFY_DEVICE ---------------------------------------------------------
        0    1    2    3    4    5    6    7    8    9
000: 0C5A 3FFF C837 0010 0000 003F 003F 0000 0000 0000
010: 4F43 5A2D 4530 3941 5033 4F30 4F30 5453 4B38 3339
020: 0000 0000 0004 322E 3232 2020 2020 4F43 5A2D 5645
030: 5254 4558 3320 2020 2020 2020 2020 2020 2020 2020
040: 2020 2020 2020 2020 2020 2020 2020 8010 4000 2F00
050: 4000 0200 0200 0007 3FFF 003F 003F FC10 00FB 0110
060: CF30 06FC 0000 0007 0003 0078 0078 0078 0078 4200
070: 0000 0000 0000 0000 0000 C70E C70E 0006 004C 0044
080: 01FC 0110 746B 7409 6163 B409 B409 6163 407F 0001
090: 0000 00FE FFFE 0000 0000 0000 0000 0000 0000 0000
100: CF30 06FC 0000 0000 0000 4000 4000 0000 5E83 A97F
110: 8857 FA5A 0000 0000 0000 0000 0000 0000 0000 401A
120: 4018 0000 0000 0000 0000 0000 0000 0000 0001 0000
130: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
140: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
150: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
160: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001
170: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
180: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
190: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
200: 0000 0000 0000 0000 0000 0021 0021 0000 0000 4000
210: 0000 0000 0100 0000 0000 0000 0000 0001 0000 0000
220: 0000 0000 103F 0000 0000 0000 0000 0000 0000 0000
230: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
240: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
250: 0000 0000 0000 0000 0000 A1A5


Seht ihr/siehst du hier was außergewöhnliches?


Danke und Gruß
evilfler
 
Die Stop 0xF4 Fehler riechen schon verdächtig nach einem Problem mit der SSD (Sandforce Controller Bug).
Hättest du denn noch eine freie HDD, auf die das System geklont werden könnte? Sollte das (geklonte) System auf der HDD dann keine Stop 0xF4 Fehler mehr hervorbringen, wäre die Sache klar.
 
Danke für die Hilfe. Ich werd das bei Gelegenheit mal testen. Falls das der Fall sein sollte und ich noch Garantie habe, kann ich die Festplatte dann einschicken?
Ich gehe davon aus, dass dieses Problem ja nicht anders zu lösen ist.


Gruß
evilfler
 
Das Problem konnte/kann vereinzelt durch Firmware Update behoben werden. Da aber bereits die aktuellste Firmware auf der SSD liegt, wird das Problem nicht anders als über eine Reklamation zu lösen sein. Und ja, wenn es an dem Bug liegt und du noch Garantie hast, kannst du die SSD einschicken.
 
Hardwareluxx setzt keine externen Werbe- und Tracking-Cookies ein. Auf unserer Webseite finden Sie nur noch Cookies nach berechtigtem Interesse (Art. 6 Abs. 1 Satz 1 lit. f DSGVO) oder eigene funktionelle Cookies. Durch die Nutzung unserer Webseite erklären Sie sich damit einverstanden, dass wir diese Cookies setzen. Mehr Informationen und Möglichkeiten zur Einstellung unserer Cookies finden Sie in unserer Datenschutzerklärung.


Zurück
Oben Unten refresh