Shader cache files showing device id and extension saying 0_APPNAME=

[Xillvion]

This appeared in driver versions 32.0.101.6297 and 32.0.101.6299:

Is this a bug? Though it will be very nice for it to show the name of the application that's using the amount of shader cache.
Also some shader cache files is outside of the Intel folder, where the LocalLow folder is, not sure if it's intentional or not.

I'm on a Acer Aspire A515-56 laptop, i5-1135G7 with Intel Iris Xe Graphics.

[Earl_Intel]

Hi Xillvion,

Thank you for posting in the communities!

Checking on your inquiry, I have few questions for me to better understand the issue.

• May I know if the graphics drivers that you installed on your system, is it on the Acer website or on our Intel website?
  • Product Support - Aspire A515-56 | Acer United States
  • Intel® Arc™ & Iris® Xe Graphics - Windows*
• How many Drives you have on your system? Which Drive do you install the graphics driver?
• Can you provide us with the screenshot where the graphics folder located? also, a screenshot where the Locallow folder located?
• What is the path of the graphics driver folder?

Best regards,

Earl E.

Intel Customer Support Technician.

[Xillvion]

1. The Intel one
2. Just only one NVME drive
3. Not sure what you mean by the graphics driver folder, same place as all other drivers? But here's the two screenshots:
    

The empty space after the Users folder is the account name folder. As you can see in the first screenshot, some of the shader cache files are outside of where the Intel folder is. I'm on a older driver due to an issue with a game I already reported, but the DeviceId shader cache files appears on those two graphics driver versions I pointed out.

[Earl_Intel]

Hi Xillvion,

Thank you for sharing this information, I will further check on this and will provide you an update as soon as possible.

Best regards,

Earl E.

Intel Customer Support Technician.

[Earl_Intel]

Hi Xillvion,

Thank you for patiently waiting.

The shader cache folder is a directory where temporary files generated by your graphics card are stored. These files include precompiled shaders, which help improve performance by reducing the need to recompile shaders every time a game or application is run. 

The LocalLow folder is a subdirectory within the AppData folder on Windows systems. It is used to store data for applications that run with lower security settings, often referred to as "low integrity" applications. This folder is typically used by web browsers running in protected mode and other applications that require restricted access.

We replicated the issue using our Intel NUC LAPBC510 system with an i5-1135G7 processor. We checked the folders and found that it is normal for the files to be stored in those locations, even on systems without an Intel graphics card. Therefore, this behavior is expected as explained above. 

Let me know if you have other concerns.

Best regards,

Earl E.

Intel Customer Support Technician.

[Xillvion]

Okay, what about those shader cache files in the first screenshot that's incorrectly saying it's a D3D12 aka DirectX 12 file?

[Earl_Intel]

Hi Xillvion,

Thank you for your response, upon further checking.

"DirectX 12 (DX12) is the API that includes Direct3D 12, Direct3D 12 provides an API and platform that allows apps to take advantage of the graphics and computing capabilities of PCs equipped with one or more Direct3D 12-compatible GPUs."

Here us the source link: Direct3D 12 programming guide - Win32 apps | Microsoft Learn

Let me know if you have other concerns.

Best regards.

Earl E.

Intel Customer Support Technician

[Xillvion]

I know about that, i'm actually talking about the fact that the shader cache for Fortnite says it's a D3D12 file but I'm using DirectX 11 since the latter requires the ultimate version of DirectX 12. And Arc Control as well, unless it uses some Direct3D stuff.

Even so, it's only some of the shader cache files that showing the DeviceId and 0_APPNAME= and not the rest like the one in the 3rd screenshot. I do have a concern about stability, performance and potential security risks for those files.