Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Those file formats can't be directly attached to posts herelook at these locations for crash dumps from the game
1. "C:\Program Files (x86)\Steam\steamapps\common\Project8Staging\game\bin\win64\project8_*_*_*_*_*.mdmp",
2. "C:\Program Files (x86)\Steam\dumps\crash_project8.exe_*_*.dmp";
it will give an idea of what happened with the game at the time of the crash, post it here and I will look at the dump.
then send them via DM, people have been able to do that in the past unless this has been changed. You could also try putting them in a .7z or zip format before uploading.Those file formats can't be directly attached to posts here
I hope this helps to figure out what is happens.look at these locations for crash dumps from the game
1. "C:\Program Files (x86)\Steam\steamapps\common\Project8Staging\game\bin\win64\project8_*_*_*_*_*.mdmp",
2. "C:\Program Files (x86)\Steam\dumps\crash_project8.exe_*_*.dmp";
it will give an idea of what happened with the game at the time of the crash, post it here and I will look at the dump.
Based on your outputs it looks like the game has an actual issue that the devs will need to resolve:I hope this helps to figure out what is happens.
project8_2024_0908_195002_0_accessviolation.mdmp
drive.google.com
crash_project8.exe_20240908194959_1.dmp
drive.google.com
project8_2024_0908_194549_0_accessviolation.mdmp
drive.google.com
crash_project8.exe_20240908194547_1.dmp
drive.google.com
I found before the game freezes, the network activity disappears. (Only game data. Other applications has network activity if its needs.) The game does not receive new data packets, the characters freeze a few seconds, and then the game crashes. The hardware configuration has not changed. It is the same as when it was installed. The problem appeared yesterday.Based on your outputs it looks like the game has an actual issue that the devs will need to resolve:
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 452
Key : Analysis.Elapsed.mSec
Value: 1280
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 46
Key : Analysis.Init.Elapsed.mSec
Value: 19580
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : Failure.Bucket
Value: NULL_POINTER_READ_AVRF_c0000005_client.dll!Unknown
Key : Failure.Hash
Value: {1eac6275-4e17-f0cd-885a-c7a121bb2ce7}
Key : Timeline.Process.Start.DeltaSec
Value: 389
Attempt to read from address 0000000000000000
PROCESS_NAME: project8.exe
READ_ADDRESS: 0000000000000000
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
looking at the error it seems the program "Porject8.exe" couldn't find a reference in the client DLL, it may have had the pointer reference or it existed at one point and then it got dumped giving the access violation as it thinks it should be there but isn't not sure if @Yoshi could bring this to someone or is already aware. Seems this might be a whole thread related to this kind of issue based on how prolific it seems to be.
Someone else found an access violation they could reproduce while in the item store, for your instance did you happen to be in the item store?
We can at least for now say it isn't your computer, but perhaps a configuration on your computer that is leading to this. Things you could possibly do to work around this issue are removing any software that influence RAM timings like MSI after burner or any software based over\under clocking software. Adjusting XMP either enabling or disabling, basically just getting the RAM to the most stable position possible.
The fact it's referencing point 0 though makes me wonder if something happened to the reference point during execution, reference 0 is basically NULL so it was referencing nothing.