Cyberpunk 2077 Intel Arc B580 Crash Fix — DXGI_ERROR_DEVICE_HUNG

Updated October 27, 2026

Cyberpunk 2077 Intel Arc B580 crash fix infographic detailing three troubleshooting steps: disabling ray tracing and path tracing, updating Intel Arc graphics drivers past version 32.0.101.8991, and disabling XeSS Frame Generation or overlays to resolve the DXGI_ERROR_DEVICE_HUNG error.

Cyberpunk 2077 can crash on some Intel Arc B580 systems with a DXGI_ERROR_DEVICE_HUNG error, particularly when ray tracing is enabled. The game may close during a mission, freeze during a cutscene, or produce a GPU crash report even though other games run normally.

One documented issue affects Intel Arc B-Series graphics cards using driver 32.0.101.8991. Intel recommends disabling ray tracing as a workaround. Checking for a newer compatible graphics driver is also worthwhile, especially if the crashes began after a recent driver installation.

However, not every Intel Arc crash has the same cause. If Cyberpunk 2077 continues crashing with ray tracing disabled, XeSS Frame Generation, driver configuration, or another graphics issue may be involved.

This guide explains how to disable ray tracing, check your Intel graphics driver, troubleshoot repeatable crashes, and inspect crash reports without immediately reinstalling Windows or deleting your game files.

Quick Answer: How to Fix DXGI_ERROR_DEVICE_HUNG on Intel Arc B580

If Cyberpunk 2077 crashes with DXGI_ERROR_DEVICE_HUNG on an Intel Arc B580:

  1. Launch Cyberpunk 2077 and open Settings → Graphics.
  2. Disable Ray Tracing, including path tracing or Overdrive settings.
  3. Apply the changes and restart the game if necessary.
  4. Load the save or mission where the crash occurred and test again.
  5. Check your installed Intel graphics-driver version. Driver 32.0.101.8991 is associated with a documented crash issue.
  6. Check Intel's website for a newer compatible graphics driver.
  7. If the crash continues, disable XeSS Frame Generation, if enabled.
  8. Verify the game files and consider testing a previously stable Intel driver.

Important: Disabling ray tracing is Intel's recommended workaround for the documented Arc B-Series issue. It is not a guaranteed solution for every DXGI_ERROR_DEVICE_HUNG crash.

⬆ Back to Table of Contents

What Does DXGI_ERROR_DEVICE_HUNG Mean in Cyberpunk 2077?

DXGI_ERROR_DEVICE_HUNG is a DirectX graphics error indicating that the GPU or graphics driver stopped successfully processing work submitted by the application.

In some crash reports, the same error appears as:

0x887A0006

Cyberpunk 2077 may also display a message such as:

Gpu Crash for unknown reasons!

The error does not automatically mean your graphics card is physically damaged.

It can occur because of a graphics-driver problem, a particular rendering feature, unstable GPU settings, or another issue affecting the graphics pipeline.

Why Intel Arc B580 Players Should Check Ray Tracing First

A documented issue affects Cyberpunk 2077 on Intel Arc B-Series graphics cards after installing graphics driver 32.0.101.8991.

The problem can trigger DXGI_ERROR_DEVICE_HUNG, and Intel recommends disabling ray tracing as a workaround.

This makes ray tracing one of the most useful settings to test first, especially if the game crashes repeatedly in the same location or cutscene.

However, a crash with ray tracing already disabled may have a different cause.

⬆ Back to Table of Contents

Fix 1: Disable Ray Tracing and Path Tracing

Disabling ray tracing is the primary workaround to test for the documented Intel Arc B-Series crash.

Even if your B580 can normally handle ray-traced effects, a driver-specific issue may cause Cyberpunk 2077 to crash when those features are active.

How to Disable Ray Tracing

  1. Launch Cyberpunk 2077.
  2. Open Settings.
  3. Select Graphics.
  4. Find the Ray Tracing settings.
  5. Disable the main Ray Tracing option.
  6. Make sure Path Tracing or Ray Tracing: Overdrive is not enabled.
  7. Apply the changes.
  8. Restart the game if prompted.

If the graphics menu exposes individual ray-traced effects, ensure those are disabled for the test as well.

Test the Same Save or Mission

After disabling ray tracing:

  1. Load the save where the crash occurred.
  2. Return to the same area or cutscene.
  3. Repeat the action that previously triggered the error.
  4. Continue playing long enough to check whether the problem returns.

If the crash disappears, ray tracing or its interaction with the driver may be contributing to the problem.

You can continue playing with ray tracing disabled while checking for a compatible driver update.

Should You Lower Every Graphics Setting?

Not immediately.

The first test should isolate ray tracing rather than changing your entire graphics preset.

If the game becomes stable after disabling ray tracing, you may be able to keep other graphics settings at their previous values.

This avoids sacrificing image quality unnecessarily.

What if the Game Crashes Before You Can Change the Setting?

If Cyberpunk 2077 cannot reach the graphics menu:

  • Restart Windows and try launching the game again.
  • Disable any active graphics overlays.
  • Verify the game files through your launcher.
  • Temporarily remove nonessential mods or graphics injectors.
  • Check for a newer compatible Intel driver.

If you decide to reset the game's configuration files, back them up first. Do not delete saved games or entire configuration folders without identifying what they contain.

⬆ Back to Table of Contents

Fix 2: Check Your Intel Arc Graphics Driver

After testing ray tracing, check which Intel graphics driver is installed.

This helps determine whether your system is using the driver associated with the documented crash.

Step 1: Find Your Installed Driver Version

On Windows 11:

  1. Right-click the Start button.
  2. Select Device Manager.
  3. Expand Display adapters.
  4. Double-click your Intel Arc B580.
  5. Open the Driver tab.
  6. Check the Driver Version field.

Look for:

32.0.101.8991

If this version is installed, your system may be affected by the documented issue.

That does not prove the driver is responsible for your particular crash, but it gives you a useful starting point.

Step 2: Check for a Newer Intel Driver

Visit the official Intel Download Center.

Find the latest compatible Intel Arc graphics driver for your hardware and Windows version.

Read the release notes before installing, particularly any known issues or fixes related to Cyberpunk 2077, DirectX 12, or Intel Arc B-Series graphics cards.

If a newer compatible driver is available, consider updating.

Step 3: Restart and Retest

After installing the driver:

  1. Restart Windows.
  2. Launch Cyberpunk 2077.
  3. Load the same save where the crash occurred.
  4. Test the affected mission or area.
  5. Check whether the crash returns.

Keep your other graphics settings unchanged during this test.

If the game still crashes, continue with the remaining troubleshooting steps.

Can a Newer Intel Driver Fix the Crash?

Possibly.

Intel has tested a newer 101.9150 driver build and reported that it could not reproduce the original crash in its testing.

That is encouraging, but it does not establish a guaranteed fix for every Intel Arc B580 system.

Check the latest compatible driver release rather than assuming one particular version will resolve every crash.

If your game works normally after updating, continue using the stable configuration.

⬆ Back to Table of Contents

Fix 3: Troubleshoot Repeatable Cutscene or Mission Crashes

Some Intel Arc B580 crashes occur at a repeatable point in Cyberpunk 2077 rather than during random gameplay.

For example, the game might run normally while exploring Night City but crash during a particular story sequence.

Identifying the crash pattern helps determine what to test next.

Case 1: The Game Always Crashes at the Same Cutscene

If the crash happens at exactly the same point:

  1. Make a manual save before the affected sequence, if possible.
  2. Disable ray tracing.
  3. Load the save.
  4. Repeat the cutscene or mission.
  5. Check whether you can progress beyond the previous crash point.

If disabling ray tracing allows you to continue, keep it disabled while checking for a compatible driver update.

Case 2: The Game Crashes Randomly During Exploration

If crashes happen in different locations or during unrelated activities, the cause may be broader than one ray-tracing workload.

Check:

  • Whether the crash occurs with ray tracing disabled.
  • Whether XeSS Frame Generation is enabled.
  • Whether the driver was recently updated.
  • Whether GPU overclocking or undervolting is active.
  • Whether third-party overlays or graphics tools are running.

A random crash pattern does not automatically rule out a driver issue, but it makes a single cutscene-specific explanation less likely.

Case 3: The Same Cutscene Crashes With Ray Tracing Disabled

If the crash continues even after disabling ray tracing, do not assume the documented workaround has failed for every affected system.

Your crash may involve another graphics feature or a separate driver problem.

The next useful test is to disable XeSS Frame Generation, if enabled.

Why You Should Change One Setting at a Time

Do not simultaneously disable ray tracing, change your upscaling method, lower every graphics setting, and reinstall your driver.

If the crash disappears after several changes, you will not know which one helped.

Testing one feature at a time gives you a clearer result.

⬆ Back to Table of Contents

Fix 4: Disable XeSS Frame Generation

If Cyberpunk 2077 continues crashing with ray tracing disabled, test XeSS Frame Generation separately.

Some Intel Arc configurations have experienced crashes involving Frame Generation even when ray tracing was not active.

This may represent a different issue from the documented ray-tracing-related DXGI_ERROR_DEVICE_HUNG problem.

How to Test XeSS Frame Generation

  1. Open Cyberpunk 2077.
  2. Go to Settings → Graphics.
  3. Locate Frame Generation.
  4. If XeSS Frame Generation is enabled, turn it off.
  5. Keep your upscaling and resolution settings unchanged.
  6. Apply the changes.
  7. Load the affected save and test again.

If Frame Generation was already disabled, skip this step.

Should You Disable XeSS Upscaling Too?

Not necessarily.

XeSS Upscaling and XeSS Frame Generation are different technologies.

XeSS Upscaling reconstructs the image from a lower rendering resolution.

XeSS Frame Generation creates additional displayed frames.

You can test Frame Generation independently where the game allows it.

If the crash continues, you can perform a separate test with upscaling disabled or changed, but do not assume both features are responsible.

What if Disabling Frame Generation Fixes the Crash?

Leave Frame Generation disabled and continue using a stable graphics configuration.

You can test it again after a compatible Intel driver update.

Remember that Frame Generation is optional. A stable base frame rate is more useful than a higher FPS counter accompanied by repeated crashes.

⬆ Back to Table of Contents

Fix 5: Test a Previously Stable Intel Graphics Driver

If Cyberpunk 2077 started crashing immediately after a graphics-driver update, a driver rollback may help.

This is especially worth considering if the game worked normally before the update and the crashes began without any other major changes.

Option 1: Use Windows Driver Rollback

  1. Right-click Start.
  2. Open Device Manager.
  3. Expand Display adapters.
  4. Double-click Intel Arc B580.
  5. Open the Driver tab.
  6. Select Roll Back Driver, if available.
  7. Follow the prompts.
  8. Restart Windows.

The rollback button may be unavailable if Windows does not retain a previous driver package.

Option 2: Install a Previously Stable Driver

If Windows cannot roll back:

  1. Visit the official Intel Download Center.
  2. Find a compatible previous graphics-driver release.
  3. Confirm that it supports your Intel Arc B580 and Windows version.
  4. Follow Intel's installation instructions.
  5. Restart Windows.
  6. Test Cyberpunk 2077 again.

Use official driver packages rather than unknown third-party download sites.

Should You Always Roll Back?

No.

A newer driver may already contain improvements for the original crash.

If you are using driver 32.0.101.8991, checking for a newer compatible release is generally a better first step than immediately installing an older version.

Rollback is most useful when you know a previous driver worked correctly on your system.

⬆ Back to Table of Contents

Fix 6: Verify Game Files and Disable Overlays

If the crash continues after testing ray tracing, Frame Generation, and drivers, check for other software problems.

These steps are general troubleshooting measures rather than confirmed fixes for the Intel Arc driver issue.

Verify Cyberpunk 2077 Files on Steam

  1. Open Steam.
  2. Go to your Library.
  3. Right-click Cyberpunk 2077.
  4. Select Properties.
  5. Open Installed Files.
  6. Click Verify integrity of game files.

Wait for the verification process to finish before launching the game again.

Verify Files on GOG or Epic Games

If you own the game through GOG Galaxy or Epic Games Launcher, use the launcher's repair or verification feature.

This checks whether important game files are missing or damaged.

Disable Unnecessary Overlays

Temporarily disable overlays from:

  • Discord.
  • Steam.
  • Intel graphics software.
  • Performance-monitoring utilities.
  • Recording and capture applications.
  • Third-party graphics tools.

Then launch the game and test again.

If the crash stops, re-enable the overlays one at a time to identify a possible conflict.

Check GPU Overclocking and Undervolting

If you use custom GPU tuning, restore the graphics card to its default settings for testing.

An unstable overclock or undervolt can cause graphics errors that resemble driver problems.

Do not assume the Intel Arc B580 is defective simply because Cyberpunk 2077 reports a device-hung error.

Test Without Outdated Mods

Mods that modify graphics rendering, inject files, or depend on older game versions can cause problems after updates.

Temporarily test the game without nonessential mods.

Back up your files and saves before making changes.

⬆ Back to Table of Contents

How to Find Cyberpunk 2077 Crash Reports

If none of the fixes work, the crash report can help distinguish the documented Intel Arc issue from another problem.

Cyberpunk 2077 may save crash reports in a Windows user-profile folder.

A common location is:

%LOCALAPPDATA%\REDEngine\ReportQueue

How to Open the Folder

  1. Press Windows + R.
  2. Paste the path above.
  3. Press Enter.
  4. Look for a report created around the time of the crash.

Not every crash generates a report in this folder.

If the folder does not exist or contains no recent report, the crash may have been logged elsewhere or may not have generated a report.

What to Look For

Useful error details include:

  • DXGI_ERROR_DEVICE_HUNG
  • 0x887A0006
  • Gpu Crash for unknown reasons!

You do not need to understand every line of the crash report.

The exact error code and your driver version are often more useful than a general description such as "the game keeps crashing."

Record Your Graphics Settings Separately

Crash reports do not necessarily include every graphics setting that was active when the game failed.

Record the following information yourself:

  • Installed Intel graphics-driver version.
  • Whether ray tracing was enabled.
  • Whether XeSS Frame Generation was enabled.
  • Whether custom GPU tuning was active.
  • The mission or location where the crash occurred.
  • Whether the crash was repeatable.
  • The approximate time of the crash.

These details can help distinguish a known driver problem from another graphics issue.

What to Include in a Support Report

If you contact Intel or the game's support team, include:

  • Your graphics card model: Intel Arc B580.
  • Your installed driver version.
  • Your Windows version.
  • The exact crash error.
  • Your relevant graphics settings.
  • Whether the crash happens randomly or at a repeatable point.
  • The troubleshooting steps you have already tested.

Avoid sharing crash reports publicly without checking whether they contain personal file paths or other identifying information.

⬆ Back to Table of Contents

Is DXGI_ERROR_DEVICE_HUNG Caused by Cyberpunk 2077 Update 2.5?

Not necessarily.

Cyberpunk 2077 Update 2.5 changed several graphics features, but the documented Intel Arc B-Series crash is associated with a particular graphics-driver configuration.

That means a player may encounter the error while running Update 2.5 without the game update itself being the confirmed cause.

If the crash began after updating both the game and graphics driver, test the driver and rendering settings before assuming one update is entirely responsible.

Other Update 2.5 Problems

Not every Cyberpunk 2077 performance issue is related to Intel Arc.

If the game takes unusually long to load on an AMD Ryzen system, our Cyberpunk 2077 2.5 AMD SMT slow-loading guide explains how to test the SMT setting while watching for possible FPS loss.

If you are using an AMD Radeon GPU and the game opens to a black screen with HDR enabled, see our Cyberpunk 2077 2.5 HDR black-screen fix.

For players experiencing high reported FPS but uneven motion, our Cyberpunk 2077 2.5 FSR Frame Generation stuttering guide covers a separate performance problem.

These issues have different causes, so use the guide that matches your symptoms and hardware.

⬆ Back to Table of Contents

Frequently Asked Questions

How do I fix DXGI_ERROR_DEVICE_HUNG in Cyberpunk 2077 on Intel Arc B580?
Start by disabling ray tracing and checking your Intel graphics-driver version. If you are using driver 32.0.101.8991, check for a newer compatible Intel release. If crashes continue, test with XeSS Frame Generation disabled.

Is Intel driver 32.0.101.8991 causing Cyberpunk 2077 crashes?
Intel has documented a Cyberpunk 2077 DXGI_ERROR_DEVICE_HUNG issue affecting Arc B-Series graphics cards after installing this driver. However, not every crash on that driver is necessarily caused by the same problem.

Does disabling ray tracing fix the Intel Arc B580 crash?
Disabling ray tracing is Intel's recommended workaround for the documented issue. It can help affected systems, but it is not guaranteed to fix crashes caused by other problems.

Can a newer Intel driver fix Cyberpunk 2077 crashes?
Possibly. Newer drivers may contain improvements for known crashes. Check the latest compatible Intel graphics-driver release and its notes rather than assuming one specific version fixes every system.

Can XeSS Frame Generation cause Cyberpunk 2077 to crash?
Some Intel Arc configurations have experienced crashes involving XeSS Frame Generation. If the game continues crashing with ray tracing disabled, turning off Frame Generation is a useful separate test.

Why does Cyberpunk 2077 crash during the same cutscene?
A repeatable crash can indicate that a particular rendering workload triggers a driver or game problem. Disable ray tracing and retest the same save. If the crash persists, investigate Frame Generation, drivers, and game files.

Is DXGI_ERROR_DEVICE_HUNG a sign of a broken GPU?
Not necessarily. The error indicates that the graphics device or driver stopped successfully processing work. Driver bugs, rendering features, and unstable tuning settings can also cause it.

Where can I find Cyberpunk 2077 crash reports?
Check %LOCALAPPDATA%\REDEngine\ReportQueue for recent reports. Not every crash produces a report there, so also record your driver version, graphics settings, and exact error message separately.

⬆ Back to Table of Contents

Final Thoughts

If Cyberpunk 2077 crashes on an Intel Arc B580 with DXGI_ERROR_DEVICE_HUNG, start by disabling ray tracing and checking your installed Intel graphics-driver version.

For the documented Arc B-Series issue associated with driver 32.0.101.8991, disabling ray tracing is the recommended workaround. Checking a newer compatible driver is also worthwhile.

If the game still crashes with ray tracing disabled, investigate XeSS Frame Generation, driver stability, and other software conflicts separately rather than assuming every device-hung error has the same cause.

The best troubleshooting method is to change one setting at a time and retest the same location or mission. That makes it easier to identify what improves stability without unnecessarily reducing graphics quality.

⬆ Back to Table of Contents

Comments