Asus Crosshair Stability Problems

[Akuen]

I have been having various system problems including the screen going black, system restarting, and a number of program crashes. The system recieved a fresh install of windows immediately after my new hardware was put in, so I am guessing that there is a problem with the way it is setup in the BIOS since basicly everything is new.

Here is the current setup:
Motherboard: Crosshair BIOS v7.3.13
RAM: Crucial Ballistix DDR2800 4-4-4-12 2.2V
Hard drive: Western Digital Caviar RE2
Processor: AMD Athlon 64 X2 6000+ Windsor 1.4V
Video card: XFX 7950GT 256MB ForceWare 169 (No longer carried on newegg, so no link for this one)

The voltages and timings listed are what I have manually entered into the BIOS, most everything else is set to auto currently. If anyone has some advice as to what I can try changing or checking to make my system stable, please let me know. I had links for more complete information on my hardware, but I can't post them because of my post count...

[Akuen]

As per another forums, the following update:

My PSU is a Thermaltake Toughpower 600W.

Running memtest, as I expected, returns a lot of errors. I believe that some of the settings that the BIOS are "auto" setting are not correct.

My voltages for the processor and ram are both in the specs for what they are supposed to need to run at their stock speeds/timings. I will work on updating the BIOS though I have not so far because I will need to buy a flash drive or floppy, since the only old one I have died recently.

I had not realized that the drive was RAID edition, actually, no. There is only one of the hard drives in the computer right now though, so it is not in RAID.

As far as event viewer, it's a lot of different things that are having problems.

AMDLLD: AdjustCoreTSC() Node[ 0 ] Core[ 0 ] Cpu[ 0 ] Affinity[ 0x1 ] Error: HalGetBusDataByOffset() failed reading north-bridge TSC.

System Error: Error code 1000007f, parameter1 00000008, parameter2 00000000, parameter3 00000000, parameter4 00000000. Apparently from kernel crash.

Application Error: Faulting application iexplore.exe, version 7.0.6000.20733, faulting module wininet.dll, version 7.0.6000.20733, fault address 0x0003fe02. Memory problems?

[shaunUK]

This is a new build? If so it could be something as simple as a badly seated RAM stick or possibly the system overheating.
Failing that the standard practice is elimination. Try removing all but one stick of RAM and running memtest. If that passes try another and so on until you can identify the problem.

[Akuen]

Originally Posted by shaunUK

This is a new build? If so it could be something as simple as a badly seated RAM stick or possibly the system overheating.
Failing that the standard practice is elimination. Try removing all but one stick of RAM and running memtest. If that passes try another and so on until you can identify the problem.

Yes, it's fairly new, about one month. I am currently in the process of moving the sticks so that I am sure they are in right and then using memtest on each one on it's own. I'll report back on that when I'm done.

This also came up on another forum while I was checking various things:
I have two sticks of the RAM, each 1GB. The BIOS seems to have some serious issues though. I just reset them to default settings in order to see if that would help. It sets my RAM timings to 5-5-5-18 2T and undervolts it at 1.9V. I don't understand why it is doing this, but if all the settings it is "auto" using for the RAM (and it has a huge number) are equally off, I can imagine that this is a problem.

I just booted with these less than stock timings on my RAM and upped the voltage back to the stock 2.2V. Running memtest resulted in only one error instead of the flurry of them I recieved before. (Again, I will try each stick in slot 1 with memtest and post results.)

[Akuen]

Testing the sticks one at at time in slot one, using various settings and voltages all seem to result in the same error filled testing process with memtest.