Analyzing the crash dump you provided, it appears that you are facing the same issue as @AbstractAlex. The root cause of the unrecoverable error is a failure in the Windows API call CreateDIBSection(). This failure should not occur since a process is normally allowed to create up to 10,000 GDI handles.
To gather additional information about this unusual issue, could you please:
Set the registry value Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\GDIProcessHandleQuota to 64000.
Reboot your system.
Test if the issue persists after implementing this change.
Hello ByteDancer,
After changing the GDIProcessHandleQuota From 2700 to 64000 and testing out Roblox, It appears to run for more than 40 minutes without issue.
Thank you for confirming our suspicion that the client is running out of GDI handles. Please keep the setting as a workaround until we find a more appropriate solution on our end.
The GDIProcessHandleQuota change is a workaround for a very specific issue that a subset of users here on the forum is facing. It is highly likely that the cause of the issues you are experiencing is different. The only way to be sure is if you provide us with an extended crash dump as outlined in Strategy Three here.
A not insignificant percentage of the crash dumps sent to us are from users who are running or have run cheat software.
As per company policy, we do not provide further support upon detecting such software. Unfortunately, we still need to analyze the crash dumps before we can be 100% certain.
This process consumes valuable time and delays processing users with valid issues.
Having said that, users who do send crash dumps indicating the usage of cheat software may face potential repercussions.
Hey Bitdancer, your solution worked well for me! I’ve been testing games and I haven’t gotten a crash since I launched it with my usual applications. I hope this will remain stable for the foreseeable future!
However, when you mentionned to raise up the GDI handles, I looked up with a GDI View application and the highest one is RobloxPlayerApp.exe having 21K GDI handles, why it consumes a LOT of GDI for no reason? This is confusing why a single app uses a lot of GDI handles.
I attempted to explain why, in your own words, you are still being ignored. You are simply at the end of an unnecessarily long queue of crash dumps to analyze.
Anybody have any bright ideas on where to look to diagnose a silent crash that happens 3-4 hours into playing and doesn’t produce a dump log? I kinda got lucky finding that other program, but this form of crashing just seems to happen at random.
I can’t even load the client itself. Every time I open up the launcher, it crashes. The other day it was fine, but now it doesn’t even work. I have tried reinstalling, opening as administrator, restarting my computer, and updating drivers. I have no idea what to do and I don’t know where I can go for help.
Hi!
I had this issue for around month now, I couldn’t launch any game from web, it would just load and completly crash.
I think I have proper solution, it worked for me but it might not work for you:
Wait 1-4 days - don’t use and open Roblox Player Client if possible. (You can use Studio and website)
After waiting update your Roblox Player Client, try it out.
It worked for me and I no longer have any issues with loading/crashing!
(Again this might’ve only worked for me but be sure to try if nothing helps.)
Please try to start the player using the command line argument --app and let me know if it resolves the issue for you. The Roblox Player executable can be found at C:\Users\<user name>\AppData\Local\Roblox\Versions\version-0ad029c119034aa8 . For example, on my machine, the full command would be C:\Users\Bitdancer\AppData\Local\Roblox\Versions\version-0ad029c119034aa8\RobloxPlayerBeta -app .
This issue seems to have been fixed after a recent update. The white screen and instant closing issue is no more, but I still get the awful ‘memory dump’ crash, which rarely doesn’t crash my client so if I try enough times, I can play Roblox without crashing again after that. I still believe this memory dump is what is causing the crashes.
