Quick Links: Download Gideros Studio | Gideros Documentation | Gideros community chat | DONATE
Windows Crash (Gideros WinRT desktop app crashes) — Gideros Forum
  • Home
    • ›

    Windows Crash (Gideros WinRT desktop app crashes)

    kussakovkussakov Member
    edited November 2015 in Bugs and issues
    Guys,
    Our Giedros WinRT app "Air Ping Pong" crashes big time on many desktops.
    Does not crash on windows phone.
    We posted it on the windows app store about a week ago.
    It does not crash on our developer devices, but crashes on many other windows 10 and Windows 8 machines.
    It does not seem to even reach the lua code. The app doesn't even start(except for the splash image).
    Fails in d3d11.dll (Direct 3D dll) somehow.
    Crash logs are bellow.
    Also here are some codes, so that you can install it on your device for free:
    H3Y7G-2MPQW-HQY3H-QHW4V-9K3YZ
    YGTMF-7MP4W-QP2FV-RMMHK-DC7HZ
    TGTQ3-H9RJD-HC9TQ-MR2XW-WWYXZ
    VRDDC-PJWYT-GX2XP-7JXYG-VCW3Z
    DVWCG-4F7C4-3V7Q6-FW9GT-DXXRZ

    Could you maybe help please?

    The crash logs I see (maybe something will make sense to you). This is Windows 10 machine:
    --------------------------
    Faulting application name: giderosgame.Windows.exe, version: 0.0.0.0, time stamp: 0x55ee1c7f
    Faulting module name: d3d11.dll, version: 10.0.10240.16384, time stamp: 0x559f3c11
    Exception code: 0xc0000005
    Fault offset: 0x00135d0e
    Faulting process id: 0x10f8
    Faulting application start time: 0x01d120ae8662045a
    Faulting application path: C:\Program Files\WindowsApps\IJSSolutions.AirPingPong_1.1.0.3_x86__d1z84xy8fkmzw\giderosgame.Windows.exe
    Faulting module path: C:\WINDOWS\SYSTEM32\d3d11.dll
    Report Id: c6133364-5a3b-4716-9e17-2263afb9c528
    Faulting package full name: IJSSolutions.AirPingPong_1.1.0.3_x86__d1z84xy8fkmzw
    Faulting package-relative application ID: App

    Fault bucket 133241199479, type 5
    Event Name: MoAppCrash
    Response: Not available
    Cab Id: 133306367371

    Problem signature:
    P1: IJSSolutions.AirPingPong_1.1.0.3_x86__d1z84xy8fkmzw
    P2: praid:App
    P3: 0.0.0.0
    P4: 55ee1c7f
    P5: d3d11.dll
    P6: 10.0.10240.16384
    P7: 559f3c11
    P8: c0000005
    P9: 00135d0e
    P10:

    Attached files:
    C:\Users\admin\AppData\Local\Temp\WERB300.tmp.WERInternalMetadata.xml
    C:\Users\admin\AppData\Local\Temp\WERB775.tmp.appcompat.txt
    C:\ProgramData\Microsoft\Windows\WER\Temp\WERB803.tmp.dmp
    C:\Users\admin\AppData\Local\Temp\WERBF18.tmp.WERDataCollectionFailure.txt

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: c6133364-5a3b-4716-9e17-2263afb9c528
    Report Status: 8
    Hashed bucket: 037737eb1948f11bce66b28612fdf500

    Report.wer:
    ---------------------------------
    Version=1
    EventType=MoAppCrash
    EventTime=130921798156339290
    ReportType=2
    Consent=1
    UploadTime=130921798158269410
    ReportIdentifier=c5f12e9f-8ca1-11e5-be75-001e373ccd1c
    IntegratorReportIdentifier=c6133364-5a3b-4716-9e17-2263afb9c528
    WOW64=1
    NsAppName=praid:App
    Response.BucketId=037737eb1948f11bce66b28612fdf500
    Response.BucketTable=5
    Response.LegacyBucketId=133241199479
    Response.type=4
    Response.CabId=133306367371
    Sig[0].Name=Package Full Name
    Sig[0].Value=IJSSolutions.AirPingPong_1.1.0.3_x86__d1z84xy8fkmzw
    Sig[1].Name=Application Name
    Sig[1].Value=praid:App
    Sig[2].Name=Application Version
    Sig[2].Value=0.0.0.0
    Sig[3].Name=Application Timestamp
    Sig[3].Value=55ee1c7f
    Sig[4].Name=Fault Module Name
    Sig[4].Value=d3d11.dll
    Sig[5].Name=Fault Module Version
    Sig[5].Value=10.0.10240.16384
    Sig[6].Name=Fault Module Timestamp
    Sig[6].Value=559f3c11
    Sig[7].Name=Exception Code
    Sig[7].Value=c0000005
    Sig[8].Name=Exception Offset
    Sig[8].Value=00135d0e
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=10.0.10240.2.0.0.256.48
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=bdcb
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=bdcb33e65a9843796b7ec31cc25bda3b
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=689d
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=689d12abf00dd47c453b5e1a156c0fa3
    UI[2]=C:\Program Files\WindowsApps\IJSSolutions.AirPingPong_1.1.0.3_x86__d1z84xy8fkmzw\giderosgame.Windows.exe
    LoadedModule[0]=C:\Program Files\WindowsApps\IJSSolutions.AirPingPong_1.1.0.3_x86__d1z84xy8fkmzw\giderosgame.Windows.exe
    LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
    ...

    LoadedModule[16]=C:\WINDOWS\SYSTEM32\d3d11.dll
    LoadedModule[17]=C:\Program Files\WindowsApps\Microsoft.VCLibs.120.00_12.0.21005.1_x86__8wekyb3d8bbwe\vccorlib120_app.DLL
    LoadedModule[18]=C:\WINDOWS\SYSTEM32\XAudio2_8.dll
    LoadedModule[19]=C:\WINDOWS\SYSTEM32\D3DCOMPILER_47.dll
    LoadedModule[20]=C:\Program Files\WindowsApps\Microsoft.VCLibs.120.00_12.0.21005.1_x86__8wekyb3d8bbwe\msvcp120_app.dll
    LoadedModule[21]=C:\WINDOWS\SYSTEM32\OLEAUT32.dll
    LoadedModule[22]=C:\Program Files\WindowsApps\Microsoft.VCLibs.120.00_12.0.21005.1_x86__8wekyb3d8bbwe\msvcr120_app.dll
    ...
    LoadedModule[46]=C:\Program Files (x86)\Common Files\Microsoft Shared\Ink\tiptsf.dll
    ...
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    File[0].CabName=WERInternalMetadata.xml
    File[0].Path=WERB300.tmp.WERInternalMetadata.xml
    File[0].Flags=851971
    File[0].Type=5
    File[0].Original.Path=C:\Users\admin\AppData\Local\Temp\WERB300.tmp.WERInternalMetadata.xml
    File[1].CabName=triagedump.dmp
    File[1].Path=WERB803.tmp.dmp
    File[1].Flags=539820035
    File[1].Type=6
    File[1].Original.Path=C:\ProgramData\Microsoft\Windows\WER\Temp\WERB803.tmp.dmp
    File[2].CabName=WERDataCollectionFailure.txt
    File[2].Path=WERBF18.tmp.WERDataCollectionFailure.txt
    File[2].Flags=851971
    File[2].Type=5
    File[2].Original.Path=C:\Users\admin\AppData\Local\Temp\WERBF18.tmp.WERDataCollectionFailure.txt
    File[3].CabName=Report.cab
    File[3].Path=Report.cab
    File[3].Flags=196608
    File[3].Type=11
    File[3].Original.Path=Report.cab
    FriendlyEventName=Stopped working
    ConsentKey=MoAppCrash
    AppName=IJSSolutions.AirPingPong_d1z84xy8fkmzw!App
    AppPath=C:\Program Files\WindowsApps\IJSSolutions.AirPingPong_1.1.0.3_x86__d1z84xy8fkmzw\giderosgame.Windows.exe
    NsPartner=windows
    NsGroup=windows8
    +1 -1Share on Facebook

    Comments

    • kussakovkussakov Member
      edited November 2015
      FYI: Just downloaded "Sea of Giants" - crashes as well on some desktops (where Air Ping Pong crashes) and works fine on other desktops (where Air Ping Pong works).
      Looks like it works on newer machines and crash on older machines (windows 10 and windows 8.1)


      Faulting application name: giderosgame.Windows.exe, version: 0.0.0.0, time stamp: 0x5633ff78
      Faulting module name: giderosgame.Windows.exe, version: 0.0.0.0, time stamp: 0x5633ff78
      Exception code: 0xc0000005
      Fault offset: 0x000b83ca
      Faulting process id: 0x258
      Faulting application start time: 0x01d120c1192b8dda
      Faulting application path: C:\Program Files\WindowsApps\2C97EF75.SeaofGiantsDemoTheSocietyofSecretGiants_1.1.1.4_x86__1wm8wfn66kqyy\giderosgame.Windows.exe
      Faulting module path: C:\Program Files\WindowsApps\2C97EF75.SeaofGiantsDemoTheSocietyofSecretGiants_1.1.1.4_x86__1wm8wfn66kqyy\giderosgame.Windows.exe
      Report Id: bfc3786d-0ffd-4512-9796-9cf726fddce2
      Faulting package full name: 2C97EF75.SeaofGiantsDemoTheSocietyofSecretGiants_1.1.1.4_x86__1wm8wfn66kqyy
      Faulting package-relative application ID: App

      Fault bucket 133233218439, type 5
      Event Name: MoAppCrash
      Response: Not available
      Cab Id: 0

      Problem signature:
      P1: 2C97EF75.SeaofGiantsDemoTheSocietyofSecretGiants_1.1.1.4_x86__1wm8wfn66kqyy
      P2: praid:App
      P3: 0.0.0.0
      P4: 5633ff78
      P5: giderosgame.Windows.exe
      P6: 0.0.0.0
      P7: 5633ff78
      P8: c0000005
      P9: 000b83ca
      P10:
      +1 -1Share on Facebook
    • john26john26 Maintainer
      The crash reports don't tell me much at the moment. If it's failing in d3d11.dll could it be the computer does not support DirectX 11? Can you find out what version of DirectX is present on the computers where it crashes? Just run dxdiag from the command prompt. Also is it a 32/64 bit issue, failing on 32-bit perhaps?

      Also, can you try to install this windows store app?

      https://www.microsoft.com/en-gb/store/apps/snow-slots-merry-christmas/9nblggh10dzk

      and let me know if it runs?
      http://giderosmobile.com
      https://github.com/gideros/gideros
      https://www.youtube.com/c/JohnBlackburn1975
      +1 -1Share on Facebook
    • kussakovkussakov Member
      You are right! The computer does not support DirectX 11.
      As I said - it looked like it crashes on older machines and now I see why.

      (FYI: I just installed several (Non Gideros) games - some work some don't)

      Thank you!
      +1 -1Share on Facebook
    • ar2rsawseenar2rsawseen Maintainer
      Is directX 11 a requirement by Winodws. Or by some specific feature?
      http://appcodingeasy.com/Gideros-Mobile
      +1 -1Share on Facebook
    • kussakovkussakov Member
      Good question. @John26 do you know?
      It does not make much sense to be Windows requirement though. Must be some Gideros features that need it.
      It comes as "integral" part of Windows (in Windows 10 you can't even install/update it separately - only via regular windows update). I guess windows 10 automatically installs the highest version supported by the hardware, which in the case of one of the older PCs I have is v. 9E.

      +1 -1Share on Facebook
    • john26john26 Maintainer
      edited November 2015
      The minimum requirement to install Windows 10 on a computer is DirectX 9 which is really ancient, going back to 2000 (it was introduced with Windows XP). Windows Phone devices are required to have DirectX 11. Currently the Gideros code running on Windows Store and Windows Phone is exactly the same so they both use DirectX 11. In principle we could introduce a DirectX 9 backend for Windows Store apps running on old computers but this is quite a challenge as DirectX 9 and DirectX 11 are completely different APIs. (each time MS brings out a new DirectX they start from scratch with no backward compatibility).

      In fact we would not write DirectX 9 code per se as this is not even allowed on the Windows Store. Instead we would write DirectX11 but with "feature level 9.3". I think this means limiting ourselves to facilities available in DX 9.3 but in a DX 11 style of programming, but I don't really understand it!

      For now you need to specify your game requires DirectX 11.

      See here for more info
      http://gamedev.stackexchange.com/questions/43861/does-windows-8-still-support-directx-9
      http://giderosmobile.com
      https://github.com/gideros/gideros
      https://www.youtube.com/c/JohnBlackburn1975
      +1 -1Share on Facebook
    Sign In or Register to comment.