/

/

Settings & Config

Settings & Config

FACEIT Demo Crashes CS2: The Chicken Bug

Your FACEIT demo closes CS2 the moment you type playdemo. It is a pet chicken bug from the 22 October 2026 update, and it is fixable.

Beginner

·

6

MIN READ

·

Beginner

·

6

MIN READ

·

WHAT YOU’LL LEARN

WHAT YOU’LL LEARN

  • The 22 October 2026 update started the FACEIT demo crash.

  • A pet chicken becomes the baseline and CS2 reads it too early.

  • Ancient and Nuke crash. Inferno plays fine. The map decides.

  • Valve bug 4672 is open with no reply after nineteen days.

  • The 22 October 2026 update started the FACEIT demo crash.

  • A pet chicken becomes the baseline and CS2 reads it too early.

  • Ancient and Nuke crash. Inferno plays fine. The map decides.

  • Valve bug 4672 is open with no reply after nineteen days.

FACEIT demo crash guide cover

You download a FACEIT demo, type playdemo in the console, and CS2 closes. No error, no message, straight back to the desktop.

It is not your file, it is not your drivers, and verifying your game files will not fix it. It is a bug in Counter-Strike 2, it is on Valve's own public tracker, and the trigger is a pet chicken.

Here is what actually happens, which maps it hits, and how to get the demo playing again today.

What is actually going wrong

The six steps from a pet chicken to a CS2 crash when playing a FACEIT demo

A demo file starts with setup data that tells CS2 what every kind of entity in the match looks like by default. That default is called a class baseline, and the game needs it before it can read anything else.

Chickens have one too. On most maps the first chicken the server sees is a map chicken, so the baseline is an ordinary chicken and everything is fine.

Now put a player with a pet chicken on a map that has no chickens of its own. The pet is the first chicken on the server, so the pet becomes the baseline, and it carries the pet item with it. In the broken demos that baseline does not arrive in the setup data at the start of the file. It arrives later, in the first packet, and by the time CS2 goes looking for it the memory it points at has been reused.

The result is an access violation inside engine2.dll and the game closes. The bug report names the two functions involved, GetClassBaseline and DecodeClassBaseline.

Two things worth being clear about. This is a Counter-Strike 2 bug, not a FACEIT bug. FACEIT demos just happen to be where players hit it. And pet chickens do not cause it, they expose it.

Which maps break and which do not

Ancient and Nuke reported crashing, Inferno reported playing fine

This is the part that makes the problem look random until you see the rule.

Ancient and Nuke are reported crashing. Neither map spawns chickens of its own, so a pet chicken is the first one the server ever sees.

Inferno is reported playing fine. Inferno has its own chickens wandering around, one of them registers first, and the baseline ends up being a normal chicken.

Only those three maps are named in the bug report, so that is all this guide will claim. Every other map follows the same rule, and whether yours breaks depends on one thing: does the map spawn chickens before a player's pet appears.

It also explains why your friend's demo from the same night plays fine and yours does not. Same patch, same FACEIT, different map, or nobody in that lobby had a pet equipped.

The timeline, because the dates matter

Timeline from the Rush Hour update to Valve bug 4672 still being open

Valve shipped the Rush Hour update on 22 September 2026, and pet chickens were live by early October, when the release notes start mentioning the pet photobook.

The crash starts later. The bug report names the 22 October 2026 update, demo protocol 14192, build 10955. Demos recorded before that update are reported to play normally.

The report went up two days after that, on 24 October 2026. A second player confirmed it on 26 October. As of today it is still open with no reply from Valve.

So if you are waiting for a patch to fix this for you, there is currently nothing to suggest one is close.

How to fix the demo today

Three steps.

1. Download the demo from FACEIT as normal. You do not need to unzip it. The file will be a .dem or a .dem.zst.

2. Drop it into the CS2 FACEIT Demo Fixer. It moves that late baseline into the setup data at the start of the file and removes the duplicate, then hands you a repaired demo back. It runs in your browser, so the file does not leave your machine.

3. Put the repaired file in your csgo folder and play it. Open the console and type playdemo followed by the file name. Every round, shot, kill and grenade is byte for byte what it was, because only the setup data is touched.

If you would rather not use a tool at all, there is one workaround reported on the bug thread: bind a key to demo_gototick and jump past the moment the game chokes. It is not reliable, you lose the start of the demo, and it does nothing for a demo that dies on load, but it costs nothing to try.

What this does not cover

Worth being clear about the edges.

The reports disagree slightly on when the crash lands. The bug report says the demo crashes on load. The player who confirmed it says his loads and dies about three seconds in, when CS2 jumps back to the start of the demo. Both end the same way.

Whether matchmaking demos are affected is not settled either. The bug report says only that the crash was seen on FACEIT demos. One commenter says matchmaking demos on this update are fine. That is one player's experience, not a tested claim, and this guide will not turn it into one.

And this is a bug under active discussion. If Valve ships a fix, the demos recorded after it will not need repairing, and this page will say so.

Where to go next

Once the demo plays, the question is what you do with it.

Most players watch their own demo, nod at the rounds they already remember, and learn nothing. How to review your own demo is the method that fixes that, including which rounds to actually watch and what to write down.

If you are in the console anyway, the 144 commands worth knowing covers the demo playback commands alongside the rest, and explains which commands need your own server.

And for the season as a whole rather than one match, the FACEIT Recap tool turns your year of matches into numbers you can actually read. The recap guide explains what each number is telling you.

KEEP IMPROVING

KEEP IMPROVING

GET YOUR DEMOS REVIEWED.

FIND YOUR MISTAKES. FIX THEM.

Want someone to look at your own games? Book CS2 coaching and get your demos reviewed, or join the CS2 Rank Up Society for a structured 20-day plan and weekly accountability.

Join the CS2 Rank Up Society for the 20-day plan, or book CS2 coaching and get your own demos reviewed.

Join the CS2 Rank Up Society for the 20-day plan, or book CS2 coaching and get your own demos reviewed.

$5/MONTH · CANCEL ANYTIME

NEXT STEP

$5/MONTH · CANCEL ANYTIME

COMMUNITY

COMMUNITY

FIND TEAMMATES. ASK ANYTHING.

Queue with players at your level instead of going solo, and ask whatever you are stuck on in the questions channel.

Queue with players at your level instead of going solo, and ask whatever you are stuck on in the questions channel.

JOIN THE DISCORD

→

Brian Sirbu, CS2 coach at GameSenseLab

WRITTEN BY

Brian Sirbu

CS2 COACH // GAMESENSELAB

STOP IMPROVING ALONE

Turn scattered practice into a repeatable system with feedback, accountability, and a clear next round.

Turn scattered practice into a repeatable system with feedback, accountability, and a clear next round.

$5/MONTH · CANCEL ANYTIME · +200 ELO GUARANTEE

GAMESENSELAB

.PRO

CS2 coaching, training systems, and improvement content.

CS2 coaching, training systems, and improvement content.

© 2026 GAMESENSELAB.PRO

© 2026 GAMESENSELAB.PRO

© 2026 GAMESENSELAB.PRO