Hello ossao.
Make it sure that your Corsair Force 3 SSD is running with the up-to-date firmware.
Do some Disc check for your 1 TB Seagate Barracuda. (Specs says about a 500 GB WD HDD, but not finding it in verification other than a Corsier force 3, Seagate Barracuda and a Kingston 4 GB pen drive).
- Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
Uninstall Marvell 91xx SATA 6G Controller in Control Panel > Programs and features. Then
free up the leftover following
Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.
- Right click on "my computer" icon and click "manage" on the context menu.
- It will open the "computer management" window.
- Select "Device Manager" in the left pane, It will list all the existing devices up.
- Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
- Select one Intel device item under it, right click, uninstall.
- Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
- Now restart the computer. At restart, windows will auto configure the appropriate native system driver.
Update JMicron JMB36X Controller. It appears to be very old.
Code:
fffff880`00fdc000 fffff880`00ffd000 jraid (deferred)
Image path: \SystemRoot\system32\DRIVERS\jraid.sys
Image name: jraid.sys
Timestamp: Tue Aug 10 14:58:44 2010 (4C611BCC)
CheckSum: 0001F0A6
ImageSize: 00021000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Get the updates from ftp://driver.jmicron.com.tw/SATA_Controller/Windows/
Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :
- Double click to open it.
- Click this button only:
- If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.
Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.
- Click on the Start button
- Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
- Select the “Startup” tab.
- Deselect all items other than the antivirus.
- Apply > OK
- Accept then restart.
And, which antivirus do you use?
Let us know the results.
________________________________________________________________________________
BSOD ANALYSIS:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa800a688b30, fffffa800a688e10, fffff80002fce350}
----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
Followup: MachineOwner
---------
7: 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: fffffa800a688b30, Terminating object
Arg3: fffffa800a688e10, Process image file name
Arg4: fffff80002fce350, Explanatory message (ascii)
Debugging Details:
------------------
----- ETW minidump data unavailable-----
PROCESS_OBJECT: fffffa800a688b30
IMAGE_NAME: csrss.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: csrss
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: csrss.exe
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.
BUGCHECK_STR: 0xF4_IOERR
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`03d60e38 fffff800`03055d22 : 00000000`000000f4 00000000`00000003 fffffa80`0a688b30 fffffa80`0a688e10 : nt!KeBugCheckEx
fffff880`03d60e40 fffff800`0300208b : ffffffff`ffffffff fffffa80`0a689a20 fffffa80`0a688b30 fffffa80`0a688b30 : nt!PspCatchCriticalBreak+0x92
fffff880`03d60e80 fffff800`02f82144 : ffffffff`ffffffff 00000000`00000001 fffffa80`0a688b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`03d60ed0 fffff800`02cc6e93 : fffffa80`0a688b30 fffff800`c0000006 fffffa80`0a689a20 00000000`003a0d40 : nt!NtTerminateProcess+0xf4
fffff880`03d60f50 fffff800`02cc3450 : fffff800`02d1281f fffff880`03d61a38 fffff880`03d61790 fffff880`03d61ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`03d610e8 fffff800`02d1281f : fffff880`03d61a38 fffff880`03d61790 fffff880`03d61ae0 00000000`003a1a50 : nt!KiServiceLinkage
fffff880`03d610f0 fffff800`02cc7282 : fffff880`03d61a38 00000000`000713b8 fffff880`03d61ae0 00000000`003a1528 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`03d61900 fffff800`02cc5dfa : 00000000`00000000 00000000`772d8af4 00000000`77a48d01 00000000`000713b8 : nt!KiExceptionDispatch+0xc2
fffff880`03d61ae0 00000000`77949c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`003a1470 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77949c12
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe
BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe
Followup: MachineOwner
---------