gw.exe error?
Puddingbroodje
i got this error 3 times within 5 minutes... all the time i get this error i am in prophecies. this time i was in Tombs of Primevall kings.
Yesterday i got these errors also when i was in Sorrow's Furnace.
Anyone else has this isues?
system:
Windows Vista SP1 (Ultimate)
2048 Ram (2gb)
AMD Athlon X2 3800+
SATA Maxtor 200gb
Nvidia 8800GT 512
Covah
try -image? see if your data archive is corrupt?
Puddingbroodje
-image works fine i do that everytime there is an update.
i got this error 4 times followed with an BSOD
i only get this when i play GW.
i got this error 4 times followed with an BSOD
i only get this when i play GW.
Chthon
Who sees two cores? I see two cores!
GW is not stable on multiple cores. Force it to one core. See if that fixes it.
GW is not stable on multiple cores. Force it to one core. See if that fixes it.
Puddingbroodje
and how am i supposed to do that? In the BIOS?
I don't think it's a core problem imo..
but a little side question: Is it usefull to send the error to anet? (Send report to ArenaNet) or are they never gonna look at it?
I don't think it's a core problem imo..
but a little side question: Is it usefull to send the error to anet? (Send report to ArenaNet) or are they never gonna look at it?
FiftyFiveD
i had a gw.exe problem previously and reported it to Anet and they successfully helped me out w/n a few days.....
Covah
[QUOTE=Puddingbroodje]and how am i supposed to do that? In the BIOS?
/QUOTE]
CTRL ALT DLT go to processes, rightclick on gw.exe, set affinity, and only have one core checked.
I run 2 cores and GW is fine for me.
/QUOTE]
CTRL ALT DLT go to processes, rightclick on gw.exe, set affinity, and only have one core checked.
I run 2 cores and GW is fine for me.
Puddingbroodje
i reinstalled GW and after a long wait of -image i tried it again.
With a little bit of succes, gw now crashes now and then without the gw.exe error, and when i tried to force gw to use 1 core i had no crashes. *knocks on wood*
With a little bit of succes, gw now crashes now and then without the gw.exe error, and when i tried to force gw to use 1 core i had no crashes. *knocks on wood*
Puddingbroodje
Update:
The gw.exe error is back....
The gw.exe error is back....
Brianna
Quote:
Originally Posted by Puddingbroodje
i reinstalled GW and after a long wait of -image i tried it again.
With a little bit of succes, gw now crashes now and then without the gw.exe error, and when i tried to force gw to use 1 core i had no crashes. *knocks on wood* |
For example on my windows XP pro I can't run it on two cores, I get problems, but on the same computer with Vista Ultimate 64 bit I get smooth performance on two.
Snograt
Yeah, we've been here before. Sometimes it's happy with 2 cores, sometimes it's happy with 4 cores, sometimes it insists on only one. It's all down to many variables - combination of components. As far as we can tell, at least.
Give it a try - set the affinity to one core as above, if it does work, there's your problem. If it doesn't, then we start to look for other possible causes.
If it does turn out to be a multi-core problem, it's time to get ForceCore which has the same effect but means you don't need to do it manually every time. (The Ctrl-Alt-Del version is a one-shot - GW will revert to running on all available cores next boot. Oh, and it's Shift-Ctrl-Esc nowadays )
Give it a try - set the affinity to one core as above, if it does work, there's your problem. If it doesn't, then we start to look for other possible causes.
If it does turn out to be a multi-core problem, it's time to get ForceCore which has the same effect but means you don't need to do it manually every time. (The Ctrl-Alt-Del version is a one-shot - GW will revert to running on all available cores next boot. Oh, and it's Shift-Ctrl-Esc nowadays )
Puddingbroodje
i get the gw.exe error on dual core as well on one core so i don't think that is the problem.
Snograt
Hum.
Well, one thing that springs to mind is that, just because you regularly -image the .dat, it doesn't mean that it isn't corrupt. You may wish to delete your .dat, install the latest one you have on disc (the one on EotN would be the most recent) and then do an -image.
Failing that, post the entire crash log - not just the little bit we can see above. Someone with more tech savvy than me might see what is actually causing the crash.
Well, one thing that springs to mind is that, just because you regularly -image the .dat, it doesn't mean that it isn't corrupt. You may wish to delete your .dat, install the latest one you have on disc (the one on EotN would be the most recent) and then do an -image.
Failing that, post the entire crash log - not just the little bit we can see above. Someone with more tech savvy than me might see what is actually causing the crash.
Puddingbroodje
i will do that!
but this isn't funny anymore, just a minute ago i got an BSOD with the message:
IRQL_NOT_LESS_OR_EQUAL
i can remember this as a memory error, am i right?
but i only get this when i play GW, when i play another game like UT i can play it for hours without any errors.
but this isn't funny anymore, just a minute ago i got an BSOD with the message:
IRQL_NOT_LESS_OR_EQUAL
i can remember this as a memory error, am i right?
but i only get this when i play GW, when i play another game like UT i can play it for hours without any errors.
Snograt
Quote:
Originally Posted by Microsoft
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS. If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. |
If we go with the MS version, have you recently upgraded to Vista, or has your system always had Vista? If the latter, have you recently installed SP1? I know I had it myself recently, but I'm not sure what caused it, although virus scanner does ring a bell. ZoneAlarm for one is certainly struggling badly with Vista.
Chthon
Quote:
Originally Posted by Puddingbroodje
IRQL_NOT_LESS_OR_EQUAL
|
Solution:
First check for an IRQ conflict. Don't always trust Windows that there's no conflict on a shared IRQ -- your video card and sound card probably can't share an IRQ, no matter what Windows thinks. If you find a dubious configuration, you'll have to uninstall and physically remove components and reshuffle the order you install in and what goes in which slot until plug-n-play comes up with a workable configuration.
Second, assuming no actual IRQ conflicts, then you need to find the buggy driver. Try updating all your drivers (maybe the problem is already fixed by an updated driver). If that doesn't help, you'll have to uninstall and remove things one at a time until you figure out which device is causing the problem. Then live without that device until a fixed driver is released.
(@Snogorat: It's possible that bad RAM (probably on the video card) or overheating could just happen to be corrupting data destined to become an IRQ signal in a way that mimics this error, but it's unlikely, and would probably also cause other noticeable (and constant) problems if it were happening.)
Puddingbroodje
Quote:
Originally Posted by Snograt
I have seen elsewhere that IRQL_NOT_LESS_OR_EQUAL can be caused by overheating processors or bad memory, not sure how true that is, though.
If we go with the MS version, have you recently upgraded to Vista, or has your system always had Vista? If the latter, have you recently installed SP1? I know I had it myself recently, but I'm not sure what caused it, although virus scanner does ring a bell. ZoneAlarm for one is certainly struggling badly with Vista. |
Edit:
here is my DxDiag Log:
http://puddingbroodje.nl/DxDiag.txt
i think is similar to the text from the error.
Snograt
The dxdiag log just shows what hardware you have and which drivers, etc. That error log would show what actually failed. (I learned several new Dutch words from that log however, I'm particularly fond of USB-hoofdhub
)
I think that it is likely an SP1 problem, and that something that was perfectly happy working with Vista suddenly isn't. It's a problem that is only happening while GW is running which complicates matters somewhat. Cthon's solution sounds spot on to me - I'd go with that.
It is odd how many problems we see that only occur when GW is running - it's natural to assume GW itself is at fault, but it seems that it often isn't. Maybe GW makes calls to odd places that can cause conflicts? I dunno, I'm just theorising here.
)
I think that it is likely an SP1 problem, and that something that was perfectly happy working with Vista suddenly isn't. It's a problem that is only happening while GW is running which complicates matters somewhat. Cthon's solution sounds spot on to me - I'd go with that.
It is odd how many problems we see that only occur when GW is running - it's natural to assume GW itself is at fault, but it seems that it often isn't. Maybe GW makes calls to odd places that can cause conflicts? I dunno, I'm just theorising here.
Chthon
Quote:
Originally Posted by Snograt
It is odd how many problems we see that only occur when GW is running - it's natural to assume GW itself is at fault, but it seems that it often isn't. Maybe GW makes calls to odd places that can cause conflicts? I dunno, I'm just theorising here.
|
Puddingbroodje
and that is the whole "problem" i only get it when i play Guild Wars.
I can play UT2k4 for hours without any problems.
I can play UT2k4 for hours without any problems.
gone
is there a .txt file in your GW folder named ArenaNet? if so, that will have the crash details in it as well.
Puddingbroodje
Quote:
Originally Posted by flubber
is there a .txt file in your GW folder named ArenaNet? if so, that will have the crash details in it as well.
|
http://puddingbroodje.nl/ArenaNet.txt
Snograt
Not an expert at deciphering crash dumps, but it looks like issues with textures. Now to ME, that means a corrupt .dat, but it could also be down to overheating?
What do you say, people-with-more-knowledge-than-me?
What do you say, people-with-more-knowledge-than-me?
Puddingbroodje
yeah i think that to, there is 1 crash log in that file and the rest are all errors with the textures, but i already reinstalled GW so the .dat file is new.
KartMan
I think I've had this issue on my old computer, and I think it was due to overheating, you might want to check the fans/heatsinks on your motherboard/cpu/graphic card
Dark Kal
Try running GW with the -dx8 and/or -noshaders command line and see if it still crashes.
http://guildwars.wikia.com/wiki/Command_line
http://guildwars.wikia.com/wiki/Command_line
Snograt
I thought of -dx8 and -noshaders too. Problem is, if that does cure the problem, your graphics are going to be so shite you're going to want to upgrade anyway
Puddingbroodje
Quote:
Originally Posted by Snograt
I thought of -dx8 and -noshaders too. Problem is, if that does cure the problem, your graphics are going to be so shite you're going to want to upgrade anyway
|
Snograt
Oh dear. Maybe "replace under warranty" was the phrase I was looking for.
Dark Kal
Quote:
Originally Posted by Snograt
I thought of -dx8 and -noshaders too. Problem is, if that does cure the problem, your graphics are going to be so shite you're going to want to upgrade anyway
|
To the OP you aren't running DirectX10 by any chance are you?
Puddingbroodje
Quote:
Originally Posted by Dark Kal
They're diagnostic commands. I'm not suggesting he runs his game with those commands forever it just helps determine the problem. If that solves the problem he will know DirectX is causing the crashes.
To the OP you aren't running DirectX10 by any chance are you? |
Edit:
I played Assassins Creed for 2,5 hours non-stop without any problems..
Snograt
Reading through that log, it covers 4 different crashes over the course of 4 days. One is certainly missing textures (cos it says so ), but googling others leads to people who had faulty RAM, faulty RAM sockets or even mismatched RAM pairs.
You might want to check your memory.
You might want to check your memory.
Puddingbroodje
I've done some research on the internet and came to the conclusion that Vista and Nvidia are not always compatible with each other.
i have downloaded the beta drivers and ik hope that solves it. (i also did a BIOS upgrade, just in case).
i have downloaded the beta drivers and ik hope that solves it. (i also did a BIOS upgrade, just in case).
Dark Kal
Quote:
Originally Posted by Snograt
Reading through that log, it covers 4 different crashes over the course of 4 days. One is certainly missing textures (cos it says so ), but googling others leads to people who had faulty RAM, faulty RAM sockets or even mismatched RAM pairs.
You might want to check your memory. |
Snograt
Hmm, again I'm not an expert, BUT... Guild Wars has often given problems to people who run other games without a hitch. It seems to reach parts of the OS/hardware that other games just cannot reach
They should use GW as a benchmark: If it can run GW, it can run anything!
They should use GW as a benchmark: If it can run GW, it can run anything!
Dark Kal
Quote:
Originally Posted by Snograt
Hmm, again I'm not an expert, BUT... Guild Wars has often given problems to people who run other games without a hitch. It seems to reach parts of the OS/hardware that other games just cannot reach
They should use GW as a benchmark: If it can run GW, it can run anything! |
Puddingbroodje
did the memtest already and resulting in nothing...
10 min ago i got a BSOD with the error:
nvlddmkm.sys
Click for image
10 min ago i got a BSOD with the error:
nvlddmkm.sys
Click for image
Snograt
Argh. That's an nVidia driver issue. Researched it a bit and found hundreds of similar tales of woe on forums all over the internet. No absolute fix on any of them. Take a look at this ten page thread as an example - http://www.ocforums.com/showthread.php?t=518749
Certainly make sure your nVidia drivers are the latest WHQL ones - don't trust betas, unless you read in their release notes that they contain a fix for your specific problem
Interestingly, it seems that nVidia drivers with the same issue numbers can be different depending on source, that is from nVidia themselves or from Microsoft Update. Not sure how true that is, but I was having a lot of problems with my 8800GTX setup until I allowed Vista to install drivers that replaced my nVidia ones. No problems since.
Certainly make sure your nVidia drivers are the latest WHQL ones - don't trust betas, unless you read in their release notes that they contain a fix for your specific problem
Interestingly, it seems that nVidia drivers with the same issue numbers can be different depending on source, that is from nVidia themselves or from Microsoft Update. Not sure how true that is, but I was having a lot of problems with my 8800GTX setup until I allowed Vista to install drivers that replaced my nVidia ones. No problems since.
Puddingbroodje
now i'm justing getting BSOD with no error, just " STOP " and a row of numbers (hexa?)
but i get them randomly, when i browse youtube of playing a game, doesn't matter.
but i get them randomly, when i browse youtube of playing a game, doesn't matter.
Dark Kal
If you're getting random BSODs that would imply faulty RAM. Replace your RAM memory sticks if you can. Could be a driver issue as Snograt said too.