Curse

Joker · May 20, 2005, 08:47 AM // 08:47

Well im glad to know its not just my compter thats having this problem. It seems to me that the system memory isnt clearing properly.

Kyokuji · May 20, 2005, 05:18 PM // 17:18

I think you may be on to something there.
Occasionally the errors I get when it doesn't reboot say something about memory read error.

whsper99 · May 20, 2005, 07:52 PM // 19:52

*chuckle* Mojo... I got the exact same msg word for word from them... hehe umm.. odd how those guys seem to think alike... *cough*

Test programs cook my card... GW... does not

Joker · May 20, 2005, 08:16 PM // 20:16

Quote:

Originally Posted by Kyokuji

I think you may be on to something there.
Occasionally the errors I get when it doesn't reboot say something about memory read error.

Ive run several memory tests, reformatted my computer, and updated all of my drivers and everything cheks out ok so I am fairly certain that this problem is being caused by GW being incompatable with AMD systems. Has anyone heard of a pentium based system having these problems?

gabby2600 · May 20, 2005, 09:30 PM // 21:30

Quote:

Originally Posted by Kyokuji

I think you may be on to something there.
Occasionally the errors I get when it doesn't reboot say something about memory read error.

I get those to< think their is an issue where GW is trying to write to a part of the memeory resrevel fir windows. Somwthings it catches it's self other times wondows beats it to it and shows us that lovely shade of blue.

Joker · May 21, 2005, 01:45 AM // 01:45

Quote:

Originally Posted by gabby2600

I get those to< think their is an issue where GW is trying to write to a part of the memeory resrevel fir windows. Somwthings it catches it's self other times wondows beats it to it and shows us that lovely shade of blue.

Either way something is definately going on with the system memory

Kyokuji · May 21, 2005, 06:15 AM // 06:15

You should send them a report about this.
"I get those to< think their is an issue where GW is trying to write to a part of the memeory resrevel fir windows. Somwthings it catches it's self other times wondows beats it to it and shows us that lovely shade of blue."

I like how they still think it's just our system's problem when this topic has over 9000 page views.

Svenn · May 21, 2005, 07:28 AM // 07:28

I said this quite a while back, and I'll say it again: the anecdotal evidence strongly suggests memory (de)allocation and access violation errors in some implementions of GW x hardware configuration. Unfortunately, those errors are notoriously difficult to debug in an app as large as GW. I am fairly sure the devs have some people working full time on this, but NCSoft is being very tight-lipped about publicly admitting to any problems with the code (with the exception of a few vague emails from the 1st-tier support team).

W O R M W O O D · May 21, 2005, 08:44 AM // 08:44

I end up having the same rebooting/restarting probs but not immediately. I can play well up to 5 hours maybe, but eventually GW takes a pooper. When I zone into a town, I notice textures are incomplete, capes are not complete, players are holographic, etc. Eventually my mouse pointer turns to a discolored block or white boxes appear over areas where Ive used a skill. Strange thing is that for a while I can window in/out of GW and the anomolies subside...for a while.

Eventually I get a blue or red screen that I can/can't window out of. If I cant then I restart GW, sometimes I get re-booted, but every day it *will* reboot. I can run any game at any settings at any time...except this one. I have de-fragged, scanned, spywared, virused, un-overclocked, clean installed drivers, whatever. Same problem. GW is to blame.

System Specs:

AMD Athlon XP 2800+ Barton
1024 Apacer DDR
ASUS A7N8X-E Deluxe
E-VGA GeForce 6800 Ultra
Antec 550 Watt TrueBlue PS
Maxtor 120 gig HD

Kyokuji · May 21, 2005, 02:07 PM // 14:07

Have you sent them that suggestion Svenn?

whsper99 · May 21, 2005, 05:02 PM // 17:02

I have just reinstalled windows .... again... since I had been crashing so much I figured... what the heck. When I was uninstalling programs just before I slicked my HD.. I noticed that the Microsoft Spyware Beta program had an issue with GW... just curious if anyone else has noticed this... since I have reinstalled and I have NOT installed the MS spyware program... I have been able to play for about 4 hours and counting... which is about 3 hours and 30 min longer than ever before but things do seem to be running fine for me now.

aeroclown · May 21, 2005, 07:23 PM // 19:23

Thats intresting, what kind of problem did it have ?

Did it just not recognize it as a normal ap. Wanted permission ?

I have it running on my laptop and I havn't had any notices or anything from it.

whsper99 · May 21, 2005, 09:22 PM // 21:22

It said something about a script violation... however.. I crashed again a few hours ago... but that was after playing for about 4 and a half hours.. so the jury is still out

Svenn · May 22, 2005, 02:37 AM // 02:37

Quote:

Originally Posted by Kyokuji

Have you sent them that suggestion Svenn?

No, they currently have volumes of more specific evidence (Remedy tickets, error logs, etc.) to analyze than the speculations that I could offer, and gamers are reporting three to four day delays to receive even canned responses from the 1st tier support team. In other words, I don't want to waste their time with something that I'm fairly certain that they are already feverishly working on.

I did think that I had something concrete to report with the new Audigy2 drivers' problem that I posted about, but, so far, no one has posted that they replicated the issue.

Vors Khedrus · May 22, 2005, 05:12 AM // 05:12

Im having the reboots and the 'failure reading memory location blah blah blah' on a gigabyte board with a intel 1.8gz processor, so its not AMD specific.

Gristy · May 22, 2005, 01:53 PM // 13:53

Hey Guys me too. i have had the CD Version and the Client Version.

Get lots of crashes when in windowed mode the one that says detected a error and loads the web page..

also had two times where it said coudlnt read memory

had one time where it rebooted (full screen)

and one time where it just completely froze teh pc (windowed).

Really sucks as i like the game quite a bit

Specs:
AMD 3500+ 64bit
Shuttle SN25P
Zalman USB Snd Crd
ATI X800XL

ShadeZeRO · May 22, 2005, 09:39 PM // 21:39

Me too, i get kicked out right of way..somethin about memory instructions i think is messing it up...

anyone tried messing with the pagefile?

i too get memory access violation at fffff or something of that nautre...

Draikin · May 22, 2005, 11:03 PM // 23:03

Quote:

Originally Posted by wonderworm

Wel that's weird, since your problem description exactly fits mine. Let your brother switch to windowed mode when the problems occur again. Then just keep the game running. It probably will take some more time but finally it will crash, too. That's when i got a real bluescreen instead of a blank one.

Well, you're right. After switching to windowed mode it did crash with a real bluescreen this time (also stating the problem was caused by ati3duag.dll). This basically means it's indeed the exact same problem. I looked at your hardware specs to see if there's anything similar, and you also have an AMD processor, an ATI card, a NForce based chipset (here its the Nforce 4 though, not NF2) and you're also running dual channel memory. Anyone else having the same problem (meaning: the sound disappears and there's a white multicolored block around the cursor shortly before you get a BSOD)?

Rhine · May 22, 2005, 11:17 PM // 23:17

Well from all these post with the same problem that i have been reading they all have SP2 maybe there is still problems with game and SP2 i remeber people in my clan having problems running Cod with it so maybe that is cuasing some conflicts If you have pro you can system restore back to before it if you have home bad luck cuz you will have to reformat to get rid of it :/

Kyokuji · May 22, 2005, 11:25 PM // 23:25

It's not service pack 2, I don't have it.
And I'm running on a pentium 4 processor on an SiS chipset, so it's not strictly an AMD/nForce problem.

Quote:

i too get memory access violation at fffff or something of that nautre

Yeah, that's the exact same error I get.
It happens generally anytime, but it seems to occur most often at the log-in screen and in pre-searing Ascalon.

Sometimes, I start to see white boxes around certain players shortly before the reboot, sometimes I don't.

And don't tell people to reformat, tons of people have tried that already, and it still reboots.
It seems to be a memory related issue, not a matter of what's on your HD.