Intel® ARC™ Graphics
Get answers to your questions or issues when gaming on the world’s best discrete video cards with the latest news surrounding Intel® ARC™ Graphics
2877 Discussions

BSOD while editing in PremierePro-Arc B580 32.0.101.6739 drivers

Mejnour32
Novice
2,871 Views

Hello,

I am doing PremierePro video edition with dual monitor set-up.
I tried really hard to keep video drivers updates but since version 6651 everything was unstable, after many DDU deinstall/install, disk scans, etc
I was running Intel Graphics Driver 32.0.101.6651 WHQL because there were the most stables drivers with my PC.

I finally decided to give a try to the lastest driver 32.0.101.6739.
But now I am getting BSOD igdkmdnd64.sys Video TDR failure Error.
It happen when I am editing in PremierePro, it can happen suddently when I am playing the timeline or simply doing Lumetri correction.

It make to sense to stay forever with outdated drivers...
I have included Windows dump File and SSU IntelScan file.



Regards
Remy

 

 

 

https://1drv.ms/f/s!AuGMfOle_TxqjRT-_Y7P2UMKMSR5?e=WOKbJh 

39 Replies
darkGT
Beginner
2,030 Views

Exactly the same even with older drivers, basically day 1 of me using the card!

 

I raised a ticked: 

Thread ID: ref:!00DU0YT3c.!500KZ06pQsR:ref

Thread Token: thread::z-v2gvxtd9ScKVCZ_wNWRFA

 

My problem triggers mostly when I replace a footage with After Effects composition, but After Effects alone can also trigger this exact Blue Screen. If someone from Intel staff is reading this, please take a look at my ticket, I have attached my BSOD dump file and my specs from Hardware info.

0 Kudos
Mejnour32
Novice
2,001 Views

Yep this problem drive me crazy.


Today I double check everything from hardware connection, window update, mobo update, ssd firmware,
Health Scan, Disk scan.

Still getting this BSOD easily after couples minutes of playing in project.  I tried different projects, same BSOD.

Then I tested encoding.  First project did encode first time.  Then I try another project, encoding just stopped avec few minutes,

like no GPU response, I could heard the GPU stop working, no activity on the Intel Graphics Software performance.  This observation was not new to me, normally I close Premiere Pro and retry until it work.

But this time since the task was stuck at 16%; I just stopped the encoding and send the encoding directly in Media Encoder, and it succeed to do the task.


I think they working hard to get stable drivers.  I could see the evolution/difference in tuning the ressource between CPU/GPU over the last month.

0 Kudos
RandyT_Intel
Moderator
1,977 Views

Hi @Mejnour32,

 

Thank you for posting in the community. To further assist you and investigate the issue, please provide answers to the following questions below.

 

  • Have you tried reinstalling the application?
  • What version of Premiere Pro are you currently using?
  • Have you contacted Adobe Support regarding this issue?
  • Have you tried loading default in BIOS?

 

Based on what I gathered online, it appears to be a RAM issue. However, I double-checked the SSU report you shared, and it seems everything is updated and meets the hardware recommendations for Premiere Pro and After Effects. This shouldn't be the cause of the issue you're encountering.

 

Please give me some time to coordinate this matter internally. I'll post an update here or notify you directly once I have more information. 

 

Regards,

 

Randy T.

Intel Customer Support Technician

 

0 Kudos
Mejnour32
Novice
1,929 Views

Hello Randy,

I am running Premiere Pro version 25.2.3 (Build 4)

Yesterday I did all kind of troubleshooting.

I did DDU Intel GPU uninstall in safe mode and then re-install the latest WHQL certified 32.0.101.6737.

I didn't contact Premiere Pro support because when I physically remove the Arc B580 from my PC, I can edit 
in Premiere Pro without, freeze, or crash issue.

You have to understand that I have been dealing with all kind of annoying problem since the purchase of this unit and all clues goes toward the GPU.  I understand that it's a new GPU and I have been patient, but now after couples month, I still have stability issue when using this GPU in Premiere Pro.  I don't do gaming.

Regards
Remy


0 Kudos
jamesoverland
Novice
31 Views

Randy, this driver issue does not have anything to do with other components, many of us are encountering it on very different systems. I'm encountering the same issue with Davinci Resolve. I have an open support case if you want to review that: Case #: 06570012. 

0 Kudos
Mejnour32
Novice
1,913 Views

Update

Encoding test for 80min SD project.

Ultra 265K alone ~30min rendering.

Ultra 265K + Arc580 ~15min rendering (dGPU 100%)

After removing Arc580 and not be able to reproduce de BSOP with the CPU alone, I did add my previous dGPU RTX2060 in the same PCIe lane with the same power cable.  So far so good.


Encoding test for 80min SD project.

Ultra 265K + RTX 2060 ~15min rendering.

 

0 Kudos
darkGT
Beginner
1,900 Views

I also didn't have BSOD when I was only using my iGPU in Ryzen 7 7700. 

What brand GPU do you have? I have Asrock Steel Legend, perhaps one of the first batches, I purchased in February this year. 

Is there any particular point during the export or timeline playing when the blue screen will trigger for you? For me it usually it's after 20min to 1 hour of use and only on demanding tasks. 

 

0 Kudos
Mejnour32
Novice
1,860 Views

Funny Ryzen 7 7700/7900 was in my initial option choice when I decided DYO PC build.

But right not cannot complain about the Ultra 265K, perform like a beast so far.

I have the Intel Limited Edition.

I am doing a lot of Lumetri Correction (HSL Layers) on old VHS footage.

So most of the time it happens when I am tweaking color.
But it already happened when I was doing simply playing timeline footage.

Before I did try a bunch of drivers version and the least "lethal" was the 32.0.101.6651 WHQL.

In the worst case he was freezing Premiere Pro, but no BSOD.

Maybe you can try it yourself if you still get BSOD with 32.0.101.6651 WHQL?

0 Kudos
Mejnour32
Novice
1,802 Views

Interesting thread this guy experienced similar observation as mine when trying different drivers.

Some were doing BSOD, others just freezing the app.

He find out that installing just the drivers without the others stuff was giving him stability.

Re:Persistent BSOD - High Probability on RDP Connect to Idle/Locked PC - Intel Community

 

Also some Adobe report talking about Windows killing some GPU capability in specific situation.
https://helpx.adobe.com/substance-3d-painter/technical-support/technical-issues/gpu-issues/gpu-drivers-crash-with-long-computations-tdr-crash.html


So it might be "bad" communications between Software, Windows and Intel...


0 Kudos
RandyT_Intel
Moderator
1,609 Views

@Mejnour32 I am also handling this case- Re:Persistent BSOD - High Probability on RDP Connect to Idle/Locked PC - Intel Community you posted. We are still investigating it. According to the user's observation, the issue occurs only when the Intel graphics software is not installed; he has only performed the driver installation.

0 Kudos
RandyT_Intel
Moderator
1,855 Views

Hi @Mejnour32,


Thank you for sharing this information. I will begin investigating the issue and attempt to replicate it on our end. I'll post an update here or notify you directly once there are any developments. If I need further details, I'll reach out to you here. I appreciate your patience as I work on this matter. 


Regards,

 

Randy T.

Intel Customer Support Technician


0 Kudos
K22
Beginner
1,775 Views

b580.jpg

B580 LE

265K +4070 Super + B580 Winodws11 24H2.
Dual QHD 240, QHD 165.

6739 Driver

BSOD PremierePro, YouTube....
igdkmdnd64.sys

 

0 Kudos
Mejnour32
Novice
1,760 Views

Do you have the same stop code Premiere Pro vs Youtube?

My stop code is VIDEO_TDR_FAILURE

How to Fix VIDEO_TDR_FAILURE BSODs | Tom's Hardware

Have you try remove the B580 and just keep the 4070 to see if the BSOD stop?

TDR.jpg

0 Kudos
RandyT_Intel
Moderator
1,606 Views

@Mejnour32 You may also check this article-Blue Screen Error: "VIDEO TDR FAILURE" with Intel® Graphics and.... However, upon reviewing your SSU logs, it appears that the BIOS is already updated.

0 Kudos
RandyT_Intel
Moderator
1,725 Views

Hi @Mejnour32,

 

I need some clarification. To assist us in further investigating the problem, could you please provide the following information:

 

  1. Could you attempt a screen recording to demonstrate how to replicate the issue? If that's not possible, please provide the exact steps for replication so we can try it on our end.
  2. Is the issue occurring exclusively with Premiere Pro version 25.2.3 (Build 4) and not with other applications, resulting in a BSOD? Is that correct?
  3. Please try using only one monitor to see if the BSOD still occurs and inform us of the outcome.
  4. What is the make, model, and power wattage of your power supply?
  5. Please share the dump/log files by following the steps under "Crashing/freezing issues/BSOD" in our "Need help? Reporting a bug or issue with Arc GPU? - PLEASE READ THIS FIRST!"

 

Your cooperation in providing this information will greatly assist us in diagnosing and resolving the issue.

 

Regards,

 

Randy T.

Intel Customer Support Technician


0 Kudos
Mejnour32
Novice
1,662 Views

Hello,

1-Look in my one drive folder, crash #8856.  There is a mp4 video, DumpFile and Intel Infos (txt file).

2-No the issue can be repeated also under previous version of PremierePro, 25.1 which was the build at the time of B580 purchased.
It's not always BSOD.  Sometime Premiere Pro just become unresponsive.  I can also easily trigger GPU shut down by starting a rendering and if I open device manager AFTER to see the GPU performance, the rendering just stop and GPU just sleep.  I have to close Premiere Pro to get it back active.

3-I already try it, one or 2 monitors, 4K monitor or just FullHD monitor, I can BSOD with all those configuration.  Also with DisplayPort only in iGPU, no difference.

4- Corsair Plus Gold RM850x...850Watt  bought new jan2025 (release date 2021)

5-Yeah already did, I have generate 4 new dump file today included in onedrive.  There is one assiated with the screen recording #8856.

Personal observation.

It' really hard to define exactly what trigger the BSOD, I don't know of accurate is the Windows Device Manager toward B580 analysis, 
but I notice that in the Lumetri Panel there is some "effect" that seem to trigger high utilisation of GPU.   HSL Secondary seem one of this effect.  

I am using third party plugins (NeatVideo; FreeLab) but NeatVideo doesn't support IntelGPU, and FreeLab is just a fancy LUT.
and I was able to get BSOD without them as well.

On the side note, been running my old RTX 2060 yesterday all day in Premiere Pro without issue, will probably use it when I need stability for delivering project. 

AppCrashDumps

0 Kudos
Mejnour32
Novice
1,648 Views

I also included a video showing that when Premiere Pro Timeline is playing, GPU get normal utilization but

when video is paused, many Lumetri effect will crush the GPU to the roof. (100%).  I get this observation 100% of the time.

I guess it can explain that if you add some others filters, second monitor, browser tab open, then there not much left for stability.
That can explain the "randomness" of the BSOD/PremierePro Crash...

The video file name is ACTIVE TIMELINE VS STOPPED TIMELINE VS COLOR LUMETRI

AppCrashDumps

 

Regards

Remy

0 Kudos
Mejnour32
Novice
1,632 Views

I am working with ProRes files.

I have notice they are hitting harder the GPU vs h264/h265...but I guess it's not a surprise.

0 Kudos
RandyT_Intel
Moderator
1,597 Views

Hi @Mejnour32,

 

Thank you for sharing this information. I will forward and coordinate this internally. I'll post an update here or notify you directly once there are any developments. If I need further details, I'll reach out to you here. I appreciate your patience as I work on this matter. 

 

Regards,

 

Randy T.

Intel Customer Support Technician


0 Kudos
RandyT_Intel
Moderator
1,596 Views

@Mejnour32 Follow-up question did this issue occur right out of the box when you first installed the card on the system, or did it only happen after the driver update?

0 Kudos
Reply