BSOD usually soon after start up error 0xf4

Anthimeria · 17 Feb 2015

Two weeks ago, I had to replace my HDD with my current Seagate one. Now, I've been having frequent BSODs for almost a week now very soon after start up and even once after being powered on for a while all with the error 0x000000F4. I've tried to troubleshoot it with the help of Google, but I haven't found anything that seems to help. I tried to uninstall things I thought could be causing an issue such as LogMeInHamachi and Avast AV, and today, I tried to run sfc and correct any problems there. The only supposed problem sfc found (Microsoft-Windows-WindowsUpdateClient-Aux) will not repair even in safe mode. I'm pretty stumped on what needs to be done. Help will be greatly appreciated. Thank you for your time.

Arc · 17 Feb 2015

Hi Anthimeria.

Test your HDD using Seatools. Take both the short generic test and the long generic test.

SeaTools for DOS and Windows - How to Use

Let us know the results.
____________________________________________

Code:

BugCheck F4, {3, fffffa8008d45b30, fffffa8008d45e10, fffff8000318f130}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

Followup: MachineOwner
---------

Anthimeria · 17 Feb 2015

I ran both tests and it passed both with no errors.

Arc · 18 Feb 2015

OK, then let us see any further crash dump. Further checks will be needed.

Anthimeria · 25 Feb 2015

I've uploaded two new dumps from yesterday. I hadn't used my computer since I posted here, but tried yesterday and got more.

Arc · 25 Feb 2015

The same issue is continuing.

Now, re-seat the sata and power.

Also, apply the SATA cable on any other SATA port on the motherboard. If possible, use a different SATA cable.

See how it goes.

Anthimeria · 06 Mar 2015

Did as you suggested and had no problems for a bit, but suddenly today while I was playing a game I got a new blue screen error. I've attached the new crash dump.

Arc · 07 Mar 2015

Code:

WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
3727 errors : !Ntfs (fffff880012fe002-fffff880012fefff)

Code:

ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

You sure you have done all that was suggested till now, and nothing changed ans Seatools did not catch any errors?

Crash dumps are steadily reporting disc errors, you can see.

In this case I will suggest you to install windows on any other HDD and see how it goes; provided you have already taken care of the SATA cables as you said.

The game that you were playing at that time was the wolf among us.

Anthimeria · 07 Mar 2015

Yes, I switched the cables on the hard drive and changed the spot the SATA cable was in. Seatools had said no errors were found on all the tests I was told to run, as I said.
I don't have any other HDDs to install windows on, would you suggest maybe returning this HDD?
Also, I really appreciate all the help so far. I've been pretty stumped on what to do.

Arc · 08 Mar 2015

Anthimeria said:

Yes, I switched the cables on the hard drive and changed the spot the SATA cable was in. Seatools had said no errors were found on all the tests I was told to run, as I said.
I don't have any other HDDs to install windows on, would you suggest maybe returning this HDD?
Also, I really appreciate all the help so far. I've been pretty stumped on what to do.

There is a little contradiction, as you can see.

The crash dumps are reporting HDD errors, but the disc checks are not. We already have taken the possible cares for the other things that may cause the issue.

One more thing may be there, a simple file system corruption on the HDD. A full format of the HDD a cure it.

Try to back up your documents etc in OneDrive or Google Drive. Then format the full HDD and install windows again.

If still the stop 0xF4 or 0x7A BSODs continue to occur, there will be no other way but not using the HDD.