Guild Wars 2

I recently purchased a Samsung Pro 850 256 Gb and GW2 couldn’t be launched from it. I tried downloading a new game client but it still gave me the same error. Is there a way to solve this? Thank you

If you have problems and want help, why can’t you at least post the error you get ?

Also more information is better .. what hardware you use, what OS, what drivers and so on.

I doubt the new hard drive has anything to do with it. I would make sure you didn’t bump any of the ram and make sure the video card is properly seated. It would help if we new the error.

I have another intel ssd in my pc which I can run GW2 from it with no problem. It’s just that this samsung ssd is what I’m having problems with. I don’t know how to fix this. Did anyone of you had the same problem?

I’m currently using this model of SSD (Samsung 850 Pro, 256 GB), and GW2 runs fine. Your problem might be caused by some other component.

When you tried downloading it did you uninstall it from the other drive.? Also what is the error you are getting?

This is the detailed error log that I am getting:

Assertion: hdr->signature == PACKFILE_SIGNATURE
File: ..\..\..\Services\Packfile\Packfile.cpp(1926)
App: Gw2.exe
Pid: 5016
Cmdline:
BaseAddr: 00FD0000
ProgramId: 101
Build: 46704
When: 2015-03-31T04:53:30Z 2015-03-31T00:53:30-04:00
Uptime: 0 days 0:00:00
Flags: 0

—> System <—
Name: MARK-PC
IpAddr: 10.0.0.20
Processors: 12 [GenuineIntel:6:14:4]
OSVersion: Windows 6.1 (64 bit)

—> System Memory <—
Physical: 14620MB/16322MB 89%
Paged: 14758MB/16521MB 89%
Virtual: 3879MB/ 4095MB 94%
Load: 10%
CommitTotal: 1762MB
CommitLimit: 16521MB
CommitPeak: 1920MB
SystemCache: 746MB
HandleCount: 19076
ProcessCount: 61
ThreadCount: 966

—> Process Memory <—
Private: 72MB
WorkingSet: 70MB
PeakWorkingSet: 82MB
PageFaults: 89091

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

—> AssetWorkerCpu0 Thread 0×1164 <—

—> Trace <—
Pc:01465ac7 Fr:05f5f820 Rt:01466819 Arg:00000003 00200cb4 08c80030 00000000
Pc:01466819 Fr:05f5f848 Rt:01466753 Arg:08c80030 00000000 00000000 00000004
Pc:01466753 Fr:05f5f864 Rt:01446a8f Arg:08c80030 00000076 0a9d5750 0a9d5560
Pc:01446a8f Fr:05f5f888 Rt:014470f2 Arg:05f5f8d4 05f5f8c8 05f5f8bc 05f5f8e0
Pc:014470f2 Fr:05f5f8ec Rt:0143bdd0 Arg:03f53db0 03f5e9b0 03f5e9b0 01340f5e
Pc:0143bdd0 Fr:05f5f910 Rt:0147edd8 Arg:03f53db0 bac4039c 00000000 03f5e9b0
Pc:0147edd8 Fr:05f5f948 Rt:0147ef00 Arg:00000000 05f5f960 74f33677 03f5e9b0
Pc:0147ef00 Fr:05f5f954 Rt:74f33677 Arg:03f5e9b0 05f5f9a0 77189d72 03f5e9b0
Pc:74f33677 Fr:05f5f960 Rt:77189d72 Arg:03f5e9b0 72d2bfe5 00000000 00000000
Pc:77189d72 Fr:05f5f9a0 Rt:77189d45 Arg:0147ee84 03f5e9b0 00000000 00000000
Pc:77189d45 Fr:05f5f9b8 Rt:00000000 Arg:0147ee84 03f5e9b0 00000000 00000000

—> Thread registers <—
eax=05f5f3dc ebx=08c80030 ecx=00000000 edx=000002c8 esi=74f31b42 edi=00000000
eip=01465ac7 esp=05f5f7f8 ebp=05f5f820
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246

eax-32 05F5F3BC 00000000 fffffd34 000002e4 fffffd34
eax-16 05F5F3CC 000002cc 00000019 00000000 05f5f3dc
eax 0 05F5F3DC 80000003 00000000 00000000 75b7b727
eax16 05F5F3EC 00000002 00000002 06674bd0 00000000
eax+32 05F5F3FC 00000000 00000000 00000000 00000000
eax+48 05F5F40C 00000000 00000000 00000000 00000000
ebx-32 08C80010 00201000 00201000 2b3bc0f2 04000000
ebx-16 08C80020 00000000 00000000 00200cb4 08c80020
ebx 0 08C80030 00000000 00000000 00000000 00000000
ebx16 08C80040 00000000 00000000 00000000 00000000
ebx+32 08C80050 00000000 00000000 00000000 00000000
ebx+48 08C80060 00000000 00000000 00000000 00000000
esi-32 74F31B20 f3094025 90909074 ff8b9090 5dec8b55
esi-16 74F31B30 909005eb ff909090 f30b8425 90909074
esi 0 74F31B40 ff8b9090 5dec8b55 909005eb ff909090
esi16 74F31B50 f30d9025 90909074 90909090 90909090
esi+32 74F31B60 0424448b 3878c00b 0824548b 880fd20b
esi+48 74F31B70 000000b2 4c8be2f7 c90b0c24 00e6880f

have you try making a shortcut to the new GW2 instillation and add the -repair command line

Yes I already did the shortcut repair methid but no luck still. I also disconnected all my other drives and ran samsung ssd with gw2 installed in it and still did not work; however, when I ran my intel ssd and made a gw2 shortcut from where the game was installed in my samsung ssd, the game would run fine.

Perhaps the shortcut is trying to run the game from your other ssd try downloading the game like its a new instal from the website