Not with 1 stick of Crucial RAM running in single channel mode, no.
I'd be tempted to try an *independent* WoW forum.
Personally, I thought it sounded strange. But believe it or not the
official forums are far better than the fan-boyism from, say,
alt.games.warcraft (with one helpful exception, I mainly got a chorus
of "obviously your hardware sucks, dude").
Anyway, I just wanted to know if I was being fobbed off. They
made it sound like an "official" issue, but no reference was given.
FWIW, I'd
suspect a problem with your graphics card (possibly bad VRAM
or overheating)
Well, I have a Radeon 9800 Pro with a VGA silencer (extra cooling)
attached, so I'd be surprised but it's possible. I've had it 1.5 years,
no problems at all, with quite a few games/demoes thrown at it.
or just poor support for your particular graphics card within WoW.
Again, possible, though the Radeon 9800 is pretty common.
Try running 3dmark05 - if it runs that ok, your hardware is probably
fine.
Will try that later,
Cheers,
P.
--
-pm
http://oceanclub.blogspot.com
"Plagarism is the highest form of art just as theft is the
highest form of commerce."[/QUOTE]
I have that board, and it is picky about RAM. And the thing is,
memtest86+ isn't guaranteed to see the problems, as the problems
would appear to be chipset noise related. Memtest86+ is a
bit "tame" for finding problems on this chipset.
My final solution to the memory problem, was to buy some CAS2
memory, as the reduced access time seemed to help. I've used
both 2x512MB and 3x512MB Crucial Ballistix PC3200 CAS2 memory,
and it worked error free, while my cheaper CAS3 memory would not.
A good test, is to get a copy of Prime95 from mersenne.org . There
is a testing option called the "Torture Test" in the menu, and
it carries out a calculation with a known answer. It is a pretty
sensitive test for computing correctness, and will tell you whether
the CPU, Northbridge, and memory are good or not. No errors are
acceptable and the test should run for hours. There is even a
Linux version, and I've run four copies of the test at the same
time under Linux.
If you find problems, and are not interested in buying new memory,
your options are:
1) Reduce the CPU clock. That will drop both the CPU and memory
clocks. This assumes a synchronous CPU/memory relationship,
which is best for performance.
2) Try running async memory. Run the CPU clock at 200MHz, and
the memory at 166MHz for example. The "83%" memory setting
would do that, when the CPU clock is at 200MHz.
3) Find a hacked BIOS. There is a "Trats" BIOS available in
both "Command Rate 1T" and "Command Rate 2T" versions. The
2T version will stabilize bad memory, at the expense of memory
bandwidth.
http://forums.pcper.com/showthread.php?t=352326&highlight=a7n8x-e+trats
Basically, all of the workarounds degrade memory bandwidth, and
the AthlonXP loves memory bandwidth. So, all of the workaround,
at least to me, are unacceptable. That is why I got CAS2 memory
and fixed it for good.
Paul