i think something is going on.
this is not just an issue with software being blocked by hyperion, but usually i’ve also noticed that before crashing my cpu usage spikes up for a few minutes. i also got a bsod because my chipset driver crashed???
4 Likes
This started happening to me too after the new year, especially whenever I zoom in or out in games, and whenever I use chat. It happens on any game. Studio seems to work fine for me though.
2 Likes
I wish their was a way to track these seemingly random client crashes because I’m not sure Roblox engineers are aware of the scope of this issue since a crash dump is not generated and nothing is logged in the client logs. I fear that Roblox is not aware of the frequency of these crashes.
I wouldn’t think these crashes would be logged in the Experience’s client crash rate either if the client doesn’t even know it crashed, its just gone and never writes to the log.
It is frustrating when you have no clues to help you move towards a resolution.
2 Likes
There’s analytics and telemetry to track crashes, but it sounds like it’s a pretty low level of crashing, and if no crash dumps are being generated the crash dump handler is probably not running.
You could also use an external program to record crash dumps. There should be some instructions in this thread somewhere.
2 Likes
I have tried those. If the crash was recorded by ‘telemetry’ then why isn’t the client log being written to? Why isn’t a crash dump generated? I have tried the procdump method suggested by @Bitdancer but it does not catch or record anything when this type of crash happens.
3 Likes
I’ve also recently started having these hard crashes. Approximately two minutes after the first log message is recorded, the client encounters a memory access violation and freezes before closing itself. This persists through clean installs and on new Windows users. I’ve made a bug report with my dump file so hopefully I hear back from them soon.
Really weird how this suddenly started happening after one of the weekly Roblox updates with seemingly no known cause. I’m not entirely sure why RobloxPlayer is trying to access memory addresses that don’t exist to begin with
4 Likes
At least you get a dump file, I get nothing, client just disappears and nothing is logged anywhere.
Good luck on yours though.
3 Likes
You used the procdump method right? I wasn’t able to get any logs either until I configured procdump
2 Likes
Yes I set that up but it doesn’t capture anything. Is there any trick to setting it up? I thought I did it right.
2 Likes
My whole Roblox Studio window has been randomly crashing without any error message too!! I can’t make a post about it because of Roblox’s leveling system, and I don’t have a Regular trust level.
Specs:
Intel Core i5-10th gen
Nvidia GeForce GTX 1660 Super
Ram: 8 GB
3 Likes
Also got that same issue too, crashing (or even BSOD) without any error message at all.
Intel® UHD Graphics 630
Intel(R) Core™ i3-8100 CPU
RAM: 8 GB
Friendly reminder that ROBLOX is a billion-dollar company.
1 Like
What is the BSoD error code? It’s pretty extreme for you whole system to just, give up, because of an application that doesn’t even ask for Administrator permissions. It could be a side-effect from another application. Do you use any GPU monitoring software? I know that there was a setting in RivaTuner Statistics Server that caused BSoDs and crashes for someone else.
I used to have this issue with my old, 8 year old PC which had an nvidia card. When I bought a new one for unrelated reasons, without an nvidia GPU, it stopped crashing. As a last resort, you could try to take out the GPU, delete ALL nvidia software and see if it works.
Thing is that the BSOD just quickly for a very few seconds after it appeared, which I can’t even find an error code. Also I don’t have GPU monitoring software.
I think based on your experience, it may just be correlated with driver issues. A better idea instead of reassembling my computer (which I have no knowledge on how to do so, and I DO NOT want to risk breaking something), is just to update, fix, or replace with newer drivers.
Look in your windows event log, filter by id: 1001
you will find the error code there
FYI these frequent(many times daily) random interval crashes are still happening, no way to troubleshoot without error messages. I get nothing, client just disappears and nothing is logged anywhere.
1 Like
Over the last two weeks, we have made significant changes. Is the issue still persistent in the latest version?
Yes still getting frequent crashes with nothing in the client log and no crash dump no popup messages.
Well I call them crashes, what happens is that the client just disappears with no evidence of a crash.(that I can find)
1 Like
There are two possible ways the client can create a crash dump: either a file called HYP*.tmp is created upon crashing, or a regular crash dump with the extension *.dmp is created. One strategy to find the files involves deleting all HYP*.tmp and *.dmp files from the disk and then running the client again. Upon crashing, check if there are any HYP*.tmp or *.dmp files.
1 Like