Crash on Prologue: Rally to Maguuma cutscene

Crash on Prologue: Rally to Maguuma cutscene

in Account & Technical Support

Posted by: Hmmmmmmmmmmnmnmz.9623

Hmmmmmmmmmmnmnmz.9623

Hey,

This is my 3rd day trying to fix this problem with crash on cutscene before entering to Verdant Brink. I’ve tried every fix i’ve read on forums about similiar crashes, but none of them worked for me. Before heading to store to buy more RAM memory, Im wondering few things.

1) May the crash be caused by low RAM memory, because there’s no any fps lags or problems while playing rest of the HoT content. (I’ve also tried to teleport to a friend, who’s at Verdant Brink, but I heard I need to unlock masteries in that first story chapter)

2. GW2 crash report (See beyond) gives me error about bink2w32.dll and something about memory could not read. I read that bink2w32.dll is common problem for games, so I tried to download it to Windows/SysWOW64 folder and also to Guild Wars 2/bin. Im running Windows 64 bit. Anyone know if theres something more to do to bink2w32.dll than just download and put it to correct folder?

Things I also tried:
– Delete and reinstall GW2
– Update drivers
– Change GW2 graphics to “best performance”

Many people are having crash problems, but Im just thinking if its not something Anet could do and I need to figure it out myself. Im hoping theres someone who actually understands about this crash report.

Any advice welcome, thank u!

—> Crash <—
Exception: c0000005
Memory at address 00000000 could not be read
App: Gw2.exe
Pid: 2716
Cmdline:
BaseAddr: 00E30000
ProgramId: 101
Build: 54555
Module: bink2w32.dll
When: 2015-10-25T07:39:39Z 2015-10-25T09:39:39+02:00
Uptime: 0 days 0:03:05
Flags: 0

—> System <—
Name: JIMMS-1035027
IpAddr: 192.168.0.100
Processors: 4 [AuthenticAMD:15:1:2]
OSVersion: Windows 6.1 (64 bit)

—> System Memory <—
Physical: 12279MB/16321MB 75%
Paged: 28132MB/32640MB 86%
Virtual: 2562MB/ 4095MB 62%
Load: 24%
CommitTotal: 4508MB
CommitLimit: 32640MB
CommitPeak: 4685MB
SystemCache: 4137MB
HandleCount: 29237
ProcessCount: 73
ThreadCount: 1154

Crash on Prologue: Rally to Maguuma cutscene

in Account & Technical Support

Posted by: Inculpatus cedo.9234

Inculpatus cedo.9234

If you continue to have issues, you can contact the Tech CS Team, and provide your crash report via the ‘Support’ link above/below and ‘Submit a Request’ for assistance.

Usually, when things show up in ‘Module:’ in the crash report, they need to be removed/disabled/etc. because they are interfering with GW2. No idea if you can remove/disable that, though.

Note: You will not be able to provide the crash details until you respond to the first email from the Tech CS Team.

Good luck.

(edited by Inculpatus cedo.9234)

Crash on Prologue: Rally to Maguuma cutscene

in Account & Technical Support

Posted by: Hmmmmmmmmmmnmnmz.9623

Hmmmmmmmmmmnmnmz.9623

If you continue to have issues, you can contact the Tech CS Team, and provide your crash report via the ‘Support’ link above/below and ‘Submit a Request’ for assistance.

Usually, when things show up in ‘Module:’ in the crash report, they need to be removed/disabled/etc. because they are interfering with GW2. No idea if you can remove/disable that, though.

Note: You will not be able to provide the crash details until you respond to the first email from the Tech CS Team.

Good luck.

Thank you, i’ll keep that in mind. Actually I solved the problem by driving to my parent’s house, install HoT, and play the chapter which caused me the crash.

Their computer is much worse than mine, so I believe the error cant be caused by low RAM memory. After reading your reply, I deleted my downloaded bink2w32.dll(and also binkw32.dll which were already there) from C:\Windows\SysWOW64 and I haven’t met any other crashes while playing the HoT content(so far xD).

Hopefully this fixed my crashes. Thank you again!

Crash on Prologue: Rally to Maguuma cutscene

in Account & Technical Support

Posted by: Inculpatus cedo.9234

Inculpatus cedo.9234

You are most welcome! =)

That should take care of that particular crash issue.