Weird problem!!!

well I have been playing guildwars close to a year now and well I have decided to upgrade computers so well I load guildwars on my new computer and and everything goes good and then I am hit with a note saying that guildwars has detected a problem and that it may be caused by overheating processor or memory corruption!!! The thing is that it works fine with all my other games and everything is basicly new and top of the line stuff....so whats my prob???

Your problem is that you're not telling what your problem is.

You're coming to the doctor, saying: " I feel a pain".

Doctor asks, "can I examine you?"

-No, just tell me what's wrong doctor!




So. Post computer specs, the exact error message and so forth and so on.

(MESSAGE) Guild Wars has deteted a possible hardware malfunction. this may be due to faulty or overheating processor or memory chip. This aplication is now terminated.....thats what it tells me when I get into the login screen well buddy if I knew all the exact specs I would tell ya but I am no Computer wiz or any thing..I gave my father a couple hundred dollars and told him to build me a really nice computer and he did so......

http://www.guildwars.com/support/en-hardwarefailure.php

Hey buddy, please read the link that Eggroll posted above.

Basically, what it says is that GW runs a little diagnostic test in background while you play the game. It performs the diagnostic by making your computer perform some basic computations, and then the answers generated by your computer are checked against a table of correct values. This incidentally is exactly how Memtest, Stress Prime, and Orthos SP2004 work.

So GW is prolly terminating because Guild Wars is detecting computational errors, which in turn leads to platform instability.

When this happens, there's a good chance the problem can be resolved in BIOS. There's also a chance that your RAM modules are defective. And there's also a very very remote chance that your CPU is defective. But generally speaking, these kinds of errors turn up due to incorrect BIOS settings. Bad overclocks are a common culprit.

Could be as simple as increasing DRAM voltage. Could be that your Dad incorrectly set the RAM timings or that BIOS did not detect the correct SPD info for your modules. Could be a lot of things.

If this was my system, the first thing I'd do is make sure the DRAM voltage is set to volts recommended by the manufacturer of your memory modules. For some reason, this often has to be manually set.

I already looked at that it but everything that is says is wrong I just dont see how because everything is new but I guess I will just replace the video card and see if that does anything

Never had a new car that broke down?

Hold On - It is precisely because your computer was newly built that the things ANet lists could be the problem. before you spend a lot of money on another video card, you might want to try a couple of things 1st because it is fairly common to have problems with a "built" computer at first.

1: download and run speedfan - it can tell the temperatures of several of your computer parts - see if anything is overheating

If there is something that is too hot, you might the following
An extra fan can make a lot of difference
Ask your dad if anything he put in was overclocked (if you only gave him a couple of hundred dollars for a really nice computer, he may have had to overclock to keep costs down) If he did overclock, then ask him to throttle it back a litte
Check the cooling fan on the CPU and make sure it is seated firmly
Make sure there is air blowing on the Hard Drives - the newer drives can run very hot and are often in an area of the case that get very little airflow

2: If nothing is overheating then check and make sure that all the cables and cards are seated firmly in their slots. Most of the time when a computer I have just put together has a glitch like that it is because a stick of RAM was not fully seated in the slot or a cable wasn't tight enough

3: Check with your dad and see if he put in a dual core CPU. If he did, ask him to double check and make sure the RAM for both cores is the same type/speed/size/brand of RAM and that they are in the correct slots for each of the two cores. Some motherboards have a 1122 and others have a 1212 configuration. In the first kind Ram has to be in slots 1 and 3. The second needs RAM in slots 1 and 2.

4: Make sure the motherboard is screwed in tightly enough to be firmly seated but not so tightly that is is bent or warped.

5: Double check your power supply and make sure it is big enough to provide enough power for the full system - if it came with the case, chances are it is too small for any kind of high end hardware and it may be having trouble running everything at full load. (If you are running a high end video card and fast processor, you will need at least 550 Watts or more.)

6: If your dad put in a video card or sound card on a board that has onboard sound or video, make sure the onboard audio/video was disabled correctly in the BIOS - in some case they disable automatically but in others you have to manually disable them.

7: Check and make sure that you have the latest drivers for all your hardware and see if there are any firmware/BIOS updates for your hardware/motherboard.

I don't think I have ever had a home-built computer run perfectly at first and those things I just listed are the areas where most trouble tend to be on a newly built system.

Hehe. As was mentioned, you typically will have the most problems with a home-built machine when it's new. Something is configured wrong, something is damaged, or one of your parts is defective. It's also possible that your PSU isn't adequate for your system or that you're using a driver that Guild Wars doesn't play well with. It's really VERY common to have problems at first, but you can't just start replacing things willy-nilly. That's a waste of time and money. You need to troubleshoot and find your problem via a process of elimination. Better yet, why not have your dad help you? That would seem to make a lot of sense since he built the machine, eh?