Since the last week update both studio and the client have started to crash randomly without any clear and direct error logs and messages. Studio itself is also crashing at a WAY higher rate than the client and often does when starting/closing a play test but can sometimes also happen during one.
Most i have found is the error “The thread tried to read from or write to a virtual address for which it does not have the appropriate access.” with the exception code “0xc0000005”.
It’s come to my attention that this is a memory based issue after talking to a professionally contracted expert in software development, and after researching the issue online.
This is a fix someone managed to find, and honestly I don’t feel the need to go through this much trouble just to play Roblox.
You can try looking under XMP/EXPO profiles for the timings. For me it was enough to just play around with the profiles around but if needed you can also play with the numbers manually. The settings should be somewhere within “overclock” or “memory” sections. Cannot give specifics since the bios of these things is not at all standardized.
Though if you do reach the point where you have to specifically play with ram timings manually, i advise you to be careful about what youre doing. Improper settings could potentially make your memory unstable.
Something else that you could try would be doing a bios update. That alone may be able to help with the issue but only maybe. Worth the try though, especially if your motherboard has easy bios install software.
I’d like to post an update to assist with the bug hunting.
I’ve discovered that Roblox runs completely fine unless interacted with by the mouse, and then it instantly closes. It’s possible that this is a logitech (G HUB) issue, i’ve head that other people have had issues where Roblox would silent crash when people had a logitech wheel installed, or something along the lines of that. I have a logitech mouse, but the issue only started occurring recently.
I’ll start experimenting with stuff like wiping the cache on my mouse (since it has internal memory for RGB settings and hotkeys etc.)
Thanks.
(Edit: I could not confirm this, also issue still not fixed)
