[Known]Shroud crashing to desktop on login

Upgraded computer recently and no longer able to get on shroud past the login screen for multiplayer

Checked drivers (multiple versions), RAM(multiple frequencies), uninstalled, Compatibility mode, running as Administrator and all failed.

Eventually @Alcedes remoted in to help figure out the problem and was able to login to single player offline in 64 bit, but could not login to multiplayer.

He reconfigured settings to 32 bit and was then able to login to multiplayer online.



System Info:
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.14393 N/A Build 14393
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
Registered Owner: Windows User
Registered Organization:
Product ID: 00330-80000-00000-AA011
Original Install Date: 3/10/2017, 2:07:18 PM
System Boot Time: 3/11/2017, 2:23:16 AM
System Manufacturer: To Be Filled By O.E.M.
System Model: To Be Filled By O.E.M.
System Type: x64-based PC
Video Card: Nvidia GeForce GTX 1080
Processor(s): 1 Processor(s) Installed.
[01]: AMD64 Family 23 Model 1 Stepping 1 AuthenticAMD ~3600 Mhz
BIOS Version: American Megatrends Inc. P1.20, 2/24/2017
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: (UTC-05:00) Eastern Time (US & Canada)
Total Physical Memory: 16,337 MB
Available Physical Memory: 10,769 MB
Virtual Memory: Max Size: 19,281 MB
Virtual Memory: Available: 13,234 MB

Error Info (Event viewer)

Log Name: Application
Source: Application Error
Date: 3/11/2017 2:57:54 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Description:
Faulting application name: Shroud of the Avatar.exe, version: 5.4.4.40123, time stamp: 0x58972e63
Faulting module name: ntdll.dll, version: 10.0.14393.479, time stamp: 0x5825887f
Exception code: 0xc0000005
Fault offset: 0x0000000000030bdd
Faulting process id: 0x550
Faulting application start time: 0x01d29a3d237e3945
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\SotA\Shroud of the Avatar.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: e56907ad-0396-4cb3-83e3-697001d2d60f
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-11T07:57:54.230255000Z" />
<EventRecordID>1330</EventRecordID>
<Channel>Application</Channel>
<Security />
</System>
<EventData>
<Data>Shroud of the Avatar.exe</Data>
<Data>5.4.4.40123</Data>
<Data>58972e63</Data>
<Data>ntdll.dll</Data>
<Data>10.0.14393.479</Data>
<Data>5825887f</Data>
<Data>c0000005</Data>
<Data>0000000000030bdd</Data>
<Data>550</Data>
<Data>01d29a3d237e3945</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\SotA\Shroud of the Avatar.exe</Data>
<Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
<Data>e56907ad-0396-4cb3-83e3-697001d2d60f</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

 

i remember a long time ago when the devs would actually pop into these threads and ask questions and acknowledge the problems. boy i miss those times. :'(

 

This is happening to me today as well.

 

Does it launch in Single Player Offline but crash when attempting to do multiplayer? And if so, were you able to get multiplayer working by flippin it over to 32 bit?

 

I only do single player online so I am sorry I cannot help you there. I did not try the flipping over to 32 bit.

 

so single player online would be part of "multiplayer" mode. Try launching in Single Player Offline and see if it lets you in.

 

will do!

 

This is a known Unity engine issue with AMD CPUs. We are upgrading to a new version of Unity this release and are constantly working toward solutions. Thank you for reporting.

 

Is there a fix or some kind of workaround for it? Or are they just kinda boned for now?

 

I've recently upgraded to Ryzen R1700, and is encountering the same issue.

How do i convert my client to 32bits so that i can continue playing?

 

At the moment, we do not have an official workaround. We believe that R40 with the upgraded version of Unity will resolve this issue, and look forward to the results that will come out of our early Dev+ QA test experience.