Problems with SM4

KwitkoKwitko Sheriff of Banning (Retired)By the thing near the stuff Icrontian
edited February 2004 in Hardware
Okay, first the stats:
XP1700+ @150x11
MSI KT3-Ultra2
256MB Crucial PC2700
300W PSU
1.6GB Western Digital HD
Windows 2000 stripped down as much as possible, SP4, AVG antivirus, ZoneAlarm firewall
Temps at 100% are about 38°C.
Machine is used for F@H and nothing else, as part of our SMx project for Team Short-Media.

The problem is that every 2-1/2 to 3 weeks the machine will freeze up. Everything runs smooth, no incomplete WUs, no other signs that things are going bad.

Before you ask, prime[suspect], I ran memtest86 and didn't find any errors. Also ran disk fitness test which passed with flying colors. The PSU is relatively new.

I'm at a loss as to what it could be. Funny thing is that it always seems to freeze after about 17 days of uptime.

Any ideas?

Comments

  • ThraxThrax 🐌 Austin, TX Icrontian
    edited February 2004
    memory! Swap it anyways. Memtest/docmem aren't 100% accurate. See what happens.
  • mmonninmmonnin Centreville, VA
    edited February 2004
    Seth are you apart of the FAH beta? I hear there is a fix for the SSE problem. Might want to try that. I have not read up on it so I dont know much else.
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited February 2004
    If the memory change doesn't help, can you run dr. watson and log what happens at the freeze? What about Windows Update? Have all patches been applied?

    Also, maybe back down on the OC a little (heresy, I know...).

    Guess I'll check back in 17 days and see if anything worked... :vimp:
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited February 2004
    Well, try what they said, and if not, try every once in a while shutting down client and saving the FAHlog.txt to something else (rename it). My XP client did this every so many LINES of text.

    Once I rebooted box, the FAHlog.txt file was VAPORWARE. Sicne I have doen this, ZERO issues with client per se. So, every few days I get a new FAHlog-Prev##.txt after a rename, and since I like them in reverse cronological order, I have FAHlog-Prev30 through FAHlog-PRev14 on box now, plus FAHlog.txt.

    NOTE, when I lost FAHlog.txt, times 4, I had not hardware errors I could find with diags, BUT every time the silly thing vaporized I had a journal error to clean up with CHKDSK. This might apply to 2000 as well as XP, but know it happens on XP without knowing WHY this version 4 client does this. AT a guess, since every time after that happened the client also had a WU to turn in, it might be the number of lines that could be appened per client to an open FAHlog.txt was exceeded. Not nice, but we are with faster boxes folding more and more WU in shorter time, possible for that symptom to surface.

    If it were other files also, would say HD, but no other files show up corrupted and no lost sectors recovered.

    I know, wild guess, but such is what you do when you see a nonsense appearing thing-- look at surrounding system circumstances.

    OH, the linux box does NOT do this with same client and core_78 releases.

    John.
Sign In or Register to comment.