Problem using Handbrake and B580

[Laroldski]

When I encode video's with HandBrake when using my ASROCK B580 card and what happens is the encoding will stop for no reason and HandBrake from what I remember doesn't show any error's and it's almost like the encode was successful.

I noticed when using  the version below is where I started to having problems.

32.0.101.8135

32.0.101.8136

32.0.101.8247

I reverted back to 32.0.101.7028 because I wasn't 100% certain when the problem started happening as I update every time a new ARC Driver comes out.

I'm going to install 32.0.101.8147 again and see exactly what happens with HandBrake,when the problem happened it happened around 1 out of every 4 to 8 encodes would be my best guess.

Once I start having the problem again I will update this thread,just to be clear I have yet to have an encode fail while using driver version 32.0.101.7028

If any Mod's that read this thread can you please let me know if this is a known problems with the newer ARC drivers.

[Laroldski]

Aren't any Mod's going to respond to my problem.

[KennethB_Intel]

Hello Laroldski,

Thank you for reaching out to Intel Community Forum. I understand you are experiencing issues when using Handbrake with your Intel® Arc™ B580 graphics. To better assist you, I would like to gather more information regarding your setup and the issue:

1. Could you describe the issue in more detail? For example, are you encountering crashes, performance issues, or visual glitches?
2. Does the issue occur only with Handbrake, or are other applications affected as well?
3. When did the issue start?
4. Were there any recent changes or updates made to your system before the issue began?
5. Is the issue consistent or does it occur randomly?
6. Could you share the steps to reproduce the issue?
7. If possible, please provide a screenshot or video showing the problem.
8. Could you please provide us the SSU logs of your system? You can find instructions on How to get the Intel® System Support Utility Logs on Windows*

Once I have this information, I will be able to provide more accurate assistance.

Thank you, and I look forward to your response.

Best regards,

Kenneth B.

Intel Customer Support Technician

[Laroldski1]

1. I'm not getting any visual or crashing problems at all and no crash's or performance issues when I run HandBrake for gaming I don't know because I don't game.

2. I only get the problem when running HandBrake.

3. I'm not 100% sure as I thought it was a problem with other thing's and then I reverted back to ARC Driver version 

4. No changes to to my system were made and it was happening before the last big update from Microsoft.

5. The problem is random and I forget when it start happening but when I went and reverted back to ARC Driver 32.0.101.7028 the problem went away 100%

6. I don't know how to reproduce the issue because sometimes HandBrake will just finish encoding a video as if everything went fine and then when you try to play the video it won't play because it's not all the there of if the video was supposed to be 44 minutes long and the video that got botched maybe only 25 or 40 minutes long and not the full the length of the original video.

I'm trying right now with the latest driver to reproduce what used to happen to me so I can give better informatiom,I don't think HandBrake showed any error's either as when HandBrake in the past ever had a problem encoding a video and terminated the encoding process you'd get and error of some sort that you could clearly see and I don't think I got any error's when a video was botched recently.

7. If I'm correct a screenshot won't help unless HandBrake gives error message's and I don't think I ever got one when it happened.

8. Should I wait to do the SSU Log's until I have the problem happen again just incase.

[Laroldski1]

@KennethB_Intel

I also noticed with Intel ARC Driver version 32.0.101.8147 WHQL Certified there a Certified version and one that wasn't,can you tell me if both version are exactly the same with no changes and if Intel just posted that driver again and called it Certified after it got Certified.

[Laroldski1]

I just got my first botched encode with HandBrake using ARC Driver 32.0.101.8147 WHQL Certified

If you look at the picture I encoded The Forsytes S1E2 The Forsytes S1E3 and The Forsytes S1E4 in a row and for whatever the reason The Forsytes S1E2 failed but The Forsytes S1E3 and The Forsytes S1E4 encoded just fine.

I was able to go back with the same setting's and encode The Forsytes S1E2 the second time with no problems what so ever.

I'm uploading 2 pictures and the SSU Log as well.

[Laroldski1]

@KennethB_Intel Were you able to review my ss log and look at those pictures yet.

[KennethB_Intel]

Hello Laroldski, 

I noticed that your recent update was posted using a different account than the one used to create the original thread. Unfortunately, I am unable to provide assistance under this account since the case is linked to your initial account.

Please accept my apologies for the inconvenience. To continue receiving support, kindly keep using your original account to post any updates or create a new thread if needed. This will help us maintain consistency and avoid confusion during the troubleshooting process.

For now, please allow me to check this internally and get back to you once I have more information.

Best regards,

Kenneth B.

Intel Customer Support Technician

[Laroldski]

@KennethB_Intel Sorry about the mix up using the second account I did that by mistake,I had an account at this forum before lost the login info some how and then after creating a second account now for some reason google found both of the accounts info and I forgot which email I used as my second account.

I'm uploading the pictures and SSU log again for you.

[Laroldski]

@KennethB_Intel Is it possible to delete or can you delete my Laroldski1 account as I don't want it anymore and I forget which account to sign in with and I don't want anymore mix up's.

[KennethB_Intel]

Hello Laroldski, 

Thank you for your continued cooperation. Please try performing a clean driver removal using Display Driver Uninstaller (DDU). This will help us confirm if the issue is related to the graphics driver.

If the issue persists after using DDU, kindly remove the B580 graphics card and use the integrated graphics only. This step will help us determine whether the problem is caused by the graphics card or if it is isolated to the system.

Please let me know the results of these steps so I can assist you further.

Best regards,

Kenneth B.

Intel Customer Support Technician

[Laroldski]

I tried doing all of the stuff you said a while back when I was trying to figure out the problem I was having.

I tried DDU and also the cpu's graphic's which I have a 9950X.

The only thing I know for sure is this problem started not that long ago maybe 2 to 4 ARC Driver release's ago but I can't say for certain,I do know that running the current ARC Driver which is 32.0.101.8247 and anywhere from 1 out of 5 to 15 encodes get's botched it could even be 1 out 20,but I do know that it has happened very often and is more like around 1 out of 5 to 8 or 9 gets botched.

I was running ARC Driver 32.0.101.8136 and I still had the problem and I switched back to ARC Driver 32.0.101.7028 for 1 month or more and never had the problem at all and I do about 5 to 15 encodes a day,but then when I thought I will try ARC Driver 32.0.101.8247 hoping the problem was fixed and it wasn't I switched back to ARC Driver 32.0.101.7028 I have not had a problem for 2 weeks and no botched encodes.

The only thing I know for sure it's a problem with the newer ARC Drivers because the older drivers never botch an encodes at all.

[Laroldski]

@KennethB_Intel  Did you see my last response and me telling you that I already tried the stuff you suggested.

I already knew about DDU from another ARC driver problem that I was having and that problem had to do with the Intel® Computing Improvement Program causing BSOD's with my PC all the time and that problem has been long solve with a Mod at the Intel forum by not installing Intel® Computing Improvement Program.

When I started having the new problem with encodes getting botched in HandBrake I tried DDU just incase and using my cpu's built in graphic and also a GTX960 card and I didn't get any botched encodes only when using the newer drivers.

Also to be clear as I stated before I don't know exactly which driver version I started getting the problem with botched encodes when running HandBrake but for sure with 32.0.101.8247 I got the problem and I think with 32.0.101.8136 I got the problem as well and I'm not certain with 32.0.101.8135 if I got the problem of botched encodes.

The only thing I know for certain that if I go back to ARC Driver 32.0.101.7028 I do not get the problem ever not once in a month span of time.

I'm going to try ARC Driver 32.0.101.8250 which just came out 1 or 2 days ago and If I get another botched encode with HandBrake I will save the HandBrake File Log and attach it to this thread.

[KennethB_Intel]

Hello Laroldski,

To help further investigate the issue and provide accurate assistance, could you please share the following details:

1. What is the exact version of HandBrake you are using?
2. Does the issue occur with all video files or only specific formats/codecs?
3. What are the exact steps you take before the problem occurs? (Please provide a short workflow.)
4. Do you have any logs from when the issue happens?
5. Is the problem reproducible every time, or does it occur randomly?
6. Could you please provide us a video of the issue?

Please share these details so we can check this further.

Thank you.

Best regards,

Kenneth B.

Intel Customer Support Technician

[Laroldski]

I'm running version 1.10.2 of HandBrake.

This problem occurs with all video file H.264 and H.265,I often encode a lot of MP4 video files.

There are no exact steps I take before the problem happens,I just open HandBrake and I have a custom Preset that is set  to default and these are the following settings for my Custom Preset below.

Video Encoder H.264 (Intel QSV) +7 Audio Gain and the resolution is set to 720x400 and that's it.

I'm running the latest ARC driver right now to see if I can get a botched video encode,the driver I'm running is 32.0.101.8250 and I have done 35 encodes with 32.0.101.8250 and not one problem,I'm going to switch back to 32.0.101.8247 and see I can get an encode to fail and when I do I will upload the log from HandBrake,I know with 32.0.101.8247 it normally would have failed 3 to 6 times with 35 encodes.

I stated before that the problem just happens randomly and why it happens or what's causing it I have no clue what so ever.

[Laroldski]

The problem with providing a video of the problem happening I never know it's going to happen it just does and nothing strange happens in HandBrake that would help.

If I have let's say 3 or 6 video's in the Queue with HandBrake if it is going to botch a video it just that that encode has failed and moves onto the next encode and thats it.

If an encode fails it's exactly the same as if the encode didn't fail,if I have multiple video's in the Queue it's the same as if it was a successful encode and it just moves to the next video but if I check the Queue after I can see if the video has failed.