B580 BSOD during Davinci Resolve export using Quick Sync encoder

frankenfurter · ‎02-24-2026

Hello,

Updating my driver to 32.0.101.8509 after uninstalling previous drivers with DDU, and exporting a video clip SPECIFICALLY using intel's quick sync encoder results in a BSOD on windows 10.

I have rolled back to driver 32.0.101.8331 where the issue no longer occurs.

Interestingly, it tends to happen the SECOND time I try to export a video through these means.

I have not tested with long videos; this happened exporting a 20-second clip from a longer clip - no complicated timelines.

My best instructions to reproduce: Open a davinci resolve project; go to the export page; choose auto or intel quick sync under Video > export video > encoder; Add to render queue; render your project; rename project (not overwriting, optional); render; BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL

Note: Attached crash dump occurred on driver 8509. SSU report captured after rolling back to 8331.

Please let me know if you need anything else from me.

(Crash minidumps)
022426-5312-01.dmp - Google Drive
022426-5703-01.dmp - Google Drive

VonM_Intel · ‎02-24-2026

Hi frankenfurter,
Thank you for posting in our Community. I want to make sure we get this resolved without disrupting your workflow. From your report, it looks like the issue occurs specifically on driver 32.0.101.8509 during a second export attempt in DaVinci Resolve, while rolling back to 32.0.101.8331 prevents the BSOD. This is a valuable observation that helps isolate the problem. To help me further investigate, could you clarify a few points for me:

Does the BSOD occur only with Quick Sync encoder, or have you noticed it happening with other encoders (like software or CUDA/Metal, if applicable)?
Are you running DaVinci Resolve on the latest version, or is it an older version?
Have you tried performing a clean export after a full system reboot with driver 8509, or does it happen on the second export regardless?
Have you tried a BIOS update?

In the meantime, since driver 8331 is stable for you, it’s safe to continue using it while I investigate.

Have a nice day!

Best regards,

Von M.
Intel Customer Support Technician

frankenfurter · ‎02-25-2026

Hello,

Thank you for getting back to me, and I am also glad that this topic is no longer marked as spam.

The Intel Arc B580 is the only graphics card on my machine, and as such I am unable to export using CUDA/Metal. I don't have an iGPU either. Please refer to the above attached SSU report for more specifics on my system, or let me know how to export using Nvidia's CUDA or the AMD equivalent.

Davinci Resolve also has a "native" encoder setting; I experience NO BSOD using this encoder, but it lacks some of the features that intel quick sync provides. Mostly CQP/ Constant Quality Pass, and it's also a smidge slower. This export method still utilizes the GPU, but it seems to utilize it differently per task manager (e.g. 3D vs Copy vs Video Decode).

I am not sure that I understand the reboot question; I'll go through my testing workflow and hope that it gives you the answer:
I booted into safemode and ran DDU; The PC restarted; Windows automatically installs drivers 8192*; I installed graphic drivers 8509; Restarted the computer; I opened davinci and exported the video twice; the pc crashed and automatically rebooted. I opened davinci and exported twice; the pc crashed and automatically rebooted; - In fact, each time I install a driver, it has a firmware update, so it's a full shutdown after updating rather than just a reboot.

*Not certain on 8192

I was on a relatively recent bios, but I have now updated to the latest one. Issue persists.

And since I am now at 8509 again, I will remain here until I get fed up again (it causes issues in a game). I am willing and able to do more tests if you send them way.

Thank you again, VonM

frankenfurter · ‎02-25-2026

Sorry, Forgot to add,
Davinci Resolve 20.3.2 Build 9. No updates available (latest).
Sincerely,

Frankenfurter

VonM_Intel · ‎02-25-2026

Hello frankenfurter,

Thank you for the very detailed breakdown of your testing workflow. I appreciate the structured testing you’ve already done.

At this point, I’ll need to conduct additional research on this issue, particularly around the Quick Sync export path behavior with this driver branch and firmware combination. I want to review this internally and check for any known issues, regression patterns, or encoder pipeline conflicts specific to this configuration.

I will post an update in this thread as soon as I have more information or recommended next steps.

In the meantime, please remain on driver version 32.0.101.8509 as planned, and avoid unnecessary driver switching so we keep the environment consistent for analysis.

Thank you again for your patience and for being willing to run further testing.

Best regards,

Von M.
Intel Customer Support Technician

frankenfurter · ‎02-28-2026

Hello Von M,

I'd like to update to the latest intel graphics driver. I'm being reminded that there's an update every hour. Maybe something there can save me. Maybe.

For now, I have some new findings:

The export format affects my findings; the above report (intel export crashing, native working) is not true across the board, and only seems to be true for h264. h265 rendering in the mp4 container crashes using both exporters, native and Intel (not certain when that started happening; I don't use h265 often). AV1 encoding only has the intel encoder as an option, and previously worked but crashes now, much like the other two. Only h264 gives me that "crashes on the 2nd render" scenario. Both h265 and AV1 crash on the first export across several tries.

I am editing blackmagic raw footage, which is 4096x2160. Exporting seems to fail reliably at any exported resolution (1080p, 720p, 2K DCI, 4K DCI). I have attached an example of my rendering configuration prior to a crash using the h265 encoder.

I am color grading my footage prior to export, though I doubt that will have an effect here.

Again, I'd love to get more information to you so I can update.

Sincerely,

Frankenfurter

VonM_Intel · ‎03-02-2026

Hello frankenfurter,

Thank you for your continued cooperation on this matter. To move forward, could you please install and test the latest graphics driver version 32.0.101.8531? After installing, kindly let me know if the issue persists.

Additionally, to help me investigate this more effectively, I would appreciate it if you could provide the following details:

A clear step-by-step guide on how to replicate or produce the issue.
A short clip of the issue.
If applicable, a sample project file that I can use to replicate the issue on our end.
Did the system work properly on any previous driver version? If yes, please let me know which specific driver version was functioning correctly.

These details will significantly help me narrow down the root cause.

Best regards,

Von M.
Intel Customer Support Technician

frankenfurter · ‎03-02-2026

I... I can't reproduce the crashes anymore.

I haven't upgraded my intel graphics drivers. I haven't updated Davinci resolve studio. I haven't installed any windows updates other than antivirus updates...

I have exactly one suspect, and one suspect alone. Visual Studio.

I tested and confirmed several times when I last posted on the 1st that the crashes were still occurring.

The only major change that I would have made to my testing environment is updating visual studio.

About 23 hours after that post, I launched VS and updated several components related to visual studio 2022.

I rarely use visual studio, so many of the components were likely old. The last time I updated anything was 6/12/2025 MMDDYYYY.

Launching the visual studio installer, selecting modify, it shows that I only have the workload `Desktop Development with C++` selected. See attachments.

I just don't understand... It worked fine on the older driver... How could this have fixed anything...

I'll update in the morning. It's late. I feel like I'm going completely mad.

Sorry if this is a wild goose chase. PLEASE let me know what information I can get for you.

For now, give me a few days to poke around and see if I can get it to crash again... If I can't, It may be related to the above. Maybe I'm just extremely lucky right now, and tomorrow morning we'll be back to the same old familiar BSOD...

frankenfurter · ‎03-03-2026

Ok. Yeah, something must have worked just right for a second there. We're back, baby! Back to crashing!

Driver 32.0.101.8331 worked properly for me; I did not test drivers inbetween. I had a performance issue with a driver after 8331, and rolled back to 8331 prior to testing if these other drivers worked/did not work when exporting in davinci resolve studio.

Example project file (This one is inconsistent with crashing when rendered, but did crash. The most consistent project currently is like... 60GB. I don't have the google drive space.): https://drive.google.com/file/d/1f-ftegb-yNmO0thnfxTWbz-R5ntTMWQx/view?usp=sharing

Video: https://drive.google.com/file/d/1rJM132YAFRy4DhPEgOXj3uQQYwXgbdsS/view?usp=sharing (and the minidump from the video) https://drive.google.com/file/d/1kp7s1O0C_5X2K-htohHqUlBEdOcBEmZP/view?usp=sharing

Step-By-Step: Purchase Davinci resolve studio. Edit videos. Purchase Intel Arc B580. Purchase Davinci Resolve Black Magic Pocket cinema Camera 4K. Used, from Ebay. Purchase a 64 GB lexar v60 SD Card. Realized that v60 is too slow to record on the higher settings. Change to a lower setting, still 4k. 12:1 compression. Record footage. Import footage onto computer. Since computer doesn't have SD card slot, use a laptop, and transfer media over to a NAS. Read data from NAS. Import into davinci resolve studio. Davinci resolve asks if you'd like to change the framerate. Say yes. Realize the timeline is only 1080p. Change timeline to match footage. Color grade footage. Find a cool shot that you'd like to show to friends and family. Mark in and out points to export clip. Set export settings (container > mp4, codec > mp4/mp5/av1) Export. Update intel drivers. Record some more. Import more footage. Color grade. Mark in and out points. Name video. Export. BSOD. Please let me know if you need me to go into more detail. Otherwise, the video demonstrates the steps quite well.

All that I did prior to the video was log in. I did not do anything else.

I am updating my drivers now.

frankenfurter · ‎03-03-2026

I mean, it behaves differently?

Now, on driver 8531, exports fail, I get color corruption in the viewport, it says it will take forever to export, and sometimes crashes.

Minidump: https://drive.google.com/file/d/1KNZLkt07Pg1AVRYmTCo68FDM7tZIrkA3/view?usp=sharing

Video detailing the 8531 experience: https://drive.google.com/file/d/1-OhIkyrPfiPpxkte83DJTzORO3R3LXke/view?usp=sharing

I'm going back to 8331 to render some videos as I have been requested to.

frankenfurter · ‎03-03-2026

Dearest Von M,

Sorry for the frantic responses. This situation is stressing me out, and the fact that it let me export properly for a second really threw me for a loop.

Thank you for your assistance and time regarding this matter.

Sincerely,

Frankenfurter.

VonM_Intel · ‎03-03-2026

Hello frankenfurter,

First off, no need to apologize. I completely understand how stressful this kind of intermittent crashing can be, especially when it affects your workflow. I’ve reviewed your detailed explanation, the step-by-step breakdown, and the files you attached in the community thread. Thank you for taking the time to document everything so thoroughly. Given the behavior differences between driver 32.0.101.8331 and 32.0.101.8531, the Visual Studio update observation, the export failures, color corruption, and the BSOD occurrences during DaVinci Resolve exports, this definitely warrants deeper analysis.

At this point, I will need to conduct further research and carefully review the logs, minidumps, and scenario details you’ve provided. Once I have more concrete findings or guidance, I will post a detailed response directly on the community thread. In the meantime, please feel free to continue your controlled testing, especially since you’ve identified that 8331 appears stable for rendering. That comparison is extremely valuable data. I appreciate your patience while I investigate this further.

I’ll update the thread as soon as I have more information.

Best regards,

Von M.
Intel Customer Support Technician