"RAGE error: ERR_GEN_ZLIB_2

To receive support, please fill out the following template, and remove this top text.

GTA V version? Latest
Up to date? Yes
Legit or Pirate copy? Legit
Steam/CD/Social Club? Steam
Windows version? 10.0.16299 Byukd 16299
Did you try to delete caches.xml and try again? Yes I did
Error screenshot (if any)
https://gyazo.com/33a48815b6b88d030139b69db98f2bd8?token=2040d59184062aeed8b727224af5fbf6

https://gyazo.com/cea00c449e49400aa8e01cb61ade9985

System specifications
NVIDIA GeForce GTX 1060 Ti
x64 based pc
i5-7400 CPU
System Model: MS-7A70
Installed Memory (RAM) 8.00 GB
What did you do to get this issue? Joined the server that I own.
What server did you get this issue on? Texas Department of Public Safety.
CitizenFX.log file
https://pastebin.com/M3iauEyD
.dmp files/report IDs

Also, add what you already tried so far.
Reinstalling FiveM

(Not for me, for a friend.)

1 Like

This has been here and no mods or anything has gotten back to him?
Im getting the same issue and i keep crashing every 10-15 mins

I’ve been experiencing this as well, I can’t be on a server for more than 2 min at this point

The reason nobody has replied is that a search for the same error comes up with the solution.

ERROR_GEN_ZLIB_2 is related to having textures that are too big. So the ymap you load does contain big textures. (and zlib can’t compress them).

For more information:

The information above was found by this post;

So thank him for coming up with the solution and I guess you can give me a little thanks for finding the post.

My server has been experiencing the issue because of a resource that is on this forum called “LA Billboards”. Some of the billboards images are too large and causes the crash so if you have that installed I would recommend removing it unless you want to go through thousands of files downsize them.

@Syntasu A friend of mine, Dracuslayer, was getting the issue on a clean server, and before this update, I never received this error once. I’ve been using 2048x2048 image quality since creating a server in July and never had this issue until the March 27th update.

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