Windows 7: BSOD a few minutes after every boot, error 0x000000F4

Hi all. I built my computer about a month ago. Worked fine for a while, and then it started to hang then crash about 4 or 5 minutes after every boot. This happens even in safe mode. I did a clean installation of Windows 7. Everything was fine for about two weeks... and now the hanging+crashing is back. This also happens in safe mode.

Its not an overheating issue so far as I can tell - CPU temp is around 41C. It happens even if no applications are open.


[I have run the file collection app, zipped the resulting file, but cannot get it to upload. The upload utility hangs indefinitely at "Uploading Files - Please wait".]


Thanks in advance!

Can you try uploading the .zip file on a different computer? We really need the crash reports in order to provide troubleshooting steps.

Also, what antivirus/firewall combination are you running?

Got it! Here's the .zip file.

I'm just using the firewall in my router... as for Antivirus, I'm using Microsoft Security Essentials.

Unfortunately, the zip file seems to be corrupted and I cannot extract it...

I asked about the antivirus/firewall mostly in relation to not being able to upload. Surprising those would cause an issue unless the router firewall is blocking it...

Hmmmm... I tried running the file collection app again. Is this a viable .zip (attached)?

I was able to open it, but no .dmp files are included.


Problem Devices:
Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION
A windows system process was terminated unexpectedly. Possible causes are hard disk errors... System file corruption... Viruses... Lack of Windows updates... Drivers...


Start by checking data corruption:

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
  
  
• Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

Also, make sure your configuration is the same as OPTION ONE part 6. of Dump Files - Configure Windows to Create on BSOD and do not use CCleaner, Windows disk cleanup, etc. to clean the hard disk after crashes.

I've enabled the small minidumps, but the BSOD screen hangs where it says it is creating a dump. I have never seen anything in the windows/minidump folder.

I will take a swing at running these diagnostics, but the problem is that I only have about 4-5 minutes of use on the machine before it hangs then crashes. For example, on the sfc/scannow, I get 31% complete and then the system goes into hang-crash mode. I'll see what I can do....

You may run SFC offline: SFC /SCANNOW : Run in Command Prompt at Boot


You can also do a disk check offline. Use Advanced Boot Options to select Repair Your Computer and get to the System Recovery Options. Then select the command prompt. Do the following:

chkdsk /r c:
chkdsk /r d:
chkdsk /r e:
chkdsk /r f:

.etc until you get the message that the volume could not be opened for direct access. For any drives that do not give the message:
"Windows has checked the file system and found no problems"
run chkdsk again as above. In other words, if it says:
"Windows has made corrections to the file system"
after running the disk check, run the disk check again.

I realize you may only have one disk show up in Windows explorer, but you may have more than one disk through recovery options. This is because the system creates a hidden boot partition (which will be C: in recovery), you may have a recovery partition for your PC that is hidden (which will be D: in recovery), and you will have your primary Windows partition (which may be E: in recovery). A custom PC will likely have at least C: and D: to scan.

Ok - I tried to run sfc/scannow offline (booted from Windows 7 installation disk, selected repair system, clicked command prompt). Ran "sfc /scannow /offbooddir=d:\ /offwindir=d:\windows". Initially said "Beginning system scan. This process will take some time." Halted after a few minutes and said "Windows Resource Protection could not perform the requested operation." I immediately retried the command, and got same message.

Tried running "chkdsk /r d:", etc., and repeatedly got "Cannot open volume for direct access."

You received "cannot open volume for direct access" for c: - f:? That is odd if you did...

When SFC returns that error, the only way to fix it is either a repair install (which does not always fix it) or a clean install/restore factory system image. A repair install seems to be out of the question given your five minute rule... Sorry to say, but you should backup any important data and clean install Windows 7.