Curse

Dex · Apr 25, 2007, 05:44 PM // 17:44

Quote:

Originally Posted by Kuldebar Valiturus

I agree: I don't think the problem has necessarily been solved.

=================================================
To the OP:
Removing your originally reported PC problem from your first post doesn't help others with possibly similar issues very much.
=================================================

AS I noted earlier "RAM freeing" utilities can often create some of these issues as well.

Additionally, bad RAM is not the only reason that will cause a PC to spontaneously reboot, but it surely is a common one.

If the OP had access to another stick of 512 MB RAM, he should swap out the original RAM with the newer stick and run his "BSOD" test a few times.. This way he can see if his problem goes away.

Otherwise, adding the newer RAM will just make the reboot happen less often...but the cause/defect will still be there.

There's still the chance the video card and RAM interaction could have been the source of the issue as well.

Time will tell, or more likely a newer PC will make it a problem no longer.

This is true. In light of the change in behavior after changing the memory configuration I'd lean toward it being a RAM problem, but I suppose that's still an assumption and not 100% conclusive.

Still, though, I think the next logical step for the OP is to run Memtest86+.

4LzH31MeR · Apr 27, 2007, 10:42 AM // 10:42

Thanks ppl... I will run the test : )

Hah i downloaded the iso but how do i boot it? I used daemon tools to mount it

Dex · Apr 28, 2007, 06:36 PM // 18:36

Quote:

Originally Posted by 4LzH31MeR

Thanks ppl... I will run the test : )

Hah i downloaded the iso but how do i boot it? I used daemon tools to mount it

Well, since Daemon Tools only works once you're already in Windows that's not going to work. Memtest86+ needs to run with nothing else in memory, and that includes Windows. You need to actually create a boot floppy diskette or a boot CD-ROM and boot your computer from it. You can't use it from Windows at all.

Nundkai · May 08, 2007, 01:49 PM // 13:49

i got a 2 maybe 3 year old laptop that meets the system requirements and for example

lays wow and bfme2 nicely , the laptop was reinstalled half a year ago so the driver shouldnt show any problems, can it be a problem only affecting guildwars?

cebalrai · May 08, 2007, 04:00 PM // 16:00

This problem almost certainly has not been fixed. All it did was give your computer more resources to cope with broken hardware.

And editing your top post like that was a bad idea. Makes everything less helpful.

Este Beat Down · May 11, 2007, 06:17 PM // 18:17

Hey all.

I was actually looking for a thread that might have a similar problem that I am encountering. I have read everything here and I am pretty sure this is where I need to be, although I can't be totally sure because the creator of this deleted the original problem with a "Thank You" message. That kind of irritated me...

Anyways, please let me know if this where I need to be. Ahem...

I recently upgraded my computer to a WinFast MB, 256mb NVidia GeForce FX 5500 video card, 1G RAM and 2.2ghz Athlon XP Processor. I did this for the sole purpose of playing Guild Wars again. However, things have not been so great.

Guild Wars has no problem booting up, and it runs real smooth on its lowest graphical settings, however every so often (about 5 times during a 3 hour session) the game will crash to desktop. Along with the crash will come an error message stating that a serious error has occured and the game had to be closed. I am then prompted to send an error report to ArenaNet.

The stinker though, is that sometimes instead of getting that error message, I will instead be treated to the blue screen crash error message that you all referred to above (exact one). This is especially irritating as I have to reboot on this one.

When I updated all the drivers (sound and video), the problem just got worse, therefore I just rolled them back.

Funny thing is though, I don't seem to have too much problems playing games like Command & Conquer 3. I get a few freezes ever now and then (game will freeze up for about 5 seconds then start again, though once it did freeze entirely), but I haven't been crashed to desktop yet.

Any thoughts?