Discussion Locked

constant hang and swiss cheese HDD

0 helpful
35 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a friend who is having troubles with his computer.
1. the computer stats....
Windows 98 Second edition, computer is an AuthenicAMD with a Duron processor, 256 MB RAM, 65% free, 32-bit file system and is configured for optimal performance.
2. The problem ...
The computer will randomly hang, CTRL +ALT + DEL will not work when this happens. A hard shut down and scandisk upon reboot is necessary. Also, even after defragging, the drive will look like it is in desperate need of a defrag again after it crashes.

3.When it began ....
He had the computer rebuilt, new mobo, HDD and more ram. It has been sent back to the techies who did the work and they say they can't find any problem. He has had someone else look at it for him and same result, no problems could be found even after thorough testing.

Apparently after the system had been rebuilt, the techies had installe windows Millennium Edition, but a lot of his software he uses would not run in WIN ME, so they reformatted and reinstalled win98se.

Any ideas about this?

35 replies

by hinrgman

It is hard to say, there are so many things that can be the cause of hanging. Is the machine on a network? do you use it on the internet?

First thing I would do is repartition the hard disk, then reformat it and then reinstall the os of your choice, I would run it with the minimum of software applications first, if it runs ok then i would install any other applications one at a time and let each run to see if there is a problem,.

Another area i would look at is the compatibility of the existing hardware that was installed on the new MOBO. Also the memory - is it compatible is it a single module or are there 2 or more?

by daz'n'ash

Thanks for the reply. The computer has been formatted and reformatted in a process of emlimination by doing as you suggested, one program at a time. The memory is SD Ram, but my suspicion is they could have mixed PC 100 and PC 133 together, I know from personal experience that some mobos just don't like that.

by thechas

I would start by manually setting the CPU bus speed and multiplier in BIOS settings.

I have seen a number of "strange" problems with socket A systems that are resolved by manually setting the CPU clock.
This most often happens when the MB is using SDRAM, and the CPU is 1GHz or faster.
While the BIOS detects the CPU correctly, it often sets the clock speed to 1/2 rated speed.
For whatever reason, AMD CPUs don't like to be underclocked.

Next, are all the latest drivers installed?
The chipset drivers for the motherboard, and the video card driver are the most common causes of Windows hanging.

As answer #1 stated, it may be a hardware incompatability with the motherboard.
Try moving the modem and other plug-in cards to different slots.
Also, disable any hardware that is not being used (COMM ports, IR ports, etc) to free up system resources.

I further recommend that the drive be setup with a seperate partition for virtual memory (swap file).
This will prevent the swiss cheese effect when the system crashes.

There is a good article on partitioning stratagy at www.aumha.org
While some will argue that a seperate partition can result in slower virtual memory speed, I opt for stability and simplicity.

Chas

by daz'n'ash

Sorry Chas to reject your answer. We have checked the CPU settings and everything appears normal. All hardware is new. Could it be possible that an IRQ setting is listed same for more than one device? If you have any other ideas, pleasedo post them. Thanks again.

by timthetoolman

Hi,

...and even before that, I'd surf all the manufacturer's websites for each card in the machine... video card, soundcard, BIOS for the motherboard, modem (if he has one) and anything else...

...and download the latest versions of the drivers for each. Its possible the techies didn't put on the correct drivers. They may simply have used the ones off the CDs which in my experience only "get you going" and often aren't stable.

Cheers,
Tim.

by daz'n'ash

Thank you for trying. I have already suggested this to him and after doing so, same problem remains. Please feel free to post more ideas if you have any.

by jimjennings

Try disabling the power saver settings in the BIOS and in windows. These can cause problems like yours if not properly configured.

by shanghai sam

Thanks for your reply, but this has already been tried, sorry I forgot to mention that. Feel free to post another answer if you think of anything that has not already been tried as listed in added comments to the question.

by timthetoolman

Hi,

If the drive looks like it definitely needs a defrag even after defragging, then I'd expect him to have only a little disk space left ?

Is it possible he's trying to write a large file to disk when it crashes ? He may not even be doing it intentionally. It could be a temp file or something.

I've never run out of disk space in Win98 so I haven't seen exactly what it does, but knowing 98, I wouldn't be surprised if it crashed. At least sometimes.

Cheers,
Tim.

by daz'n'ash

Thanks again Tim, but no, he says he still has plenty of free space on his drive. Keep trying though :)

by shanghai sam

Hi,

When you say configured for "optimal performance" do you mean set that way in the BIOS?

Many BIOS's allow you to specify an "optimal performance" setting which in practice means tightening up on all the wait states in the motherboard.

States like... (From my motherboard)

"SDRAM 1T Command

This item controls the SDRAM command rate. Selecting Enabled allows SDRAM signal controller to run at 1T (T=clock cycles) rate. Selecting Disabled makes SDRAM signal controller run at 2T rate. 1I is faster than 2T. The default value is Disabled."

There are other settings too. If this is what you mean by "optimal performance", then I suggest running with more conservative values.

...and to save on time and rejection messages....
Next suggestion : Download and install Sisoft's Sandra. Its available from here...

http://www.sisoftware.demon.co.uk/sandra/

(remove spaces from the above URL)

Then use that to stress test the machine. You will be able to stress test individual components such as memory, video, disk... and you may be able to make the machine crash during a particular test.

That will help to narrow it down.

Cheers,
Tim.

by daz'n'ash

Thanks for your reply, but after trying your suggestions, nothing there that will tell us any faults. Any other ideas, please post them. Thanks.

by daz'n'ash

I forgot to mention that he has run the msconfig and disabled all that does not need to start when windows starts. Also have moved PCI cards around to different slots and reinstalled with all the latest drivers.

by daz'n'ash

Okay, also have disabled power options. Has it set to always on, standby mode disabled, montior turn itself off after 30 minutes inactivity, hard disks turn off after 1 hour of inactivity.

by a. square

Can you try running without the case cover on it? It may be possible that the system's building up too much heat causing the erratic behavior...

by daz'n'ash

Thanks for your reply, but after trying your suggestion, still have the same problem. I appreciate your effort though. Keep trying though.

by thechas

Just to double check the CPU clock speed setting.

For a SDRAM equipped Socket A:
FSB = 100MHz
Multiplier set as needed to acheive rated speed.
Memory clock; either FSB (100MHz) or FSB + PCI (133MHz)

The BIOS does display the correct speed at boot, but often sets the multiplier assuming a 200MHz FSB.

Of course, it is possible that you have a bad Windows install, or a bad hard drive.

Have you tried another hard drive in the system?
For that matter, is the hard drive an ATA66, and the MB an ATA100 or 133?

Perhaps, the ATA/UDMA mode is set wrong, and the motherboard is sending data to the hard drive faster than it can handle it.
Or, the 80 pin IDE cable is bad.

Chas

by daz'n'ash

Thanks very much for taking the time to answer Chas. We have checked all of these and everything seems to be correctly set. I wish I could give away thse points to someone, I truly hate rejecting answers. If you have any more ideas, please post them..

by maxwell edison

During shutdown, data from the cache is written to the hard disk for storage until the computer is turned on again. During a typical shutdown process, any data written just before shutdown may still reside on the hard disk's hardware cache. Modern IDE hard drives typically store disk writes in a hardware cache (temporary memory) and write the data to the hard disk later.

This may be what you are experiencing.

This issue affects Windows 98, Second Edition (SE) and Windows Millennium Edition (Windows Me) customers, and Microsoft offers an update until the industry can address the issue.

See this link for the whole explanation, download link, and other related links.

http://www.microsoft.com/windows98/downloads/contents/WUCritical/q273017/Default.asp

(REMOVE SPACES from the pasted URL.)

Maxwell

by daz'n'ash

Thanks for your answer Maxwell. We have tried this and still the problem remains. If you have any otehr ideas, please post them. I really hate having to reject answers.

by shanghai sam

Okay, I have heard that the windows refresh rate can be adjusted. Is it actually a good idea to do this? Is it even safe to do? Could this be the cuase of the problem?

by stephen.berry

Please don't take offense, but he's not placing this PC in direct sunlight or beside other electrical equipment such as a tv or any magnatized objects. Just a thought.

Personally, the techies that did the installation need to see it happen. After that they need to replace the installed components to make sure it's not defective. It's their responsibility not his to fix the issue, legally and morally.

by daz'n'ash

I have asked him and no he has nothing magnetic or electrical close to it nor does he have it in direct sunlight, has plenty of ventilation and have even run it without the case on it to see how it runs, no change. So overheating is not anissue. O and no offense taken, I appreciate your input. If you have any other ideas feel free to post them, I do hate rejecting answers.

by daz'n'ash

Any other ideas out there? I will keep adding points until we get a satisfactory answer. I appreciate all the input so far, some unrated answers are still being tested.

by thechas

With all that has been done and tried, you are left with the potential of a hardware problem.

I suspect either the CPU, or the motherboard itself.

I have also seen strange symptoms when the 2 DIMMs were not matched.

I even had a system where the power supply connector had a little bit of corrosion on 1 pin, and had similar symptoms.

If I had the system, I would try the hard drive in another similar system to verify the drive, drivers, and windows install.

Then, start swapping hardware until the bad part was located.

Chas

by daz'n'ash

Well Chas, I truly appreciate your effort in trying to help with this. I believe the one last thing left proved to be the trouble, that is the power supply. Although new, seems that he got a couple of problematic ones. He has tried 2 so far and both gave varying degrees of the same problem. Again, thanks for your helop.

by ron

Replace the Power Supply already and give me my points..;)

Hehe, seriously though, you should try replacing the power supply. I've had alot of systems behave after swapping out the PSU.

To fix the Swiss Cheese drive, specify a tiny amount of swap space. The smallest possible.
Reboot to Windows and run Defrag, twice.
Make sure you have as much contiguous freespace as possible.
Go and set your Swap space to something reasonable. 500-800MB on a 256MB RAM system should do fine.
This has the affect of locking down 1 single, solid piece of HDD real estate for swap. This makes for faster swaps and less random fragmentation when the system crashes. All of the fragmentation is confined to the pre-defined area and gets cleaned up when you reboot.

Ron Velotta

by daz'n'ash

Thanks for your input and your humour is appreciated. The power supply was the last thing left to try, and having done this 2 times altready with new power supplies, bith proved to give the same problem. So far, power supply #3 is going strong with the problem recurring.

This discussion is closed to new replies.