Curse

Chuckman Joney · Dec 10, 2006, 11:41 PM // 23:41

When they updated GW liek 2 months ago they fixed it...

Now it returns...10 times in the past 4 mins

Arabian_Night · Dec 11, 2006, 12:55 AM // 00:55

Care to explain what it is?

dansamy · Dec 11, 2006, 01:03 AM // 01:03

That code is actually a hardware failure on your end. I had a similar error while playing Diablo 2. Specifically, only when I accessed the Catacombs waypoint. I tested everything in my system. I finally traced it to one bad stick of RAM. I RMA'ed that RAM and got a replacement, reinstalled D2 and never had any further troubles. I reccommend downloading Memtest and starting there.

Linda Heartilly · Dec 12, 2006, 10:29 AM // 10:29

Quote:

Originally Posted by dansamy

That code is actually a hardware failure on your end.

Lol?

With all respect, that is really one of the worst assumptions I ever heard of.

0xC0000005 is the constant STATUS_ACCESS_VIOLATION which could indicate any memory operation failing with no error handling and it is possibly one of the most commonly encountered errors ever on the Win32 subsystem.

If you want to know why it's happening, your best lead to start with is the memory offset where the error occurred.
In most cases you should be able to find this in the log file of error dumps locating in your Guild Wars installation folder.