Question about CPU Temp and SSD Health - Hardware & Software

So couple months ago I purchased two mushkin chronos (value) 120gb ssd drives. After about a month one of drives had an issue where it's serial number has been overwritten. Then about a month later both drives died on same day. Then I asked for replacement and to send in one 240. Which I got and used for about a month until smart errors started to show up. RMA again and received 240 Chronos Deluxe this time. About a month in (i think) and drive is crashing when copying files, or downloading, or doing lots of operations to ssd. Then system starts to freeze. First of all the access to ssd is blocked like it's not connected at all. Whatever is in background (movie, music, game) runs fine until it has to access the drive (i assume) and hangs, until whole system just crashes with bsod. Recent crash [QUOTE]On Sun 12/23/2012 8:30:58 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: Unknown (0x00000000) Bugcheck code: 0xF4 (0x3, 0xFFFFFA800DA1AB30, 0xFFFFFA800DA1AE10, 0xFFFFF800031EADB0) Error: CRITICAL_OBJECT_TERMINATION 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. A third party driver was identified as the probable root cause of this system error. Google query: CRITICAL_OBJECT_TERMINATION[/QUOTE] Switched ssd into laptop and same happened. However this has been issue while connected to sata3 port only, but now, after i connected it to sata2 and used for couple weeks, same thing happens... Could it be that my system is causing the ssd drives to fail? I have replaced both cpu and mobo but no luck. Could it be that mushkin is bad about making SSD? COuple years ago I purchased their Mushkin black line memory, 12GB (3x4GB) 1600Mhz for $700 a kit... And I got 2 kits, $1500 for 24gb of ram. Wow [IMG]http://s7.postimage.org/gg5razld7/Capture.png[/IMG] Note: other kit was purchased locally So that's one thing. Hopefully I will get another replacement or maybe just buy samsung 840. Anyway onto CPU temp. I short, one core is always under-heating. Running prime with three cores at 60 degrees and one at 50. Should I be worried? I replaced the thermal paste with arctic silver 5 after using whatever was on from factory. Also AS5 dropped temps from 65 to 60 :thumbsup: [IMG]http://s7.postimage.org/6ugs8fjl7/Capture2.png[/IMG]

Could you PM your latest minidump (C:\Windows\Minidump) to me so I can open it up and do a stack trace? That bug check isn't useful at all, maybe throwing some symbols at it might show something. You could try a basic memory test just to rule that out (mdsched.exe in run, or shove any reasonably recent linux live CD in and run memtestx86). I'd be hesitant to say it was the SSD causing CRITICAL_OBJECT_TERMINATION, but you never know. Also if that core is stable I wouldn't be too concerned, try an intelburntest on burn-in mode for half an hour or so and if it still isn't responding then you might want to consider re-pasting if you're paranoid. Could just be a faulty temperature probe though.

Here's your debug dump: [code]16.2: kd:x86> .load wow64exts 16.2: kd:x86> !analyze -v The context is partially valid. Only x86 user-mode context is available. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_OBJECT_TERMINATION (f4) A process or thread crucial to system operation has unexpectedly exited or been terminated. Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no longer function. Arguments: Arg1: 0000000000000003, Process Arg2: fffffa800ddb2b30, Terminating object Arg3: fffffa800ddb2e10, Process image file name Arg4: fffff8000338cdb0, Explanatory message (ascii) Debugging Details: ------------------ <Failed to Read Entire ETW Buffer (expected 1704, read 0)> PROCESS_OBJECT: fffffa800ddb2b30 IMAGE_NAME: wininit.exe DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: wininit FAULTING_MODULE: 0000000000000000 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0xF4 CURRENT_IRQL: 0 STACK_TEXT: 00000000 00000000 00000000 00000000 00000000 0x0 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0xF4_IMAGE_wininit.exe BUCKET_ID: X64_0xF4_IMAGE_wininit.exe Followup: MachineOwner ---------[/code] From what I can find on the internets, I'd say it's the SSD at fault. Try doing a Secure Erase using the instructions [url=http://www.corsair.com/applicationnote/secure-erase]here[/url] (don't worry, it's not just corsair SSD's, it's all flavours) which will reset the NAND to factory and then retry installing Windows. If you get the same bugcheck, it's most likely a duff NAND and it's happy clappy returns time.

7[QUOTE=leach139;38996582]Here's your debug dump: [code]16.2: kd:x86> .load wow64exts 16.2: kd:x86> !analyze -v The context is partially valid. Only x86 user-mode context is available. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_OBJECT_TERMINATION (f4) A process or thread crucial to system operation has unexpectedly exited or been terminated. Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no longer function. Arguments: Arg1: 0000000000000003, Process Arg2: fffffa800ddb2b30, Terminating object Arg3: fffffa800ddb2e10, Process image file name Arg4: fffff8000338cdb0, Explanatory message (ascii) Debugging Details: ------------------ <Failed to Read Entire ETW Buffer (expected 1704, read 0)> PROCESS_OBJECT: fffffa800ddb2b30 IMAGE_NAME: wininit.exe DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: wininit FAULTING_MODULE: 0000000000000000 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0xF4 CURRENT_IRQL: 0 STACK_TEXT: 00000000 00000000 00000000 00000000 00000000 0x0 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0xF4_IMAGE_wininit.exe BUCKET_ID: X64_0xF4_IMAGE_wininit.exe Followup: MachineOwner ---------[/code] From what I can find on the internets, I'd say it's the SSD at fault. Try doing a Secure Erase using the instructions [url=http://www.corsair.com/applicationnote/secure-erase]here[/url] (don't worry, it's not just corsair SSD's, it's all flavours) which will reset the NAND to factory and then retry installing Windows. If you get the same bugcheck, it's most likely a duff NAND and it's happy clappy returns time.[/QUOTE] Awesome. May I include dump info in the rma? I have been told by RMA guy to do secure erase. I did try secure erase but it looked like it didnt do anything because process was completed in a second. Mushkin been pretty cool about RMA.

[QUOTE=P1X3;38997016]I did try secure erase but it looked like it didnt do anything because process was completed in a second.[/QUOTE] Feel free to use that dump in any RMA. Bear in mind that Secure Erase doesn't actually take long as it's just an instruction to the SSD's controller to wipe the NAND (which is done in milliseconds)