As stated in the title, while attempting to create a D3D11 device the above exception is being raised by the UM-side WDDM driver (igd10iumdxx.dll), specifically:
0xE06D7363: Microsoft C++ Exception (parameters: 0x19930520, 0x0019A034, 0x5C2EE5A4).
Stack trace:
> KERNELBASE.dll!_RaiseException@16 () Unknown
igd10iumd32.dll!5b4d4913() Unknown
igd10iumd32.dll![Frames below may be incorrect and/or missing, no symbols loaded for igd10iumd32.dll] Unknown
igd10iumd32.dll!5b50a623() Unknown
igd10iumd32.dll!5b5097a4() Unknown
igd10iumd32.dll!5b5085f1() Unknown
igd10iumd32.dll!5b506288() Unknown
igd10iumd32.dll!5b5053ef() Unknown
igd10iumd32.dll!5b50022c() Unknown
igd10iumd32.dll!5ad37ee5() Unknown
igd10iumd32.dll!5b3d39e9() Unknown
igd10iumd32.dll!5b3d33fe() Unknown
d3d11.dll!NDXGI::CDevice::CreateDriverInstance() Unknown
d3d11.dll!CDevice::CreateDriverInstance(class CContext *,void *,void *,void *,void *,unsigned int,long (**)(struct D3D10DDI_HDEVICE,unsigned int,unsigned long,void *,unsigned long,void *)) Unknown
d3d11.dll!CContext::LUCCompleteLayerConstruction() Unknown
d3d11.dll!CBridgeImpl<struct ILayeredUseCounted,struct ID3D11LayeredUseCounted,class CLayeredObject<class CContext> >::LUCCompleteLayerConstruction(void) Unknown
d3d11.dll!NOutermost::CDeviceChild::LUCCompleteLayerConstruction() Unknown
d3d11.dll!NOutermost::CDevice::CreateLayeredChild() Unknown
d3d11.dll!CDevice::LLOCompleteLayerConstruction(void) Unknown
d3d11.dll!CBridgeImpl<struct ILayeredLockOwner,struct ID3D11LayeredDevice,class CLayeredObject<class CDevice> >::LLOCompleteLayerConstruction(void) Unknown
d3d11.dll!NDXGI::CDevice::LLOCompleteLayerConstruction(void) Unknown
d3d11.dll!CBridgeImpl<struct ILayeredLockOwner,struct ID3D11LayeredDevice,class CLayeredObject<class NDXGI::CDevice> >::LLOCompleteLayerConstruction(void) Unknown
d3d11.dll!NOutermost::CDevice::LLOCompleteLayerConstruction() Unknown
d3d11.dll!NOutermost::CDevice::FinalConstruct() Unknown
d3d11.dll!TComObject<class NOutermost::CDevice>::TComObject<class NOutermost::CDevice>(void *,struct NOutermost::CDevice::TConstructorArgs const &,struct _GUID const &,void * *) Unknown
d3d11.dll!D3D11CreateLayeredDevice() Unknown
d3d11.dll!D3D11CoreCreateLayeredDevice() Unknown
d3d11.dll!D3D11RegisterLayersAndCreateDevice(struct D3D11_EXTENSIONS const &,class NDXGI::CUMDAdapter *,enum D3D_FEATURE_LEVEL,enum D3D_FEATURE_LEVEL,unsigned __int64,unsigned int,struct ID3D11Device * *) Unknown
d3d11.dll!_D3D11CoreCreateDevice@40 () Unknown
d3d11.dll!D3D11CreateDeviceAndSwapChainImpl(struct IDXGIAdapter *,enum D3D_DRIVER_TYPE,struct HINSTANCE__ *,unsigned int,enum D3D_FEATURE_LEVEL const *,unsigned int,unsigned int,struct DXGI_SWAP_CHAIN_DESC const *,struct IDXGISwapChain * *,struct ID3D11Device * *,enum D3D_FEATURE_LEVEL *,struct ID3D11DeviceContext * *) Unknown
d3d11.dll!D3D11CreateDeviceImpl() Unknown
This issue began occurring after updating to Intel driver version 30.0.101.1340 (for UHD 630). Rolling back the driver solves the issue.
Thanks, and I apologize if this isn't the correct forum; I couldn't find one more appropriate.
链接已复制
Hello Emjayen,
Thank you for posting on the Intel®️ communities. In order to have a better understanding of the issue, please share with us the following information:
- Is this a desktop or a laptop?
- Have you tried using the drivers provided by the OEM?
- When doing the rollback, which driver gets installed?
Also, please download and install the Intel®️ System Support Utility (Intel®️ SSU):
https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows-
Open the application and select "Everything" click on "Scan" to see the system and device information. By default, Intel®️ SSU will take you to the "Summary View". Click on the menu where it says "Summary" to change to "Detailed View".
Click on "Next", save the report and attach it to your response.
Regards,
Josue O.
Intel Customer Support Technician
Hi Josue,
1) Desktop
2) Yes.
3) 30.0.100.9805 (see below however)
After some testing the issue appears to be related to the image name, which I suspect is due to this being used as a key to apply driver-level hacks/fixes for particular applications. I can reliably mitigate this problem by merely changing the name of the image to anything else, and reliably reproduce it by using the original image name (in this case: "Age.exe").
I've excluded this being related to Windows ACL shims ("compatibility layers").
-Matt
Hello Emjayen,
We have not heard back from you, so we will close this thread. If you need any additional information, please submit a new question as this thread will no longer be monitored.
Regards,
Josue O.
Intel Customer Support Technician
