BSOD With Intel 320 120gb SSD [ I've tried everything! Pics Included ]

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 20
    Windows 7 Home Premium 64bit
    Thread Starter
       #11

    Here's the logs from SF Diagnostic Tool!
      My Computer


  2. Posts : 20
    Windows 7 Home Premium 64bit
    Thread Starter
       #12

    Correct me if i'm wrong, but is the Intel SSD Firmware the problem? I'm not sure how to analyze the SF File.
      My Computer


  3. Posts : 20
    Windows 7 Home Premium 64bit
    Thread Starter
       #13

    Anyone? I'm sitting here waiting for someone to answer, because i dont know what to do.
      My Computer


  4. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #14

    You seem to have missed Post #9.Try that and see if it helps.
      My Computer


  5. Posts : 20
    Windows 7 Home Premium 64bit
    Thread Starter
       #15

    Golden said:
    You seem to have missed Post #9.Try that and see if it helps.
    I dont really see how that would help me when it's probably a driver issue and The answer is in the SF Log File? :)
      My Computer


  6. Posts : 15,026
    Windows 10 Home 64Bit
       #16

    TimPonken said:
    Golden said:
    You seem to have missed Post #9.Try that and see if it helps.
    I dont really see how that would help me when it's probably a driver issue and The answer is in the SF Log File? :)
    So you're trying to say that we're passing on wrong information to you?

    These are the output of your dumps:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck F4, {3, fffffa800676ab30, fffffa800676ae10, fffff80002b96db0}
    
    ----- ETW minidump data unavailable-----
    Probably caused by : wininit.exe
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: fffffa800676ab30, Terminating object
    Arg3: fffffa800676ae10, Process image file name
    Arg4: fffff80002b96db0, Explanatory message (ascii)
    
    Debugging Details:
    ------------------
    
    ----- ETW minidump data unavailable-----
    
    PROCESS_OBJECT: fffffa800676ab30
    
    IMAGE_NAME:  wininit.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: wininit
    
    FAULTING_MODULE: 0000000000000000 
    
    PROCESS_NAME:  wininit.exe
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    BUGCHECK_STR:  0xF4_c0000005
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`040b40e8 fffff800`02c1b982 : 00000000`000000f4 00000000`00000003 fffffa80`0676ab30 fffffa80`0676ae10 : nt!KeBugCheckEx
    fffff880`040b40f0 fffff800`02bc90ab : ffffffff`ffffffff fffffa80`07183610 fffffa80`0676ab30 fffffa80`0676ab30 : nt!PspCatchCriticalBreak+0x92
    fffff880`040b4130 fffff800`02b4c698 : ffffffff`ffffffff 00000000`00000001 fffffa80`0676ab30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17ad6
    fffff880`040b4180 fffff800`028928d3 : fffffa80`0676ab30 fffff800`c0000005 fffffa80`07183610 00000000`00a405c0 : nt!NtTerminateProcess+0xf4
    fffff880`040b4200 fffff800`0288ee70 : fffff800`028df11f fffff880`040b4b78 fffff880`040b48d0 fffff880`040b4c20 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`040b4398 fffff800`028df11f : fffff880`040b4b78 fffff880`040b48d0 fffff880`040b4c20 00000000`00a41e00 : nt!KiServiceLinkage
    fffff880`040b43a0 fffff800`02892cc2 : fffff880`040b4b78 00000000`00050a34 fffff880`040b4c20 00000000`00a418d8 : nt! ?? ::FNODOBFM::`string'+0x49974
    fffff880`040b4a40 fffff800`0289183a : 00000000`00000001 00000000`00a40b78 00000000`00a7e601 00000000`00050a34 : nt!KiExceptionDispatch+0xc2
    fffff880`040b4c20 00000000`76dd8e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    00000000`00a40b80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76dd8e3d
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0xF4_c0000005_IMAGE_wininit.exe
    
    BUCKET_ID:  X64_0xF4_c0000005_IMAGE_wininit.exe
    
    Followup: MachineOwner
    ---------
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck F4, {3, fffffa8006ecab30, fffffa8006ecae10, fffff80002b93db0}
    
    ----- ETW minidump data unavailable-----
    Probably caused by : csrss.exe
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: fffffa8006ecab30, Terminating object
    Arg3: fffffa8006ecae10, Process image file name
    Arg4: fffff80002b93db0, Explanatory message (ascii)
    
    Debugging Details:
    ------------------
    
    ----- ETW minidump data unavailable-----
    
    PROCESS_OBJECT: fffffa8006ecab30
    
    IMAGE_NAME:  csrss.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: csrss
    
    FAULTING_MODULE: 0000000000000000 
    
    PROCESS_NAME:  csrss.exe
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    BUGCHECK_STR:  0xF4_c0000005
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`04d5e0e8 fffff800`02c18982 : 00000000`000000f4 00000000`00000003 fffffa80`06ecab30 fffffa80`06ecae10 : nt!KeBugCheckEx
    fffff880`04d5e0f0 fffff800`02bc60ab : ffffffff`ffffffff fffffa80`07391950 fffffa80`06ecab30 fffffa80`06ecab30 : nt!PspCatchCriticalBreak+0x92
    fffff880`04d5e130 fffff800`02b49698 : ffffffff`ffffffff 00000000`00000001 fffffa80`06ecab30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17ad6
    fffff880`04d5e180 fffff800`0288f8d3 : fffffa80`06ecab30 fffff800`c0000005 fffffa80`07391950 00000000`009e0a20 : nt!NtTerminateProcess+0xf4
    fffff880`04d5e200 fffff800`0288be70 : fffff800`028dc11f fffff880`04d5eb78 fffff880`04d5e8d0 fffff880`04d5ec20 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`04d5e398 fffff800`028dc11f : fffff880`04d5eb78 fffff880`04d5e8d0 fffff880`04d5ec20 00000000`009e2260 : nt!KiServiceLinkage
    fffff880`04d5e3a0 fffff800`0288fcc2 : fffff880`04d5eb78 00000000`00013200 fffff880`04d5ec20 00000000`009e1d38 : nt! ?? ::FNODOBFM::`string'+0x49974
    fffff880`04d5ea40 fffff800`0288e83a : 00000000`00000001 00000000`009e0fd8 fffffa80`05f8cb01 00000000`00013200 : nt!KiExceptionDispatch+0xc2
    fffff880`04d5ec20 00000000`77298e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    00000000`009e0fe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77298e3d
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0xF4_c0000005_IMAGE_csrss.exe
    
    BUCKET_ID:  X64_0xF4_c0000005_IMAGE_csrss.exe
    
    Followup: MachineOwner
    ---------
    A bugcheck F4 is a driver related error. Driver as in Hard drive - a storage device.

    A list of things to do were recommended in many posts earlier, seeing that the latest firmware does not bring stability we also recommended switching the drive with a platter based HD.
      My Computer


  7. Posts : 20
    Windows 7 Home Premium 64bit
    Thread Starter
       #17

    Well I thought I would need new drivers or something. But okay I'll try the Power Cycle. so the SSD is freaking out on Its own.. Weird. Last time the problem was Usb 3.0 drivers.
      My Computer


  8. Posts : 20
    Windows 7 Home Premium 64bit
    Thread Starter
       #18

    Golden said:
    Hi,

    I would like to recommend you power cycle the SSD. I've seen a few cases where this solves apparently unsolvable BSOD.

    See this here for instructions.

    Regards,
    Golden
    Weirdly this worked. Well the computer hasn't shutdown yet! I'll wait a few hour and see if it's still working.

    At first I didn't believe that mumbo jumbo but it worked. I must ask, Golden, what is happening to the computer when you do this? Or exactly what did I do?

    Regards
      My Computer


  9. Posts : 20
    Windows 7 Home Premium 64bit
    Thread Starter
       #19

    BSOD now.. Hrrm same error.. F4

    And now it's the same as before.. BSOD every 10th second.
      My Computer


  10. Posts : 20
    Windows 7 Home Premium 64bit
    Thread Starter
       #20

    I've now tried another harddrive that's not an SSD. The computer works good. Maybe i should buy a new SSD?

    I've been looking on Samsung 840 120GB SSD it seems good and stable.
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:43.
Find Us