Very random BSOD, 0xF4

Mackful · 21 May 2016

So yesterday, my PC gave me a BSOD twice within a few hours of each other. I've gotten blue screens very infrequently in the past and never thought much of it. Anyway, a friend recommended that I try using WhoCrashed to try and figure out whats causing it. I'll just copy and paste the analysis that WhoCrashed provided for both crashes. Note that my PC only blue screened twice, but there are 3 crash logs.

On Fri 5/20/2016 10:12:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052016-5257-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800F01FB30, 0xFFFFFA800F01FE10, 0xFFFFF800031C5270)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 5/21/2016 3:16:33 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800D811B30, 0xFFFFFA800D811E10, 0xFFFFF80003183270)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 5/21/2016 3:16:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052016-6255-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800D811B30, 0xFFFFFA800D811E10, 0xFFFFF80003183270)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

It states that it could be a thermal issue, but the blue screens happened when I was idling at the desktop, I also ran stress tests and monitored the temps so I know that's not it. I also updated my SSD to the latest firmware. I have my specs on my profile, and I've uploaded my bsod dump info. Thanks!

Arc · 24 May 2016

0xF4 is storage related issue, mostly. Please do two things:

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall the program 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.

Make it sure that your SSD is having the latest firmware. Samsung Magician will tell you about it.

Let us know the resulting situation.