Hi, Everyone!
I’m having an Issue upon my roblox crashing constantly, after playing 10 - 15 minutes.
Device Specifications (Laptop)
- Intel i5-4210U CPU @ 1.70GHz 2.40 GHz
- 8.00 GB RAM
- Intel Graphics Family
- SanDisk 128GB SSD
- Windows 10 22H2 (Activated)
Anyway, I’ll start already with payload description. Crashing is immediate, roblox becomes unresponsive after 10 - 15 minutes of playtime sometimes it crashes instantly upon loading like In Arsenal, It also happends in games that have too much assets.
What i’ve tried so far :
- sfc /scannow
- reboot few times
- re-installing roblox couple times
- Updating my graphics drivers
- Updating my display drivers (some said it was display hardware faulty)
- C:\ cleanup check and corruption check
- \temp and tmp folders are empty,
- Adjusted VRAM capacity
- Tried disconnecting some of my devices like Mouse (still didn’t work)
- tried updating graphics settings, also didn’t work.
- Tried playing roblox on different levels of graphics
Expected behavior
Payload description :
So, while playing some of the games, like Forsaken, the game runs pretty smoothly, I play on lowest graphics levels, after 10 - 15 minutes of playtime, ** the screen itself on roblox application freezes, displays a frame before like in reverse half a second before and just crashes and says “Roblox Stopped Responding.” I have done some of the research, couldn’t come up with the fix, some microsoft experts say that it’s probably application bug since roblox is more likely to update.
It also affects on the games with Most assets like Arsenal, Jailbreak, etc…
Anyway, I have gathered many details, I have been watching my GPU while playing roblox, it goes smoothly, only after 10 - 15 minutes and the GPU itself has a big downfall and spikes up to 100% already upon crash impact. And THEN displays windows application crash message! Reliability history says it’s AppHangB1

A private message is associated with this bug report