Crash on Win : Fatal Error: unknown 0x00008000 / 0x7ffb833b01dc

We are having random crash happening on windows platform. Please find the call stack below.

Steps to Reproduce
We are having random crash happening on windows platform. Please find the call stack below.

`OS Version: Windows 10 (22H2) [10.0.19045.5796] 10.0.19045 (None)
Report Version: 104

Crashed Thread: 2052

Application Specific Information:
Fatal Error: unknown 0x00008000 / 0x7fffe645af29

Thread 2052 Crashed:
0 KERNELBASE.dll 0x7fffe645af29 RaiseException
1 MyWhoosh.exe 0x7ff6a2477e52 ReportGPUCrash (WindowsPlatformCrashContext.cpp:1780)
2 MyWhoosh.exe 0x7ff6a39c7bb7 TerminateOnDeviceRemoved (D3D11Util.cpp:135)
3 MyWhoosh.exe 0x7ff6a39c959d VerifyD3D11Result (D3D11Util.cpp:233)
4 MyWhoosh.exe 0x7ff6a39b5102 FD3D11DynamicRHI::GetQueryData (D3D11Query.cpp:354)
5 MyWhoosh.exe 0x7ff6a39bfd6f FD3D11DynamicRHI::RHIGetRenderQueryResult (D3D11Query.cpp:228)
6 MyWhoosh.exe 0x7ff6a37d350e [inlined] RHIGetRenderQueryResult (DynamicRHI.h:1337)
7 MyWhoosh.exe 0x7ff6a37d350e FGPUOcclusionPacket::OcclusionCullPrimitive (SceneVisibility.cpp:2371)
8 MyWhoosh.exe 0x7ff6a37dc9ad FGPUOcclusionSerial::AddPrimitives (SceneVisibility.cpp:2995)
9 MyWhoosh.exe 0x7ff6a37f6324 FVisibilityTaskData::ProcessRenderThreadTasks (SceneVisibility.cpp:3936)
10 MyWhoosh.exe 0x7ff6a37dd102 FDeferredShadingSceneRenderer::BeginInitViews (SceneVisibility.cpp:4922)
11 MyWhoosh.exe 0x7ff6a3240409 FDeferredShadingSceneRenderer::Render (DeferredShadingRenderer.cpp:2760)
12 MyWhoosh.exe 0x7ff6a37bbd20 RenderViewFamilies_RenderThread (SceneRendering.cpp:4571)
13 MyWhoosh.exe 0x7ff6a37b1b26 [inlined] FRendererModule::BeginRenderingViewFamilies::__l44::::operator() (SceneRendering.cpp:4846)
14 MyWhoosh.exe 0x7ff6a37b1b26 [inlined] TEnqueueUniqueRenderCommandType::DoTask (RenderingThread.h:209)
15 MyWhoosh.exe 0x7ff6a37b1b26 TGraphTask::ExecuteTask (TaskGraphInterfaces.h:1265)
16 MyWhoosh.exe 0x7ff6a22ee9ad [inlined] FBaseGraphTask::Execute (TaskGraphInterfaces.h:866)
17 MyWhoosh.exe 0x7ff6a22ee9ad [inlined] FNamedTaskThread::ProcessTasksNamedThread (TaskGraph.cpp:758)
18 MyWhoosh.exe 0x7ff6a22ee9ad FNamedTaskThread::ProcessTasksUntilQuit (TaskGraph.cpp:648)
19 MyWhoosh.exe 0x7ff6a3ba1494 [inlined] FRHICommandListImmediate::AcquireThreadOwnership (RHICommandList.h:4511)
20 MyWhoosh.exe 0x7ff6a3ba1494 [inlined] RHIAcquireThreadOwnership (RHICommandList.h:5363)
21 MyWhoosh.exe 0x7ff6a3ba1494 [inlined] RenderingThreadMain::__l7::FScopedRHIThreadOwnership::{ctor} (RenderingThread.cpp:397)
22 MyWhoosh.exe 0x7ff6a3ba1494 RenderingThreadMain (RenderingThread.cpp:409)
23 MyWhoosh.exe 0x7ff6a3ba2fc6 FRenderingThread::Run (RenderingThread.cpp:536)
24 MyWhoosh.exe 0x7ff6a2481876 FRunnableThreadWin::Run (WindowsRunnableThread.cpp:146)
25 MyWhoosh.exe 0x7ff6a247eff0 FRunnableThreadWin::GuardedRun (WindowsRunnableThread.cpp:79)
26 kernel32.dll 0x7fffe8087373 BaseThreadInitThunk
27 ntdll.dll 0x7fffe8a3cc90 RtlUserThreadStart

Thread 9756 name: GameThread
0 ntdll.dll 0x7fffe8a8d574 ZwWaitForSingleObject
1 KERNELBASE.dll 0x7fffe6448a9d WaitForSingleObjectEx
2 MyWhoosh.exe 0x7ff6a2482f05 FEventWin::Wait (WindowsPlatformProcess.cpp:1600)
3 MyWhoosh.exe 0x7ff6a3b9adb0 GameThreadWaitForTask (RenderingThread.cpp:1242)
4 MyWhoosh.exe 0x7ff6a3ba71bf FRenderCommandFence::Wait (RenderingThread.cpp:1305)
5 MyWhoosh.exe 0x7ff6a4dc891b FEngineLoop::Tick (LaunchEngineLoop.cpp:6058)
6 MyWhoosh.exe 0x7ff6a4dcfd3b [inlined] EngineTick (Launch.cpp:61)
7 MyWhoosh.exe 0x7ff6a4dcfd3b GuardedMain (Launch.cpp:190)
8 MyWhoosh.exe 0x7ff6a4dcfdb9 GuardedMainWrapper (LaunchWindows.cpp:118)`

Hi,

This is a long-standing DX11 crash (UE-92814) that can be caused by a variety of factors, but the lack of debug info means we’re typically unable to track an exact cause unless you have specific repro steps. If you’re seeing this occasionally in crash reports from players, it could be caused by out-of-date drivers or by updating video drivers while the application is open, but any possible GPU driver crash will cause a similar callstack (TerminateOnDeviceRemoved) regardless of the exact cause of the crash. If you’re able to narrow down a specific repro case where the crash occurs, we can dig into it more to see if there may be a solution.

Best,

Cody