Tell me more ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I have updated the question with sections, so that people won't find it difficult to read.

Basic System Information

Let me give a basic introduction on my system. I have a system of following configuration:

  • Processor: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz 3.40GHz
  • RAM: Corsair Vengeance - 4GB Single Module DDR3 Memory Kit (CMZ4GX3M1A1600C9) x 2
  • OS: Windows 7 Ultimate, SP1 Build 7601
  • HDD: 1 TB Seagate 7200 RPM

The Problem

It was working fine for about an year. Yesterday I planned to increase my RAM to 16 GB by putting another set of two Corsair Vengeance - 4GB Single Module DDR3 Memory Kit (CMZ4GX3M1A1600C9).

I got it from an authorized reseller and also, the RAM was fitted by a service engineer only. After the RAM was fit (all the four), the system failed to start, with an error code of 0x000000f4. The complete information of it is:

Problem signature:
  Problem Event Name:   BlueScreen
  OS Version:   6.1.7601.2.1.0.256.1
  Locale ID:    16393

Additional information about the problem:
  BCCode:   f4
  BCP1: 0000000000000003
  BCP2: FFFFFA8008A39060
  BCP3: FFFFFA8008A39340
  BCP4: FFFFF800037C8510
  OS Version:   6_1_7601
  Service Pack: 1_0
  Product:  256_1

Files that help describe the problem:
  C:\Windows\Minidump\093012-13041-01.dmp
  C:\Users\Praveen Kumar\AppData\Local\Temp\WER-30716-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Another Problem

We first thought that it was the RAM, which caused the issue. So I returned the RAMs and now my computer configuration is exactly how it was the previous day. But, following the removal of the RAM, I also had several crashes after that. One suspicious thing was with an error code c0000134:

STOP: c0000135 The program can’t start because %hs is missing from your computer
. Try resintalling the program to fix this problem.

After reading contents from this, this and this, which were never my case, they didn't help me. But I didn't receive any more STOP c0000134 messages. But this 0x000000f4 keeps on coming.

I am writing from the same system and it allows me to work for say, half an hour max. Then I hear a device disconnect sound, the one you hear in Windows 7, when a USB Mass Storage Device is plugged out.

Immediately following that, my screen goes blank and I get 0x000000f4 blue screen. Okay, now I am really concerned about my Hard Disk data, but I have no clue if there is a problem with the HDD.

My Question

What all files do I need to submit for your reference? Can this issue be fixed? I am getting more time if I remove my RAM, clean it and then put it back. Weird! Hope I have given the necessary information to help you guys. Thanks in advance.

Minidumps

I have uploaded all the Minidump DMP files from C:\Windows\Minidump folder here: http://www.praveen-kumar.com/Minidumps.zip

Let me know if you face any issues in accessing it. Will be able to share elsewhere.

Updates

30-Sep-2012 10:15 AM IST: When I keep the system cover opened, pressed the HDD Cable well, it is allowing me to be on for about half an hour, I guess? Also, I feel that the CPU fan speed is kind of slow. It rotates at around 900 RPM, but the CPU Temperature is not more than 70° C.

30-Sep-2012 10:30 AM IST: My Modem (Beetel 220BX ADSL2+ Router) failed. I have no idea how it is related to this issue, but I thought that I need to document this too. I really have a bad day here.

30-Sep-2012 11:00 AM IST: System still running fine, with the cabinet cover open, now for about an hour.

30-Sep-2012 12:00 PM IST: I shut down the system and closed the cabinet. Started the system, and it hung after giving the password. After a few minutes, got the same 0x000000f4 error. So, while it is in the upright position, fixed the Hard Disk cable and now it is booting fine. Waiting for more observations and answers.

share|improve this question

closed as too localized by techie007, Indrek, 8088, Randolph West, ChrisF Sep 30 '12 at 20:42

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, see the FAQ.

2 Answers

0x000000F4 stop codes are (almost always) related to hard drive controller failure. Either your hard drive, or your hard drive controller, is failing.

To me this is further evidenced by the system finding that "%hs is missing from your computer", which is referring to a missing file.

Backup all your data as soon as possible. Do disk checks (OS file system and manufacturer's utilities) and figure out if anything is broken. Attempt a full format and a full reinstall with current drivers. If all goes well restore your data and programs.

If all doesn't go well, then start replacing parts based on further observations.

share|improve this answer
Omg this is kind of serious. But yeah, now what I have observed was, keeping the cabinet open and removing and reinserting the HDD Cable, I am able to work on this for about an hour till now. :) – Praveen Kumar Sep 30 '12 at 5:31
System still running fine, with the cabinet cover open, now for about an hour. – Praveen Kumar Sep 30 '12 at 5:34

After getting panic'd by those things shown on the Internet, finally I was able to solve the problem. Didn't know which step solved, but these are what I did:

  1. Opened the Cabinet.
  2. Removed the RAM, HDD, and ODD.
  3. Cleaned all the connection points.
  4. Removed the CMOS Battery, checked for its life by connecting to a small bulb. (Good)
  5. Inserted the CMOS Battery.
  6. Replaced the RAM, HDD, and ODD.
  7. Started the system again.
  8. Again there was the 0x000000f4 Error.
  9. When it was on, I opened the cabinet and pressed the SATA Ports hard.
  10. Started the system again.

There was no problem till now. Guess the problem was because of a loose connection of SATA Connector. Finally I got it done.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.