locked
Sometimes XAML init crashes in D3D11 module

    Question

  • Not very often, just want to know is it a bug of the graphic driver or ...

    Some dump info, thanks.

    -----------------------------------

    FAULTING_IP:
    atiuxpag!OpenAdapter10_2+7707
    5a33ba57 8a01            mov     al,byte ptr [ecx]

    EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 5a33ba57 (atiuxpag!OpenAdapter10_2+0x00007707)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 00000000
       Parameter[1]: 03ddd068
    Attempt to read from address 03ddd068

    PROCESS_NAME:  d3dtest.exe

    ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx

    EXCEPTION_PARAMETER1:  00000000

    EXCEPTION_PARAMETER2:  03ddd068

    READ_ADDRESS:  03ddd068

    FOLLOWUP_IP:
    atiuxpag!OpenAdapter10_2+7707
    5a33ba57 8a01            mov     al,byte ptr [ecx]

    NTGLOBALFLAG:  2

    APPLICATION_VERIFIER_FLAGS:  0

    APP:  customtimetile.exe

    FAULTING_THREAD:  00001d90

    BUGCHECK_STR:  APPLICATION_FAULT_INVALID_POINTER_READ_STACK_POINTER_MISMATCH

    PRIMARY_PROBLEM_CLASS:  INVALID_POINTER_READ_STACK_POINTER_MISMATCH

    DEFAULT_BUCKET_ID:  INVALID_POINTER_READ_STACK_POINTER_MISMATCH

    LAST_CONTROL_TRANSFER:  from 5a338feb to 5a33ba57

    STACK_TEXT: 
    WARNING: Stack unwind information not available. Following frames may be wrong.
    03b3e1e8 5a338feb 03b3efec 00000100 03ddd068 atiuxpag!OpenAdapter10_2+0x7707
    03b3e214 5a338f6b 040705a8 63c79a90 03b3efec atiuxpag!OpenAdapter10_2+0x4c9b
    03b3e23c 5a334279 63c79a90 040705a8 03ddc3d6 atiuxpag!OpenAdapter10_2+0x4c1b
    03b3e268 63c7948a 03b3eb58 03b3f1c8 040705a8 atiuxpag!XopQueryAdapters10+0x45
    03b3e27c 63c796d8 03b3e2a4 03b3e3b0 03b3e2e0 aticfx32!OpenAdapter10_2+0x83aa
    03b3f18c 63c793ef 00000001 0395c0c4 03b3f1ac aticfx32!OpenAdapter10_2+0x85f8
    03b3f19c 63c710ed 03b3f1c8 00000001 03b3f200 aticfx32!OpenAdapter10_2+0x830f
    03b3f1ac 5a376418 03b3f1c8 8e20163d 03b3f454 aticfx32!OpenAdapter10_2+0xd
    03b3f200 5a374e25 03d92b28 63c70000 5a376458 d3d11!NDXGI::CUMDAdapter::CUMDAdapter+0x137
    03b3f26c 5a374044 00000002 8e201681 887a0004 d3d11!CCreateDeviceCache::CUMDAdapterCache::Load+0x75
    03b3f2bc 5a372c0e 03b3f41c 03b3f36c 0000b100 d3d11!CCreateDeviceCache::CAdapterCache::ResolveUMDAndVersion+0x9c
    03b3f6d8 5a36de96 00000000 0395c0a8 00000000 d3d11!D3D11CoreCreateDevice+0x2eb
    03b3f960 5a36d8cc 0395c0a8 00000000 00000000 d3d11!D3D11CreateDeviceAndSwapChain+0x1ff
    03b3f998 555d4469 0395c0a8 00000000 00000000 d3d11!D3D11CreateDevice+0x2c
    03b3f9dc 555c9455 004bc7a8 00473a90 00000000 Windows_UI_Xaml!CD3D11Device::EnsureResources+0xc4
    03b3f9f4 555c9384 00471db0 004bc7a8 00000001 Windows_UI_Xaml!CHardwareCompositor::EnsureDeviceResources+0x33
    03b3fa14 55702e3b 004d1590 00481750 004bca00 Windows_UI_Xaml!HardwareCompositionCommand::CRetargetCommand::Execute+0x4f
    03b3fa48 554ab9ee fffffff8 004d1590 00000000 Windows_UI_Xaml!CHardwareCompositor::ExecutePreDrawCommands+0xea
    03b3fac4 55447dee 00481750 00000000 03b3fae0 Windows_UI_Xaml!CompositorScheduler::RenderThreadFrame+0x45c
    03b3fad4 555fc289 00000000 03b3faec 754f8543 Windows_UI_Xaml!CompositorScheduler::RenderThreadMain+0x6d
    03b3fae0 754f8543 00481750 03b3fb30 77dcac69 Windows_UI_Xaml!CompositorScheduler::RenderThreadMainStatic+0xe
    03b3faec 77dcac69 00481750 a38206e7 00000000 kernel32!BaseThreadInitThunk+0xe
    03b3fb30 77dcac3c 555fc27b 00481750 ffffffff ntdll!__RtlUserThreadStart+0x72
    03b3fb48 00000000 555fc27b 00481750 00000000 ntdll!_RtlUserThreadStart+0x1b


    STACK_COMMAND:  ~6s; .ecxr ; kb

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  atiuxpag!OpenAdapter10_2+7707

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: atiuxpag

    IMAGE_NAME:  atiuxpag.dll

    DEBUG_FLR_IMAGE_TIMESTAMP:  50d215fc

    FAILURE_BUCKET_ID:  INVALID_POINTER_READ_STACK_POINTER_MISMATCH_c0000005_atiuxpag.dll!OpenAdapter10_2

    BUCKET_ID:  APPLICATION_FAULT_INVALID_POINTER_READ_STACK_POINTER_MISMATCH_atiuxpag!OpenAdapter10_2+7707

    • Edited by Raptor K Wednesday, March 13, 2013 2:51 AM
    Tuesday, March 12, 2013 2:50 PM

All replies

  • This doesn't appear to be a known bad stack. There isn't enough information here to tell for sure if it's a driver bug or not, but it seems likely. Can you tell from the DLL versions in the dump file if this is the latest version of the ATI driver?

    --Rob

    Wednesday, March 13, 2013 2:04 AM
    Owner
  • System has 2 graphic cards:

    Indepedent "AMD HD7970", and CPU(2600k) integrated "Intel(R) HD Graphics 3000, Revision 9".

    Even I use the intel card (plug LCD to intel card), the AMD module still loaded and may crash.

    Drivers are all official newest versions:

    atiuxpag.dll atiuxpag.dll Advanced Micro Devices, Inc.  E:\Windows\SysWOW64\atiuxpag.dll 
    8.14.1.6290

    aticfx32.dll aticfx32.dll Advanced Micro Devices, Inc.  E:\Windows\SysWOW64\aticfx32.dll 
    8.17.10.1172

    igd10umd32.dll LDDM User Mode Driver for Intel(R) Graphics Technology Intel Corporation E:\Windows\SysWOW64\igd10umd32.dll 
    9.17.10.2932

    • Edited by Raptor K Wednesday, March 13, 2013 2:32 AM
    Wednesday, March 13, 2013 2:27 AM