- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
VALORANT has been crashing mid-game (All modes, except for Shooting Range) on my device for quite a while now. It happens suddenly, with no specific in-game triggers that I could identify. A quick check of the ShooterGame.log file at the crash logs folder reveals an error message "DXGI_ERROR_DEVICE REMOVED DXGI_ERROR DEVICE HUNG" at the crash time, repeated multiple times.
The crash itself hangs the game and quite a few error prompts pop up in rapid succession, but all of them have blank descriptions with just "Error" as title.
This issue is limited only to VALORANT and all other games seem to work perfectly and at expected performance levels.
I have tried multiple driver versions (8136, 8135, 8132, 6913), as well as multiple Windows versions (11 25H2, 11 24H2 LTSC, 11 22H2, 10 22H2, 10 21H2 LTSC), but none of them seem to fix the issue. In particular, Windows 10 22H2 tends to have more frequent crashes. Furthermore, I have noticed that crashes seem to get more frequent the more you play the game, but reinstalling the driver reduces the frequency for some time. Driver version 32.0.101.6913 also seems to have less frequent crashes than the other versions, but the crash behavior remains the same.
Fixes I have found on the internet so far do not work in this case. I tried the ones detailed at the official Intel support article for this error, as well as the "TdrLevel" registry tweaks mentioned in various forums, but they do not fix the crashes or make them more unlikely to happen. (The latter one in particular simply stops the appearance of the error prompts and hangs the whole PC instead.) Underclocking/overclocking does not impact the crash frequency.
BIOS changes, like toggling on and off the SMT and PBO controls, or Secure Boot and TPM, do not impact the issue at all. I do not think that my GPU itself is failing - I bought the entire PC not even a month ago, and GPU brackets were there from the beginning to prevent sag, and it has a 650W 80+ Silver PSU. The latest VALORANT crash logs as well as an SSU report will be attached here, and I'll list my specs, just in case:
CPU: AMD Ryzen 5 7500F
GPU: GUNNIR Intel Arc B580 Photon OC 12G
RAM: (2x8) = 16GB Team T-Force Vulcan 8GB DDR5 6000MHz
Motherboard: ASUS B650M-AYW WIFI
SSD: Kingston NV3 1TB
PSU: Gigabyte P650SS 80+ Silver
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Jed! Thanks for waiting, and I'm back with some testing results. They seem to be quite strange.
After several attempts at trying to find this sneaky crash bug, I have not gotten a single crash to happen whatsoever. I've tried multiple new Windows versions, driver versions, settings, but they all give the same result.
I'm assuming that Riot Games released a fix in one of their numerous micro-updates around the time I said that "Low Latency Mode fixes the issue" in one of my previous replies. This also does mean that Low Latency Mode was not a fix, and that if the issue still persisted today, it would most likely not have impacted it, just like any other settings change.
I do have some reasoning that it was specifically a fix that came from Riot Games. At around the same timeframe, on a random day, my average uncapped FPS took a big 50-70 FPS hit, but it was more stable overall and Low Latency Mode did not reduce the framerates too much. I also started seeing some screen tearing if I allowed my FPS to hit below my refresh rate, which is expected behavior for games but it rarely happened with me on VALORANT before. No changes happened to my system prior to that moment, and so I theorize that the micro-update in question was released on that day.
That said, I'm glad to report that the game has been running quite stably so far. Also, if any other people are looking at this post with a similar crash bug, I do still suggest that you play around with your settings and driver/Windows installations before declaring it unfixable. I will be marking this as a solution for now, but only because it will allow other users to quickly know the current state of this issue. And Jed, you have been quite a great help these past few days, and I appreciate you for it.
Sincerely,
GlitchX.
(Post marked as answer on 29 October 2025.)
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello GlitchX,
Thank you for posting on Intel Community Forum. The troubleshooting steps and isolation that you did is crucial to possibly identify the root cause of the issue. Your efforts are highly appreciated and this would really help with our investigation moving forward.
To investigate further, kindly share the additional information below.
1. Did you use DDU prior to installing the drivers?
2. Have you tried using different in game settings?
3. Does it happen in specific maps?
4. Was the game functioning correctly before?
I look forward to your response.
Best regards
Jed G.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi JedG! Thanks for the quick response.
1. Yes, I did use DDU in Safe Mode for every driver reinstallation.
2. Yes, and the issue persists regardless of settings. I've tried setting the graphics to High, Medium, Low and everything in between, trying both Fullscreen and Windowed Fullscreen mode and capping the FPS to 240 (monitor refresh rate).
3. No, the map does not seem to matter as far as I've seen. I've faced crashes on just about every map. (with the sole exception of the Training Range, of course.)
4. No, the game has been like this since I bought this PC (not prebuilt) in the last week of September. It's been quite a few game updates since then, but they did not impact the crash issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quick update: Just tested with Intel oneAPI Level Zero disabled during driver reinstallation. No effect on crash issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello GlitchX,
Thank you for sharing all this information. I'll be investigating this matter internally and I'll give you an update at the earliest opportunity.
Best regards
Jed G.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello GlitchX,
I’m reaching out to share the results of our replication efforts. After thoroughly testing, we were unable to reproduce any issues or crashes on our end. To help us investigate further, could you kindly provide a sample video demonstrating the steps to replicate the problem? This will allow us to test it again in our lab and work toward a resolution.
Best regards
Jed G.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Welcome back, Jed! Thanks for the update.
Sure, I can provide you with a recording of the crash, but I cannot guarantee when I'll be able to give it to you, due to the inherently random and unpredictable nature of the crash. It can take anywhere between half a match to two days or more for a crash to happen, but I'll send it here as soon as I get one on recording.
Also, I think it's a good time to mention that I've found somewhat of a "workaround". After enabling Low Latency Mode for VALORANT through the Intel Graphics Software, or by capping the frames to just about any value (Intel Graphics Software again, in-game limiter does not make the workaround), I've not gotten a crash for quite a few days. I've tested with both my current Windows installation as well as a new one, and this workaround has worked on both the installations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello GlitchX,
I completely understand that capturing a short video clip might take some time, and I truly appreciate the effort you’re putting into this. Please take the time you need—I’ll be here and ready to continue troubleshooting once you’re able to share it. Your cooperation really helps us move closer to resolving the issue effectively.
I also want to sincerely thank you for sharing the temporary workaround you discovered. That kind of initiative is incredibly valuable, and I’m hopeful it will assist other users who encounter the same problem. Your contribution makes a real difference.
If you have questions, please let me know.
Best regards
Jed G.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi GlitchX,
I'm checking to see if you were able to capture a short video clip demonstrating the issue. Please let me know so we can proceed accordingly.
Best regards,
Jed G.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Jed! Thanks for waiting, and I'm back with some testing results. They seem to be quite strange.
After several attempts at trying to find this sneaky crash bug, I have not gotten a single crash to happen whatsoever. I've tried multiple new Windows versions, driver versions, settings, but they all give the same result.
I'm assuming that Riot Games released a fix in one of their numerous micro-updates around the time I said that "Low Latency Mode fixes the issue" in one of my previous replies. This also does mean that Low Latency Mode was not a fix, and that if the issue still persisted today, it would most likely not have impacted it, just like any other settings change.
I do have some reasoning that it was specifically a fix that came from Riot Games. At around the same timeframe, on a random day, my average uncapped FPS took a big 50-70 FPS hit, but it was more stable overall and Low Latency Mode did not reduce the framerates too much. I also started seeing some screen tearing if I allowed my FPS to hit below my refresh rate, which is expected behavior for games but it rarely happened with me on VALORANT before. No changes happened to my system prior to that moment, and so I theorize that the micro-update in question was released on that day.
That said, I'm glad to report that the game has been running quite stably so far. Also, if any other people are looking at this post with a similar crash bug, I do still suggest that you play around with your settings and driver/Windows installations before declaring it unfixable. I will be marking this as a solution for now, but only because it will allow other users to quickly know the current state of this issue. And Jed, you have been quite a great help these past few days, and I appreciate you for it.
Sincerely,
GlitchX.
(Post marked as answer on 29 October 2025.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello GlitchX,
Thank you so much for providing such detailed feedback. I truly appreciate the time and effort you put into sharing your observations, and I’m really glad to hear that everything is now working as expected. Based on the behavior you described, it’s very likely that Riot Games implemented a fix for these issues recently. Your input has been incredibly helpful in confirming that the changes are effective.
Since the initial concern is addressed, I will now close this inquiry. Should you have other questions or concerns in the future, please submit a new question as this thread will no longer be monitored.
Best regards
Jed G.
Intel Customer Support Technician
 
					
				
				
			
		
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page