- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello! I have an ASRock A770 Phantom Gaming D 8GB OC and I have been getting BSODs with increased frequency. The stop code is VIDEO_TDR_FAILURE, what failed: igdkmdnd64.sys.
As of today I am using 32.0.101.6557
I bought this card new in 06/2023 and it has worked great for the most part. Around the end of 2023 I started getting these bluescreens in Fortnite. I attributed it to the new chapter at the time and was regularly updating the graphics drivers as they were released (with DDU) however the crashes still persisted. A work around I have been using since then, is to play in DX11. The bluescreens still occur here however I seem to be able to avoid it if I quickly unfocus the game window as soon as I notice a stutter in game. Usually this means spamming the Windows Key then entering back into the game. The whole thing takes less than 2 seconds. I generally have no problems for the remaining time I play. This seems to be the only way I can play now which sucks as the game takes quite a performance hit in DX11 but it's worth it to not be crashing on my teammates.
By the end of 2024 i started to get these same Bluescreens in other games too. First was Marvel Rivals (Sometimes on launch, sometimes after a few matches), which I just put down to it being an Unreal Engine game like Fortnite, but now also in Rainbow Six Siege (on launch), and Baldurs Gate 3 (after about 20min).
An odd thing I have noticed is that a lot of the time the Bluescreen is over and done with in half a second. Theres no time for the percentage shown to tick up, it just restarts immediately. This sometimes means a minidump doesn't even get saved.
Prior to using .6557, BlueScreenView says the trouble files are "dxgkrnl.sys" and "igdkmdnd64.sys" but in the .6557 minidumps it suggests that it is "ntoskrnl.exe." I have provided a screenshot of this.
For testing purposes I turned everything to low in Fortnite just to make sure the gpu is not pushing itself too hard and there is no difference.
Specs:
Gigabyte B660M DS3H AX DDR4 MATX
i7 12700F
2x16GB 3200Hz DDR4 G.SKILL RAM
Samsung 970 EVo Plus 2TB
Deepcool PM750D 750W gold
Hopefully we can figure this out! It has otherwise been a really great card.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ctrl-Hams,
I wanted to let you know that I've posted in the community, advising that you should contact Asrock for a possible RMA claim regarding your graphics card issue. This step is based on our email conversation and should help you move forward with resolving the problem.
You can reach Asrock support through their official website: Asrock Support. They should be able to assist you with the RMA process.
Since I haven't received a response from you, I will proceed to close the thread. If you have any further questions or need assistance, please feel free to reach out. Your satisfaction is important to me, and I'm here to support you.
Best regards,
Dean R.
Intel Customer Support Technician
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here are the actual minidumps I forgot to add.
https://drive.google.com/drive/folders/1oRLhenT99AQe5c0PcCE0gz2t4NRC5FXD?usp=sharing
11125-01 was on driver .6460
11593-01 was on driver .6557
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ctrl-Hams,
Thank you for posting in the Community!
We have a new driver version 32.0.101.6559 (WHQL Certified) released on February 10, 2025. I suggest installing this and let me know if the issue still persists.
Intel® Arc™ & Iris® Xe Graphics - Windows*
Apply DDU to the driver as well: How to Use the Display Driver Uninstaller (DDU) to Uninstall an...
Best regards,
Dean R.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi DeancR,
I installed .6559 WHQL after DDU today and the problem still persists. Bluescreen after about 2 minutes into a battle royale match in Fortnite.
Here is the minidump text
==================================================
Dump File : 021225-11578-01.dmp
Crash Time : 12/02/2025 11:54:14 am
Bug Check String :
Bug Check Code : 0x00000116
Parameter 1 : ffffcb8b`cd7f5290
Parameter 2 : fffff801`455411b0
Parameter 3 : ffffffff`c0000001
Parameter 4 : 00000000`00000003
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b8460
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+4b8460
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\021225-11578-01.dmp
Processors Count : 20
Major Version : 15
Minor Version : 26100
Dump File Size : 227,328
Dump File Time : 12/02/2025 11:54:49 am
==================================================
Also unrelated to the crashing issue.. This driver update failed to install the Intel Graphics Software. I had to use the 7zip extract method to manually install it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ctrl-Hams,
I appreciate your efforts for providing this information. I would like to request for the following:
Please provide an application event viewer log from your system. Below are the steps to generate the logs
- Right Click on the Start Button
- Click on Event Viewer
- Click on the chevron of the Windows Logs
- Right Click on the Application and select Save All Events As
- Save the file and send us a copy (make sure to indicate the timestamp of the crash)
Please provide a System event viewer log from your system. Below are the steps to generate the logs
- Right Click on the Start Button
- Click on Event Viewer
- Click on the chevron of the Windows Logs
- Right Click on the System and select Save All Events As
- Save the file and send us a copy (make sure to indicate the timestamp of the crash)
Best regards,
Dean R.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I saved the info you requested as a .txt, as the default .evtx is not a supported upload type. Will that work?
I replicated the crash today in Fortnite. Although it crashed much faster this time. I didn't even get to find a match.
Timestamp for today's crash is 13/02/2025 11:44 am
Timestamp for yesterday's crash is 12/02/2025 11:54 am
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ctrl-Hams,
Thank you for your efforts on providing this information however, I suggest uploading the .evtx on a Zip File as checking .txt file on event viewer will not work.
Best regards,
Dean R.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here is the .evtx in a zipped folder.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ctrl-Hams,
I appreciate your efforts for this, let me check this further internally and get back to you once I have the necessary information you need.
Best regards,
Dean R.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have an A770 16GB and Im experiencing exactly the same symptoms as Ctrl-Hams. But sometimes it's just a blackscreen and then a reboot. GPU-Z (setting to 0.1 refresh rate) usually shows my GPU skyrocketing its Core Frequency to 3100+ then going down to 23xx again while my game is glitching, and Core Frequencies above 4000+ at 0,000001 femtoseconds before the BSOD/Blackscreen happens.
Using the latest WHQL driver available btw. Horrible experience.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've since had crashes in modded Minecraft, Civ 5, and Blender. They were all running smoothly, then a sudden freeze, then BSOD. Always the same VIDEO_TDR_FAILURE, what failed: igdkmdnd64.sys.
It's pretty frustrating to not be able to play much anymore. Hopefully a fix can be found soon.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I did some trial and error and actually found the issue. Disabling XMP temporally fixed my issue for a few hours; I found that VCCIO and VCCSA voltages were related (lowering = less BSOD/Blackscreens) but were not the root of this mayhem.
It was the ATX 24 pin connector; any load on the 12v line (regardless of the source's connector) caused a drop in the motherboard's 12v line (giving context: this GPU draws around 75W from the PCIe port). Even if it had good values (11.7v), that wasnt enough for this crapp... creepy, this creepy graphics card for some weird reason.
Just download HWINFO and check the 12v, 5v and 3.3v values. Minimum values must stay at 11.9v, 4.9v (5v not related but some USB devices / chipsets are picky) and 3.2v or above under load (im forced to tell you again that its only for this card because 11.7v is covered by 12v atx specs / tolerance range and nothing is wrong with your PSU). If not, try reseating the ATX 24 pin connector from the motherboard. Tell me if this works for you. Do u have a modular PSU? Then, reseat the connector from the PSU side too.
Im trulyintrigued; in those situations why tf does the power management algorithm think its a good opportunity to unrealistically increase the core frequency? My theory its... well, spaghetti-like driver's codebase + bad electrical design (shunts or something else).
My ancient gtx 1080 gpu ran fine within those values btw xd. Sorry for my "barely acceptable"? english. I tried c':
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is my first time using HWinfo. If i'm reading these sensor readings correctly then my voltages were,
At desktop
12V: 11.880
5V: 5.010
3.3V: 3.225
Under Load (Fortnite at time of crash)
12V: 11.808
5V: 5.010
3.3V: 3.206
This was with XMP off. I've experimented with XMP on/off in the past trying to fix this issue but it has not made a difference in my experience. I did unseat and reseat the 24pin connector however it made no change to the voltages or the crashing.
Thank you for trying to help though! And don't worry your English is great! Although i've never seen the word 'creepy' be used to describe a GPU before lol
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ctrl-Hams,
I'm still looking this further internally and will reach out to you once I have the necessary information.
Hi Aceitunator,
Thank you for sharing this concern in the community however to avoid further confusion I suggest creating a new thread for this.
Best regards,
Dean R.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ctrl-Hams,
Thank you for providing the dump files for analysis. The review indicates different root causes for each BSOD, but both are linked to the GPU.
Here are the highlighted error messages:
- 020325-11125-01.dmp: Failure Bucket ID: 0x116_TdrBCR:3:C0000001_Tdr:9_DxgKdxFailed_IMAGE_igdkmdnd64.sys_GEN12_0_ENGINE
- 020825-11593-01.dmp: Failure Bucket ID: 0x116_TdrBCR:3:C0000001_IMAGE_igdkmdnd64.sys
At this point, I recommend performing a clean OS installation to rule out any software issues.
Please let me know if this suggestion helps. Also, if you are reporting an Intel-branded graphics card, I can assist you in processing the warranty through Intel Customer Support on your behalf. If you are reporting an (ASRock) OEM-branded Intel Arc card, you can use this message as proof of my assessment of your graphics card's condition.
Best regards,
Dean R.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for the update. I will report back after a clean OS install. It may be a few days before I get around to doing it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ctrl-Hams,
I appreciate you for getting back to me, take the time you need, and I look forward for your update.
Best regards,
Dean R.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ctrl-Hams,
I just wanted to check in regarding my previous message about your inquiry. Have you had a chance to look it over? If there's anything you're unsure about or if you need more information, please feel free to reach out.
Best regards,
Dean R.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Dean R,
Sorry for the delay. I performed a clean OS install (Win11 Pro 24H2 (KB5050575)). Unfortunately the issue still persists even with the only software installed being
- The latest graphics driver (32.0.101.6632) + intel graphics software
- Epic Games launcher
- Fortnite
lasted about 5min in Fortnite, no stutters or anything then sudden BSOD.
I still seem to get 2 different causes for the crash, ntoskrnl.exe and dxgkrnl.sys + igdkmdnd64.sys. Another thing I've noticed is that in BlueScreenView it says the product name and company is Microsoft whereas before it did not state these. Does this mean it's potentially a windows issue and not the intel driver? I have attached a screenshot and the minidumps files.
9656-01 is the first crash in Fortnite after the fresh windows install
10750-01 is also in Fortnite after some more programs are installed and other component drivers updated through the Gigabyte Control Center App.
Is this looking like a faulty card? I have seen some other forum posts online with similar or the same issues regarding igdkmdnd64.sys BSOD across both A and B series cards. Here is one example: https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/967
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ctrl-Hams,
Thank you for your efforts for providing this information. I would like to know if you agree to continue our communication via email for this issue.
Best regards,
Dean R.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page