Welcome guest. Before posting on our computer help forum, you must register. Click here it's easy and free.

Author Topic: Windows 2000 NT Freezing....  (Read 7201 times)

0 Members and 1 Guest are viewing this topic.

TxOutlaw

  • Guest
Windows 2000 NT Freezing....
« on: October 28, 2007, 07:27:28 PM »
I have a custom madeTower w/ 2.5G P4 with ABIT MB, ASUS video, Audigy sound... It had 512 DDR and I just plugged in another 1G today.

This has been goin on a while. Computer freezes with any program or activity. Sometimes it will freeze before loading windows completely and sometimes will work for a day or two. All fans but one case fan work, cleaned the inside of the tower, updated virus, firewall, windows, and spyware. Cleaned out as much as I could. I had a guy come by and told me I should add mem. I did and no change. I got far enough in windows to see that the computer recognized the added ddr.

Am I missing anything??? Any help appreciated!!

patio

  • Moderator


  • Genius
  • Maud' Dib
  • Thanked: 1709
    • Yes
  • Experience: Beginner
  • OS: Windows 7
Re: Windows 2000 NT Freezing....
« Reply #1 on: October 29, 2007, 12:49:03 AM »
Travel to Crucial's website and enter your systems info to determine what type of RAM that machine likes...then compare the RAM specs you have to see if it is the proper match.
   
 
" Anyone who goes to a psychiatrist should have his head examined. "

dahlarbear



    Specialist

    Thanked: 101
    Re: Windows 2000 NT Freezing....
    « Reply #2 on: October 29, 2007, 04:11:12 AM »
    1. Are you sure you don't need that case fan working?

    2.  Run memory diagnostics from a bootable CD or floppy diskette.  MemTest86 3.3 is a "free" reputable memory diagnostic.  Boot it, it loops thru different memory tests forever until you hit "Escape" to terminate.  You should do at least one complete pass if possible.  Look for free download on their site:

    http://www.memtest86.com/

    Don't forget to save and read documentation file (I think it's included with download?).  If you have trouble reading text file, open it in Microsoft word, then save it out again as text file.  I believe this adds explicit cr-lf to text so you can read in Notepad.

    If it passes memory test without error, let it run all night, then your memory is probably good.

    3.  You should also get motherboard documentation off internet to ensure you don't have to add "matched" pairs of memory (dual channel?) and you're using correct slots on motherboard.  Sometimes a board will accept certain size memory module (e.g. 512 MB) using low density memory chips but not high.  Sometimes documentation suggests adding larger module before smaller module.  Your modules also need to be speed compatible in order to play together.
    « Last Edit: October 30, 2007, 07:05:32 AM by dahlarbear »

    TxOutlaw

    • Guest
    Re: Windows 2000 NT Freezing....
    « Reply #3 on: October 29, 2007, 08:20:22 AM »
    Cool thanks for the help. I will try the boot disc tonight.

    As for the memory, I did put the 1Gig in DIMM1 and the old 512KB in DIMM2... It freezes instantly now. I cant even get windows fully started. Tonight I may take out the 512KB and see if that helps.

    If I had hair, I would be pulling it out... LoL... I am about ready to sell this PC for parts... lol

    TxOutlaw

    • Guest
    Re: Windows 2000 NT Freezing....
    « Reply #4 on: October 29, 2007, 12:39:04 PM »
    Also, where can I get the files I need to create a boot disk for Win2000pro? I don't think I have a cd anymore...

    Thanks!

    patio

    • Moderator


    • Genius
    • Maud' Dib
    • Thanked: 1709
      • Yes
    • Experience: Beginner
    • OS: Windows 7
    Re: Windows 2000 NT Freezing....
    « Reply #5 on: October 29, 2007, 01:00:02 PM »
    bootdisk.com
       
     
    " Anyone who goes to a psychiatrist should have his head examined. "

    TxOutlaw

    • Guest
    Re: Windows 2000 NT Freezing....
    « Reply #6 on: October 29, 2007, 01:36:01 PM »
    OK. I am looking for any more clues to fix this thing. I plan on making a boot disk, swapping the 1gig in DIMM1 and removing the 512K from DIMM2, removing the sound and network cards... If that doesn't help and I have to use the boot disk, can it be from CD or have to be 1.44 diskette? Running a boot disk, will this allow me to windows so that I can get to the memory test?

    Any additional pointers would be greatly appreciated!!

    patio

    • Moderator


    • Genius
    • Maud' Dib
    • Thanked: 1709
      • Yes
    • Experience: Beginner
    • OS: Windows 7
    Re: Windows 2000 NT Freezing....
    « Reply #7 on: October 29, 2007, 01:42:08 PM »
    You can DLoad the Win2k files and make a bootable CD with it...
    You can also DLoad MemTest and create a bootable CD ...follow the directions on the MemTest site...
    I still believe you may have the wrong type/specs of RAM...did you travel to Crucial's site to see for sure ? ?
       
     
    " Anyone who goes to a psychiatrist should have his head examined. "

    TxOutlaw

    • Guest
    Re: Windows 2000 NT Freezing....
    « Reply #8 on: October 29, 2007, 02:02:27 PM »
    I read in my MB manual and it called for DDR PC 2700, 3200 and several other 184pin DIMM. I got that in a 1Gig.

    This may help. A tech told me to try crucial.com yesterday before I bought the new RAM and the site said I had no memory at all. Didn't recognize the 512K that was in there... Did recognize that my MB had 3 DIMM spots tho....


    patio

    • Moderator


    • Genius
    • Maud' Dib
    • Thanked: 1709
      • Yes
    • Experience: Beginner
    • OS: Windows 7
    Re: Windows 2000 NT Freezing....
    « Reply #9 on: October 29, 2007, 02:25:29 PM »
    The site won't "see" what you have installed...it will only advise on what is the correct type.
    What do your RAM stick specs say ? ?
       
     
    " Anyone who goes to a psychiatrist should have his head examined. "

    dahlarbear



      Specialist

      Thanked: 101
      Re: Windows 2000 NT Freezing....
      « Reply #10 on: October 30, 2007, 08:00:23 AM »
      1.  MemTest86 is a bootable program (it is self-contained within its own operating system).  It boots directly from floppy or CD and is the only program running in your machine.  It does not run under Windows...  there is no Windows running.

      That's the great part about it.  It not only tests your memory, it allows you to run software that's independent of your current software.  If your problems continue while running MemTest86, then your Windows software is NOT the problem.

      Then you can look towards "heat", bad hardware, loose connections.  But work on one thing at a time.  Ensure both memory modules meet specs, are compatible with each other, and are "good" before moving on to something else.

      Does motherboard documentation and/or Crucial confirm that you may put 1GB memory module in a "single" DIMM slot or even a 512MB module?

      You might be able to run with either the 1GB or the 512MB but not both at the same time (some modules aren't compatible with each other).

      If you encounter memory errors while testing, then test each module separately (remove one module from PC); again they may not be compatible with each other (or your motherboard).

      If you want a bootable CD then look for this download "Memtest86 v3.3 ISO image (zip)" on the "Free Download" page of the site: 

          http://www.memtest86.com/


      2.  Per "patio's" request, be sure to post the "specs" from each memory module that you're attempting to use.  It would also be helpful to know "which" ABIT motherboard you're using.

      3.  Thermal Compound/Paste.  You implied "freeze" started before addition of new memory.  Depending upon how your CPU, heatsink, and fan mount you may need to use a "thermal" compound or paste between them.  If you don't, the CPU will overheat and freeze.  And the harder you work it (running programs), the hotter it gets.  An example of a thermal compound/paste is:

          http://www.articsilver.com/

      Although if it sometimes runs for a day or two without freeze (are you working it hard?), then thermal compound/paste may not be a factor.


      4.  Just a thought...  Did the system ever run smoothly or has it always had problems?

      Quote
      This has been goin on a while.
      « Last Edit: October 30, 2007, 08:36:20 AM by dahlarbear »

      TxOutlaw

      • Guest
      Re: Windows 2000 NT Freezing....
      « Reply #11 on: October 30, 2007, 07:06:59 PM »
      OK Geek Squad are idiots... I was at best buy and SHOWED them my ABIT SR7-8X manual. It calls for 184bit PC2700 up to 1gig and they gave me a KByte 1GB PC3200 DDR DT. Think thats the problem. The old 512K is a PC2700 and it worked fine for 5plus years... The problem started a few months ago...

      Thanks for the help. I am gonna swap out the new memory and try that.

      TxOutlaw

      • Guest
      Re: Windows 2000 NT Freezing....
      « Reply #12 on: October 31, 2007, 05:58:00 AM »
      Well I got the old mem back in DIMM1 and the new memory out. It lets me get back to windows for a little while. I made the memtest CD (put the iso file burned on a CD) and left it in the cd rom drive and turned off the computer and turned it back on. Went up to windows, but I did see it say "trying to boot from CDROM" before windows started to open.

       ???

      dahlarbear



        Specialist

        Thanked: 101
        Re: Windows 2000 NT Freezing....
        « Reply #13 on: October 31, 2007, 09:29:20 AM »
        1.  The "Geek Squad" are not idiots.  While it is true that your Abit SR7-8X motherboard manual does call for "Unbuffered PC 2700 DDR Module up to 1GB" in a two slot configuration, the Crucial website says the motherboard "Supports up to two PC2700 (DDR333) or faster DIMMs" (and they go on to list their compatible unbuffered PC2700, PC3200, and PC4000 1GB modules as available).  On a separate page Crucial goes on to state:

        Quote
        Memory is designed to be backward-compatible, so generally speaking, you can safely add faster memory to a computer that was designed to run slower memory. However, your system will operate at the speed of the slowest module or system component (the "lowest common denominator" effect).

        Does that guarantee that your two memory modules are compatible? No.


        2.  Background and Troubleshooting links:

             a.  Abit SR7-8X Motherboard User Manual (zipped PDF download):

            http://www.uabit.com/downloads/downloads.php?file=/downloads/manual/english/sr7-8x.zip

             b.  KByte Memory Troubleshooting link:
            http://www.kbytememory.com/pages/troubleshooting_main.shtml
           
             c.  Crucial Troubleshooting and Background Info Links:
            http://www.crucial.com/support/troubleshooting_install.aspx

            http://www.crucial.com/kb/answer.aspx?qid=4003

            http://www.crucial.com/support/memory_speeds.aspx


        3.  MemTest86:

        I made the memtest CD (put the iso file burned on a CD) and left it in the cd rom drive and turned off the computer and turned it back on. Went up to windows, but I did see it say "trying to boot from CDROM" before windows started to open.

        I've never made a bootable CD, so I'm not sure of the procedure.  Is there a working floppy drive handy?  If not some ISO image research is required.
        « Last Edit: October 31, 2007, 09:45:57 AM by dahlarbear »

        TxOutlaw

        • Guest
        Re: Windows 2000 NT Freezing....
        « Reply #14 on: October 31, 2007, 10:00:50 AM »
        Yeah I read that too... PC 3200 should be ok, but it sure doesnt let me do much... I will make a floppy tonight and see how that goes...

        My appologies to any members of the "Geek Squad"!!! Just getting frustrated is all!!

        dahlarbear



          Specialist

          Thanked: 101
          Re: Windows 2000 NT Freezing....
          « Reply #15 on: October 31, 2007, 11:17:26 AM »
          1.  Apparently when you want to make a bootable CD from an ISO image, the CD burner program must be told to treat it as an "image burn" not a "file burn", otherwise you're just saving another file to CD.  Lots of tutorials on web thru google, but this post thread gave me some quick insight:

              http://forums.majorgeeks.com/showthread.php?t=106429


          2.  Test Memory Modules and Slots.  If you get memory errors during the test runs, record the locations.  Then run the memory test again.  If you don't get the same "bad" memory locations, the problem is probably outside of your memory module.  Start with just one memory module, the 512MB.  You might want to try it in different slots.  After you have completely tested it (possibly verify all three slots are working if motherboard allows it), pull it out, and test the new 1GB memory module.  Then if both modules test good, test them together to see if they're compatible with each other.  Put larger one in front of smaller one.  If that doesn't work put smaller one in front of larger one.

          If you get the same bad memory locations each time, that module is probably bad or incompatible with your motherboard.


          3.  If system doesn't stay up long enough to test, I would look elsewhere for the problem, but continue to use the memory test to verify future changes have resolved the problem.  If it's hanging on the memory test, your Windows operating system software and drivers were not the problem.  I'd look to heat, bad/loose connections, and bad hardware (I'm not sure about power).  You can either start with nothing and add on or start with everything and take off components.


          4.  Since it usually boots up, I'd start with power supply, motherboard, CPU, one stick of memory (probably 512MB), video card, monitor, keyboard, mouse, and floppy drive.  There's also your BIOS configuration in CMOS.  If you can't run in a minimal configuration you might want to reset your BIOS to its factory default settings.

          5.  Heat.  I believe there are heat sensors on your motherboard that you may be able to read during CMOS setup.  See what the temperature readings are.  Generally if you remove heat sink/fan from CPU you need to reapply a thermal compound/paste between the connecting surfaces to help draw heat off CPU.  Are all your fans supposed to be working?

          6.  IDE Cable.  If you're using the newer PATA hard drives that operate at 66/100/133 (something?), you should have an 80-wire flat ribbon cable with a 40-pin connector.  At those higher throughput speeds the old 40-wire cable won't cut it (will cause problems).

          7.  Hard Drive.  What shape is your hard drive in?  Most hard disk drive manufacturers have diagnostic programs on their web sites that you can download and run to check the integrity of the drive and its disk surfaces.

          TxOutlaw

          • Guest
          Re: Windows 2000 NT Freezing....
          « Reply #16 on: October 31, 2007, 01:49:44 PM »
          Thanks again for all the help. I will complete these steps later. Yes all fans do work with the exception of one case fan. One fan was locked up when I went searching for the problem initially.

          I don't think its heat related, I can have the computer unplugged all night then turn it on and it can freeze instantly. I will read up on burining it as an image.

          Thanks again!

          TxOutlaw

          • Guest
          Re: Windows 2000 NT Freezing....
          « Reply #17 on: November 01, 2007, 06:57:00 AM »
          OK, so I am still running memtest and its showing one read bar with 8 errors so far... says ecd917fe is bad, ecd907fe is good... Thats all its reading thus far...

          I did move the 512K DDR around and it didn't change much.

          Guess I will post more when the memtest is done...

          Thanks again!

          TxOutlaw

          • Guest
          Re: Windows 2000 NT Freezing....
          « Reply #18 on: November 02, 2007, 07:33:10 PM »
          ok 48hours and still running... still showing the same thing with alot of errors... whats my next step???

          Thanks!

          dahlarbear



            Specialist

            Thanked: 101
            Re: Windows 2000 NT Freezing....
            « Reply #19 on: November 03, 2007, 05:47:33 AM »
            1.  Memtest86 v3.3 Documentation.  The best source for interpretating the test results is the "readme.txt" file for the test program.  I got it from the floppy diskette version of the download and ran it thru Microsoft Word to add explicit <CR><LF> to end of each line so it's readable by "notepad.exe".  Let me try to attach it to this post.  If it attaches successfully, read it; especially numbered paragraph 8.


            2.  I wasn't expecting "alot" of errors.  Are these different memory locations or the same one (or few) repeatedly testing bad.  How many "different" memory locations are testing bad?

            If you're getting errors you don't have to test for 48 hours.  Normally you test overnight only to ensure the memory is good (i.e. you're not getting "any" errors).  Hit the "Escape" key to terminate the test.

            Record the "bad" memory locations and as much information about them as you can.  If you rerun the test and get the same "bad" memory locations, the module is probably bad.  If you get different "bad" memory locations then those locations are not necessarily bad (problem may originate elsewhere, e.g CPU, cache L1, cache L2, motherboard).


            3.  If you've tested with 512 MB memory module and gotten errors, I'd reseat that memory card in the same slot and test again to see if it repeats with the same "bad" memory locations.

            Then I'd remove it, plug in the 1 GB memory module in its slot, and test it.  If you get errors, record them and try to analyze what's happening using the "readme.txt" documentation for the test.  Repeat the test to see if you get same bad memory locations each time for 1 GB stick.

            If either memory module tests clean, run the test overnight to make sure.  Then I'd run with that one to see if your system is now stable running Windows operating system.

            Memory module replacement method works best if you're using known good compatible memory (and we're not).


            4.  You know about the dangers of Electro Static Discharge (ESD) right?  There should have been some installation instructions with that new memory module you bought.


            5.  When troubleshooting basic system failures you probably should be using the factory default settings.  You don't want to be overclocking anything.  Work within the normal settings.  So if you continue to have problems you'd want to check your motherboard and BIOS settings for everything.

            [getting disk space - attachment deleted by admin]

            dahlarbear



              Specialist

              Thanked: 101
              Re: Windows 2000 NT Freezing....
              « Reply #20 on: November 03, 2007, 06:16:12 AM »
              I only see the "attached" documentation for Memtest86 v3.3 in my previous post if I am logged in.  If you can't see it, TxOutlaw, when you are logged in (or otherwise) let me know and we'll have to make other arrangements.  The file size is approximately 36 KBytes, too large to include "inline" as single post (Forum has 10 KByte limit on posts). 

              However, I will include numbered paragraph 8:

              ------------------------------------------------------------------
              Quote

              8) Trouble-shooting Memory Errors
              ================================
              Please be aware that not all errors reported by Memtest86 are due to
              bad memory. The test implicitly tests the CPU, L1 and L2 caches as well as
              the motherboard.  It is impossible for the test to determine what causes
              the failure to occur.  Most failures will be due to a problem with memory.
              When it is not, the only option is to replace parts until the failure is
              corrected. 

              Once a memory error has been detected, determining the failing
              module is not a clear cut procedure.  With the large number of motherboard
              vendors and possible combinations of simm slots it would be difficult if
              not impossible to assemble complete information about how a particular
              error would map to a failing memory module.  However, there are steps
              that may be taken to determine the failing module.  Here are three
              techniques that you may wish to use:

              1) Removing modules
              This is simplest method for isolating a failing modules, but may only be
              employed when one or more modules can be removed from the system.  By
              selectively removing modules from the system and then running the test
              you will be able to find the bad module(s).  Be sure to note exactly which
              modules are in the system when the test passes and when the test fails.

              2) Rotating modules
              When none of the modules can be removed then you may wish to rotate modules
              to find the failing one.  This technique can only be used if there are
              three or more modules in the system.  Change the location of two modules
              at a time.  For example put the module from slot 1 into slot 2 and put
              the module from slot 2 in slot 1.  Run the test and if either the failing
              bit or address changes then you know that the failing module is one of the
              ones just moved. By using several combinations of module movement you
              should be able to determine which module is failing.

              3) Replacing modules
              If you are unable to use either of the previous techniques then you are
              left to selective replacement of modules to find the failure. 

              4) Avoiding allocation
              The printing mode for BadRAM patterns is intended to construct boot time
              parameters for a Linux kernel that is compiled with BadRAM support. This
              work-around makes it possible for Linux to reliably run on defective
              RAM.  For more information on BadRAM support
              for Linux, sail to

                     http://home.zonnet.nl/vanrein/badram

              Sometimes memory errors show up due to component incompatibility.  A memory
              module may work fine in one system and not in another.  This is not
              uncommon and is a source of confusion.  The components are not necessarily
              bad but certain combinations may need to be avoided.

              I am often asked about the reliability of errors reported by Mestest86.
              In the vast majority of cases errors reported by the test are valid.
              There are some systems that cause Memtest86 to be confused about the size of
              memory and it will try to test non-existent memory.  This will cause a large
              number of consecutive addresses to be reported as bad and generally there
              will be many bits in error.  If you have a relatively small number of
              failing addresses and only one or two bits in error you can be certain
              that the errors are valid.  Also intermittent errors are always valid.

              All valid memory errors should be corrected.  It is possible that a
              particular error will never show up in normal operation. However, operating
              with marginal memory is risky and can result in data loss and even
              disk corruption.  You can be sure that Murphy will get you if you know
              about a memory error and ignore it.

              Memtest86 can not diagnose many types of PC failures.  For example a
              faulty CPU that causes Windows to crash will most likely just cause
              Memtest86 to crash in the same way.

              TxOutlaw

              • Guest
              Re: Windows 2000 NT Freezing....
              « Reply #21 on: November 03, 2007, 02:48:56 PM »
              Ive got the 1gig in now and so far no errors... The computer just freezes in windows quicker with the 1gig in. I am REALLY considering parting the computer out!!! lol


              TxOutlaw

              • Guest
              Re: Windows 2000 NT Freezing....
              « Reply #22 on: November 03, 2007, 04:31:56 PM »
              Test passed with a 1 gig in.....what should I run or do now?   ???


              TxOutlaw

              • Guest
              Re: Windows 2000 NT Freezing....
              « Reply #23 on: November 04, 2007, 09:44:52 AM »
              OK assuming I have the correct memory (1 gig tested fine) where should I look next? Should I run a boot disk? What will I do with that? I will leave the 512K mem out for now.

              dahlarbear



                Specialist

                Thanked: 101
                Re: Windows 2000 NT Freezing....
                « Reply #24 on: November 04, 2007, 10:00:20 AM »
                1.  1 GB Memory Module.  If the test passed, sometime in the near future you should run it all night or longer to ensure it and the basic memory subsystem is solid.  You want to be sure the memory is "good" before you decide to keep it.  Having said that, you should run with the memory that is "good".

                If the memory test doesn't freeze then I would look elsewhere for the problem:

                    o  Hardware (devices, cables, connections)
                    o  Software (application, operating system, device drivers)
                    o  Motherboard and/or BIOS configuration


                2.  Let's start with the software.  Start by minimizing your Windows environment.  Safe Mode loads a minimal set of basic device drivers to allow you to troubleshoot and fix your system.  If your system freezes running this minimal set of drivers, then it's not your third party drivers.

                Boot your system into "Safe Mode" (the regular one, not with networking or comand prompt only).  Let it set for awhile.  If no freeze, then exercise the operating system and some of its utilities.  Still no freeze, exercise your security software ensuring only one is active at a time.  If system freezes, try to identify what you were doing and what software was active at the time of the freeze.  Still no freeze, then add your second security product concurrent with first.  Still no freeze, then add your third security product if you normally run them all concurrently.

                You may want to disconnect from internet before testing in Safe Mode because your security software will not automatially start in this mode (although I guess if you're not running Safe Mode with Networking it wouldn't matter).

                3.  Potential Software Issue (don't address these yet - background info only):
                     a.  Application.  One or more of it's files may be corrupt.  Uninstall, reboot, and re-install the application (possibly download new installation file).  It may also be incompatible with other software.  This is relatively common for security software that operate at low levels within the system.

                     b.  Operating System.  One or more of your operating systems files may be corrupt.

                     c.  File System.  May want to check the integrity of the file system and possibly the surface of the disk.

                     d.  Device Drivers.  One or more of your device drives may be corrupt, bad, or incompatible with your system.
                « Last Edit: November 04, 2007, 01:18:34 PM by dahlarbear »

                patio

                • Moderator


                • Genius
                • Maud' Dib
                • Thanked: 1709
                  • Yes
                • Experience: Beginner
                • OS: Windows 7
                Re: Windows 2000 NT Freezing....
                « Reply #25 on: November 04, 2007, 10:02:30 AM »
                If the 1G stick checked out OK then just re-boot to Windows ...run the machine thru it's paces and see if the freezing is gone.
                If so you have found the culprit...
                   
                 
                " Anyone who goes to a psychiatrist should have his head examined. "

                TxOutlaw

                • Guest
                UPDATE!!!! Windows 2000 NT Freezing....
                « Reply #26 on: December 04, 2007, 11:42:38 AM »
                Finally gave up and took it in... They called and basically said the motherboard was shot... I couldnt find another Abit SR7 - 8X so I guess im computer shoppin... Im not sure weather to buy another tower or to get a laptop. I use my cpu for work email, maps and microsoft office things... Any suggestions for me under 1000.00???

                Thanks

                dahlarbear



                  Specialist

                  Thanked: 101
                  Re: Windows 2000 NT Freezing....
                  « Reply #27 on: December 05, 2007, 04:41:16 AM »
                  Finally gave up and took it in... They called and basically said the motherboard was shot... I couldnt find another Abit SR7 - 8X so I guess im computer shoppin... Im not sure weather to buy another tower or to get a laptop. I use my cpu for work email, maps and microsoft office things... Any suggestions for me under 1000.00???

                  Thanks

                  1.  I cannot advise on a computer purchase as I don't follow the market that closely.  I have strong bias toward desktops as I believe maintenance/repair is cheaper and easier.

                  2. Motherboard Shot.  Anything's possible.  How did they determine the motherboard is shot?  Who determined it was shot?  Geek Squad?

                  3.  Does your system freeze when you're running MemTest86 v3.3 against a single 1 GB module?  MemTest86 is designed to run forever until you terminate with "Escape" key.

                  Test passed with a 1 gig in.....what should I run or do now?   ???

                  So the 1 GB tests OK with "no errors".  How many "passes" did the test complete and/or how long did you run the test? (I'm trying to get some data on the stability of your system.  Test passed because... no errors were reported; it ran for several hours and complete passes; and you manually terminated test with "Escape" key; it did not terminate via freeze.)

                  4.  Hard Drive.  What shape is your hard drive in?  Most hard disk drive manufacturers have diagnostic programs on their web sites that you can download and run to check the integrity of the drive and its disk surfaces.

                  5.  IDE Cable.  If you're using the newer PATA hard drives that operate at 66/100/133 (something?), you should have an 80-wire flat ribbon cable with a 40-pin connector.  At those higher throughput speeds the old 40-wire cable won't cut it (will cause problems).

                  6.  Does your system freeze when you boot and run it in Windows "Safe Mode"?

                  Safe Mode loads a minimal set of basic device drivers to allow you to troubleshoot and fix your system.  If your system freezes running this minimal set of drivers, then it's not your third party drivers.

                  Boot your system into "Safe Mode" (the regular one, not with networking or comand prompt only).  Let it set for awhile.  If no freeze, then exercise the operating system and some of its utilities.  Still no freeze, exercise your security software ensuring only one is active at a time.  If system freezes, try to identify what you were doing and what software was active at the time of the freeze.  Still no freeze, then add your second security product concurrent with first.  Still no freeze, then add your third security product if you normally run them all concurrently.

                  You may want to disconnect from internet before testing in Safe Mode because your security software will not automatially start in this mode (although I guess if you're not running Safe Mode with Networking it wouldn't matter).

                  7.  I can't tell you it's not the motherboard, but there are other things that may cause a freeze.
                  « Last Edit: December 05, 2007, 05:06:19 AM by dahlarbear »