spectate mode crashes game repeatedly

Glad to know it wasn't just me. The game worked fine two days ago, now in the middle of a match, there's suddenly a couple of lag spikes that last for few seconds, then the game unceremoniously shuts down.
 
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.
 
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.
Those file formats can't be directly attached to posts here
 
Here are the console errors I get associated with the crash. There are a lot more sync errors than this but it is a decent sample.

[HLTV Broadcast] 235.77. Playcast cannot retrieve fragment 1698, retrying
[HLTV Broadcast] 235.77. Playcast cannot retrieve fragment 1700, retrying
[HLTV Broadcast] 235.92. Playcast cannot retrieve fragment 1701, retrying
[HLTV Broadcast] 235.92. Playcast cannot retrieve fragment 1699, retrying
[HLTV Broadcast] 235.92. Playcast cannot retrieve fragment 1702, retrying
[HLTV Broadcast] 236.08. Playcast cannot retrieve fragment 1700, retrying
[HLTV Broadcast] 236.12. Playcast cannot retrieve fragment 1701, retrying
[HLTV Broadcast] 236.12. Playcast cannot retrieve fragment 1698, retrying
[HLTV Broadcast] 236.22. Playcast cannot retrieve fragment 1699, retrying
[HLTV Broadcast] 236.27. Playcast cannot retrieve fragment 1700, retrying
[HLTV Broadcast] 236.27. Playcast cannot retrieve fragment 1702, retrying
[HLTV Broadcast] 236.42. Playcast failed to retrieve fragment 1701 (succ=1697, 25.1 sec)
[HLTV Broadcast] 236.42. Playcast failed to retrieve fragment 1698 (succ=1697, 25.1 sec)
[HLTV Broadcast] 236.42. Playcast failed to retrieve fragment 1699 (succ=1697, 25.1 sec)
[HLTV Broadcast] 236.56. Playcast failed to retrieve fragment 1702 (succ=1697, 25.2 sec)
[HLTV Broadcast] 236.56. Playcast failed to retrieve fragment 1700 (succ=1697, 25.2 sec)
[HLTV Broadcast] 238.77. Requesting sync
[HLTV Broadcast] 238.94. stream http://dist1-ord1.steamcontent.com/tv/9904055/sync (2) failed. Error 405 Retrying sync
[HLTV Broadcast] 238.94. Retrying sync in 7.18 sec
[HLTV Broadcast] 246.14. Requesting sync
[HLTV Broadcast] 246.30. stream http://dist1-ord1.steamcontent.com/tv/9904055/sync (3) failed. Error 405 Retrying sync
[HLTV Broadcast] 246.30. Retrying sync in 6.56 sec
 
Same, crashes over and over. MatchID 9931505. it's an ongoing match. crashed 3-4 times already. AMD 5600x, RX6700XT, 24GB RAM, Windows10
 
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.
I hope this helps to figure out what is happens.
 
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.
 
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.
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.
I associate the reason of crash with the fact that the game stops receiving data from the server.
 
I had the same thing. It no longer occurs after disabling the memory integrity option in windows security settings. I hope this helps.
 
I haven't done anything to solve the issue, yet it seems it's gone on its own, I can watch games again without interruptions. Maybe that small, 100 kb patch the game had today on Steam fixed the issue?
 
Back
Top