locked
FatalEngineException when accessing Windows.Devices.Enumeration.DeviceInformation.Properties RRS feed

  • Question

  • When I was running my application with an option to stop on all exceptions I started getting strange exceptions in the place in code where I access DeviceInformation.Properties to check the details of a webcam (integrated webcam built into a T410s laptop). The reason I was querying the properties was I was looking for supported capture resolutions. I disabled stopping on handled exceptions for now and the app runs fine, but I have a feeling there might be something wrong going on in that property accessor.


    First it was only these two EETypeLoadExceptions:

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

    First-chance exception at 0x76da4b32 in MySecretApp.exe: Microsoft C++ exception: EETypeLoadException at memory location 0x04ebcd74.

    If there is a handler for this exception, the program may be safely continued.

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

    First-chance exception at 0x76da4b32 in MySecretApp.exe: Microsoft C++ exception: EETypeLoadException at memory location 0x04ebcd54.

    If there is a handler for this exception, the program may be safely continued.

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

    Then I got a FatalExecutionEngineError:

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

    Managed Debugging Assistant 'FatalExecutionEngineError' has detected a problem in 'C:\Projects\MySecretClient\MySecretApp\Win8_RP\MySecretApp\bin\Debug\AppX\MySecretApp.exe'.

    Additional Information: The runtime has encountered a fatal error. The address of the error was at 0x62b096c2, on thread 0x10d0. The error code is 0xc0000005. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.



    If there is a handler for this exception, the program may be safely continued.

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

    An unhandled exception of type 'System.ExecutionEngineException' occurred in Windows.Devices.winmd

    If there is a handler for this exception, the program may be safely continued.

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

    First-chance exception at 0x0fc84d51 in MySecretApp.exe: 0xC0000420: Assertion failed.

    If there is a handler for this exception, the program may be safely continued.

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

    First-chance exception at 0x76da4b32 in MySecretApp.exe: Microsoft C++ exception: [rethrow] at memory location 0x00000000.

    If there is a handler for this exception, the program may be safely continued.

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

    First-chance exception at 0x76da4b32 in MySecretApp.exe: Microsoft C++ exception: [rethrow] at memory location 0x00000000.

    If there is a handler for this exception, the program may be safely continued.

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

    Checking eventvwr - this is what I found:

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

    Fault bucket , type 0
    Event Name: PnPGenericDriverFound
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: x64
    P2: HID\VID_045E&PID_074F&REV_0140&Col01
    P3: 
    P4: 
    P5: 
    P6: 
    P7: 
    P8: 
    P9: 
    P10: 

    Attached files:

    These files may be available here:
    C:\Users\Filip\AppData\Local\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_473fb153c5709f6c827a79ed6a6cbd8ee6b1202f_cab_0be8aa45

    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e4c16a05-ebe7-11e1-be68-5cac4cc4363e
    Report Status: 4
    Hashed bucket: 

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

    Fault bucket , type 0
    Event Name: PnPGenericDriverFound
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: x64
    P2: USB\VID_045E&PID_074F&REV_0140
    P3: 
    P4: 
    P5: 
    P6: 
    P7: 
    P8: 
    P9: 
    P10: 

    Attached files:

    These files may be available here:
    C:\Users\Filip\AppData\Local\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_65f8a33e696134bf95d641ad61705fc04f885557_cab_0be8aa54

    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e4c16a06-ebe7-11e1-be68-5cac4cc4363e
    Report Status: 4
    Hashed bucket: 

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

    Fault bucket -1688569632, type 5
    Event Name: PnPGenericDriverFound
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: x64
    P2: HID\VID_045E&PID_074F&REV_0140&Col01
    P3: 
    P4: 
    P5: 
    P6: 
    P7: 
    P8: 
    P9: 
    P10: 

    Attached files:

    These files may be available here:
    C:\Users\Filip\AppData\Local\Microsoft\Windows\WER\ReportArchive\NonCritical_x64_473fb153c5709f6c827a79ed6a6cbd8ee6b1202f_31c8abbc

    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e4c16a05-ebe7-11e1-be68-5cac4cc4363e
    Report Status: 0
    Hashed bucket: 890f9bb2b0c573ba212f053fe9cfd61e

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

    Fault bucket 1450814957, type 5
    Event Name: PnPGenericDriverFound
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: x64
    P2: USB\VID_045E&PID_074F&REV_0140
    P3: 
    P4: 
    P5: 
    P6: 
    P7: 
    P8: 
    P9: 
    P10: 

    Attached files:

    These files may be available here:
    C:\Users\Filip\AppData\Local\Microsoft\Windows\WER\ReportArchive\NonCritical_x64_65f8a33e696134bf95d641ad61705fc04f885557_035cabbc

    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e4c16a06-ebe7-11e1-be68-5cac4cc4363e
    Report Status: 0
    Hashed bucket: a7a7c0c7bce52c67ea5dfcc6194b48b1

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


    Filip Skakun

    Wednesday, August 22, 2012 3:55 AM

All replies

  • Which 2 types fail to load? Can you capture details of the first 3 exceptions? (Stack trace, message, etc.)

    -Karel

    Thursday, August 23, 2012 4:51 AM
    Moderator