Computer started to BSOD frequently but Randomly (0F4) no .dmp created

Starting today my laptop has been BSODing about 10 minutes after I log on normally. It doesn't seem to be the result of some program being run, as I only had Skype, Steam, and Google Chrome open each time and all of them were opened when I logged on, not when the BSOD occured. Also, I have followed the advice of solutions in many forums and question boards similar to this one, but to no avail. I have noticed that there are no new dump files in the Minidump folder since a few months ago, even though I have seen the BSOD about 10 times today. I have followed the instructions on how to configure dump settings already. Also, it seems that my computer is mostly fine in Safe Mode, which I am in now. However, sometimes it will freeze and lock up, where I can only turn it off by holding down the power button for a little while. Unfortunately, this is what occurs when I click the Upload File button in the Add Attachments screen. I will see if I can upload the zip file out of safe mode, as I should be able to do it in time before the BSOD. If this is the case, then my next post will have more info.

Any help is appreciated, and thank you.

EDIT: SF files below.
Actually, I've noticed that Safe Mode does not handle as well as my regular computer should. It is slower and freezes up more. I suppose that makes sense, BUT I have actually gotten about two BSODs in Safe Mode if I put it under a lot of pressure, it freezes up badly, and I leave it.

My computer freezes regardless of Safe Mode when I click "Choose File" in the Attachments screen, so I can't upload the SF .zip file. However, I got 1 dump file back after a BSOD, I think it was the one after I tried uploading an attachment under regular settings. I have some information on that. Also, I can simply copy/paste any info you need from the SF report to a reply in this thread, so let me know. Thanks!

EDIT: By power of flash drives and alternate computers, I have attached the SF zip file.

WhoCrashed

On Sat 11/30/2013 9:19:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\113013-27752-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80079A4B30, 0xFFFFFA80079A4E10, 0xFFFFF80003BDA7B0)
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.

Welcome to SF, 0bitasy0 :) .

You just recently started to get 0xF4 bug check codes, you had several (5) others spanning
from mid-June to early-September, the other two are 0xF4 which are usually attributed to storage issues.

Please test the HDD.

   Warning

The Following Method Should NOT Be Performed On An SSD!

Testing the HDD:

1. Perform a Disk Check | Disk Check- Scroll down to OPTION TWO of the tutorial and use the /R switch in the CHKDSK command | chkdsk C: /R.
2. Then Post the Disk Check results following | This Tutorial.
3. Once back in Windows, download Crystal Disk Info and post a screenshot (multiple shots if you have more than one drive).
4. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
5. If SeaTools for DOS is unable to recognize your HDD:
6. Visit HDDdiag and follow the instructions | Or follow the instructions below.

If SeaTools For DOS does not recognize the drive;
Boot into the BIOS using the *Fx key.
Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
Set it to IDE then save and exit usually by pressing the F10 key.
Now boot into SeaTools and it should detect the drives.
Start the Long Test and let it run.
Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
and change the SATA setting back to what it was in the first place.

• *Popular BIOS access keys.

Arc said:

Re-seat the sata and power.

Code:

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: fffffa80079b6b30, Terminating object
Arg3: fffffa80079b6e10, Process image file name
Arg4: fffff80003b887b0, Explanatory message (ascii)

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

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

PROCESS_OBJECT: fffffa80079b6b30

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.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`02a21e38 fffff800`03c11ab2 : 00000000`000000f4 00000000`00000003 fffffa80`079b6b30 fffffa80`079b6e10 : nt!KeBugCheckEx
fffff880`02a21e40 fffff800`03bbcabb : ffffffff`ffffffff fffffa80`085abb00 fffffa80`079b6b30 fffffa80`079b6b30 : nt!PspCatchCriticalBreak+0x92
fffff880`02a21e80 fffff800`03b3c674 : ffffffff`ffffffff 00000000`00000001 fffffa80`079b6b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`02a21ed0 fffff800`03882e53 : fffffa80`079b6b30 fffff800`c0000006 fffffa80`085abb00 00000000`02480e40 : nt!NtTerminateProcess+0xf4
fffff880`02a21f50 fffff800`0387f410 : fffff800`038ce82f fffff880`02a22a38 fffff880`02a22790 fffff880`02a22ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`02a220e8 fffff800`038ce82f : fffff880`02a22a38 fffff880`02a22790 fffff880`02a22ae0 00000000`02481b50 : nt!KiServiceLinkage
fffff880`02a220f0 fffff800`03883242 : fffff880`02a22a38 00000000`0000aab7 fffff880`02a22ae0 00000000`02481628 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`02a22900 fffff800`03881dba : 00000000`00000000 00000000`ff86f630 00000000`777e9c01 00000000`0000aab7 : nt!KiExceptionDispatch+0xc2
fffff880`02a22ae0 00000000`777e9c42 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`02481570 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777e9c42


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe

Followup: MachineOwner

Let us know the results :).

6 steps and I get stuck on #1...
But yeah I had to restart to run the disk check and I instinctively opened in safe mode with networking and it is stuck on the end of the list of Loading Windows Files. Is the check disk running or should I manually turn off and try running it under regular conditions?

EDIT: Nvm Got it to run, will continue and post results when done

Well it's technically only four .
Awaiting your update :) .

0bitasy0 said:

So after i think more than 24 hours of waiting, I come home to a good old BSOD. And now it started over. So.... It'll be awhile before I might get any results

I'm sorry I didn't understand.
What were you waiting for?

Ahh, thanks for clearing that up.

Skip the CHKDSK test for now.
Are you able to reach the desktop? If you are please post a screenshot of Crystal Disk Info (step #3).
And continue to step #4, testing the HDD with SeaTools for DOS.