Error Description
Upon attempting to join a game, roblox do one of three things, it will either:
a) Launch into a white screen and then crash without the error popup message.
b) Launch into the typical loading screen, but freeze at some point through and then crash, without the error popup.
c) Load fine, starts on white, then gets into load screen, then puts me into the game.
Videos of Error
Crash Dumps
White Screen Logs:
0.648.0.6480781_20241024T150937Z_Player_3558C_last.log (25.3 KB)
attachment_0.648.0.6480781_20241024T150937Z_Player_3558C_last.log (25.3 KB)
Relevance
Medium Impact
I cannot join some games on roblox, despite the device being specced properly to the point where it should be able to do so.
Affected games I have tested: generic roleplay gaem, Jailbreak, Dummies vs Noobs,
System Specifications
ASUS Zenbook 14S 14" Intel Lunar Lake Laptop
CPU - Intel Core Ultra 7 258V @2.20 GHz
GPU - Intel Arc 140V GPU (16GB)
Memory - Row of chips form factor, 8533 MT/s 8/8 slots used, 32GB
Storage - Standard, ample storage.
Operating System - Windows 11 24H2
Extra Information / Solutions Tried
-
Turned off Variable Refresh Rate
-
Tried forcing Roblox to open on Windows Performance Graphics Mode (Still on iGPU)
-
Tried putting Roblox in Windows 8 Compatibility mode which has fixed other issues people have had in the past.
-
Tried disabling Optimization for Windowed Games
-
I do not think the laptop is under powered, despite having an iGPU, it should still be plenty powerful enough to run the games fine. I think the issue may lie with too much of the memory getting used because Roblox has shown that it dislikes certain types of memory in the past, and this is a somewhat unsual memory form factor, but I’m not sure.
-
Im really not sure if the games are responsible, but I dont see how they could work on every other device but not mine, so, I decided to write a report.
Expected behavior
Roblox should launch normally, without failing to get past the loading screen.
If more info is needed, reach out.
A private message is associated with this bug report
