Causes
- Intel Arc B390 GPU uses the new Xe3 architecture with 12 Xe3 cores — the driver stack is still maturing and older DirectX 9/10/11 games may trigger a TDR (Timeout Detection and Recovery) crash when the driver fails to properly translate legacy draw calls to the Xe3 pipeline. This is a known growing pain for Intel Arc GPUs that manifests as a sudden black screen followed by a "display driver stopped responding and has recovered" notification, or a hard system freeze requiring a forced shutdown
- The Intel Arc G3 Extreme processor integrates both CPU and GPU die in the same package, sharing a fixed thermal and power budget. When the CPU boost algorithm (Intel Turbo Boost Max 3.0) spikes one or two cores to 4.6 GHz while the GPU is under sustained gaming load, the combined package power can exceed the AeroBlade cooling system's dissipation capacity, causing the GPU driver to hit a TDR timeout as the GPU clocks drop abruptly to stay within thermal limits
- XeSS 3 (Xe Super Sampling 3) with Multi-Frame Generation requires the Intel Graphics Command Center driver to negotiate with each game's implementation. Games that lack native XeSS 3 support or use an older XeSS 1.x DLL can crash when the driver attempts to enable frame generation, especially when running at 120 Hz VRR on the internal 1920×1200 display. The crash typically occurs during the loading screen or within the first minute of gameplay
- Windows 11 Xbox Mode applies a system-level overlay and game-specific GPU scheduling that can conflict with the Intel Arc B390 driver's native D3D12 graphics pipeline. The Xbox Game Bar overlay's "Capture" and "Performance" widgets hook into the same GPU command queues as the Xe3 driver, which can cause a video scheduler internal error (VIDEO_DXGKRNL_FATAL_ERROR blue screen or a game hard crash with no error dialog)
- Dual Thunderbolt 4 ports enabling eGPU docking — when an external GPU is connected via Thunderbolt 4 while the internal Arc B390 is under load, Windows' GPU switching logic can incorrectly route rendering calls to the wrong adapter. The Intel Arc driver's hybrid-graphics context management may handshake improperly with the Thunderbolt 4 PCIe tunnel, leading to a "driver crashed and was restarted" event and a black screen for 2–5 seconds while the display reinitialises
- Outdated Intel Graphics Command Center or Arc Control Panel versions — Intel issues driver-only updates separately from the Control Panel app. Running an older Control Panel build (pre-2026 Q2) with a newer driver, or vice versa, can cause the driver's game profile database to fail loading, resulting in crashes on game launch or settings that refuse to apply (XeSS toggle greyed out, resolution locked to 1280×800)
How to Fix
- Install the latest Intel Arc & Iris Graphics driver directly from Intel. Open your browser, go to intel.com/content/www/us/en/download/785597/ (Intel Arc & Iris Graphics Driver for Windows). Download the latest full driver package (version 101.6252 or newer, released June/July 2026). Before installing, download Display Driver Uninstaller (DDU) from guru3d.com. Boot into Windows Safe Mode (hold Shift while clicking Restart → Troubleshoot → Advanced Options → Startup Settings → Restart → press 4). Run DDU, select "GPU" → "Intel" → "Clean and restart". Once back in normal Windows, install the new Intel driver with a clean installation (check the "Clean Installation" checkbox in the installer). Restart again after installation completes. This removes any corrupted driver state, stale registry entries, or conflicting XeSS DLLs from previous installations
- Disable Intel Turbo Boost Max 3.0 during gaming to prevent power spikes. Open the Intel Graphics Command Center (right-click desktop → Intel Graphics Settings). Go to System → Power. Set GPU Power Limit to Balanced instead of Performance. Then click the Advanced tab and enable GPU Tarkov Stabilizer (a misnamed but effective power smoothing feature). Back on the Windows desktop, press Win + R, type
powercfg.cpl, press Enter. Click Change plan settings on your active plan → Change advanced power settings. Scroll to Processor power management → Maximum processor state → set to 99% (this disables CPU turbo). For gaming, switch between this power plan for stability and a separate 100% plan for non-gaming tasks. This prevents the 14-core G3 Extreme from drawing sudden power spikes that trigger GPU TDR events - Enable Hardware-Accelerated GPU Scheduling (HAGS) and adjust graphics settings. Open Windows Settings → System → Display → Graphics. Click Change default graphics settings. Ensure Hardware-accelerated GPU scheduling is turned ON. Below that, turn Variable Refresh Rate to On. Then click Browse under Graphics settings and add each problematic game's .exe file. Click the game → Options → select High performance (the Arc B390) — this forces the game to run on the Arc GPU rather than potentially being misrouted through the iGPU. Also in the Intel Graphics Command Center, go to Gaming → select each game profile → set XeSS to Quality (not Ultra Performance) for 1200p and disable Frame Generation for games that crash on loading
- Disable the Xbox Game Bar overlay or remove it for specific games. Press Win + I → Gaming → Game Mode. Toggle Game Mode ON (this is fine — it helps with scheduling), but scroll down and click Xbox Game Bar → toggle it OFF. Alternatively, if you still want the Game Bar for screenshots, open the game you're having trouble with, press Win + G to open Game Bar, click the Settings gear icon, then uncheck all Performance widgets and disable the Capture overlay. The Game Bar's GPU monitoring hooks into the same WDDM context as the Intel driver, and disabling these widgets eliminates the interference that causes driver timeouts
- Set a fixed GPU clock speed in the Intel Arc Control Panel (undervolt + frequency lock). Download Intel Arc Control from the Microsoft Store (if not pre-installed). Open it, go to the Performance tab. Under Tuning, enable Custom mode. Set the GPU Frequency Offset to −50 MHz (this slightly undervolts and stabilises the Xe3 GPU). Set Voltage Offset to −20 mV. Click Apply. Under Advanced Control, set Power Limit to 28W (the B390's optimal efficiency point) — this prevents power spikes that cause TDR events while only reducing peak performance by about 5–8% in most titles. Click Save Profile and name it "Stable Gaming". Create a second profile at 35W for games that don't crash. Applications will use whichever profile you have active
- Update the game's XeSS DLL to the latest version. For games that support XeSS but crash when enabling it, the game may bundle an outdated XeSS 1.x DLL. Download the latest libxess.dll (version 3.0 or newer) from Intel's GitHub releases: github.com/intel/xess/releases. Navigate to your game's installation folder (e.g.,
C:\Program Files\Steam\steamapps\common\GameName), locate the libxess.dll file in the game's root orEngine\Plugins\folder. Back up the original file, then replace it with the newer version. Right-click the new DLL → Properties → check Unblock if Windows Defender blocks it. Launch the game and re-enable XeSS — the updated DLL fixes many compatibility issues with the Xe3 architecture on the Arc B390 - Disable the Thunderbolt 4 controller when not using an eGPU. Open Device Manager (Win + X → Device Manager). Expand System devices. Locate Thunderbolt(TM) 4 Controller or Intel Thunderbolt 4 Controller (there are two entries, one for each USB4 port). Right-click each → Properties → Driver tab → Disable Device. Confirm. When you need to use an eGPU or Thunderbolt dock, re-enable them. Disabling the Thunderbolt controllers removes the PCIe tunneling overhead from the GPU driver's context management, eliminating driver crashes related to display-route switching when no eGPU is connected. Restart the Predator Atlas 8 after disabling the controllers
- Perform a clean driver reinstall using Intel's driver repair tool as a last resort. If crashes continue after the above steps, download the Intel Driver & Support Assistant (IDSA) from intel.com. Run it and let it scan. It will detect that the current driver is installed. Click Repair. After repair, restart. Then download and run the Intel Arc Control Panel installer again to re-register the gaming profiles. If the issue persists and produces a VIDEO_DXGKRNL_FATAL_ERROR blue screen with the error code 0x113 (TIMEOUT_DETECTED), the GPU may have a hardware defect. Contact Acer Predator Support at acer.com/support and reference the TDR error code — the Predator Atlas 8 ships with a one-year limited warranty covering the Intel Arc B390 GPU, and Acer has an advanced RMA program for GPU-related blue screens within the first 90 days of ownership