New SSD drive causes BSODs when PC is idle (have debug information)

Hey everyone!

So, I got a new SSD, corsair force 60GB if it matters, and I installed it, my problem is that when it's idle (cause it didn't happen when I was using it), it gets me a BSOD.
I'm almost positive it's the SSD, and it might be connected to a winint.exe process.

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Roy\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*D:\Symbols*[Linktomicrosoftsymbolserver-can'tpostlinks]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c5c000 PsLoadedModuleList = 0xfffff800`02e99e50
Debug session time: Sun Sep 12 09:31:08.450 2010 (UTC + 2:00)
System Uptime: 0 days 22:13:09.136
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8008f8bb30, fffffa8008f8be10, fffff80002fd75d0}

Probably caused by : hardware_disk

Followup: MachineOwner
---------

1: 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: fffffa8008f8bb30, Terminating object
Arg3: fffffa8008f8be10, Process image file name
Arg4: fffff80002fd75d0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8008f8bb30

IMAGE_NAME:  hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

EXCEPTION_RECORD:  fffff880038deb78 -- (.exr 0xfffff880038deb78)
ExceptionAddress: 00000000776a5ac5
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000ffcf3900
   Parameter[2]: 00000000c000000e
Inpage operation failed at 00000000ffcf3900, due to I/O error 00000000c000000e

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000ffcf3900

EXCEPTION_PARAMETER3:  00000000c000000e

IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

EXCEPTION_STR:  0xc0000006_c000000e

FAULTING_IP: 
+23a
00000000`776a5ac5 ??              ???

BUGCHECK_STR:  0xF4_IOERR_C000000E

FOLLOWUP_IP: 
+23a
00000000`ffcf3900 ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk

BUCKET_ID:  X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk

Followup: MachineOwner
---------

1: kd> lmvm hardware_disk
start             end                 module name
1: kd> !process fffffa8008f8bb30 3
PROCESS fffffa8008f8bb30
    SessionId: 0  Cid: 01d0    Peb: 7fffffdf000  ParentCid: 017c
    DirBase: 1234be000  ObjectTable: fffff8a0083a5310  HandleCount:  79.
    Image: wininit.exe
    VadRoot fffffa8008efa850 Vads 66 Clone 0 Private 419. Modified 13. Locked 2.
    DeviceMap fffff8a000008bb0
    Token                             fffff8a0040ed5c0
    ElapsedTime                       22:12:57.280
    UserTime                          00:00:00.000
    KernelTime                        00:00:00.000
    QuotaPoolUsage[PagedPool]         0
    QuotaPoolUsage[NonPagedPool]      0
    Working Set Sizes (now,min,max)  (1217, 50, 345) (4868KB, 200KB, 1380KB)
    PeakWorkingSetSize                1217
    VirtualSize                       48 Mb
    PeakVirtualSize                   52 Mb
    PageFaultCount                    1459
    MemoryPriority                    BACKGROUND
    BasePriority                      13
    CommitCharge                      520

        THREAD fffffa8008f8cb60  Cid 01d0.01d4  Teb: 000007fffffdd000 Win32Thread: fffff900c00e4c30 WAIT: (UserRequest) UserMode Non-Alertable
            fffffa8008ecad60  NotificationEvent

        THREAD fffffa8008fc9b60  Cid 01d0.01fc  Teb: 000007fffffd5000 Win32Thread: 0000000000000000 WAIT: (UserRequest) UserMode Alertable
            fffffa8008fc8880  SynchronizationTimer
            fffffa8008fc89f0  SynchronizationTimer
            fffffa8008fddb30  ProcessObject
            fffffa8008fdf910  ProcessObject
            fffffa8008fcaef0  SynchronizationTimer

        THREAD fffffa8008ffeb60  Cid 01d0.0238  Teb: 000007fffffd7000 Win32Thread: 0000000000000000 WAIT: (WrQueue) UserMode Alertable
            fffffa8008f8c880  QueueObject

        THREAD fffffa8009e03060  Cid 01d0.0e9c  Teb: 000007fffffdb000 Win32Thread: 0000000000000000 WAIT: (WrQueue) UserMode Alertable
            fffffa8008f8c880  QueueObject

        THREAD fffffa8009c18460  Cid 01d0.0484  Teb: 000007fffffd9000 Win32Thread: 0000000000000000 RUNNING on processor 1

it's really annoying and I would appreciate your help very much!
Thanks in advance!
 
Take it out

Shut down the computer, take out the drive, boot it back up. Do you get a bluescreen?
 
Back