India-winter-beryllium is slaughtering us

crash
memory-corruption
uncommon

#1

Twice today, following the 171231 update, and successive masterlist fail to list, I’ve seen india-winter-beryllium strip my favorite server 446 of every player from 18 to 0, and six hours later from 13 to 0, and never ever before this.

GTA V version? 1.42
Up to date? Yes
Legit or Pirate copy? Legit
Steam/CD/Social Club? Social Club
Windows version? 8.1 Pro
Did you try to delete caches.xml and try again? Yes, but this causes endless loading first rejoin.
Error screenshot (if any) None
System specifications i7 nVidia
What did you do to get this issue? Played FiveM
CitizenFX.log file https://sites.google.com/site/newgameplay1/CitizenFX.log
.dmp files/report IDs https://sites.google.com/site/newgameplay1/f8da1bec-2764-4569-a733-950e6256131e.dmp

If an issue with starting:
My GTA Folders: https://sites.google.com/site/newgameplay1/FiveM-Screenshots.jpg
Did you try to disable/uninstall your Anti-virus? No Anti-virus. I want to lag. And be part of a bot net.


Delta-red-lithium the Copycat Killer
#2

This is an awkward one. There’s usually no reports on any given day, however some days the report count increases to 20-30 - but it’s only happened a total of ~600 times over the course of the past few months.

Investigating to be sure.


#3

CPed+4328d being null during handling of (presumably received?) clone sync data. Adding it to the bucket of ‘uncommon crashes caused by data corruption’.


#4

4264d/10A8h in 323, seemingly… ped helmet state.


India-winter-beryllium is slaughtering us II
#5

17 people were killed today in yet another senseless India-winter-beryllium mass murder. The killer or killers remain at-large, and should be considered only active on busy servers.


#6

12 more innocent players cut down in their prime. There were no survivors to this sudden, unexpected, and yet unsolved mass-killing.

https://sites.google.com/site/newgameplay1/India-winter-beryllium_crashes-180110.zip


#7

The mass-murderer known only as India-winter-beryllium has struck again, but this time completely differently. I was the only crash and while FiveM client was idle and minimized for over an hour. All other players were unaffected, escaping this certain tragedy unscathed.

https://sites.google.com/site/newgameplay1/India-winter-beryllium_crashes-Single-User-Only-No-Other-Players-Crashed-180110.zip


#8

After 5 days of peace, India-winter-beryllium kills 13 more in typically random, unprovoked, Monday night attack: https://sites.google.com/site/newgameplay1/India-winter-beryllium_crashes-180115.zip


#9

8 more into the wood chipper: https://sites.google.com/site/newgameplay1/India-winter-berylium-Crashes-180116.zip This time on my identically outfitted i7 all previous on my i3

I’m thinking it might be time to drop the uncommon from this forum tag: “crash memory-corruption uncommon” It is apparently quite common. Hitting me 6 times in 3 weeks, killing 82 players.


#10

May the victims families be brought peace and closure soon. Rest in peace to all the 82 victims. You will be missed


#11

It strikes without warning: 10 killed, 6 Wounded, Crash and Logs from two computers for the same event.

https://sites.google.com/site/newgameplay1/India-winter-berylium-180124-i7.zip
https://sites.google.com/site/newgameplay1/India-winter-berylium-180124-i3.zip

4 Weeks. 7 Times. 96 Players.


#12

2018-01-26 06:19 5 Dead. 9 Wounded.
https://sites.google.com/site/newgameplay1/India-winter-berylium-180126-i3.zip

An observation from someone who runs a lot of mps and has seen all the systemic unsolvable errors hell can create for our ego’s to inevitably triumph over or workaround… this one is regular but not reoccurring. Once it has happened that is it for the day. This, if correct, and not just the assumption of short term data, would indicate that whatever causes the error is solved by the error. And it seems equally likely that it is the result of an accumulation of issues rather than an infrequently accessed single trigger mechanism.

The errors accumulate until triggering this mass error India-winter-beryllium, in a ‘straw that breaks the camel’s back’ manner, crashing every client, and not again for quite some time, because each new trigger is just one more piece of straw. That is my guess… so far. Like some sync cache is stored and stored instead of being sent and sent, stored until it floods then ultimately released. Or some similar stacking up mechanism to that. Just a guess.


#13

1 month and 5 days. Felt like we were safe again. But it is back.


India-winter-beryllium is slaughtering us II
#14

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.


#15