Tom's Guide | Tom's Hardware | Tom's Games | PC Safety Suite
![]() |
![]() |
![]() |
Comment:
Hello,
In an effort to speed up my girlfriend's computer and perform routine maintenence, I've run into a problem.
Initially, it started out with the computer making a loud, almost grinding-like noise while being on for a few hours. Girlfriend was worried about it, so she asked me what it might be. I initially thought it might be the hard drive, so I thought I'd back up all her data and try a reformat.
So, I tried the reformat initially and during the first reformat it did not recognize that the drive was there, saying that it did not detect a drive to install Windows on.
I waited a day and tried to fire up the Windows XP disk again, this time, the drive was detected. I continued with the installation, cleared the old partition, reformatted the drive with NTFS (Quick) setting, and let the installation proceed. As it reached the point in the installation in which it has the status bar stating that it is installing Network Components, about halfway into that, it gives me a stop error with the "0x000000F4 Memory Dump" and what not. Exact details can be replicated if necessary.
Also too, I noticed in the installation when you are prompted to enter a name for the system, only about half of the keys on the keyboard worked. I also had this problem when I tried to perform a chkdsk in the Windows repair console. I am totally at a loss, and I really hope this isn't some major repair as her desktop just took a hit as well.
Please help me! I am in EXTREMELY dire straits here.
Thanks in advance.
+1 | ![]() |
Maybe this will lead you in the right direction:
ASUS A8N32-SLI Deluxe
AMD Athlon X2 4800+
2GB RAM, X1900GT
2x37GB WD Raptors, RAID 1
1x250GB WD Storage
+1 | ![]() |
I tried that site and the information it has about the 0x000000F4 error is not even applicable. It's a laptop with one single hard drive, not a slave drive. It simply does not give me enough information. Thanks for the site though.
Any other suggestions?
+1 | ![]() |
You could read this, but I'm not sure how much help that will be.
If you're lucky, it's just a bad hard drive. (And by "bad," I mean "in pieces.") If not, the grinding was a fan, and the laptop overheated to the point of failure.
+1 | ![]() |
My only qualms against testing another hard drive are having to buy one. Should I try to attach an external drive and see if it will run off of that?
+1 | ![]() |
Windows (pre-Win2k3sp1) won't boot from USB; something about a conflict between the BIOS and USB drivers. But if you have something that'll get the job done, don't let me stop you.
Question: If you remove the HDD and shake it, does it make a sound?
+1 | ![]() |
this utility will clear the drive of all foramtting, partioning etc. When installing undertake a Full Format in NTFS
+1 | ![]() |
Sometimes Stop errors and memory dumps can be just because the ram module contacts are not getting a good connection - this worked for me when I got a simlar error:
See response 2 in this - try cleaning the contacts on the ram modules.
http://www.computing.net/hardware/w...You don't need to install or connect another hard drive in order to test the one you suspect is giving you problems.
See the latter part of response 1 in this:
http://www.computing.net/windows95/...Grinding like noises are almost always coming from the failing bearings on a fan, or from a fan that is extremely filthy or rubbing on something else, not a hard drive. It may be coming from the cpu fan, the PS fan(s), or the case fan(s) if you have them.
+1 | ![]() |
Thanks for all the advice. I'll perform all these tests and get back with you guys.
Thanks again.
+1 | ![]() |
I let memtest86 run overnight with finding no errors and when I ended it and let the computer sit I got another stop error as Windows XP tried to load to continue the setup.
"0x000000ED UNMOUNTABLE_BOOT_VOLUME"
So I attempted to install Windows 2000 on the machine to see if I would have any other result and it said the partition was "Unformatted or Damaged."
I undocked the laptop in attempt to find where the hard drive was located, and being an Inspiron 300m, it is so small.
Would I have good reason to believe the hard drive is bad in the machine?
+1 | ![]() |
I'm being lead to believe, that with all of the issues about the disk showing as damaged and what not, that the hard drive is bad in the machine. I would like to solidify that as the ruling before a purchase a new hard drive and that is not the issue. Don't want to get stuck eating a cost that isn't going to resolve the issue.
Also... what special hard drive, if any, will I need with the Inspiron 300m?
+1 | ![]() |
You only need to let memtest86 or similar make a complete test of the ram and pass that a couple of times - any more than that is a waste of time. If it does occaisionally produce errors when you let it run longer, you probably do have a poor connnection in the slots and cleaning the ram contacts will almost always cure that.
Your UNMOUNTABLE_BOOT_VOLUME error could be because of the hard drive being defective or just because the data on it is corrupted, and/or the partition structure data is corrupted.
See the second reference in response 7.
If there is nothing physically wrong with the drive or it's logic board, you can simply delete the corrupted partition(s) and make it(them_ again at the beginning of Windows Setup.It could also be because of a poor data cable connection. Make sure all the connectors on the data cable are fully seated onto what they plug into, there are no gaps beween the connectors and the data cable where they connect to the data cable, and that there are no damaged wires/insulation at the edges of the cable at each connector or under the cable clamp there. If in doubt, try another data cable.
+1 | ![]() |
There's not many cables in an Inspiron. For the most part, just the monitor ribbon (upper left, I believe), the keyboard ribbon (dead center of keyboard to upper center, I think), and the speaker cables. In any case, you're taking the laptop apart to reach it, whereas the hard drive should be removable once you take the cover over its bay off.
The grinding noise you heard: If it sounded like metal on metal and your laptop no longer makes the sound, then what you heard was the platters being shredded by the remains of your heads. If it was more of a makin' margaritas sound, and your laptop still occasionally gets noisy, then it's probably the fan.
+1 | ![]() |
I have an AMD Athlon 64 X2 6000+
2 GB of Corsar XMS Ram
Windows XP Pro SP2
NVidia GForce 7950 GT video card
BFG 650 Watt Power Supply
4 Hard Drives
System HD. 320 GB Western D. 7200 RPM
10,000 RPM Raptor for Media
500 GB WD
500 GB WD
==============Every now and then, sometimes every 5 minutes, and sometimes not for days, when I edit video or rendering video out of my editing system, Play PC games, I will get a Blue Screen of DEATH that has the 0x000000F4 Stop Error
Memory Dumb and Crash.I have replaced the RAM, the power Supply, reformated and installed Windows.
My new ASUS Crosshair MB did fry 4 FireWire devices. So would I be correct to assume it's caused from a bad motherboard?
Help!
I just built this system new and it's driving me crazy!
+1 | ![]() |
CrazyAce
This web site gets a large number of posts, especially in the General Hardware and XP forums, and any post more than a few days old is not nearly as likely to be responded to except by people who still happen to have the subject in their MyComputing.Net list.
If you want more people to see and possibly respond to your post, make a new post with your own subject title at the bottom of any forum list on this site. Copy the URL of this subject if you like and place that in your new post if you want to refer to it.
......A common mistake people make when they build a new system is to install ram in the wrong slots - e.g. dual channel ram must be installed in specific slots, usually in matched pairs you buy at the same time that are the same size - see your mboard manual.
Another common mistake people make when they build a new system is to buy ram or use used ram that isn't compatible with their mboard - it has to be compatible with the mboard, particularly it's main chipset, or it won't work properly.
Go to the Corsair web site, and using your mboard make and model, look up which Corsair modules are listed for your mboard. If the ID strings on the modules you have installed are not on that list, there is no way of telling whether it is compatible and it's a crap shoot whether they will work properly.Another problem you can have even if the ram is compatible or new is the ram may have a poor connection in it's slots.
It is COMMON for you to experience memory dumps if this is the case, and if you have a large amount of ram you may not have a problem until you are using a lot of the ram to do something.
See response 2 in this - try cleaning the contacts on the ram modules, and making sure they are properly seated in their slots:
http://www.computing.net/hardware/w...Contary to popular belief, bad ram is extremely RARE! If you test your ram with a program or utility such as memtest86, do that AFTER trying cleaning the contacts on it and making sure it is properly seated, or any errors found may be invalid. If you DO get errors after doing those things, it is much more likely the ram is incompatible with your mboard than it is bad.
There is no need to run a ram test for more than a couple of complete passes."My new ASUS Crosshair MB did fry 4 FireWire devices."
That can be because.....
- you have connected a firewire port (ports) that is (are) not built into the mboard edge to the wrong header(s) on the mboard.
See the fifth paragraph in response 3 in this:
http://www.computing.net/hardware/w...
Same thing, except you might have connected a firewire port to a USB header, and you plugged in a firewire device.
- the original PS was producing way too much voltage, probably +5v.
Faulty power supplies are common.
Check both your PSs.
See response 4 in this:
http://www.computing.net/hardware/w...
- you don't have anything connected to at least one device connected to your computer that protects it from voltage surges or spikes and you experienced a power surge or spike, or the mboard was exposed to a static electricity discharge. That includes everything connected to your computer that connects to AC, and your cable that connects you to the internet, and your telephone line if you are also using that for a dial-up modem. E.g. Have there been any power failures or lightning storms in your area since the devices last worked?
Lightning can damage anything connected even if everything is protected. If there is an led on a protection device that tells you whether the protection is wiorking, it may or may not show something is wrong, but if it does you have experienced a power surge or spike, whether you were aware of it or not.
Also, ATX mboards are always powered in some places as long as the AC power is live to the PS/mboard, even if the computer isn't turned on. If you don't disconnect the AC to your computer whenever you are fidlling with connections or components inside the case, you can damage anything connected to the mboard.
![]() |
Gateway EV 500 Monitor
|
Faulty Wireless
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.