Has stopped working » Forum Post by FatIgor2

sdrohan

Join Date 10/2012

+635

Quoting ,

quoting post

Was working last time I played, which was a couple of months ago.

I assume I now have the new update, and it doesn't start, just get a popup box saying

"The application was unable to start correctly (0xc0000142)

Click OK to close the application."

Downloaded the test version and that is exactly the same.

Tried rebooting as well.

Please do a full uninstall, reboot, reinstall, and let us know the results.

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

Same result.

Also installed on my laptop which has not had it on it, same result.

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+635

Quoting FatIgor2,

reply 2

Same result.

Also installed on my laptop which has not had it on it, same result.

See if reinstalling the redists helps:

https://aka.ms/vs/17/release/vc_redist.x64.exe

Reboot \ retry after and let us know, please.

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

Just want to confirm that you're running the Epic Client when you're trying to start the game as well right? What's the default language your PCs are set to? Shouldn't impact the game starting, but it's good to have as much info as we can gather about this.

Check your log file location for Sins2, should be C:\Users\%username%\AppData\Local\sins2\logs
and try to get us the most recent log file in the directory. If it's empty, you may be having some sort of operating system issue.

You should be able to share the file with us through OneDrive, Google Drive, or another file sharing service. Could always fallback to sharing it via pastebin. Just some thoughts here.

Successfully updated karma reason!

No log files. Oldest one is about 4 weeks old when it still worked.

The vc_redist made no difference.

There is a brief mention in the launcher logs

[2024.02.29-18.45.15:766][309]FCommunityPortalLaunchAppTask: Preparing to launch app 'D:/Epic Games/SinsII/sins2.exe' with commandline ' -AUTH_LOGIN=unused -AUTH_PASSWORD=<it was a password> -AUTH_TYPE=exchangecode -epicapp=77ecfd3c08c340aab57b8033e31a4875 -epicenv=Prod -EpicPortal -epicusername="FatIgor" -epicuserid=073f4f56e9144002ba94b0717180ef63 -epiclocale=en -epicsandboxid=24285307a56445f1bc5d546df7af3025'

[2024.02.29-18.45.15:766][309]FCommunityPortalLaunchAppTask: Launching app 'D:/Epic Games/SinsII/sins2.exe' with commandline ' -AUTH_LOGIN=unused -AUTH_PASSWORD=<hello fans> -AUTH_TYPE=exchangecode -epicapp=77ecfd3c08c340aab57b8033e31a4875 -epicenv=Prod -EpicPortal -epicusername="FatIgor" -epicuserid=073f4f56e9144002ba94b0717180ef63 -epiclocale=en -epicsandboxid=24285307a56445f1bc5d546df7af3025'

[2024.02.29-18.45.15:768][309]LogRunningAppService: Display: New foreground process [3220] D:/Epic Games/SinsII/sins2.exe for app D:\Epic Games/SinsII

[2024.02.29-18.45.15:768][309]LogRunningAppService: Display: New foreground app D:\Epic Games/SinsII

[2024.02.29-18.45.15:769][309]LogRunningAppPresenceHandler: Display: No foreground apps with monitored presence: clearing override presence

[2024.02.29-18.45.22:491][702]LogRunningAppService: Display: Dead foreground process [3220] D:/Epic Games/SinsII/sins2.exe for app D:\Epic Games/SinsII

[2024.02.29-18.45.22:492][702]LogRunningAppService: Display: App D:\Epic Games/SinsII moved from foreground to dead

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+635

I am a bit out of my depth here (with Sins troubleshooting) but...

Use Winkey + R and past this in:

%AppData%\Local\

Find the 'sins2' directory and rename it to sins2.old

Try to run the game. If it failed, is a new 'sins' directory created in \AppData\Local?

Sean Drohan
Stardock Product Lifecycle Manager

+1

Successfully updated karma reason!

I've also encountered such a situation, the operating system is win11. But on my win10 notebook, it works fine.

Successfully updated karma reason!

游戏无法启动，并且无法在此位置生成 sin 文件夹。

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+635

Quoting pnpxx2290,

reply 7

I've also encountered such a situation, the operating system is win11. But on my win10 notebook, it works fine.

Quoting pnpxx2290,

reply 8

The game fails to launch, and a sin folder cannot be generated in this location.

There are a few suggestions here, please review them, try them, and let us know your results.

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

Please also make sure you've got your mods disabled if you're using them.

Successfully updated karma reason!

I'm having the same issue with Sins 2 - neither test edition or regular will load for me from the epic store with the same error:

Deleting the folder appdata folder doesnt make a difference, no log gets generated to review.

Running windows 11, latest nvidia drivers etc.

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+635

Quoting Spiffington,

reply 11

I'm having the same issue with Sins 2 - neither test edition or regular will load for me from the epic store with the same error:

Deleting the folder appdata folder doesnt make a difference, no log gets generated to review.

Running windows 11, latest nvidia drivers etc.

Is this new, meaning, it once ran fine but now does not... or no, its never worked?

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

Sadly this is new - I last played in January 2024 I believe and the game ran perfectly. Now in March I have this issue; have tried reinstalling the game and deleting temp files etc. My hardware hasn't changed since then, just usual windows and graphics driver updates.

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+635

Quoting Spiffington,

reply 13

Sadly this is new - I last played in January 2024 I believe and the game ran perfectly. Now in March I have this issue; have tried reinstalling the game and deleting temp files etc. My hardware hasn't changed since then, just usual windows and graphics driver updates.

While 'sad' indeed, its actually good news as we can work from a 'what changed' point of view.

Did you also try:

See if reinstalling the redists helps:

https://aka.ms/vs/17/release/vc_redist.x64.exe

Reboot \ retry after and let us know, please.

Sean Drohan
Stardock Product Lifecycle Manager

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

True, I know the game updated a couple of times since last time I got it to load successfully.

I did try installing that redist and restarting etc, didn't seem to make any difference to the error message that I get .

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+635

What, if anything, shows up in Windows Event Viewer\ Windows Logs \ Applications for the issue.

If something is there, copy \ paste the entry here

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

I also recommend trying to run the game in administrator mode once. That seems to fix this issue in many cases with other games from my own googling.

Successfully updated karma reason!

Quoting Unikraken,

reply 17

I also recommend trying to run the game in administrator mode once. That seems to fix this issue in many cases with other games from my own googling.

This doesn't seem to make a difference, same error message.

Nothing too helpful in the windows event I think, but here it is anyway:

Log Name: Application

Source: Application Error

Date: 30/03/2024 17:40:15

Event ID: 1000

Task Category: Application Crashing Events

Level: Error

Keywords:

User: CCO\<myname>

Computer: CCO

Description:

Faulting application name: sins2.exe, version: 1.20.9.0, time stamp: 0x65f35c60

Faulting module name: ntdll.dll, version: 10.0.26090.1, time stamp: 0x8b19f0a7

Exception code: 0xc0000005

Fault offset: 0x0000000000012c30

Faulting process id: 0xBF8

Faulting application start time: 0x1DA82C953164C63

Faulting application path: C:\Program Files\Epic Games\SinsIITesting\sins2.exe

Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

Report Id: 454d429c-c1ed-4ca1-96e7-c78363d8ce44

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" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />

<EventID>1000</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>100</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000000</Keywords>

<TimeCreated SystemTime="2024-03-30T17:40:15.7750384Z" />

<EventRecordID>416</EventRecordID>

<Correlation />

<Execution ProcessID="20900" ThreadID="13776" />

<Channel>Application</Channel>

<Computer>CCO</Computer>

<Security UserID="S-1-5-21-3559463869-1330231773-2596112881-1001" />

</System>

<EventData>

<Data Name="AppName">sins2.exe</Data>

<Data Name="AppVersion">1.20.9.0</Data>

<Data Name="AppTimeStamp">65f35c60</Data>

<Data Name="ModuleName">ntdll.dll</Data>

<Data Name="ModuleVersion">10.0.26090.1</Data>

<Data Name="ModuleTimeStamp">8b19f0a7</Data>

<Data Name="ExceptionCode">c0000005</Data>

<Data Name="FaultingOffset">0000000000012c30</Data>

<Data Name="ProcessId">0xbf8</Data>

<Data Name="ProcessCreationTime">0x1da82c953164c63</Data>

<Data Name="AppPath">C:\Program Files\Epic Games\SinsIITesting\sins2.exe</Data>

<Data Name="ModulePath">C:\WINDOWS\SYSTEM32\ntdll.dll</Data>

<Data Name="IntegratorReportId">454d429c-c1ed-4ca1-96e7-c78363d8ce44</Data>

<Data Name="PackageFullName">

</Data>

<Data Name="PackageRelativeAppId">

</Data>

</EventData>

</Event>

Log Name: Application

Source: Windows Error Reporting

Date: 30/03/2024 17:40:18

Event ID: 1001

Task Category: None

Level: Information

Keywords:

User: CCO\

Computer: CCO

Description:

Fault bucket , type 0

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: sins2.exe

P2: 1.20.9.0

P3: 65f35c60

P4: ntdll.dll

P5: 10.0.26090.1

P6: 8b19f0a7

P7: c0000005

P8: 0000000000012c30

P9:

P10:

Attached files:

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ada9eb8f-31a2-43af-a438-c5bac844bb6e.tmp.mdmp

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5589125b-b970-4e43-8db3-3fa05544ea8f.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_sins2.exe_4e5e0a0725918ee30cf7d14deff96d81cd08324_73584e51_cab_674bc49b-b006-4bf4-8e9c-9adae47f7aa3\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20240329_1_EC_0_inject.etl

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.da9777d4-5296-484f-9525-f10c234a6b64.tmp.etl

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_sins2.exe_4e5e0a0725918ee30cf7d14deff96d81cd08324_73584e51_cab_674bc49b-b006-4bf4-8e9c-9adae47f7aa3\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.2e3c9076-a4e5-4ac1-9c15-2c826a6b0a6d.tmp.etl

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7acb2308-8ae0-42f9-a295-de6536120c06.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.fb6b44b9-9065-4f36-8c0d-ab373c354776.tmp.txt

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.eb54ecb1-1328-4b30-8755-ef4114cc4db9.tmp.xml

\\?\C:\Users\callu\AppData\Local\Temp\WER.76b49943-3064-4d5a-831e-64d3e11eaaee.tmp.appcompat.txt

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_sins2.exe_4e5e0a0725918ee30cf7d14deff96d81cd08324_73584e51_cab_674bc49b-b006-4bf4-8e9c-9adae47f7aa3\memory.hdmp

These files may be available here:

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_sins2.exe_4e5e0a0725918ee30cf7d14deff96d81cd08324_73584e51_cab_674bc49b-b006-4bf4-8e9c-9adae47f7aa3

Analysis symbol:

Rechecking for solution: 0

Report Id: 454d429c-c1ed-4ca1-96e7-c78363d8ce44

Report Status: 4

Hashed bucket:

Cab Guid: 0

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Windows Error Reporting" Guid="{0ead09bd-2157-539a-8d6d-c87f95b64d70}" />

<EventID>1001</EventID>

<Version>0</Version>

<Level>4</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000000</Keywords>

<TimeCreated SystemTime="2024-03-30T17:40:18.2283713Z" />

<EventRecordID>417</EventRecordID>

<Correlation />

<Execution ProcessID="20900" ThreadID="13776" />

<Channel>Application</Channel>

<Computer>CCO</Computer>

<Security UserID="S-1-5-21-3559463869-1330231773-2596112881-1001" />

</System>

<EventData>

<Data Name="Bucket">

</Data>

<Data Name="BucketType">0</Data>

<Data Name="EventName">APPCRASH</Data>

<Data Name="Response">Not available</Data>

<Data Name="CabId">0</Data>

<Data Name="P1">sins2.exe</Data>

<Data Name="P2">1.20.9.0</Data>

<Data Name="P3">65f35c60</Data>

<Data Name="P4">ntdll.dll</Data>

<Data Name="P5">10.0.26090.1</Data>

<Data Name="P6">8b19f0a7</Data>

<Data Name="P7">c0000005</Data>

<Data Name="P8">0000000000012c30</Data>

<Data Name="P9">

</Data>

<Data Name="P10">

</Data>

<Data Name="AttachedFiles">

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ada9eb8f-31a2-43af-a438-c5bac844bb6e.tmp.mdmp

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5589125b-b970-4e43-8db3-3fa05544ea8f.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_sins2.exe_4e5e0a0725918ee30cf7d14deff96d81cd08324_73584e51_cab_674bc49b-b006-4bf4-8e9c-9adae47f7aa3\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20240329_1_EC_0_inject.etl

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.da9777d4-5296-484f-9525-f10c234a6b64.tmp.etl

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_sins2.exe_4e5e0a0725918ee30cf7d14deff96d81cd08324_73584e51_cab_674bc49b-b006-4bf4-8e9c-9adae47f7aa3\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.2e3c9076-a4e5-4ac1-9c15-2c826a6b0a6d.tmp.etl

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7acb2308-8ae0-42f9-a295-de6536120c06.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.fb6b44b9-9065-4f36-8c0d-ab373c354776.tmp.txt

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.eb54ecb1-1328-4b30-8755-ef4114cc4db9.tmp.xml

\\?\C:\Users\callu\AppData\Local\Temp\WER.76b49943-3064-4d5a-831e-64d3e11eaaee.tmp.appcompat.txt

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_sins2.exe_4e5e0a0725918ee30cf7d14deff96d81cd08324_73584e51_cab_674bc49b-b006-4bf4-8e9c-9adae47f7aa3\memory.hdmp</Data>

<Data Name="StorePath">\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_sins2.exe_4e5e0a0725918ee30cf7d14deff96d81cd08324_73584e51_cab_674bc49b-b006-4bf4-8e9c-9adae47f7aa3</Data>

<Data Name="AnalysisSymbol">

</Data>

<Data Name="Rechecking">0</Data>

<Data Name="ReportId">454d429c-c1ed-4ca1-96e7-c78363d8ce44</Data>

<Data Name="ReportStatus">4</Data>

<Data Name="HashedBucket">

</Data>

<Data Name="CabGuid">0</Data>

</EventData>

</Event>

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+635

That error typically indicates something is up with Windows:

Error code 0xc0000142 typically appears in Windows environments and indicates that an application failed to initialize properly. This error can occur for various reasons, including corrupted or missing system files, compatibility issues between the application and the operating system, problems with the application itself, or issues related to permissions.

Here are some common scenarios where you might encounter this error:

1. **Launching a Program**: When trying to open a software application, the program might fail to start, and Windows displays the error message with code 0xc0000142.

2. **After a Windows Update**: Sometimes, after installing Windows updates, certain applications might not launch due to compatibility issues or changes in the system that affect the application's operation.

3. **Corrupted System Files**: If essential Windows system files are damaged or missing, it can prevent applications from starting, resulting in this error.

4. **Compatibility Issues**: Applications not designed for your version of Windows might not run correctly and could produce this error.

5. **Insufficient Permissions**: If the user account doesn't have the necessary permissions to run the application, Windows might display this error.

To resolve error 0xc0000142, you can try several approaches:

- **Run the Application as an Administrator**: Right-click the application's shortcut and select "Run as administrator" to provide it with the necessary permissions.

- **Compatibility Mode**: Right-click the application's shortcut, go to Properties, then the Compatibility tab, and select a previous version of Windows that the application supports.

- **Update or Reinstall the Application**: Ensure you have the latest version of the application. If the error persists, try uninstalling and then reinstalling the application.

- **Check for Windows Updates**: Make sure your Windows is up to date, as updates can provide fixes for known issues that might be causing the error.

- **System File Checker (SFC) Scan**: Run the System File Checker tool to repair missing or corrupted system files. Open Command Prompt as an administrator and type `sfc /scannow` then press Enter.

https://support.microsoft.com/en-us/windows/using-system-file-checker-in-windows-365e0031-36b1-6031-f804-8fd86e0ef4ca

- **Clean Boot**: Perform a clean boot to start Windows with a minimal set of drivers and startup programs. This can help you determine if background programs are interfering with the application.

https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!