Crash immediately entering FOTM

Crash immediately entering FOTM

in Account & Technical Support

Posted by: Shifu.4321

Shifu.4321

I immediately crash during the loading screen of FOTM, any level. I haven’t done FOTM in a couple of months, and joined to help a guildie, but I am unable to join my party due to crashing immediate upon entering.

Here’s the details:

—> Crash <—
Fatal Error: Fatal disk-error (23) on read,
App: Gw2.exe
Pid: 2488
Cmdline: -isRelaunch
BaseAddr: 00400000
ProgramId: 101
Build: 24043
When: 2013-09-29T08:27:41Z 2013-09-29T16:27:41+08:00
Uptime: 0 days 0:01:30
Flags: 0

—> System <—
Name: PC1
IpAddr: 192.168.0.102
Processors: 2 [GenuineIntel:6:7:6]
OSVersion: Windows 5.1 (32 bit)

—> System Memory <—
Physical: 1628MB/ 3583MB 45%
Paged: 3543MB/ 5465MB 64%
Virtual: 748MB/ 2047MB 36%
Load: 54%
CommitTotal: 1921MB
CommitLimit: 5465MB
CommitPeak: 3549MB
SystemCache: 1628MB
HandleCount: 14609
ProcessCount: 49
ThreadCount: 631

—> Process Memory <—
Private: 940MB
WorkingSet: 749MB
PeakWorkingSet: 939MB
PageFaults: 324012

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

—> ThreadPoolFile01 Thread 0xbd4 <—

—> Trace <—
Pc:00d22c47 Fr:0296fe08 Rt:006dfe95 Arg:0138d870 0000020e 0138d8c4 00000017
Pc:006dfe95 Fr:0296fe40 Rt:006e10cf Arg:03332260 033321e0 0dceb9b0 030a2020
Pc:006e10cf Fr:0296fe58 Rt:006e1379 Arg:00000017 00000000 0296fe84 006e3f60
Pc:006e1379 Fr:0296fe68 Rt:006e3f60 Arg:0dceb9b0 00000000 030a2020 00000000
Pc:006e3f60 Fr:0296fe84 Rt:006e27c6 Arg:0dceb9b0 00000000 030a2020 030a2060
Pc:006e27c6 Fr:0296ff2c Rt:006e28b1 Arg:033321e0 000003e8 0296ff54 030a2060
Pc:006e28b1 Fr:0296ff4c Rt:006e2915 Arg:00000000 7c80e63b 02b368b0 006e1f0f
Pc:006e2915 Fr:0296ff70 Rt:0094e8dd Arg:02b368b0 1ceeab1c 7c80e63b 02224b18
Pc:0094e8dd Fr:0296ffa8 Rt:0094e985 Arg:02b363c4 0296ffec 7c80b699 02224b18
Pc:0094e985 Fr:0296ffb4 Rt:7c80b699 Arg:02224b18 7c80e63b 02b363c4 02224b18
Pc:7c80b699 Fr:0296ffec Rt:00000000 Arg:0094e903 02224b18 00000000 49474542

—> Thread registers <—
eax=0296f8d8 ebx=00000000 ecx=00000000 edx=0000003c esi=00000000 edi=00000003
eip=00d22c47 esp=0296fcec ebp=0296fe08
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246

eax-32 0296F8B8 7c97e178 7c91928d 01508ab4 02224b18
eax-16 0296F8C8 0000ffff 7ffdf000 002535d8 006e7ba5
eax 0 0296F8D8 80000003 00000000 00000000 7c812a6b
eax
16 0296F8E8 00000002 00000002 1052a730 00000280
eax+32 0296F8F8 00000000 0000003c 0296fc60 0296f9e0
eax+48 0296F908 0296f92c 00952693 0296f9e0 00000000

—> Code <—
00D22C27 c5d39aff 8b450c6a 0050568d 95fcfeff …..E.j.PV…..
00D22C37 ffb90300 0000c785 f8feffff 00000000 …………….
00D22C47 e874519c ff8b4dfc 33cd5ee8 c290c2ff .tQ…M.3.^…..
00D22C57 8be55dc3 cccccccc cc535657 b9b05d7c ..]……SVW..]|
00D22C67 01e8d3bb 9bff8b1d 80456c01 8b3d7845 ………El..=xE
00D22C77 6c0133c0 b9b05d7c 01a37845 6c01a37c l.3…]|..xEl..|

Crash immediately entering FOTM

in Account & Technical Support

Posted by: Lexandro.1456

Lexandro.1456

The first line of the crash log states a fatal disc error “on read”. In my experience that normally indicates damaged data files. I suggest your run a repair command on the launcher.

If you are having problems running Guild Wars 2, the data archive may have become corrupted. Please follow these steps to verify and repair the archive:

Locate your Gw2.exe file.
Right-click on the file and select Create shortcut.
Rename this new shortcut to Guild Wars 2 Repair.
Right-click on Guild Wars 2 Repair and select Properties.
Locate the Target line and add -repair to the end.
Example: “C:\Games\Guild Wars 2\gw2.exe” -repair
Click OK.

Double-clicking Guild Wars 2 Repair will begin the repair process. The game will launch when it is complete.

Note: Keep in mind that the verification and repair process will run each time you double-click the Guild Wars 2 Repair shortcut. If you would like to play the game immediately without repairing the archive, double-click on Gw2.exe or another shortcut without the -repair command