Some BSOD's and games crashing and only working after restart till it repeats.

K

Krawchuk

Member
Joined
Feb 11, 2020
Posts
9
Hello,

As the title states, I get a rare occurrence of BSOD and games crashing after a certain amount of time.
I was able to get a dump file of one of the games that crashed and was wondering if anyone can take a look into it.
Some games include: Tera: Fate of Arun, Final Fantasy XI (11) and Distance.
I am willing to provide more information on anything required to help get this issue fixed.

xiloader.rar

I have compressed the dump file into a rar file just for simplicity's sake. I created the dump file from the windows task manager, then after some failed attempts at trying to read it myself, I thought I should leave it to people who know what they are doing.

As stated before, I am willing to provide more info on the issue.

Other messages I can find are:

The program xiloader.exe version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 223c
Start Time: 01d5de388c5ed9bd
Termination Time: 1429
Application Path: C:\Users\(name was here)\Documents\xiloader\xiloader.exe
Report Id: ad4b7097-3a2e-4a82-a0e8-0ab3ee2ab1cd
Faulting package full name:
Faulting package-relative application ID:
Hang type: Unknown

-------------------------------------------------------

Description
Faulting Application Path: C:\Users\(name was here)\Documents\xiloader\xiloader.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: xiloader.exe
Application Version: 0.0.0.0
Application Timestamp: 5b568153
Fault Module Name: StackHash_d218
Fault Module Version: 10.0.18362.387
Fault Module Timestamp: a4208572
Exception Code: c0000374
Exception Offset: PCH_52_FROM_ntdll+0x0007232C
OS Version: 10.0.18363.2.0.0.768.100
Locale ID: 4105
Additional Information 1: d218
Additional Information 2: d21893d5e423d541ee422fc83ef8ad1e
Additional Information 3: b5be
Additional Information 4: b5bed89a2686ac8731fd6aa51ad27769

Extra information about the problem
Bucket ID: 0386a8f2c8a370c018de64c213866ee9 (1791980486454046441)

----------------------------------
And one error of:

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffff9f8e37511010
Parameter 2: fffff805839eb938
Parameter 3: 0
Parameter 4: 4b4
OS version: 10_0_18363
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.18363.2.0.0.768.100
Locale ID: 4105


I have ran multiple stress tests on some hardware pieces; CPU GPU and Memory, and nothing is out of the ordinary from my eyes.
For memory, I ran Memtest86 for around 10 hours, for the GPU I ran Valley Unigine for 5 hours, and for CPU, I ran Prime95 for around 3 hours.
Memtest came without errors, the same for the CPU and GPU.

Thanks,
Krawchuk
 
Krawchuk said:
As the title states, I get a rare occurrence of BSOD and games crashing after a certain amount of time.
Click to expand...

The issue you've posted isn't related to BSOD but rather an application crash, I would suggest that you contact the developer(s) and report the issues you're experiencing.
 
Setting up the Launcher
In this section you will configure FFXI to connect to a DarkStar Server

You can use Windower or xiloader directly to connect to a Dark Star server. Windower has more features, but take longer to set up. xiloader usually work with minimal configuration.

Ashita also works as it always has, but do not expect the Darkstar developers to help you with any issues you experience installing/using it.

SOURCE

It seems you can use other loaders, since xiloader is giving you issues perhaps try another loader.

I have never played any of those games so I don't know, this is something I came across while researching.
 
xrobwx71 said:
Setting up the Launcher
In this section you will configure FFXI to connect to a DarkStar Server

You can use Windower or xiloader directly to connect to a Dark Star server. Windower has more features, but take longer to set up. xiloader usually work with minimal configuration.

Ashita also works as it always has, but do not expect the Darkstar developers to help you with any issues you experience installing/using it.
SOURCE

It seems you can use other loaders, since xiloader is giving you issues perhaps try another loader.

I have never played any of those games so I don't know, this is something I came across while researching.
Click to expand...

I have set up both launchers, reinstalled both, and same things happen each time.
 
Errors along the lines of software such as drivers or some sort of corruption. Which would make sense since the crashes are across multiple games, not just XIloader/DSP itself.
 
Number of hyperthreads detected: 0
Warning - the number of hyperthreads detected (0) is not half the total number of processors (6)
GetGlyph failed for character 0x00F1 (Warning Unknown Glyph)
2018-09-30 09:00:38 - Language es-AR is not supported
2018-09-30 09:00:38 - GetGlyph failed for character 0x00C3 (Warning Unknown Glyph)
2018-09-30 09:00:39 - Language pt-BR is not supported
2018-09-30 09:00:39 - Language ca-ES is supported
2018-09-30 09:00:39 - Language de-DE is supported
2018-09-30 09:00:39 - GetGlyph failed for character 0x010C (Warning Unknown Glyph)
2018-09-30 09:00:39 - Language cs-CZ is not supported
2018-09-30 09:00:39 - Language ru-RU is supported
2018-09-30 09:00:39 - GetGlyph failed for character 0x3041 (Warning Unknown Glyph)
2018-09-30 09:00:39 - Language ja-JP is not supported
2018-09-30 09:00:39 - GetGlyph failed for character 0x4E0F (Warning Unknown Glyph)
2018-09-30 09:00:40 - Language zh-CN is not supported
2018-09-30 09:00:40 - GetGlyph failed for character 0xF944 (Warning Unknown Glyph)


These are what I can find in the txt document given.
 
Nevermind, with my cpu being a I5 9400F, it's doesn't support hyperthreading, which are those tests if i'm not mistaken.
 
Have you tried running it with one RAM stick? Sometimes one RAM stick could be bad, or it could be a slot on the motherboard. The only reliable way is to run the test with an individual stick in each slot.

Have you ensured that the BIOS settings are set to their defaults?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top