Lock-ups, Reboots, and other strange problems.

[Jason1971]

About a week ago I deiced that I needed to re-install Windows XP (why I did that I don't know? my system was working just fine). So I did a format and a clean install. Everything seem to be working just fine then about 24 hours after that I started having lock-ups, drops to desktop, and even the occasional reboots. So thinking I had a bad install I reformatted the hard drive and once again installed Win XP. I've done this about four times. At that point I was thinking that my reinstallation of Win XP was just coincidently and my problems were hardware related. So I tested every piece of hardware I could one at a time until I had a failure (video card, sound card, ram, power supply/source, networking card, CD ROM). I was using Battlefield 1942 as my testing software. I am having errors no matter what I am doing but playing a game like BF1942 caused me to have a failure faster. At that point I figured out that the problem is one of two things, CPU or MB. So I went to CNET and d-loaded Hot CPU Tester. Ran the program and kept getting a SSE error. After seeing this I thought that I had a bad CPU. So I went to the store and got a new CPU and guess what?? Still having the same problems. I guess that it's the MB but could it be the hard drive? It's the only other hardware I have not tested :( At this point my system is about 9mm away from true happines. Any ideas? Here is my system: 1800 Athlon XP, GA-7VTXE MB, Audigy 2, Ge-Force 4 Ti-4400, 512 DDR, 400 Watt power supply, and 2 HDs.

[shamrock_uk]

SSE is an Intel technology thats been around for some time...incorporated into all Pentium 3 processors. AMD decided to include it in the Athlon XP, renaming it 3D Now Professional. As far as I know it makes the FPU more efficient, whilst rendering it slightly more prone to errors.

This would indicate your processor, except you've already swapped that out, so I guess the only thing left is to try someone else's motherboard in your machine.

I doubt its the HD, but you may as well close all options, ...if you have two, just unplug one and boot off the other. It's probably better to try that first than muck around changing motherboards. Much less hassle :-)

Sorry I can't be more help

PS If the errors only happen after the computers on for a while, check your CPU fan, is the heatsink secure etc? You never know!

[ranchdog]

Memory errors are very suspect here. Power supply is
second.

Please go to www.bootdisk.com and d/l MemTest86 (DocMem
is also good.) Send it to a clean floppy after you d/l.

Power up with this floppy inserted and this program will
run for you in DOS mode. RAM errors will be listed if
there are problems with your memory module(s). Any at all
are too many.

Memory testing programs that do not run in true DOS
mode are only testing cache memory.


Luck.


RD.

[Whyzman]

Random reboots are most often attributed to RAM, Power Supply, or Heat.

As RD has already pointed out two of these possibilities, I thought I'd just brighten your day by introducing the third! :( :D

You could try a fan gently blowing on an open case...would be a good idea to have a heat monitoring utility if you don't already. Many folks use Motherboard Monitor (http://mbm.livewiredev.com/about.html).

[mjc]

So I did a format and a clean install. Everything seem to be working just fine then about 24 hours after that I started having lock-ups, drops to desktop, and even the occasional reboots. So thinking I had a bad install I reformatted the hard drive and once again installed Win XP.

When you did the reinstall did you include any mothboard/chipset drivers? Updated device drivers?

[Jason1971]

Thank you all for your help. I d-loaded the Mem test86 and I got some very strange results. First I tested my system with both of the 256 meg sticks in and I had over 4,000 errors. Next I tested my ram one stick at a time. On the first test I got 42 errors and on the other stick of ram I tested I had 93 errors. So I guess that my question is what's my problem is it ram or my MB and why did I get 4000 errors with both of them in at the same time?
MJC, I did intsall all of my drivers. My first thought was that I had a bad driver for my MB.
Whyzman, I tried that too. In fact if I don't find out what's going on with my system soon my computer is going to have a big problem with heat when I set it on fire :D
Thanks again everyone,
Jason

[Jason1971]

It was my RAM. Thanks to everyone who responded to my thread.

Jason:)