Curse

cleric · Apr 27, 2005, 04:23 AM // 04:23

i dont think memory timeings would cuase problems in only one game that seems odd to me. i know people that have run insane timings but still had progs work.

what error by the way?

as far as i know the servers arent open yet

Terik Stoermshade · Apr 27, 2005, 11:19 AM // 11:19

Quote:

Originally Posted by cleric

i dont think memory timeings would cuase problems in only one game that seems odd to me. i know people that have run insane timings but still had progs work.

what error by the way?

as far as i know the servers arent open yet

The servers don't have to be open for me to get this error. Sometimes, if I stay on the login screen for an extended period, GW will just shut down. It happened last night while I was entering my retail CD key. I restarted the game, re-entered the key and was off.

I wish I had a screenshot of the popup message, but it's something along the lines of:

"GuildWars has detected a hardware issue and is shutting down."

Then it throws me to a webpage where it provides possible causes for the error. I believe it suggests overclocking, overheating, insufficient power supply and memory timings. As I don't overclock, my CPU/GPU are running at 37/43 C and I have a 480W Antec PSU; I don't suspect the first three causes. Which leaves memory timings.

I can run the game just fine for hours without error -- it just occurs at the login.

To be honest, I am very hesitant to make any adjustments to default memory timings.

Colbin · Apr 27, 2005, 11:27 AM // 11:27

Quote:

Originally Posted by cleric

i dont think memory timeings would cuase problems in only one game that seems odd to me. i know people that have run insane timings but still had progs work.

what error by the way?

as far as i know the servers arent open yet

It can cause issue in specific programs. FarCry is a prime example. I couldn't get it to even launch into the game but every 1 out 10 attempts until I read several threads about memory and adjusted my timings. Also I can play WoW, PoE, Battlefield Vietnam, America's Army, and several other games without error. Not to mention Benchmarks and burn-ins in SiSoft Sandra and other benchmarks.

Terik you may want to try adjusting your CAS to 3 vs. 2.5. I haven't had a chance to look at the mem specs for your model/partnumber but that would put you at the same timings I have. Mine went away when I did and I also have no issue in game.

Quote:

Originally Posted by Terik Stoermshade

"GuildWars has detected a hardware issue and is shutting down."

Then it throws me to a webpage where it provides possible causes for the error. I believe it suggests overclocking, overheating, insufficient power supply and memory timings. As I don't overclock, my CPU/GPU are running at 37/43 C and I have a 480W Antec PSU; I don't suspect the first three causes. Which leaves memory timings.

I can run the game just fine for hours without error -- it just occurs at the login.

To be honest, I am very hesitant to make any adjustments to default memory timings.

Same error I received Terik. If you adjust your CAS to 3.0 vs. 2.5 you are actually slowing it down a bit. No danger there but do what your are most comfortable with.

Terik Stoermshade · Apr 27, 2005, 11:31 AM // 11:31

Quote:

Originally Posted by Colbin

Terik you may want to try adjusting your CAS to 3 vs. 2.5. I haven't had a chance to look at the mem specs for your model/partnumber but that would put you at the same timings I have. Mine went away when I did and I also have no issue in game.

Colbin,

Thanks again for your suggestions. Unfortunately, I'll be at work for the next 10 hours or so... I'll give it a try tonight when I get home.

nr1rhg · Apr 27, 2005, 12:16 PM // 12:16

i have same problem..

also a7n8x-e dlx and a 3200+
corsair xms 2-3-2-6 and checked..
board reads out memory timing fine..
allready tried on 2.5 -3-3-8 still crashes at client..

to test i just start the client and doesn't login yet

just stayed there for about a few minutes..

mostly crashes under 1 minute.

i know athlon doesn't like to run at 200 mhz.. but no problems with other games.

will try at 166 mhz later today and see if that will help.

racingx · Apr 30, 2005, 04:07 PM // 16:07

I just got the same error when logging out of the game sitting at the login screen. I am testing it right now and it hasnt done it again yet. It has only happened once so I wont adjust timings yet. Here are my system specs.

Asus A8V Deluxe rev 2
Athlon64 3200+ Winchester core
His IceQ X800XT with Cats5.4
1gig Corsair XMS3200LL pro 2-3-2-6-1t timings Dual Channel
Audigy 2zs
Antec True Power 550W

Like I said it only has happened once so I think it might be an error with the way the GW program is checking the hardware but we will see.

krafzig · Aug 18, 2006, 07:26 PM // 19:26

I also have this error message from GW:
"Guild Wars detected a possible hardware malfunction. This may be due to a faulty or overheating processor or memory chip. The application will now terminate."
But 3 of 4 times I start GW it crashes without any error message. Then the display just shows nice artefacts and hangs.
This can occurr afer a minute or after several hours - there seems to be no plan behind it.
OK, so far I supposed that this error was caused by overheating of my processor because I changed my MB and processor - I have now: Asus A7V600-X with AMD Athlon-Thoroughbred 2600+
But I did not change the cooler because specs did allow to be used with this processor. I also optimized the internal cooling of my PC by adding another fan. However, the game crashes
I did not change other stuff like memory, HD, DVD, graphics card (AGP ATI X800.)
After checking with the wonderful CPUZ tool (posted earlier in this thread) I checked now the CAS latencies and tried some variations but this did not help.

Default setting on the MB was 2-3-2-6
CPU-Z sais that I have 3 different memory chips:
1. Kensigton
512 MB
PC2300 (142MHz)
at 133MHz: 2.0-3-3-6
at 142MHz: 2.5-3-3-7

2. MSC
256 MB
PC2100 (133MHz)
at 100MHz: 2.0-2-2-5
at 133MHz: 2.5-3-3-6

3. 000000000000000000000
256 MB
PC2700 (166MHz)
at 133MHz: 2.0-3-3-6
at 166MHz: 2.5-3-3-7

Any suggestions?
I have no idea but I also don't want to damage things.
Should I use other memory or just keep one of the memory chips?

causation · Aug 18, 2006, 08:19 PM // 20:19

You said you changed mobo, did you clean out the processor heat sink of dust, and it was reseated with new thermal paste? Also check that all the chip fans, ( the little ones ) are spinning ok, as from experience i have had to have 2 Asus chip fans replaced from my Asus mobo.

krafzig · Aug 18, 2006, 08:38 PM // 20:38

First, thank you for the fast reply.
Everything is clean and I used also thermal paste. I think this should be ok.
I checked again all fans - they all seem to work fine.
But I want also to add that other progs work fine - unfortunately I have no other games installed, which demand as many processing power than GW does.
I still have no idea what to do now?

Amy Awien · Aug 18, 2006, 09:05 PM // 21:05

You could try to run it on the 512MB stick, that would eliminate any problems with using different sticks.
Try underclocking, specifically your mainboard ('frontend' bus). Processor may be cool, but there might be overheating or timing problems in there.

krafzig · Aug 18, 2006, 09:09 PM // 21:09

I took out two memory chips and left only the Kensington with the 500MB. This should be suficient for testing GW. Another reason is that Kensington supports ECC - the other two chips do not.
I tested with the default settings for the Kensington chip:
2-3-3-6 at 133MHz
and I tried
2-2-2-6 at 133MHz
becuase someone in this thread said this setting was failsave in his case.
But on my PC GW still crashes?!
Now I am running out of ideas what to check?
Any ideas are highly apreciated!

krafzig · Aug 18, 2006, 09:45 PM // 21:45

I underclocked now with 1666MHz (before: 2083 MHz ).
CPU-Z said bus speed is 133MHz (before: 166MHz) and FSB 266MHz (before 333MHz)
But the problem continues...
Is it woth trying othe memory chips?

Amy Awien · Aug 19, 2006, 06:01 AM // 06:01

Maybe not, if you can borrow one, you could try. But keep in mind that all the focus on memory is because of a message grom GW. You don't know why that foucesses on memory and temperature, for all we know, they found those to be the problem in 9/10 cases ... and yours could be the 10th...