John said:
Here's the latest..
The problem still is that the computer will run normally for a period,
then "stall" and not espond to either Mouse or Keyboard. By pulling the
Power Plug and then reconnecting and restarting right away, it will
again run normally for a period of time. AVG will provide a pop-up
Threat Alert for a Trojan Horse Generic4.TAB detected in the "smss.exe"
file. If I click "Ignore", the computer may continue to run. I have made
online downloads where the computer ran for over an hour without
stalling/freezing.
The "Beast" is a Presario 5000 with a 900 MHz AMD Athlon CPU, 256 Mb
RAM, 30 Gb Quantum Fireball HD, Windows 2000 Pro SP4 with ALL the
upgrades, 56K PCTEL Platinum v.90 Compaq modem, SMC 10/100 Compaq LAN
card, gForce nVidia Compaq Video card, CDROM, CD-RW, 3-5" 1.44Mb FD.
Installed s/w includes... AVG 7.5 Anti-Virus, MS Office 2000, SpyBot
S&D, Ad-Aware, and some lesser applications.
I have spent the best part of yesterday and this morning playing with
the computer and have tried a number of things to no avail. Here are
some of the things I did, that made no difference to the problem:
[1] Ran a complete Anti-Virus scan using AVG 7.5 with latest
updates...it found nothing....made no improvement.
[2] Ran SpyBot S&D new update install and it picked up 12
items...removed them and rebooted....made no improvement.
[3] Ran new instal and updaatel of Ad-Aware and it detected 56 Cokies
items which I deleted...made no difference
[4] I replaced the2 256Mb RAM sticks with 2 new known good ones....made
no difference, still had the Freeze condition.
[5] Removed 2 USB Flash Drives [that both share IRQ 11] I had installed
and that made no difference as I still got a Freeze.
[6] I have rechecked and installed ALL the Microsoft Win2K
Updates....all 65 of them and it made no difference afterward...still
got the Freezes.
[7] I ran the defrag [even tho it didn't really need Defrag] and after
restart, that made no difference as a stall happened about 20 minutes
later.
In GOOGLE checking the "smss.exe". I found that a problem was a sign of
a Trojan infection. Said that the SMSS.EXE file should be located in the
C:\WINNT\system32\config folder...and if not, that was a sign of the
Trojan problem. I have not found a "fix" to correct that problem and any
help or suggestions are ost welcome and appreciated.
Sorry for the long post....TIA....John
So with that processor, it probably isn't based on a slot 1 Intel processor
I notice in the Crucial.com memory list, there are many sub-models of
Presario 5000.
What I would do, seeing as you could potentially be facing two problems
at the same time, is boot Knoppix (knopper.net) or Ubuntu (ubuntu.com)
Linux LiveCDs. These are versions of Linux, where you don't need to install
anything on disk. You can even leave your hard drive in the computer while
testing (if it is NTFS formatted, then it probably won't be mounted in
Linux automatically - NTFS capability exists, but if available in a
distro, may be read only).
http://www.knopper.net/knoppix-info/index-en.html
"What are the minimum system requirements?
32 MB of RAM for text mode, at least 96 MB for graphics mode with KDE
(at least 128 MB of RAM is recommended to use the various office products)"
Both of those distros are a 700MB download. You need a CD burning program
that can take an ISO9660 image and burn it to a CD. The first time I did
it, I actually had to purchase a new burner, because the archaic one I
had previously, wouldn't even do 700MB. I used the Nero that was bundled
with the new burner, to prepare the CD.
Once you boot from the CD, and the Linux desktop appears, you can use
Firefox (browser) and go to mersenne.org and find the Linux version of
Prime95. Download the executable package to your home directory.
Then run Prime95, to see if there is a processor or memory
stability problem. (The nice thing about Linux, is you can run multiple
copies of Prime95 if you want, as long as each copy has its own directory
to play in.) You download each time you boot into Linux, because if using
a LiveCD, there may not be any permanent file space to save stuff.
Prime95 may be too big to keep on a floppy (although I've put other
test programs on a floppy, for testing via this method).
So Linux can be used as an independent verification of a hardware problem.
For example, on my 440BX box, I was having problems with graphics freezing
when more than 512MB of memory was present. I thought the problem was
with Windows, until one day on a lark, I booted the Linux CD. Within
10 seconds or so, Linux froze too. Which told me there was a problem
with the hardware (as both OSes were doing it, and there would be no
virus present in the Linux bootup). If I only installed 2x256MB on
that machine, it was as stable as a rock (I could run Prime95 for
16 hours). The instant I used 3x256MB or 4x256MB, it would freeze
in no more than a minute or two after the desktop appeared.
So the only potential limitation with a technique like that, is the
minimum amount of memory that will work with those boot discs. It
would seem you meet the minimum, but I've never tested on a
machine with less than 512MB.
Paul