These roblox staffs are gaslighting u frfr. Go and download roblox from microsoft store (because the one from microsoft store is 32bit no byfron). If you dont have microsoft store or you use linux go on and downgrade to ZLIVE channel via bloxstrap on github (watch out tho they may be honeypotting)
3 Likes
They definitely are.
Instead of trying to help with the issue, a Roblox staff member told me my logfile was spam and instead of reading it, he just removes it
1 Like
On my machine, for example, no crash dump is generated automatically, and there is no error message.
I have no idea how common this behaviour is.
check every single app on your pc to see if they trigger hyperion
I encourage other people to try this, but I have not been able to identify any specific conflicting programs myself.. even down to disabling VMware and VirtualBox network drivers and so on.
Note that rebooting my machine usually gets the game to run successfully, but after one or two plays, it refuses to run again. I have no explanation for this, and I have looked through background processes 'til kingdom come.
We’re on day 26 of this issue.
If you want I can give a list of functions that trigger Hyperion.
If this anticheat is set off by random unspecified Windows API function calls, and it manifests by instantly killing the program, they may want to rethink it
2 Likes
Yep you are correct.
These are the funny functions that are detected by the anti tamper.
[2] [00007FFAAC94A900] [ntdll.dll!RtlExitUserProcess] [jmp RobloxPlayerBeta.dll+0x254ef50]
[2] [00007FFAAC9517F0] [ntdll.dll!LdrInitializeThunk] [jmp RobloxPlayerBeta.dll+0x11cc1c0]
[2] [00007FFAAC97C3B0] [ntdll.dll!NtAllocateVirtualMemory] [jmp RobloxPlayerBeta.dll+0x2492ff0]
[2] [00007FFAAC97C470] [ntdll.dll!NtFreeVirtualMemory] [jmp RobloxPlayerBeta.dll+0x15a3230]
[2] [00007FFAAC97C510] [ntdll.dll!NtQueryVirtualMemory] [jmp RobloxPlayerBeta.dll+0x17a7b70]
[2] [00007FFAAC97C5B0] [ntdll.dll!NtMapViewOfSection] [jmp RobloxPlayerBeta.dll+0x19b99d0]
[2] [00007FFAAC97C5F0] [ntdll.dll!NtUnmapViewOfSection] [jmp RobloxPlayerBeta.dll+0x1ab5da0]
[2] [00007FFAAC97C630] [ntdll.dll!NtTerminateProcess] [jmp RobloxPlayerBeta.dll+0x1ac5e10]
[2] [00007FFAAC97C770] [ntdll.dll!NtQuerySystemInformation] [jmp RobloxPlayerBeta.dll+0x15b2480]
[2] [00007FFAAC97C910] [ntdll.dll!NtContinue] [jmp RobloxPlayerBeta.dll+0x25fbac0]
[2] [00007FFAAC97C9F0] [ntdll.dll!NtCreateSection] [jmp RobloxPlayerBeta.dll+0x254eeb0]
[2] [00007FFAAC97CA70] [ntdll.dll!NtCreateThread] [jmp RobloxPlayerBeta.dll+0x16d2530]
[2] [00007FFAAC97CAB0] [ntdll.dll!NtProtectVirtualMemory] [jmp RobloxPlayerBeta.dll+0x1be68f0]
[2] [00007FFAAC97CAF0] [ntdll.dll!NtResumeThread] [jmp RobloxPlayerBeta.dll+0x1e328d0]
[2] [00007FFAAC97CB10] [ntdll.dll!NtTerminateThread] [jmp RobloxPlayerBeta.dll+0x1fcb850]
[2] [00007FFAAC97CF20] [ntdll.dll!NtAllocateVirtualMemoryEx] [jmp RobloxPlayerBeta.dll+0x1599fb0]
[2] [00007FFAAC97D7E0] [ntdll.dll!NtCreateSectionEx] [jmp RobloxPlayerBeta.dll+0x1d04410]
[2] [00007FFAAC97D840] [ntdll.dll!NtCreateThreadEx] [jmp RobloxPlayerBeta.dll+0x1be57c0]
[2] [00007FFAAC97E280] [ntdll.dll!NtMapViewOfSectionEx] [jmp RobloxPlayerBeta.dll+0x1970730]
[2] [00007FFAAC97ECA0] [ntdll.dll!NtRaiseException] [jmp RobloxPlayerBeta.dll+0x19c2d70]
[2] [00007FFAAC97ECC0] [ntdll.dll!NtRaiseHardError] [jmp RobloxPlayerBeta.dll+0x2353ea0]
[2] [00007FFAAC97F140] [ntdll.dll!NtSetContextThread] [jmp RobloxPlayerBeta.dll+0x1881e20]
[2] [00007FFAAC97F760] [ntdll.dll!NtSuspendThread] [jmp RobloxPlayerBeta.dll+0x207c850]
[2] [00007FFAAC97F960] [ntdll.dll!NtUnmapViewOfSectionEx] [jmp RobloxPlayerBeta.dll+0x15cbe90]
[2] [00007FFAAC97FCE0] [ntdll.dll!KiUserApcDispatcher] [jmp RobloxPlayerBeta.dll+0x11cc170]
[2] [00007FFAAC97FDF0] [ntdll.dll!KiUserCallbackDispatcher] [jmp RobloxPlayerBeta.dll+0x11cc080]
[2] [00007FFAAC97FE40] [ntdll.dll!KiUserExceptionDispatcher] [jmp RobloxPlayerBeta.dll+0x11cc050]
[2] [00007FFAAC97FEB0] [ntdll.dll!KiRaiseUserExceptionDispatcher] [jmp RobloxPlayerBeta.dll+0x207e530]
[2] [00007FFAAA4C7640] [KERNELBASE.dll!SetUnhandledExceptionFilter] [jmp RobloxPlayerBeta.dll+0x1d84590]
The jump addresses on these are all wildly different though, and most of these functions are completely benign by all accounts
…where did you even pull this from?
It saddens me that we’ve gotten to the point of debugging this ourselves. No news from ROBLOX for more than a week.
Thank you for drawing my attention to this tool!
5 Likes
If they continue to ignore us. Ill just contact my state’s attorney general on behalf of everyone that has spent money that’s now unusable
11 Likes
Object code can’t really be read anywhere. Only the CPU understands the language in your dump file.
1 Like
I already got moderated
They removed the post and its not only the one post they removed from this account.
Hopefully they didnt instantly perm ban my account so getting these posts just removed is alot better than getting perm banned on roblox
1 Like
Have you tried this solution? It worked for me although it still crashed or closed itself when I joined two or three games but then it worked again
This Didnt work for me, unfortunately
1 Like
I’ve tried many things to fix this problem, and absolutely nothing works. I guess i will continue using the desktop app 
1 Like
Hi, everyone,
I would like to share my experience with Roblox crashing; for the past ~2 weeks I have been crashing consistently after ~7 minutes of play time, today I fixed my problem.
The issue:
By default, I was playing Roblox through the directory C:\Users\<username>\AppData\Local\Roblox\Versions\version-<VersionNumber>\RobloxPlayerBeta.exe, which I assume is the new 64-bit version.
For some reason, I would crash after ~7 of having Roblox open consistently.
The solution:
By manually going to the directory C:\Program Files (x86)\Roblox\Versions\version-<VersionNumber> and starting RobloxPlayerBeta.exe through there, I was able to play Roblox without crashing.
Around the time I expected to crash, I instead received a memory dump notification. Something to note is if I don’t press ‘OK’ for the memory dump quick enough, I will crash.
The notification:
^^Full screenshot^^
What I get when I press ‘OK’:
What I think the problem is:
Obviously, I think that whatever that ‘memory dump’ notification is, the 64-bit client does not like it and instead chooses to crash.
I hope my information has been invaluable to someone.
Also, please start compressing images using WebP instead of JPEG 1, and allow DevForum users to upload WebP images.
- Knew
3 Likes
Unfortunately, that solution didn’t work for me.
4 Likes
That’s unfortunate to hear. I don’t understand how such a problem can happen for so long, it definitely seems memory related (on Roblox’s end, I have 32GB@3200MHz).
EDIT: I should also mention that you NEED to press that ‘OK’ button, you have like 5 seconds to do it before it crashes. After that, you are golden. It isn’t a fix, but a workaround for the time being.
On the Roblox down outage site, over 800 reports in the past hour alone.
Why is this still happening after 3 weeks??
4 Likes
For me, Roblox didn’t even show up.
So maybe with the update the way cache is read and wrote, and the code changed too much so it couldn’t update properly, and when it tries to read the code/cache but it doesn’t understand it, it freaks out and crashes?
For me it didn’t run at all but when I uninstalled roblox and manually removed everything, and reinstalled it, it was able to even show up for 3 seconds.
So I removed cache (using the “Clean Disk” feature of Windows, and include DirectX cache) and now it does the same thing as niyuuesuto.
2 Likes