BSOD almost every 5 minutes, error 0x00000f4

[infinis]

Past problem : My computer started giving me BSODs about a month ago. During that time, my computer would not even go past the windows logo before it gave me a BSOD. After tampering with the connections of my hard drives, it suddenly decided to work, so I didn't bother looking it up.

Current problem : My computer now gives me a BSOD every 5-10 minutes after booting it. It started yesterday when I was playing Diablo 3 when suddenly, my screen froze and a distorted BSOD popped up. I then restarted my computer and after around 5 minutes, many of my programs would close and a BSOD would pop up. I decided to give up for the night. This morning, I booted up my computer and the problem persists, same scenario, same behavior.

I entered all the information I could find on my computer's hardware before it blue screened again in my profile. Does anyone know how to fix this?
Thank you

 

[Boozad]

All of your dumps (bar the first two in the logs) are 0xF4 which is a Critical Object Termination. They all look as if they're blaming your hard drive.

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: fffffa8007e23320, Terminating object
Arg3: fffffa8007e23600, Process image file name
Arg4: fffff800033d0130, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----

KERNEL_LOG_FAILING_PROCESS:  

PROCESS_OBJECT: fffffa8007e23320

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

EXCEPTION_CODE: (NTSTATUS) [COLOR=Red]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.[/COLOR]

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

STACK_TEXT:  
fffff880`06994e38 fffff800`03458ee2 : 00000000`000000f4 00000000`00000003 fffffa80`07e23320 fffffa80`07e23600 : nt!KeBugCheckEx
fffff880`06994e40 fffff800`0340487b : ffffffff`ffffffff fffffa80`07e31340 fffffa80`07e23320 fffffa80`07e23320 : nt!PspCatchCriticalBreak+0x92
fffff880`06994e80 fffff800`03384e08 : ffffffff`ffffffff 00000000`00000001 fffffa80`07e23320 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17436
fffff880`06994ed0 fffff800`030c8153 : fffffa80`07e23320 fffff800`c0000006 fffffa80`07e31340 00000000`00b70d80 : nt!NtTerminateProcess+0xf4
fffff880`06994f50 fffff800`030c4710 : fffff800`0311478f fffff880`06995a38 fffff880`06995790 fffff880`06995ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`069950e8 fffff800`0311478f : fffff880`06995a38 fffff880`06995790 fffff880`06995ae0 00000000`76fa0794 : nt!KiServiceLinkage
fffff880`069950f0 fffff800`030c8542 : fffff880`06995a38 00000000`00bf0000 fffff880`06995ae0 00000000`76fadbb4 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`06995900 fffff800`030c70ba : 00000000`00000000 00000000`76fa0797 fffff880`06995b01 00000000`00bf0000 : nt!KiExceptionDispatch+0xc2
fffff880`06995ae0 00000000`76fd8f56 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00b714a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fd8f56


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  [COLOR=Red]X64_0xF4_IOERR_IMAGE_wininit.exe[/COLOR]

BUCKET_ID:  [COLOR=Red]X64_0xF4_IOERR_IMAGE_wininit.exe[/COLOR]

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xf4_ioerr_image_wininit.exe

FAILURE_ID_HASH:  {7e8d25f6-54c6-2456-f4df-269f2fd35200}

​

:ar: Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

:ar: Run chkdsk. http://www.sevenforums.com/tutorials/433-disk-check.html

:ar: Uninstall Alcohol 120%, a proven cause of BSODs.

1. Uninstall Alcohol 120%.
2. Download the SPTD standalone installer and perform the following steps.

• Double click the executable to open it.
• Click the button shown below.

   Information

If the button it is grayed out as shown in the image, there is no more SPTD installation on your system and you can just close the window.

Post back with the results.

 

[infinis]

Thanks for the reply.
Since I couldn't run my computer without getting a BSOD after a few minutes, I just switched the connections of my HDD and SSD and booted up my SDD as my primary (nothing has changed, only my connections). Surprisingly, it doesn't BSOD anymore.
I ran SeaTools and all 3 tests (Short drive self test, short generic and long generic) failed for my Samsung SSD 830 (where Windows is installed) and all of them passed for my other drive.
I then followed the rest of your instructions and uninstalled STPD.
Should I replace the SSD?

 

[Boozad]

No, those tests will show failures on an SSD as they're not designed for them. Test the system for stability for a day or two and report back, maybe a loose connection was causing the issue.

 

[infinis]

Alright, thank you. I'll report back in 2 days with some good news hopefully!

 

[infinis]

It seems like the blue screens have stopped for now. Thanks for the help!

 

[Boozad]

You're welcome, glad to hear you're BSOD free.