Crash after server selection - Technical Support - WarpPortal Community Forums

Jump to content


Photo

Crash after server selection


  • Please log in to reply
8 replies to this topic

#1 noizmakaz

noizmakaz

    I am New.

  • New Members
  • 6 posts

Posted 12 November 2017 - 04:34 AM

Hi all,

 

This seems to be a problem that has existed for years and looks like there is no solution for it, atleast I cannot see any threads where the suggested actions have helped to solve the issue. My issue is that once I have selected the a server and clicked enter, the loading screen pops up for a second and then the client gets closed automatically. The log file shows the following:

 

[Procedure Infomation]
Version=10.2.0.14, Nov  7 2017-10:17:22, EB
ProcessID=3756
ThreadID=584
Date="2017/11/12 15:09:54"

[Exception Information]
ExceptionDescription="EXCEPTION_ACCESS_VIOLATION"
ExceptionCode=C0000005
ExceptionAddress=0023:3844AEEF
ModuleName=C:\Gravity\Dragon Saga\Release\PhysXCore.dll
AccessViolationReason=Read
AccessViolationlocation=00000004

[Register Information]
EAX=024AA228
EBX=04714304
ECX=019D86A4
EDX=00BC6E00
ESI=4714E398
EDI=024AA21C
EBP=00000000
ESP=019D8590
EIP=3844AEEF
FLG=00010202
CS=0023
DS=002B
SS=002B
ES=002B
FS=0053
GS=002B

[Call Stack Information]

 

My PC has an i7-4790 CPU and AMD R270X GPU and Windows 7, if that matters. Also the things I've tried to solve the issue:

 

1) Disable hyper-threading

2) Download the client from here - https://forums.warpp...rupted-message/

3) Install newest Physx

 

Any other suggestion what exactly is causing this issue and how to fix it?

Regards,

Noiz


  • 0

#2 Popcorn

Popcorn

    Woodie-Holic

  • Dragon Saga Staff
  • 5556 posts
  • LocationGermany, Europe, Earth, Milky Way, Universe
  • Playing:Dragon Saga

Posted 12 November 2017 - 04:50 AM

Then you are doing something wrong this solution definitely works perfectly fine because your stack trace shows what the problem is: one or more of the 3d model files have been corrupted by patching. Because of this the data are wrong and physx can't create physics objects from the corrupted loaded files (crash in PhysXCore.dll).

 

Make sure you copy over the files to the right location and overwrite the old ones. Don't do the Steam integrity check afterwards if playing from steam. Check if you are overwriting the right version of the game. Many people have multiple installations of the game (for example when they re-installed to a different location or just copied the version from a friend). Also if the game patches again something went wrong. 

 

  • 0

#3 noizmakaz

noizmakaz

    I am New.

  • New Members
  • 6 posts

Posted 12 November 2017 - 05:29 AM

I'm not using Steam for this game.

 

I've made sure that I do not have any other copies of the game installed. I now re-downloaded, installed and updated it through the patcher. After that I tried to log in - same result. I then also re-downloaded the files mentioned in the link above and copied them to the install directory - in the end, same result.

 

I can't imagine what I could possibly do wrong here. Am I perhaps missing some software or an update related to it?


  • 0

#4 noizmakaz

noizmakaz

    I am New.

  • New Members
  • 6 posts

Posted 15 November 2017 - 12:08 PM

Whatever the reason was, after formatting and installing windows 10, everything seems to work without issues...


  • 0

#5 Popcorn

Popcorn

    Woodie-Holic

  • Dragon Saga Staff
  • 5556 posts
  • LocationGermany, Europe, Earth, Milky Way, Universe
  • Playing:Dragon Saga

Posted 15 November 2017 - 12:25 PM

I am glad to here that it is working for you now. :)

 


  • 0

#6 noizmakaz

noizmakaz

    I am New.

  • New Members
  • 6 posts

Posted 20 November 2017 - 09:46 AM

I'm back!

 

Not sure how this is even possible, but the same problem has come up, again. From the moment that I last launched the client and played (which was today, like 40 min ago) I got disconnected from the server and now that I try to login I get the same problem as described earlier - after server selection the client starts loading and then closes. I haven't updated/installed/deleted anything, so how can this physx error come up again which Popcorn earlier said was related to corrupted files...

 

I did try downloading again the files from here (https://forums.warpp...rupted-message/) and replace the old ones, didn't help.

 

I will get a new graphics card soon (nvidia instead of the old amd), but I doubt that will solve the issue.

 

Regards,
Noiz


  • 0

#7 Popcorn

Popcorn

    Woodie-Holic

  • Dragon Saga Staff
  • 5556 posts
  • LocationGermany, Europe, Earth, Milky Way, Universe
  • Playing:Dragon Saga

Posted 20 November 2017 - 10:34 AM

Did you ever add the game's exe / folder to the exceptions of your anti-virus / firewall solution?

 


  • 0

#8 noizmakaz

noizmakaz

    I am New.

  • New Members
  • 6 posts

Posted 20 November 2017 - 01:44 PM

There's no anti-virus installed, other than Windows Defender. There seem to be some differences though in the logs, not sure if those show anything, although prior to the second log I added the firewall expcetion for patcher and client exe:

 

[Procedure Infomation]
Version=10.2.0.15, Nov 14 2017-23:11:21, EB
ProcessID=6132
ThreadID=3988
Date="2017/11/21 00:34:16"

[Exception Information]
ExceptionDescription="EXCEPTION_ACCESS_VIOLATION"
ExceptionCode=C0000005
ExceptionAddress=0023:1548AEEF
ModuleName=C:\Gravity\Dragon Saga\Release\PhysXCore.dll
AccessViolationReason=Read
AccessViolationlocation=00000004

[Register Information]
EAX=06356778
EBX=063ECED4
ECX=008484AC
EDX=02044000
ESI=28BC8130
EDI=0635676C
EBP=00000000
ESP=00848398
EIP=1548AEEF
FLG=00010206
CS=0023
DS=002B
SS=002B
ES=002B
FS=0053
GS=002B

 

and

 

[Procedure Infomation]
Version=10.2.0.15, Nov 14 2017-23:11:21, EB
ProcessID=1840
ThreadID=6788
Date="2017/11/21 00:37:46"

[Exception Information]
ExceptionDescription="EXCEPTION_ACCESS_VIOLATION"
ExceptionCode=C0000005
ExceptionAddress=0023:2B2FAEEF
ModuleName=C:\Gravity\Dragon Saga\Release\PhysXCore.dll
AccessViolationReason=Read
AccessViolationlocation=00000004

[Register Information]
EAX=06475438
EBX=0650CED4
ECX=022F8304
EDX=0201A000
ESI=38EF3030
EDI=0647542C
EBP=00000000
ESP=022F81F0
EIP=2B2FAEEF
FLG=00010202
CS=0023
DS=002B
SS=002B
ES=002B
FS=0053
GS=002B


  • 0

#9 noizmakaz

noizmakaz

    I am New.

  • New Members
  • 6 posts

Posted 21 November 2017 - 12:36 PM

Since I just installed W10, I thought I'd do it again as it's not hard. A fresh windows install with few updates seems to work just fine, atleast for now.

 

What I noticed however about the previous W10 install was that there were some updates done before the problems started again, so all I can think of is that the client's files somehow get in conflict with Windows, if it makes sense. For now I've disabled automatic updating to see whether the problem will come back.


  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users