Working in IT, I’ve come across number strange STOP errors in Windows that are only fixed by doing something ridiculously obscure! Recently, I came across another STOP error that is very obscure, but pretty easy to fix! Well, at least it was easy to fix for me.
Here’s the error on the associated blue screen when I am working on the troubled computer:
Stop: 0x000000F4 (0×00000000003, 0xFFFFFADF50, 0xFFFFFADF50EC32A8, etc)
To fix this, I tried all kinds of things before calling Dell support, such as replacing the memory, switching out video cards, replacing the motherboard, running all kinds of hardware and memory diagnostic tools, etc, etc. Sadly, nothing worked!
We knew it was not a software issue because we have a bunch of identical machines, all with the same software configuration. Hence, we had to make a call to good ol Dell technical support.
Note that recently we had installed a new hard drive into the computer and starting getting these blue screen errors a few days later. While talking with the Dell rep, he had me do all kinds of stuff!
Firstly, I had to un-plug the computer, and pull out the monitor, keyboard and mouse cords. After that, we removed all the memory, plugged everything back in and rebooted. Same blue screen!
We then took out and replaced other parts of the computer, rebooting and unplugging the computer each time we took something out or put something back in.
Finally, I took out the CMOS battery (the small round battery on your motherboard), rebooted, then re-installed it, and rebooted the machine again. It fixed the problem! So this STOP error is related to either a low CMOS battery or simply having to take it out and put it back in.
Next time you add some new hardware to your computer, you have get this error because the components do not get configured properly during the install. Removing and reinstalling ensures that the device can reconfigure correctly with the new hardware.
Other strange errors I’ve gotten include The location that you specified does not contain stored information relating to the File and Settings Transfer Wizard.
[...] device! If not, post a comment and I’ll try to help! Also, check out my previous post on how to fix Stop:0×000000F4 or what to do if you are getting a hal.dll is missing error. Enjoy! Enjoyed this post? Subscribe [...]
You work in IT and yet you think it is necessary to remove the cmos battery to reset the settings? Duh.
ppehrson… um, yeah, it is necessary sometimes. all IT people know this that at one point or another removing and reseating the cmos battery solves odd issues by clearing all bits in memory that maybe don't clear on shutdown. the board is constatly running even when the pc is unplugged, but not if you remove the cmos battery. duh.
I had exactly the same blue screen. My computer started to reboot randomly every 1 or 2 days then 1 or 2 times a day until I couldn't boot windows. I didn't make any hardware or software changes for months and didn't believe it could be hardware. First I thought it might be a temperature or overclocking issue but the temperature was always cool since I had 2 fans and verified they worked OK. Also, I had the same overclocked configuration for more than a year I that I use to do some very intensive processing, but never had any problem with this before.
I bought a brand new HD and installed windows from scratch but the same problem came up only a couple hours later.
Trying to fix the problem, I worked on it for almost an entire week using HD tools or chkdsk in vain. After a lot of research I found this page. :) Then, I disabled automatic reboot on system error and saw that blue screen. Eventually, I saw the Windows system event logs and saw a lot NTFS errors accessing a specific drive. Then, I knew it had to be the CMOS or the SATA Cable. I followed these steps:
- Disconnect/Connect CMOS battery and reconfigure BIOS settings again based on defaults
- Replace "ALL" SATA Cables and reconnect all drives
- Run HD Diagnostic tools (Western Digital Data LifeGuard Diagnostics) to fix already corrupted data on HD.
Finally, the 500 GB HD I thought I was going to throw in the garbage is working perfectly and without damaged sectors.
I am getting the same error and have tried everything I can think of, including the battery and even replacing the battery with a new one, but no luck yet.
Further info: The system runs after I'm in windows for about 3 minutes, then out of nowhere, with no open programs, it will crash. Safe mode seems to be fine, but many features to find the problem are disabled and I can't find anything in the system logs. The dump files it says the data went to during the crash are missing.
I'm getting this error every time I boot my Dell laptop, Inspiron 1564 – Bug check code: 0x000000f4 and 0x1000007e alternately every time I start windows.
It restarts a few times with this error and then finally runs. My laptop is still under warranty only 30 days left, and I'm out of the country.
Any suggestions?
Oh, by the way, this started happening suddenly one day when I started the system. No new programs or hardware installed.
Thank you very much!!! I wouldn't bother to contact Dell and it had been bugging me. I tried the fix and walla!! The blue screen disappeared and Windows booted smoothly like before!!!
I had the same problem with a desktop computer that had not had any changes to its configuration for years. I checked the hard disk for errors using CHKDSK, to make sure there was nothing wrong with the OS. It passed. Next, I ran a system diagnostic to check hardware, (memory, Hard-disk, etc.), and it checked out OK. I didn't reset the BIOS or remove the CMOS battery as they checked out earlier with the diagnostic test. The problem? I found that the data cable, (it was a SATA hard-disk), was either loose or faulty. Having replaced it and made sure it was connected firmly and squarely (sometimes, they can work a little loose and be pulled sideways), everything worked fine.
I’ve had this same issue caused by bad display drivers and by conflicting display drivers like swapping from an ATI to Intel graphics chip-set on a laptop.