Graphic Hardware Crashes when Loading Local Test Server

Hello,

Whenever I attempt to load a local server in Roblox Studio, my client has graphics-related crashes.
This happens exactly as studio attempts to render any frames on a server client. It only occurs in server test, regular single player test functions as normal. It is not my roblox game, because the issue persists on an empty baseplate.

So far I have received two different crash exception codes: 0x517a7ed and 0x887a0005
Both crash codes are related to “graphics device removed.”
0x887a0005 specifically is DeviceD3D11RemovedError.

On crash, studio hangs and my screen flashes black.

Lenovo ThinkPad P16v
Intel Core Ultra 7 155H
NVIDIA RTX 2000 Ada Generation Laptop GPU
NVIDIA Drivers 581.15 & 573.73

The graphics devices function as normal for any other applications.
I have tried restarting my device, reinstalling my graphics drivers, changing my windows graphics settings for Roblox, nvidia control panel settings, changed my studio graphics mode, but none have solved my issue.

Any help is appreciated.

I have included the studio log below contain the span of time from server start to crash.

2025-09-25T22:11:37.725Z,801.725525,8848,6,Info [FLog::StudioKeyEvents] start local server/player test
2025-09-25T22:11:37.727Z,801.727539,8848,6 [FLog::UpdateUIManager] Start waiting for long process(000001E81FA377C0): Start server
2025-09-25T22:11:37.729Z,801.729553,8848,6 [FLog::UpdateUIManager] Pausing status bar update (000001E81FA377C0)
2025-09-25T22:11:37.751Z,801.751282,8b34,6 [FLog::StudioLocalSaveMD5HashOutput] Place saved locally to C:/Users/****/AppData/Local/Roblox/server.rbxl with hash *************************
2025-09-25T22:11:37.756Z,801.756287,8848,6,Info [FLog::RenderSchedulerState] Pushing skip render state (count 1)
2025-09-25T22:11:37.756Z,801.756287,8848,6 [FLog::UpdateUIManager] (DEPRECATED) Showing progress for long process(000001E81FA377C0): Start server
2025-09-25T22:11:37.757Z,801.757263,8848,6 [FLog::UpdateUIManager] (DEPRECATED) Hiding progress for long process (000001E81FA377C0)
2025-09-25T22:11:37.757Z,801.757263,8848,6,Info [FLog::RenderSchedulerState] Popping skip render state (count 0)
2025-09-25T22:11:37.758Z,801.758301,8848,6 [FLog::UpdateUIManager] Resuming status bar update (000001E81FA377C0)
2025-09-25T22:11:37.783Z,801.783203,8848,6 [FLog::UpdateUIManager] Done waiting for long process: Start server
2025-09-25T22:11:37.784Z,801.784241,8848,6 [FLog::CloseDataModel] closeDataModel - 0000000000000000
2025-09-25T22:11:37.784Z,801.784241,8848,6,Info [FLog::StudioKeyEvents] launching new studio instance
2025-09-25T22:11:37.784Z,801.784241,8848,6,Info [FLog::StudioApplicationManager] Create ChildProcessHandler
2025-09-25T22:11:39.204Z,803.204224,8848,6,Info [FLog::StudioApplicationState] State: Qt::ApplicationInactive 
2025-09-25T22:11:39.204Z,803.204224,8848,6,Info [FLog::RenderSchedulerState] Pushing throttle render state (count 1)
2025-09-25T22:11:39.204Z,803.204224,8848,6,Debug [FLog::DataModelSoundManager] onApplicationStateChanged: m_isApplicationActive = false
2025-09-25T22:11:39.204Z,803.204224,8848,6,Debug [FLog::DataModelSoundManager] onApplicationStateChanged: with shouldMute = true
2025-09-25T22:11:39.204Z,803.204224,88bc,6,Debug [FLog::DataModelSoundManager] DataModelSoundManager::updateSoundState(true)
2025-09-25T22:11:39.204Z,803.204224,88bc,6,Debug [FLog::DataModelSoundManager] soundService->muteAllChannels(true)
2025-09-25T22:11:45.873Z,809.873535,8848,6,Warning [FLog::Graphics] WARNING: D3D Frame query much longer than expected.
2025-09-25T22:11:47.772Z,811.772034,8848,6,Warning [FLog::Graphics] WARNING: D3D Frame query timed out, has device hung?
2025-09-25T22:11:52.287Z,816.287048,8848,6 [FLog::Graphics] D3D11 FATAL ERROR: Device removed with reason 0x887a0005 (DXGI_ERROR_DEVICE_REMOVED)
2025-09-25T22:11:52.569Z,816.569397,8848,6 [FLog::Error] DeviceError encountered, shutting down Studio: (DeviceD3D11RemovedError) Device encountered an error: Device removed (0x887a0005)
2 Likes

This crash stopped happening about a month ago for me. I don’t believe a change on my end solved the issue.