We are fielding reports of this happening as of today in Jailbreak. I’m personally not crashing from any games.
1 Like
my friend had such issue all he did is replacement of processor/ram/additional disk to new parts, so no such issues after.
I am also getting reports from my game NORTHWIND, having around 40ish people experiencing this.
So, just a quick update. I have played that game now for 4 hours straight with no issues/crashes.
It somehow fixed “itself” but if something happens ill write it here.
I find this extremely hard to believe.
I use Windows 11 currently, and have never had issues with any of the ROBLOX products prior to the implementation of the 64bit client and Hyperion. However, as of recent, I have had more crashes in the past 2 months than prior since 2014.
I would also like to implement that my friend, who usually used Linux, has switched to Windows for ROBLOX lately.
I can attest that when playing games, he crashes nearly 1/2 of the time joining into a new game, despite not changing nearly anything from out of the box Windows 11.
It’s really frustrating playing a game and being booted out as soon as it teleports you to another place.
1 Like
Hi Bitdancer,
I’ve been following this thread for over a month and now Im finally able to post myself. I’ve been having the same “Roblox loads for about 3 seconds then crashes” thing since around June 14th now.
I’ve tried a bazillion amount of things to fix, from the other answers in this thread to youtube videos, people that already have experience with this and completely reinstalling both Windows 10 & 11. Not a single thing worked. I kept starting Roblox every now and then to check if it fixed itself, especially on Wednesdays since it would usually update that day but from June ~14th till today not a single update fixed this crash. I have another laptop, which is very old but for some reason Roblox works completely fine on it. The current Laptop I am having the crash issue on is a new one from February 2023. The Microsoft version of Roblox works since Hyperion is not there.
Here’s the crash dump generated with procdump, strategy three in “how to post a bug report” does not work for me
also some more info:
Using Bloxstrap - An open-source, feature-packed alternative bootstrapper for Roblox I changed my deployement channel from “LIVE” to “ZClientwatcher”
Since Hyperion wasn’t integrated in 0.570.268.5700017 Roblox actually launches, like getting past the white loading screen with the green bar, but I obviously can’t get ingame since its way to outdated.
3 Likes
This is also happening to tons of players in my game NORTHWIND,
it seems to happen at complete random with no warning prior to something causing it. People join, stay for a few seconds, sometimes minutes, and then get the Roblox crash error.
Very upsetting to have this issue be so constant as it is quite literally killing my player base.
2 Likes
Thank you very much for the guidance, i look on it to try solve the issue.
I’ve been having a similar issue, but roblox loads for about 15 seconds instead of 3. I’ve tried many things to no avail, and my issue also started on june 14th, however was fixed on the 15th, and broke on the 16th again, and it’s still broken as of August 8th 2023. What’s most strange though is that this isn’t producing any kind of dump file, only log .tmp files.
For strategy 3 on how to create a dump file, to create the ClientAppSettings.json, you can simply use a text editor such as notepad. Write the command into notepad and then save it as a .json file.
For the ClientSettings Folder, just create it.
Eh, if you only focus on this thread alone, you’ll probably think that the new 64-bit client is the worst thing that’s ever happened, but that’s just a form of survivorship bias.
Overall, among the entire Roblox player base, migrating the engine to 64-bit is completely fine and I’m confident to assume that, given Roblox’s size, at least 99% of users don’t notice any difference or have any issues.
But even if it is the 64-bit migration that’s causing the issues, then I’d still put my faith into it. I’m sure Roblox has teams patching the engine as we speak, and it’ll get better with time.
Been having this issue. I’ll join a Roblox game. And I will get the highest ping while My internet. Is at high speed. and works perfectly.
I get the exact same bug and the game just closes itself, must be the anti-cheat update thing, I’m not exactly sure
1 Like
Hello Fexler,
Thank you for providing the crash dumps. I took a quick, preliminary look, and it appears that the issue is not directly related to Hyperion. In other words, there is no badware issue on your machine; instead, something else (possibly a bug on our end) is causing the problem. We will continue to investigate further, but unfortunately, this is a case where I can’t provide an immediate solution.
1 Like
Hello Everybody,
A few words about getting the exact same bug. What people experience may show the same symptoms, but it doesn’t mean they have the exact same bug. In this thread alone, we have identified at least 50 different reasons why the client crashes. So, please do not assume that just because you see the same symptoms as other folks, it is necessarily the same root cause.
As always, the quickest and hopefully the least painful way to determine the cause is by creating a full crash dump and forwarding it to us. In cases of badware issues, we can usually resolve them relatively quickly. However, when there is a genuine bug, it takes us longer to resolve. Some of these bugs we have successfully fixed have taken several weeks before they made it into the release.
Anyone having High Ping spikes or nah?
Oh well. Also this may or may not be helpful but I looked a bit into my files to see when this “bug” appeared then compared it with the client versions online and I‘m 100% sure that It, atleast for me, started happening in v580.
v578 worked completely fine
seems like v579 wasn‘t released so this bug appeared somewhere between 579-580
1 Like
I followed what it said, created the ClientSettings and ClientAppSettings.json file, and for some reason there is no logs folder.
The crash dumps sometimes show up in other locations. Just do a search for *.dmp files.
This was a bug in the engine. It should be fixed by now.