Stepping B0 of x6414RE Elkhart Lake supported by current GPU drivers?

[ulfhei]

I am using a x6414RE based COMExpress card that uses a stepping B0 CPU and is showing GPU stability problems, but another similar card has stepping B1, and that works fine. I am using Windows 10 Pro 22H2, fully updated.

The issue is GPU stability issues with some standard Passmark DirectX performance tests, which makes the GPU locks up in testing. It can perhaps recover once after a black screen, but a second black screen and lockup makes it fail with an error message, and Windows even locks out Passmark from using the GPU, on recent drivers.

On older drivers(9xxxx) it will blue screens with a TDR error right away, and not even try recovering.

I cannot find any information if the B0 stepping is still supported on current drivers, but there seems to be a big difference in stability, so can you please confirm if it is supported or not?

[CarlosAM_INTEL]

Hello,  @ulfhei:

Thank you for contacting Intel Embedded Community.

We received your consultations but we need to address the following questions:

Has the affected design been designed by a third-party developer or by you?

In case it is a third-party device, what is the manufacturer's name and the device's part number?

Where did you purchase the processor related to your consultations?

We are waiting for your reply.

Best regards,

@CarlosAM_INTEL.

[ulfhei]

Yes, the card is a COMExpress card developed by a third party developer, but I do not wish to name them specifically here, since it does not matter to the case at hand. 

We just need to know if the latest versions of the Intel GPU drivers, 31.0.101.2125, is compatible with x6414RE stepping B0 or not, as there are some strange indications that it is not, like this below:

"Intel Atom® x6000E series, and Intel® Pentium® and Celeron® N and J Series Processors (Code Name: Elkhart Lake) Windows* 10 x64 LTSC21H2 IPU23.4+MR7 Release Best Known Configuration 

This release supports B1 and PU Silicon (not backward compatible with A0 and B0 silicon)"

The document ID is 782334.

But there is unfortunately no information in the actual released driver files if this is the case, only on that  overview/BKC download page, which is a very odd place to put that information..??

[CarlosAM_INTEL]

Hello, @ulfhei:

Thanks for your reply.

Reviewing the information related to the driver and its version (31.0.101.2125) listed in your previous message, the part number of the processor that you are using is not listed as a valid one. You can confirm this information in the list of valid processors at the bottom of the following website:

https://www.intel.com/content/www/us/en/download/776137/intel-7th-10th-gen-processor-graphics-windows.html  

Best regards,

@CarlosAM_INTEL.

[ulfhei]

Hello Carlos, 

thank you for the link to the driver, but this is still confusing, since under Platform (OS Support) Elkhart Lake is listed:

• Intel® Atom®, Pentium® and Celeron® processor family (Codename Apollo Lake, Elkhart Lake) (1809+) 

The x6414RE CPU is, as far as can tell, a part of the Elkhart Lake family of CPUs, so according to that section, it should be generally supported, even though it is not specifically listed in the scrolling list at the bottom.

On the other hand, that list is missing a lot of other CPUs that actually are supported, if you look at the list under the Platform (OS Support) section, so that list must be considered far from complete.

Again, what I am trying to confirm is if the B0 stepping is supported or not, not whether Elkhart Lake is supported, that is clearly defined.

As mentioned, I am trying to confirm the note below on document 782334 which I cannot find any where else, see below.

But since there is multiple drivers included in this  package (11 pcs), I need to know which driver is specifically not supported, but failing that, which available version of the "Best Known Konfiguration" does actually support the B0 stepping?

Again, the trouble we are having is GPU lockups during standard DX10 Passmark benchmarks, which a J6412 with stepping B1, using the exact same driver, does not have any problems with at all. 

[CarlosAM_INTEL]

Hello, @ulfhei:

Thanks for your reply.

We received your reply, but we need to address the following question:

What is the procedure that you have followed to have access to the information stated in the picture provided in your last communication?

By the way, we need to clarify that in the case of third-party devices, Intel provides generic drivers that may not work properly with them. You need to contact the manufacturer of the devices to obtain the proper drivers or verify the compatibility of the Intel drivers.  

Best regards,

@CarlosAM_INTEL 

[ulfhei]

Hello Carlos, 

I have accessed it as a part of personally authorized extended access to the Intel homepage about the Elkhart Lake CPU family. I do know that the document itself is a document that requires this elevated and authorized login to access, so I have of course not  tried to access it in any type of illicit or unauthorized manner and certainly not shared the document itself with anyone else against any rules or regulations.

For complete information, the document is available here with a higher level login: 

https://www.intel.com/content/www/us/en/products/platforms/details/elkhart-lake/docs.html

If you feel this is not the proper forum to discuss this type of information, please advise how I can get in contact with the proper channels to further this inquiry in a more appropriate manner, so that me, and in extension, my employer can find the answers that we need in this matter.

[CarlosAM_INTEL · Accepted solution]

Hello, @ulfhei:

Thanks for your reply.

We are going to transfer this thread to the Graphics channel since they would help to give you the information that may clarify your questions.

They will contact you as soon as possible.

Best regards,

@CarlosAM_INTEL. 

[ulfhei]

Carlod,

thank you for the help so far, I have now found more correct information that the CPU actually is stepping B1,  there was an error in the BIOS recognition function and I will now close this thread and open a new one with the correct information.