The VK_ERROR_DEVICE_LOST at BOS-07 wasn't a hardware failure. It was a death by a thousand paper cuts. A shader had requested a 64-bit float operation. The driver had tried to emulate it with a software routine. The routine had taken 50 milliseconds too long. The Vulkan queue had timed out. The GPU had reset. And now, Boston was 3.4 seconds behind the rest of the grid.
Three point four seconds. In a power grid synchronized to 60 cycles per second, that was an eternity. That was a phase angle of 734 degrees. That was a direct short circuit across two thousand miles of transmission lines. The VK_ERROR_DEVICE_LOST at BOS-07 wasn't a hardware failure
Time to consider an upgrade or adjust your driver expectations. Details in the latest Mesa release notes. The driver had tried to emulate it with a software routine
Modern games, DXVK, vkd3d (DirectX 12), or Vulkan compute. The GPU had reset
: For better overall 3D performance on older chips, ensure you are using the newer Gallium3D driver rather than the older Hardware Realities
: Ivy Bridge (Gen7) graphics were designed before Vulkan existed. Intel has never officially certified these chips as fully Vulkan-compliant. Driver Evolution
<device driver="intel"> <application name="all"> <option name="vk_disable" value="true"/> </application> </device>