Client crashes: Memory at address 00000000 could not be read

Client crashes: Memory at address 00000000 could not be read

in Account & Technical Support

Posted by: Leroynidus.3528

Leroynidus.3528

Q:

I recently purchased the game from a retailer, installed it, and every time I open Gw2.exe it tries to patch, and then inevitably crashes. The error log is in the post below. These are the things I have tried to fix/locate the problem:
Ran program as administrator (for all users)
Disabled all security software (I use AVG Free)
Disabled all background applications
Ran Gw2.exe -repair
Installed GW2 on another hard drive
Ran program in Safe Mode with networking
Ran a chkdsk – no errors
Ran a Disk Defrag
Ran a memtest – no errors
Submitted a ticket with GW2 support, have not heard back from them in almost 2 days.

My system runs great, I have never had any problems like this with other games.
Any help would be appreciated, it’s frustrating to spend $60 on a game, and not be able to play it :(

(edited by Leroynidus.3528)

Client crashes: Memory at address 00000000 could not be read

in Account & Technical Support

Posted by: Leroynidus.3528

Leroynidus.3528

—> Crash <—
Exception: c0000005
Memory at address 00000000 could not be read
App: Gw2.exe
Pid: 4976
Cmdline:
BaseAddr: 00400000
ProgramId: 101
Build: 15459
Module: ntdll.dll
When: 2012-09-07T13:59:01Z 2012-09-07T09:59:01-04:00
Uptime: 0 days 0:00:09
Flags: 0

—> System <—
Name: CHRIS-HP
IpAddr: 192.168.0.8 192.168.0.7
Processors: 6 [AuthenticAMD:15:10:0]
OSVersion: Windows 6.1 (64 bit)

—> System Memory <—
Physical: 5565MB/ 8191MB 67%
Paged: 12609MB/16380MB 76%
Virtual: 773MB/ 4095MB 18%
Load: 32%
CommitTotal: 3771MB
CommitLimit: 16380MB
CommitPeak: 4109MB
SystemCache: 2158MB
HandleCount: 29461
ProcessCount: 72
ThreadCount: 1386

—> Process Memory <—
Private: 923MB
WorkingSet: 166MB
PeakWorkingSet: 166MB
PageFaults: 67601

[DbgHelp.dll is C:\Windows\system32\dbghelp.dll]
[DbgHelp.dll version 6.1.7601.17514 (64/32-bit compatible)]

—> Thread 0×17c0 <—

—> Trace <—
Pc:77d8b6d8 Fr:3721e01c Rt:77d83cee Arg:000001ce 000001d8 38ac00c4 d7f40040
Pc:77d83cee Fr:3721e0a0 Rt:3788622e Arg:38ac0000 00000000 000001ce 000000e7
Pc:3788622e Fr:3721e0c0 Rt:378760c6 Arg:000001ce 38cbbfa8 3721e788 3721e77c
Pc:378760c6 Fr:3721e130 Rt:90222041 Arg:00000000 00000000 01bc8e58 01c6d638
Pc:90222041 Fr:3721e134 Rt:00000000 Arg:00000000 01bc8e58 01c6d638 01bc96b0

—> Thread registers <—
eax=d7f40048 ebx=38ac0000 ecx=00000000 edx=00000000 esi=d7f40040 edi=38ac0000
eip=77d8b6d8 esp=3721df4c ebp=3721e01c
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010282

eax-32 D7F40028 d8f10000 00000fce 00000001 00000000
eax-16 D7F40038 d7f41ff0 d7f41ff0 f70003f4 0001f133
eax 0 D7F40048 00000000 00000000 00000000 00000000
eax
16 D7F40058 00000000 00000000 00000000 00000000
eax+32 D7F40068 00000000 00000000 00000000 00000000
eax+48 D7F40078 00000000 00000000 00000000 00000000
ebx 0 38AC0000 9e7a692b 0100f13b ffeeffee 00000000
ebx
16 38AC0010 38ad0010 38ac00a8 38ac0000 38ac0000
ebx+32 38AC0020 00000010 38ac0588 38ad0000 00000000
ebx+48 38AC0030 00000001 00000000 38acfff0 38acfff0
esi-32 D7F40020 00000fd0 d7f40040 d8f10000 00000fce
esi-16 D7F40030 00000001 00000000 d7f41ff0 d7f41ff0
esi 0 D7F40040 f70003f4 0001f133 00000000 00000000
esi
16 D7F40050 00000000 00000000 00000000 00000000
esi+32 D7F40060 00000000 00000000 00000000 00000000
esi+48 D7F40070 00000000 00000000 00000000 00000000
edi 0 38AC0000 9e7a692b 0100f13b ffeeffee 00000000
edi
16 38AC0010 38ad0010 38ac00a8 38ac0000 38ac0000
edi+32 38AC0020 00000010 38ac0588 38ad0000 00000000
edi+48 38AC0030 00000001 00000000 38acfff0 38acfff0

(edited by Leroynidus.3528)

Client crashes: Memory at address 00000000 could not be read

in Account & Technical Support

Posted by: Leroynidus.3528

Leroynidus.3528

—> Code <—
77D8B6B8 e86b0000 008bf089 751485f6 0f844da8 .k……u…..M.
77D8B6C8 03008d46 088b1089 55b88b4e 0c894d98 …F….U..N..M.
77D8B6D8 8b098b52 043bca0f 85a1f804 003bc80f …R.;…….;..
77D8B6E8 8599f804 000fb706 2947788b 87b80000 ……..)Gx…..
77D8B6F8 0085c00f 84a984ff ff0fb73e 898544ff ………..>..D.
77D8B708 ffff8b48 043bf90f 82d7fdff ff8b1085 …H.;……….

—> Stack <—
3721DF4C 40ccf054 77d7e046 38ac035c 38ac0000 T..F..w\..8...8 3721DF5C 38ac0150 77d838be 38ac0138 77d8389a P..8.8.w8..8.8.w 3721DF6C 40ccf004 00000000 38ac0000 38aca3d0 ...…….8…8
3721DF7C 38ac9300 38ac0150 00000025 38b1bfe8 …8P..8%……8
3721DF8C 38ac0150 000000a5 38b1bfe8 0000003b P..8…….8;…
3721DF9C 02000002 38ac0000 38ac0150 0000029a …….8P..8….
3721DFAC 00000000 38ac2e98 00000000 0a000a00 …….8……..
3721DFBC 0a000a00 000000a5 00000000 000007ff …………….
3721DFCC 00000003 00000000 00000000 00000001 …………….
3721DFDC 00000000 00000002 38ac00c4 38ac00c4 ………..8…8
3721DFEC 00000000 0000003b 00000000 0100007f ….;………..
3721DFFC 38ac0000 01000000 3721df4c 3721db14 …8….L.!7..!7
3721E00C 3721e120 77dc71d5 003ad838 00000000 .!7.q.w8.:…..
3721E01C 3721e0a0 77d83cee 000001ce 000001d8 ..!7.<.w……..
3721E02C 38ac00c4 d7f40040 77d7e046 000001ce …8@…F..w….
3721E03C 38ac2a30 00000000 3721e084 0001201f 0*.8……!7. ..
3721E04C 3721e06c 00000010 00000000 7356457d l.!7……..}EVs
3721E05C 1549cc69 38cbbf50 3721e788 3721e77c i.I.P..8..!7|.!7
3721E06C 3721e77c 00000001 00000000 00000000 |.!7…………
3721E07C 3721e0d4 77d72260 00000000 000000ed ..!7`".w……..
3721E08C 77082f7d 00000003 00000000 000001d8 }/.w…………
3721E09C ffffffff 3721e0c0 3788622e 38ac0000 ……!7.b.7…8
3721E0AC 00000000 000001ce 000000e7 38ac2a30 …………0*.8
3721E0BC 3721e788 3721e130 378760c6 000001ce ..!70.!7.`.7….
3721E0CC 38cbbfa8 3721e788 3721e77c 3787a9f0 …8..!7|.!7…7
3721E0DC 00001a74 0a0fb8f0 000000e7 00000000 t……………
3721E0EC 1547e98e 00000000 0359e350 0a0fb8f0 ..G…..P.Y…..
3721E0FC 38cbbfa8 0359cf88 00000010 00000000 …8..Y………
3721E10C 3721e794 00000000 3721e788 3721e0ec ..!7……!7..!7
3721E11C 3721db10 3721ff6c 37884da0 15ec9fae ..!7l.!7.M.7….
3721E12C fffffffe 50000002 90222041 00000000 …….PA "…..
3721E13C 00000000 01bc8e58 01c6d638 01bc96b0 ….X…8…….
3721E14C 00000000 3721e0e4 00000000 3721e218 ……!7……!7
3721E15C 01c6d638 77d82ca9 01c6d638 00000000 8….,.w8…….
3721E16C 00000080 00000000 00000080 00000008 …………….
3721E17C 00000000 00000000 01002829 38cb00c4 ……..)(…..8
3721E18C 03567cb8 00000001 00000004 00000002 .|V………….
3721E19C 00000008 3721e160 0359d2a0 0359d29b ….`.!7..Y…Y.
3721E1AC 00000000 0008418c 03560000 0100000c …..A….V…..
3721E1BC 3721e104 76b40a91 3721e590 77dc71d5 ..!7…v..!7.q.w
3721E1CC 00000002 00000000 00000088 77d83cee ………….<.w
3721E1DC 3721e228 76b4443a 01bc0000 00100008 (.!7:D.v……..
3721E1EC 76b4457d 1554f051 00000000 01c04f14 }E.vQ.T……O..
3721E1FC 00000009 0a0f6e60 0a0f6efa 00000008 ….`n…n……
3721E20C 3721e220 0064260e 00000009 0a0e7510 .!7.&d……u..
3721E21C 0a0e75aa 00000008 3721e238 0064260e .u……8.!7.&d.
3721E22C 0a0e75aa 0a0fb911 00000008 3721e250 .u……….P.!7
3721E23C 00856128 00000008 0a0e7450 0a0fb919 (a……Pt……
3721E24C 0a0fb911 3721e270 3721e6ac 3721e6c0 ….p.!7..!7..!7
3721E25C 00000000 3721e6c0 3721e6bc 3721e738 ……!7..!78.!7
3721E26C 008439af 0a0fb91b 0a0e7450 00856c44 .9……Pt..Dl..
3721E27C 000000e7 0a0e7450 00856c56 0a0fb910 ….Pt..Vl……
3721E28C 3721e764 0a0e75a9 0a0e758d 0a0fb8f0 d.!7.u…u……
3721E29C 0a0fb919 3721e2c4 00004000 00000005 ……!7.@……
3721E2AC 00000000 00000000 3721e2b4 3721e2b5 ……….!7..!7
3721E2BC 00000005 00000000 3721e2c4 3721e2c5 ……….!7..!7
3721E2CC 000003d8 00000000 38313733 00003733 ……..371837..
3721E2DC e7006465 11cfab8b 8000a38c 92a1485f ed………._H..
3721E2EC 000003e9 00000001 00000000 00000000 …………….
3721E2FC 00000000 77d6f901 73566267 00001870 …….wgbVsp…
3721E30C 000013d0 00000000 00000000 3721e348 …………H.!7
3721E31C 0001203b 3721e338 00000010 00000000 ; ..8.!7……..
3721E32C 00000000 39420db0 3721e5d8 00000002 ……B9..!7….
3721E33C 77d6f901 73562ecf 00001870 77d6f901 …w..Vsp……w

—> DirectX Device Info <—
VendorId = 0×1002
DeviceId = 0×6739
Version = 8.17.0010.1140
Description = AMD Radeon HD 6800 Series
Compat = 0×00000000
VidMem = 752 MB

Client crashes: Memory at address 00000000 could not be read

in Account & Technical Support

Posted by: Drintar.1246

Drintar.1246

I notice your driver for your video card is from july. You may want to get the new one from august and the CAP file from Sep 4 and see if that solves it. May not but worth a shot.

Client crashes: Memory at address 00000000 could not be read

in Account & Technical Support

Posted by: Grammarye.3064

Grammarye.3064

Have you tried a full uninstall & downloading the client direct from the web & trying that one? Perhaps you’ve been very unlucky and got a corrupt install somehow?

If you haven’t pressed Call Target at least once today, please go press it now.

Client crashes: Memory at address 00000000 could not be read

in Account & Technical Support

Posted by: Leroynidus.3528

Leroynidus.3528

Thank you,
I thought my drivers were up to date, but I just tried to update them again. I also fully uninstalled and attempting to install it in a different directory from a fresh client from the web. I’ll keep you updated…

(edited by Leroynidus.3528)

Client crashes: Memory at address 00000000 could not be read

in Account & Technical Support

Posted by: assassinated.2870

assassinated.2870

ntdll errors mean you have a hardware error. It doesn’t mean your hardware is bad, it can be a coding issue (drivers), it can be a problem with how something is coded within the game, or it can be genuinely faulty hardware. Anything which results in your hardware going bonkers and crashing, basically. Unfortunately windows is not more specific than that, but maybe that will help for perspective? That can potentially include things like: game download being corrupted, running something in the background which is causing an issue, overheating your graphics card, etc.

Client crashes: Memory at address 00000000 could not be read

in Account & Technical Support

Posted by: draeath.8536

draeath.8536

Trying to read 0×0? Sounds like a pointer being used either without proper initialization or after “deleting” it.

Client crashes: Memory at address 00000000 could not be read

in Account & Technical Support

Posted by: Sarikano.9375

Sarikano.9375

If they try to read the address 0, then it was initialize correctly or set after it have been deleted. Otherwise it would try to access some random place that might be used by another program.

Client crashes: Memory at address 00000000 could not be read

in Account & Technical Support

Posted by: Moriturus sum.2069

Moriturus sum.2069

In my case I’m running a dual core Athlon 64 processor. That ‘memory could not be read’ error almost made me abandon the game.

In the end – and after trying and failing with the other solutions – this work-around seems to do it. Run in a window, and quickly minimize and resize whenever mem usage hits over 500k (this flushes some buffer – otherwise if you have low memory as I do, the memory leaks and eventually causes a crash).

Then it became clear that even with settings on ‘best performance’ the comp was struggling. Oddly enough the solution was to set the program’s affinity to CPU 0. (You do this by task manager by right-clicking on the process.) Obviously there’s a bug somewhere that can’t cope with dual-core athlon 64s. Not had a crash since.

Good luck!

Client crashes: Memory at address 00000000 could not be read

in Account & Technical Support

Posted by: abomally.2694

abomally.2694

Moriturus -

I use an Athlon 64 dual core CPU and have no issues with the game (FX-60 running at 2.8 Ghz) – other than 16 to 30 Fps in Lion’s Arch – which is to be expected with my system.

Client crashes: Memory at address 00000000 could not be read

in Account & Technical Support

Posted by: Stormcrow.7513

Stormcrow.7513

i7 3770k oc 4.5 H100i(push/pull) 8gb Corsair Dominator Asus P877V-LK
intel 335 180gb/intel 320 160gb WD 3TB Gigabyte GTX G1 970 XFX XXX750W HAF 932

Client crashes: Memory at address 00000000 could not be read

in Account & Technical Support

Posted by: Moriturus sum.2069

Moriturus sum.2069

abomally.2694 -

In my case, I suspect it’s not just the Athlon 64 dual core but the fact that this runs Win XP with just 2 gig of memory, so my rig is a borderline case anyway.

The ‘memory at xxxx could not be read’ error seems to have a wide variety of causes, but they come down to either faulty software/hardware or lack of resources. That’s why sometimes – for example – disabling sound works. It either frees up resources or there was an issue with the sound card.

In my case, setting affinity slows up the game – occasionally to below the minimum fps so in frantic firefights I drop frames. But it seems to allow my geriatric rig to cope. Previously switching between cores ended up with something getting ahead of itself and crashing the game.