Reproduction steps:
1. Connect an external monitor with a USB Type-C-to-Type-C cable to the first Type-C port from the left on the back of the Alienware 16X Aurora (AC16251) laptop
2. Open Unity Hub and create a new 3D project (doesn’t matter if it’s BiRP or Universal)
3. Drag the Editor window to an external monitor
4. In the Editor, grab the splitter of the Inspector and keep dragging it from one side to the other
5. Observe the Editor and the whole OS freeze/lag for some time, and then the Editor crashes

Reproducible with: 2023.3.0a3, 6000.0.59f1, 6000.1.16f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Not reproducible with: 2023.1.0a1, 2023.3.0a2

Reproducible on: Windows 11 Pro (24H2)
Not reproducible on: macOS Sequoia 15.7 (M3 Pro)

Notes:

• CQA and the reporter were only able to reproduce this crash with the Alienware 16X Aurora (AC16251) laptop
• Issue is only reproducible when a Type-C cable is connected to the left Type-C port on the back of the laptop
• Issue is reproducible when using Dell U2720Q (made in May, 2021) and HP Z27k G3 4K USB-C monitors (made in July, 2021)
• Issue is not reproducible when using Dell U2719Q (made in December, 2019) monitor
• Reproducible on Direct3D 11, Direct3D 12, Vulkan, OpenGLES3
• Not reproducible on Metal
• Reproducible even with the newest NVIDIA graphics driver (both Game Ready and Studio)
• If the Editor freezes/lags and goes back to normal after a while, repeat the 4th reproduction step
• If you keep repeating the 4th reproduction step, but the Editor always goes back to normal and never crashes, try changing the layout and then repeating the 4th step
• The freezing/lagging is consistent, but the crashing is not - sometimes it takes a few seconds of the 4th step, and the Editor crashes after the first freeze/lag, and sometimes it takes a few minutes and a lot of freezing/lagging and going back to normal cycles to finally make the Editor crash
• Sometimes, moving the mouse from the external monitor to the main display and pressing on the Unity icon while in the middle of the freezing/lagging helps to cause the Editor to crash

First few lines of each encountered stack trace (all from crashes on Direct3D 12):
0x00007FF83FF188AF (Unity) GfxTaskExecutorD3D12::RunTask
0x00007FF83FF1B6BE (Unity) GfxTaskExecutorD3D12::Task
0x00007FF8416D1930 (Unity) Thread::RunThreadWrapper

0x00007FFDFE9244AF (Unity) D3D12RenderPass::SetupDeviceResources
0x00007FFDFE9211B4 (Unity) D3D12RenderPass::Begin
0x00007FFDFE8F6A27 (Unity) GfxDeviceD3D12::BeginRenderPassImpl
0x00007FFDFE6407FA (Unity) GfxDevice::ReleaseSetupAndBeginRenderPass
0x00007FFE0009539D (Unity) GfxDeviceWorker::RunCommand

0x00007FFAE9E15ABE (nvwgf2umx) OpenAdapter10
0x00007FFAE9A58B55 (nvwgf2umx) NVENCODEAPI_Thunk
0x00007FFAE9DE0B37 (nvwgf2umx) OpenAdapter10
0x00007FFAE03F3E9F (D3D12Core) D3D12GetInterface
0x00007FFAFB7CDF96 (Unity) FillRootConstantBuffers