8 Replies Latest reply on May 11, 2017 6:07 PM by Intel Corporation

Graphic driver crash creating a D3D11_SM4 pixel shader with recent hlsl compiler

JSeb May 4, 2017 10:35 AM

Hello,

I've recently updated our hlsl compiler with Windows kit 8.1's fxc.exe.
But some (very simple) pixel shader make igd10umd32.dll crash after a call to CreatePixelShader() with new byte code.the

Here is the byte code of the shader (given to CreatePixelShader)

char ByteCodes[] = {

0x44, 0x58, 0x42, 0x43, 0xDF, 0x86, 0xAB, 0x1E, 0x92, 0x1F, 0x5F, 0x21, 0x96, 0x0B, 0x38, 0xD0, 0x9C, 0xEE, 0xB6, 0x64, 0x01, 0x00, 0x00, 0x00, 0xFC, 0x02, 0x00, 0x00, 0x05, 0x00, 0x00, 0x00,

0x34, 0x00, 0x00, 0x00, 0xB4, 0x00, 0x00, 0x00, 0xE8, 0x00, 0x00, 0x00, 0x1C, 0x01, 0x00, 0x00, 0x80, 0x02, 0x00, 0x00, 0x52, 0x44, 0x45, 0x46, 0x78, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x1C, 0x00, 0x00, 0x00, 0x00, 0x04, 0xFF, 0xFF, 0x00, 0x01, 0x00, 0x00, 0x46, 0x00, 0x00, 0x00, 0x3C, 0x00, 0x00, 0x00, 0x02, 0x00, 0x00, 0x00,

0x05, 0x00, 0x00, 0x00, 0x04, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x54, 0x4D, 0x61, 0x70, 0x49, 0x6E, 0x70, 0x75,

0x74, 0x00, 0x4D, 0x69, 0x63, 0x72, 0x6F, 0x73, 0x6F, 0x66, 0x74, 0x20, 0x28, 0x52, 0x29, 0x20, 0x48, 0x4C, 0x53, 0x4C, 0x20, 0x53, 0x68, 0x61, 0x64, 0x65, 0x72, 0x20, 0x43, 0x6F, 0x6D, 0x70,

0x69, 0x6C, 0x65, 0x72, 0x20, 0x36, 0x2E, 0x33, 0x2E, 0x39, 0x36, 0x30, 0x30, 0x2E, 0x31, 0x36, 0x33, 0x38, 0x34, 0x00, 0x49, 0x53, 0x47, 0x4E, 0x2C, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00,

0x08, 0x00, 0x00, 0x00, 0x20, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x03, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0F, 0x03, 0x00, 0x00, 0x53, 0x56, 0x5F, 0x50,

0x6F, 0x73, 0x69, 0x74, 0x69, 0x6F, 0x6E, 0x00, 0x4F, 0x53, 0x47, 0x4E, 0x2C, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x08, 0x00, 0x00, 0x00, 0x20, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

0x00, 0x00, 0x00, 0x00, 0x03, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0x01, 0x0E, 0x00, 0x00, 0x53, 0x56, 0x5F, 0x44, 0x65, 0x70, 0x74, 0x68, 0x00, 0xAB, 0xAB, 0xAB, 0x53, 0x48, 0x44, 0x52,

0x5C, 0x01, 0x00, 0x00, 0x40, 0x00, 0x00, 0x00, 0x57, 0x00, 0x00, 0x00, 0x58, 0x18, 0x00, 0x04, 0x00, 0x70, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x55, 0x55, 0x00, 0x00, 0x64, 0x20, 0x00, 0x04,

0x32, 0x10, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x65, 0x00, 0x00, 0x02, 0x01, 0xC0, 0x00, 0x00, 0x68, 0x00, 0x00, 0x02, 0x03, 0x00, 0x00, 0x00, 0x1C, 0x00, 0x00, 0x05,

0x32, 0x00, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x46, 0x10, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x29, 0x00, 0x00, 0x07, 0x32, 0x00, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x46, 0x00, 0x10, 0x00,

0x00, 0x00, 0x00, 0x00, 0x01, 0x40, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x36, 0x00, 0x00, 0x08, 0xC2, 0x00, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02, 0x40, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x2D, 0x00, 0x00, 0x08, 0xF2, 0x00, 0x10, 0x00, 0x01, 0x00, 0x00, 0x00, 0x46, 0x0F, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00,

0x46, 0x7E, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x2D, 0x00, 0x00, 0x88, 0x01, 0x02, 0x00, 0x00, 0xF2, 0x00, 0x10, 0x00, 0x02, 0x00, 0x00, 0x00, 0x46, 0x0F, 0x10, 0x00,

0x00, 0x00, 0x00, 0x00, 0x46, 0x7E, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x33, 0x00, 0x00, 0x07, 0x12, 0x00, 0x10, 0x00, 0x01, 0x00, 0x00, 0x00, 0x0A, 0x00, 0x10, 0x00, 0x01, 0x00, 0x00, 0x00,

0x0A, 0x00, 0x10, 0x00, 0x02, 0x00, 0x00, 0x00, 0x2D, 0x00, 0x00, 0x88, 0x01, 0x20, 0x00, 0x00, 0xF2, 0x00, 0x10, 0x00, 0x02, 0x00, 0x00, 0x00, 0x46, 0x0F, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00,

0x46, 0x7E, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x2D, 0x00, 0x00, 0x88, 0x01, 0x22, 0x00, 0x00, 0xF2, 0x00, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x46, 0x0E, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00,

0x46, 0x7E, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x33, 0x00, 0x00, 0x07, 0x12, 0x00, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0A, 0x00, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0A, 0x00, 0x10, 0x00,

0x02, 0x00, 0x00, 0x00, 0x33, 0x00, 0x00, 0x06, 0x01, 0xC0, 0x00, 0x00, 0x0A, 0x00, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0A, 0x00, 0x10, 0x00, 0x01, 0x00, 0x00, 0x00, 0x3E, 0x00, 0x00, 0x01,

0x53, 0x54, 0x41, 0x54, 0x74, 0x00, 0x00, 0x00, 0x0B, 0x00, 0x00, 0x00, 0x03, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02, 0x00, 0x00, 0x00, 0x03, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00,

0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

0x00, 0x00, 0x00, 0x00, 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00,

0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

};

I've joined the minidump debugger says:
"Unhandled exception at 0x66C03309 (igd10umd32.dll) in GbxGame.exe.1700.dmp: RangeChecks instrumentation code detected an out of range array access."

Here are the system spec.:
Intel HD Graphics 3000

Video BIOS: 2119.0
Driver Version: 9.17.10.4459

OS: Windows 10 Pro (10.0.14393)

Could you tell me what is going on please ?
(going back to previous hlsl compiler version is not trivial for us)

Thanks

GbxGame.exe.1700.dmp.zip 524.0 K

1. Re: Graphic driver crash creating a D3D11_SM4 pixel shader with recent hlsl compiler

Al Hill May 4, 2017 10:42 AM (in response to JSeb)

Intel HD 3000 Graphics are not supported on Windows 10:
Supported Operating Systems for Intel® Graphics Products

The best you can do on Windows 10 is to get the driver from here: Microsoft Update Catalog

Doc

1 of 1 people found this helpful
Like Show 0 Likes(0)

Actions
2. Re: Graphic driver crash creating a D3D11_SM4 pixel shader with recent hlsl compiler

JSeb May 4, 2017 10:56 AM (in response to Al Hill)

Thanks for fast feedback, you're right but,

I've a player with a
[Sys] Gpu Adapter 0: (0x8086,0x0166) "Intel(R) HD Graphics 4000", 2 Outputs, 32MB dedicated video, 0MB dedicated system, 1 760MB shared system
[Sys] Os = Windows 8.1(9600.winblue_ltsb.170204-0600) 64bhis

I don't know his driver version but I can ask him.
But to get back to my question, I'm almost sure his crash is the same than this one.

And about windows 10 + 3000, I've the latest from the link you gave.

Thanks
Like Show 0 Likes(0)

Actions
3. Re: Graphic driver crash creating a D3D11_SM4 pixel shader with recent hlsl compiler

JSeb May 4, 2017 11:29 AM (in response to Al Hill)

I've a solution:

On all Intel graphics, I'll skip the 2 shaders which makes that driver crash.
(they're not mandatory: zbuffer downsize)

I could do better by checking also the driver version.
Before with D3D9 it was easy (it was part of adaptater description).
But now with D3D11 I don't know how to get that driver version.

Do you know a robust way of getting that ?
Thanks
Like Show 0 Likes(0)

Actions
4. Re: Graphic driver crash creating a D3D11_SM4 pixel shader with recent hlsl compiler

May 4, 2017 2:05 PM (in response to JSeb)

This message was posted on behalf of Intel Corporation

Thank you very much to Al Hill for providing the information above.

Hi, JSeb, Thank you very much for joining the Intel® Graphics communities.

As it was mentioned before, the Intel® HD Graphics 3000 graphics controller is not supported on Windows® 10, based on that some errors are expected.

Now, if you need to get more details about this matter, in that case you can always visit our developer zone to get further peer assistance:
https://software.intel.com/en-us/forum

Any further questions, please let me know.

Regards,
Alberto
Like Show 0 Likes(0)

Actions
5. Re: Graphic driver crash creating a D3D11_SM4 pixel shader with recent hlsl compiler

JSeb May 5, 2017 2:44 AM (in response to Intel Corporation)

Hello Alberto and Al Hill again,

Hum few points, just to be clear:

a) I understand my test configuration is not "ideal": I'm using an HD 3000 on windows 10 which is not officially supported.
I fully understand that point.

b) But one of our players as an issue (driver crash on same shader code) very close to the one I reproduce on my (a) test configuration.
And this player is using an HD 4000 on Windows 8, I don't have it's driver version yet, but I assume he've the latest.

c) I found a solution in our case to avoid these driver crash.
So this issue is no longer "so important to me".

d) I'm quite surprised you keep talking me about point (a) rather than asking yourself if that issue could also concern "officially supported systems".

Best regards
Like Show 0 Likes(0)

Actions
6. Re: Graphic driver crash creating a D3D11_SM4 pixel shader with recent hlsl compiler

Stefan3D May 5, 2017 11:54 AM (in response to JSeb)

JSeb schrieb:

I've a solution:

On all Intel graphics, I'll skip the 2 shaders which makes that driver crash.
(they're not mandatory: zbuffer downsize)

I could do better by checking also the driver version.
Before with D3D9 it was easy (it was part of adaptater description).
But now with D3D11 I don't know how to get that driver version.

Do you know a robust way of getting that ?
Thanks
You might get further support in the developer forum: Developing Games & Graphics on Intel
Probably you should post your shader as source code there, byte code is impossible to read (at least for me).

1 of 1 people found this helpful
Like Show 0 Likes(0)

Actions
7. Re: Graphic driver crash creating a D3D11_SM4 pixel shader with recent hlsl compiler

May 5, 2017 12:00 PM (in response to Stefan3D)

This message was posted on behalf of Intel Corporation

Stefan3D, Thank you very much for your suggestion.

Regards,
Alberto
Like Show 0 Likes(0)

Actions
8. Re: Graphic driver crash creating a D3D11_SM4 pixel shader with recent hlsl compiler

May 11, 2017 6:07 PM (in response to JSeb)

This message was posted on behalf of Intel Corporation

Hi, JSeb, I hope the information posted previously was useful for you and that you were able to get further assistance on the Intel® developer zone.

Let me apologize for any inconvenience.

Any questions, please let me know.

Regards,
Alberto
Like Show 0 Likes(0)

Actions

Go to original post