Roblox games load for about 3 seconds then instantly crash

Bug Reports Engine Bugs
#776

.pdb files contain debugging information and aren’t actually run.

NTDLL is the file that defines how Windows NT functions - it’s basically the framework for the entire operating system. Hyperion should only have problems with it if it’s modified, which you can’t even do without getting TrustedInstaller permissions.

1 Like
#777

i fixed the store version bugs i can finally open it everytime i want to open it

1 Like
#778

@Bitdancer do we have any estimate for as to when a fix will be pushed out? I cannot access roblox at all, either via Player or UWP. They both just instantly crash.

2 Likes
#779

if you have problems with both versions better dm/pm the procdump generated Crash Message to Bitdancer Or To Deraxile [subto_deraxileonyt] Deraxile Answered My DM a bit quicker than Bitdancer… If You Have Patience Message Bitdancer He Knows More than Deraxile although he knows how to identify the problematic byfron flagged DLLs

i learned my lession from this: never buy asus products if they have AsusTEK Software Installed (tbh its your choice its my only good pc…)

2 Likes
#780

Hopefully you guys fix Vulkan Hyperion compatibility
For the most part there’s a significant performance benefit over D3D with older Hardware
Over current D3D, I’m able to run at over 2 times the performance
Perhaps a note to make Vulkan the base renderer should be brought up in a meeting?

1 Like
#781

Yes, you are correct, but zavatarteam2 is still unlocked, also they do exist it’s only that they have only been locked down for Roblox staff only.
Only a select few channels were locked.

CC: @mimi235664556655

Let the poor guy have a break? :frowning: I’m sure other engineers are sliently working on the issue
Also have you tried the following:

  • Unplugging all hardware apart from your keyboard and mouse to verify the crashing isn’t caused by other non-essential peripherals
  • Make sure to not enforce the Player to use the Vulkan rendering API via FastFlags
  • Make sure you have quit out of Bitdefender fully (If you have it)
  • Make sure you have unplugged any Logitech steering wheels as it has been confirmed to cause crashes (If you have one)
  • Quit out of non-critical processes and try again
  • Go into Task Manager, disable most if all applications on start-up and restart your machine to try again
  • Changing your deployment channel to zavatarteam2 or other (Has been confirmed to fix SOME instances)

If all else fails, check if a crash dump has been generated, these strategy steps are very helpful.
Send your crash dump to @Bitdancer via DevForums direct messages, remember to:

  • Do not directly upload or link your dump publicly, to anyone other than Roblox staff
  • Crash dumps will be massive (We are talking 5 to 1 GB) be sure to upload them to a file sharing platform like Google Drive
  • Make sure that only people with the link can view and access the file so Bitdancer will be able to download the crash dump without issues
1 Like
Roblox client unexpectedly crashes without error message
Logitech G923 Crashes Roblox Upon Boot
#782

soo it fixes my steamvr crashes the zavatarteam2 channel?

#783

Unsure, you’ll have to try and troubleshoot it yourself with all the information currently available, I’m not a wizard.

1 Like
#784

it says failed to fetch information

1 Like
#785

I have no idea what Vulkan Rendering or zavatarteam2 is.

I’ve only got my mouse and keyboard plugged in, I don’t have BitDefender, I don’t have any Logitech Products, i’ve already quit processes and Applications on startup.

1 Like
#786

I got crash when connecting a rumble activated [Installed Driver] gamepad controller (SpeedLink SL-6635)
0.601.0.6010507_20231105T105738Z_Player_E2D03_last.log (15.8 KB)
This is only client side (not studio)

Studio using this gamepad controller fine but no rumble feature (Rumble feature driver already installed)

#787

Vulkan runs far better with studio than D3D11 ever has. Seems like a stupid arbitrary block to disallow use of vulkan on the client, and I would love to know the admin’s reasoning.

#788

Is it because Vulkan on Roblox was made for mobile devices first?

#789

My guess is:
More work for the Hyperion Development Team
They’re focusing on D3D to prevent any sort of hacking
It’s time consuming enough to focus on preventing one renderer from any ESP vulnerabilities let alone two

Hyperion shouldn’t be active in Studio, so Vulkan should work compared to the Game Client

#790

Yes, this is exactly why. It is not an “arbitrary block” like some people would like to think. Their general expectation is that only Direct3D will be used on Windows, Metal for Apple devices, OpenGL for anything that’s old enough, which leaves Vulkan to be expected to only run on Android.

3 Likes
#791

Vulkan is not blocked at all, it just has a poor implementation that causes issues with Hyperion.

No, not at all, that’s now how that works.

#793 
2023-11-05T21:07:14.634Z,280.634857,12e8,6 [FLog::Output] Flamingo
2023-11-05T21:07:14.634Z,280.634857,12e8,6 [FLog::Output] addedFlamingo
2023-11-05T21:07:14.665Z,280.665802,2738,6 [FLog::Output] table: 0x1b881462e70a29cb
2023-11-05T21:07:14.665Z,280.665802,2738,6 [FLog::Output] Fish
2023-11-05T21:07:14.665Z,280.665802,2738,6 [FLog::Output] addedFish
2023-11-05T21:07:14.665Z,280.665802,2738,6 [FLog::Output] table: 0x1b881462e70a29cb
2023-11-05T21:07:14.665Z,280.665802,2738,6 [FLog::Output] Goggles
2023-11-05T21:07:14.666Z,280.666809,2738,6 [FLog::Output] table: 0x1b881462e70a29cb
2023-11-05T21:07:14.666Z,280.666809,2738,6 [FLog::Output] FlipFlop
2023-11-05T21:07:14.666Z,280.666809,2738,6 [FLog::Output] table: 0x1b881462e70a29cb
2023-11-05T21:07:14.666Z,280.666809,2738,6 [FLog::Output] BloxyCola
2023-11-05T21:08:35.421Z,361.421814,1d0c,6 [FLog::Output] Settings Date header was Sun, 05 Nov 2023 21:08:35 GMT
2023-11-05T21:08:35.422Z,361.422791,1d0c,6 [FLog::Output] Settings Date timestamp is 1699218515
2023-11-05T21:09:06.381Z,392.381104,1188,6 [FLog::Graphics] D3D11 FATAL ERROR: Device removed with reason 0x887a0006 (DXGI_ERROR_DEVICE_HUNG: La GPU no responderá a más comandos, probablemente porque la aplicación que realiza la llamada ha pasado un comando no válido.)
2023-11-05T21:09:07.572Z,393.572266,33c0,6 [FLog::Output] StartProcessException...
2023-11-05T21:09:10.829Z,396.829071,33c0,6 [FLog::Output] Studio D3D9 GPU: Intel(R) Iris(R) Plus Graphics
2023-11-05T21:09:10.829Z,396.829071,33c0,6 [FLog::Output] Studio D3D9 GPU: Vendor 8086 Device 8a52
2023-11-05T21:09:10.829Z,396.829071,33c0,6 [FLog::Output] Studio D3D9 Driver: igdumdim64.dll 30.0.101.2079
2023-11-05T21:09:10.830Z,396.830048,33c0,6 [FLog::Output] ESGamePerfMonitor GPU: Vendor 00008086 Device 00008a52
2023-11-05T21:09:10.830Z,396.830048,33c0,6 [FLog::Output] ESGamePerfMonitor GPU: SubSys 85f3103c Revision 00000007
2023-11-05T21:09:10.830Z,396.830048,33c0,6 [FLog::Output] ESGamePerfMonitor GPU: DedicatedVidMem 134217728 DedicatedSysMem 0 SharedSystemMemory 8475533312
2023-11-05T21:09:12.094Z,398.094086,33c0,6 [FLog::Output] Uploading crash analytics...

Now i get this after crashing… i finally got it to show the actual issue in the FloG file, can someone tell me what does this even mean?

#794

Completely ignore this now, Roblox has decided to axe and brutally murder any and all non-production deployment channels. Including zavatarteam2 which helped some people fix crashing issues.
image

Now I can no longer archive the cool little easter eggs that don’t make it to prod by Roblox engineers :sad:

Apparently from what I’ve heard, majority of the crashing issues (same on Linux) has been resolved, let’s just hope something like this never happens again.

#795

The GPU will not respond to further commands, probably because the calling application has passed an invalid command.)

Check if your drivers are up-to-date, that’s all I can say. (This error message from DirectX, not exclusive to Roblox)

1 Like
#796

This has been happening to me alot recently.
For some reason, sometimes it stops happening, then it suddenly happens again.

It also results on wacky images like these two (please mind that they are old)

funnycrash
funnycrash1440×840 8.93 KB

whack.PNG
whack.PNG1438×831 95.8 KB

2 Likes