Curse

ne33us · Aug 14, 2009, 08:09 AM // 08:09

I bet 20.000 gold coins on the PSU(s).

http://forums.extremeoverclocking.co...d.php?t=325517

rb.widow · Aug 14, 2009, 11:20 AM // 11:20

Quote:

Originally Posted by ne33us

I bet 20.000 gold coins on the PSU(s).

http://forums.extremeoverclocking.co...d.php?t=325517

I agree, in all my time troubleshooting hardware faults and building systems, complete random shutdowns point to a faulty PSU.

Elder III · Aug 14, 2009, 01:41 PM // 13:41

Quote:

Originally Posted by rb.widow

I agree, in all my time troubleshooting hardware faults and building systems, complete random shutdowns point to a faulty PSU.

aye - but if the OP did indeed check it with both PSUs on their own that would seem to rule it out. If this happens with GW only then I'm thinking it's a firewall/anti-virus thing - or perhaps it does indeed need to be forced to run on 1 core.

Also, even if you don't have an extra set of RAM - you can take one DIMM out and test it with just one DIMM (either 1-2 GB depending on your system) at a time.

Divinus Stella · Aug 14, 2009, 02:14 PM // 14:14

If it only happens in GW then its a compatability issue.

The most likely causes are graphics drivers, sound drivers and your quad core.

Someone already mentioned the quad core issue, just do as they said and assign GW to run from core 0, if that doesn't fix it then delete all your sound and video drivers and get some new ones installed.

If you have a creative sound card then throw it in the bin and go back to using onboard sound, it will save you years of hassle.

GoneRebel · Aug 14, 2009, 06:32 PM // 18:32

first off, thanks for the help. second, i tried making it all but one core, and it still shut down, just took a little bit longr to do it. And my cpu is 4 physical cores 8 logical, so i tried running it on all 8 cores and it still did it. I run ad-aware ( www.adaware.com ) bi-weekly, and i have some personal firewalls yes, i turned off the firewalls, but i dont think that should have any effect. MB might be it, but i picked this one out specifically cause it was supposedo to be tougher. weird. anyways, thanks for your help, if i run it on one core i can get more time out of it.

rb.widow · Aug 14, 2009, 10:50 PM // 22:50

If this was software related, drivers etc, the event viewer would pick it up and record it before the crash, as the interrupt would be there before the hard crash itself,

If the event viewer does not record anything under application as an error, this is hardware related.

Do you overclock your system?
What operating system do you run?

Also if you can, download 3dmark06 and run that, this will put your system under more stress than GW can, if it can make it threw this programs benchmark on a loop of say 5 times, then its purely GW related, if it cannot, you have a hardware fault.

GoneRebel · Aug 14, 2009, 11:49 PM // 23:49

well, i downloaded 3dmark06 and ran it, but personally, i dont think its a hardware issue. i mean, it seems that way, but i can run everquest II on one monitor and WoW on the other. and ahve no problem at all. I just think theres a hiccup in the guild wars installation or something

DarkRazzie · Aug 15, 2009, 01:43 AM // 01:43

Did you try reinstalling GW? I know people hate to do that, but if nothing else works?

If this ONLY happens when you run GW, it seems only logical to me that 1, you have a bad installation, or 2, you can't run GW with your current configuration. You're sitting here saying that you can run this on one monitor and that on the other at the same time and it doesn't shut off on you. Absolutely sounds like a GW issue.

I have a better question for you: Were you running it with no problems before? If so, what all have you done with your system since it last ran fine? Did this happen after a recent update to GW? All things to think about.

Good luck

GoneRebel · Aug 15, 2009, 01:49 AM // 01:49

@ darkrazzle, nah , i just got guildwars like 1 month ago, and i just started playing it for the first time, ( i know lol can u believe it?) and yeah, another person suggested i try it on my other hard-drive, so i reinstalled it on the other one, and it still happens. and, no, i have never tried running it on two monitors at once