Will Window Virtual Machines be forever blacklisted by the new client?
I’ve been having a similar issue ever since the 64 bit client went live. Roblox works for about five minutes before crashing.
Interestingly, this issue only happens on Windows 11. Running Roblox on the same machine with Windows 8.1 hasn’t given me a single crash yet.
Hello all,
We just released version 0.581. This version contains a couple of fixes that we have seen popping up in this thread, namely, a multithreading issue and a GDI resource leak. Please feel free to give feedback at any time.
4 Likes
Hello Bitdancer,
Time of writing: 1:38 AM GMT+4
I’ve performed a clean boot and launched Roblox(right now I have this tab open in my browser, and Roblox) - I’m in the game for over than 10 minutes now(which is definitely a good sign). Nothing seems to be crashing, and there are no freeze frames. Before the 0.581 update - I’ve been getting freeze frames whenever I was playing a rhythm game - maybe due to mass input of keypresses. I will edit this post whenever my Roblox crashes - for now everything is going alright.
On my Roblox crash dump file i ran !analyze -v, since the file is corrupted(for me). Currently waiting for the debugger to finish analyzing the crash dump file;
Regarding the .dmp file, I get an Access violation - code c0000005 (first/second chance not available) because of its’ size(probably). I’ve created 4 .dmp files:
First crash dump - a rhythm game with many instances running at the same time. Result: file corrupted, sizeL >2gb
Second crash dump - plain baseplate with nothing running. Result: file corrupted, size: >2gb
Third crash dump - (clean boot) a rhythm game with many instances running at the same time. Result: file corrupted, sizeL >2gb
Fourth crash dump - (clean boot) plain baseplate with nothing running. Result: file corrupted, size: >1.5gb
Elapsed time of writing: 27 minutes, 2:04 AM GMT+4
Edit while sending:
- Roblox has crashed after 24 minutes and 13 seconds of uptime. I’ve sent you a PM with the crash dump file - surprisingly the size of it is low, >50k kB
- WinDbg gave me some information - link
2 Likes
Can Confirm, Latest Update Failed To Show Any Improvements.
7 Likes
Update: Everything works fine after deleting a specific file in C:\Windows\System32\; it being a .dll - Itcspea.Dll; roblox hasn’t crashed after an hour.
I am 100% sure that the reason of your Roblox crashing is specific - you can fix it manually, or PM any staff member in here, or PM Bitdancer - doesn’t really matter. In my case, I’ve dmed Bitdancer - I got a response from him the same day; although, PM’s to the bug-report group still remains unanswered after 4 days of waiting.
Reproduction steps for manual fix:
- Download WinDbg from Microsoft’s website (free download)
- Open WinDbg
- Open Roblox, and wait for it to crash
3.1. Open the crash dump file (don’t know where it is? check this thread for more info, specifically the 3rd strategy; might have to rejoin roblox so that it will generate a crash dump file) - Check
C:\Program Files (x86)\Roblox\Versions\(your version)\- yourClientSettings.jsonfile must only contain this content:{"DFIntWriteFullDmpPercent": 100}(if there’s noClientSettings.jsonfile - you can create it)
4.1 Your Roblox folder should look like this:
Content ofClientSettingsfolder must containClientSettings.jsonfile - the same one in the aforementioned directory - Manually search for processes that tamper with
RobloxPlayerBeta.exe(Don’t know how? Check this for more info!) - Delete the
.dllfile; if it’s not deleting, follow these reproduction steps:
1) Change the file extension of the new-found.dllfile tonothingexample:test.dllshould be justtest, no file extension whatsoever
2) Reboot your pc (crucial, you should actually do that)
3) Delete the renamed file - Launch Roblox again
If Roblox still crashes - don’t hesitate sending a PM to aforementioned contacts on the top of this reply; Have a great day!
4 Likes
0.581 has triggered this issue again for me.
2 Likes
No I’m talking about my Windows 10 laptop.
The newest windows update makes the machine almost unusable, and makes Roblox completely unusable.
I have to uninstall the windows update, but Roblox won’t open when I do that. It keeps telling me my system is too outdated.
Is there a way to bypass that?
I accidentally left Roblox open and now after ages I get this popup, which is QUITE the concerning popup to get because it’s error 403 saying I’m forbidden. That doesn’t explain it dragging my CPU in the background before it popped up.
EDIT: When this popup appeared I actually got somewhat of a log which I read through and I think it just failed to login because my auth ticket expired from Roblox taking literally 16 minutes to start.
5 Likes
It’s been two weeks (two updates) and it still isn’t fixed… any updates?
2 Likes
I am seeing tons of people having this issue (not me, but I have been having the same issue for the past almost two months). I’m linking your post so they know they aren’t the only ones.
1 Like
Glad we could be of help. I’d like to point out that when I mentioned the name of the DLL causing the issue, I meant you should uninstall the product that installed it instead of deleting the DLL itself. After our investigation, we found that the DLL belongs to this product. I’m surprised, but also glad that deleting it didn’t cause any other issues.
2 Likes
Hello again,
The product you mentioned was not installed on my PC - i haven’t found it anywhere, but I was stopped from deleting the aforementioned DLL file because it was being used in another program - I couldn’t find it anywhere; so I just deleted that in my sys32 folder. Thanks, Bitdancer!
6 Likes
I think I sent you a PM on June 14th with some dumpfiles, first time using the forum so not sure if that was the proper communication channel to get my issue across. Would appreciate any help there.
@subto_deraxileonyt
Your directory state seems to differ a bit from what’s described in Strategy Three, namely the json file name (ClientSettings.json vs ClientAppSettings.json) and how many files should be created. I have no idea if that would affect anything, just pointing it out.
Strategy Three only has you create a single ClientAppSettings.json under a ClientSettings directory, whereas you have your json file under that directory and another one at the same level as the directory. I did not have any such ClientSettings.json files, and originally followed the troubleshooting instructions to create ClientSettings\ClientAppSettings.json .
However, just now I replicated what you have, and regardless of which set of instructions I followed, I did not find any logs under %UserProfile%\AppData\Local\Roblox\logs or %UserProfile%\AppData\Local\Roblox\logs\crashes . Instead, each time I found the dumpfiles under C:\Users\USERNAME\AppData\Local\CrashDumps .
For your step 5, “Manually search for processes that tamper with RobloxPlayerBeta.exe,” how did you identify the processes? I took a look at the dumpfiles in WinDbg and wasn’t able to figure out much from it.
Anything happening to solve this? Roblox takes ages to open since the release of 0.581 and when it does the authentication ticket has expired either way so it doesn’t even get in-game and nothing happens in the logs while it’s running in the background.
Do I need to factory reset my PC?
Hey Pinbat,
As far as I know, ClientAppSettings and ClientSettings don’t really differ from eachother - although both files worked for me.
I’ve made 2 files just to ensure that the crash dump files get generated - the file in ./ClientSettings/ folder is the same(as mentioned before), was done solely out of clarification; I was searching for an FPS unlocker for the Roblox client and I saw that you have to create a folder in order to FPS unlocker to work. The directory doesn’t matter - I did it only for functionality
About the directory of crash dumps, it really is sort of random. I copied the directory from Bitdancer’s thread - I found my files there.
Regarding the 5th step, to identify the process you should first check:
- If you ran WinDbg with admin rights - gives you more control over the dump file
-
Second, as soon as you opened the
.dmpfile - you should see this:
-
Pay attention to the arrow - you should type in
lminside the textbox, and wait for WinDbg to list all loaded modules (inside RobloxPlayerBeta) -
You should see this:
Typically, the process responsible for tampering with Roblox can be found towards the end of the crash dump file; you must search for the process name in a browser and see if its a vital Windows process(that shouldn’t be messed around with) - when you’ve searched for the .dll file, you would have to check if the process was called by NT AUTHORITY\SYSTEM or these 2:
- you have to check them twice(before doing anything with it), as they may be called upon booting the PC up, either by a windows subprocess. Examples: svchost.exe (should not be tampered with; crucial process that hosts various services), dwm.exe (shouldn’t be tampered with - dwm.exe is a crucial process that is responsible for UI elements on your screen; if suspended/terminated, expect bad stuff(sadly, tested on myself)), MsMpEng.exe (shouldn’t be tampered with - resets your antivirus), and such. To identify if the process was called upon boot, search it up - doesn’t hurt to try! Otherwise, if the process is not ran upon PC boot, you can safely delete it, either the delete the program that is using the .dll file.
For example; You have a process called IAStorDataMgrSvc.exe. But oh well, it has been called by the system - you have to search it up whether its crucial; after finding out that it is not crucial - suspend the process:
Open task manager(ctrl + shift + esc) → find process name → Win + R → cmd → tasklist | findstr "process name here" → should give you the process id, memorize it; → (should be a new line after executing the previous command) taskkill /f /t /pid <PID>.
After that, if Windows doesn’t crash - locate the .dll file’s path and proceed to step 6 in here
Hope it helps!
4 Likes
Thanks for the detailed write-up and pictures. Unfortunately, nothing stood out unlike in your case with Itcspea.dll. Everything was some sort of Windows service, and while some might not have been absolutely critical, I think I’ll wait for a staff reply first instead of going through and disabling.
1 Like
Sad to see that it didn’t work for you, but just to be sure:
- When you executed the
lmcommand in WinDbg, it should have displayed a list of loaded modules. Have you checked the top results? Look for any modules that are related to Roblox or any third-party software that could potentially be causing conflicts. If possible, try the following:
-
If possible, PM me the
.dmpfile - I’ll try to look into it myself. I don’t promise you anything - I may or may not find the root of the cause. -
Create a new crash dump, join this blank experience so that no other stuff gets in the way, and wait for roblox to crash. After the roblox crashed, open the newly created crash dump file inside WinDbg, and try the following steps:
- If you didn’t find any “failure”-d modules, you can try some additional steps:
-
Execute the
!analyze -vcommand to see if there are any other relevant details or error messages that might have been missed initially. -
Execute the
!exploitablecommand - see if it gives you anything, just a simple recheck. -
Caution! The following command reveals sensitive information about your computer. Avoid executing it while screen sharing.
-
Execute the
!pebcommand: It will displays information from the Process Environment Block (PEB), including the command line, environment variables, and loaded modules. Beneath the line that saysLdr.InMemoryOrderModuleList: 0000025d8b606330 . 0000025d8b5a66e0, you should see all loaded modules - I found my “failure” module there, maybe you have it listed there. Just, be advised that the list may be really long; although, if i were you, I’d spend the time to fix the issue lol -
Execute the
!threadscommand: it should list all threads in the crash dump, displaying their IDs, stack frames, and thread states. If you find anything that is not related to Windows - might want to check that out. (most of the time it doesn’t work, but you should try anyways - doesn’t hurt to try!) -
Execute the
lmfcommand: it should displays loaded modules and their associated symbols in a compact format; better thanlmthat I mentioned earlier. -
Consider uninstalling and installing roblox again, then generate a crash dump again
-
Check for any recent software installations or updates that could have coincided with the start of the crashing issue. If so, try rolling back those changes or uninstalling the newly installed software to see if it resolves the problem.
TL;DR, join this, let roblox create a fresh crash dump, and use these commands to debug it: lmf, !analyze -v, !peb.
yeah also check if you have C:\Program Files (x86)\InfoTeCS\ViPNet CSP\Itccspbs64.Dll inside the directory, after executing !peb i spontaneously found it there, although it doesn’t do anything now since that dll was disabled way long ago, before i even got my pc
It’s better to PM Bitdancer (in this case), since they know better; all I can say is that I hope that this gets fixed soon. Goodbye for now!
5 Likes
Hi, I was told by someone who had this issue that they fixed it by disabling Riva-Tuner Statistics Server (RTSS) and/or MSI Afterburner. Not sure how much this may help you.
3 Likes
Hi thank you so much!!! I actually do have both MSI Afterburner and RTSS and tried your solution and it works!
Edit: Found a permanent solution by setting “Application detection level” to None in RTSS.
5 Likes