none
Configuration Verifier Crash RRS feed

  • Question

  • The Kinect Configuration Verifier crashes on my system. All the other demo's run fine.

    The stack trace I get when catching the verifier in debug is the following:
    ---
    'KinectV2ConfigurationVerifier.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_32\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll'
    'KinectV2ConfigurationVerifier.exe' (Managed (v4.0.30319)): Loaded 'C:\Program Files\Microsoft SDKs\Kinect\v2.0-PublicPreview1409\Tools\ConfigurationVerifier\KinectV2ConfigurationVerifier.exe'
    'KinectV2ConfigurationVerifier.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\PresentationFramework\v4.0_4.0.0.0__31bf3856ad364e35\PresentationFramework.dll'
    'KinectV2ConfigurationVerifier.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\WindowsBase\v4.0_4.0.0.0__31bf3856ad364e35\WindowsBase.dll'
    'KinectV2ConfigurationVerifier.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll'
    'KinectV2ConfigurationVerifier.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_32\PresentationCore\v4.0_4.0.0.0__31bf3856ad364e35\PresentationCore.dll'
    'KinectV2ConfigurationVerifier.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xaml\v4.0_4.0.0.0__b77a5c561934e089\System.Xaml.dll'
    'KinectV2ConfigurationVerifier.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\PresentationFramework.Aero2\v4.0_4.0.0.0__31bf3856ad364e35\PresentationFramework.Aero2.dll'
    'KinectV2ConfigurationVerifier.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll'
    'KinectV2ConfigurationVerifier.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll'
    'KinectV2ConfigurationVerifier.exe' (Managed (v4.0.30319)): Loaded 'C:\Program Files\Microsoft SDKs\Kinect\v2.0-PublicPreview1409\Tools\ConfigurationVerifier\Microsoft.WindowsAzure.Storage.dll'
    'KinectV2ConfigurationVerifier.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll'
    'KinectV2ConfigurationVerifier.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\UIAutomationTypes\v4.0_4.0.0.0__31bf3856ad364e35\UIAutomationTypes.dll'
    'KinectV2ConfigurationVerifier.exe' (Managed (v4.0.30319)): Loaded 'Microsoft.GeneratedCode'
    'KinectV2ConfigurationVerifier.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Management.dll'
    'KinectV2ConfigurationVerifier.exe' (Managed (v4.0.30319)): Loaded 'C:\Program Files\Microsoft SDKs\Kinect\v2.0-PublicPreview1409\Tools\ConfigurationVerifier\EnumUSB.dll'
    An unhandled exception of type 'System.Management.ManagementException' occurred in mscorlib.dll
    Additional information: Critical error 
    The program '[5812] KinectV2ConfigurationVerifier.exe: Managed (v4.0.30319)' has exited with code 0 (0x0).
    ---

    Any clues about why the verifier crashes on launch?

    Tuesday, October 7, 2014 2:56 PM

All replies

  • Can you provide more detail on the Windows configuration? Is this a clean install or was it an upgrade from Windows 7? Do you have third party security software/anti-virus? Can you download the ProcDump tool from sysinternals website and create a crash dump for us?

    http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

    From an admin command prompt, run the following command lines to create the dump file. If there is a crash, you should get a .dmp file in the C:\dump directory. If you can make that available through DropBox or OneDrive that would be of great assistance.

    // make sure you have the ProcDump tool in a folder you can access
    // this script assumes it is in C:\Tools directory
    mkdir C:\dump
    cd /d C:\Tools
    procdump -e 1 -f"" -ma -x C:\dump "C:\Program Files\Microsoft SDKs\Kinect\v2.0-PublicPreview1409\Tools\ConfigurationVerifier\KinectV2ConfigurationVerifier.exe"
    


    Carmine Sirignano - MSFT

    Tuesday, October 7, 2014 6:21 PM
  • It was a clean windows 8 install (now 8.1). There's no anti-virus running.

    Procdump didn't write a log file, but I copied the output from the command prompt:

    ProcDump v7.1 - Writes process dump files
    Copyright (C) 2009-2014 Mark Russinovich
    Sysinternals - www.sysinternals.com
    With contributions from Andrew Richards

    Process:               KinectV2ConfigurationVerifier.exe (3704)
    CPU threshold:         n/a
    Performance counter:   n/a
    Commit threshold:      n/a
    Threshold seconds:     10
    Hung window check:     Disabled
    Log debug strings:     Disabled
    Exception monitor:     First Chance+Unhandled
    Exception filter:      *-ma*
    Terminate monitor:     Disabled
    Cloning type:          Disabled
    Concurrent limit:      n/a
    Avoid outage:          n/a
    Number of dumps:       1
    Dump folder:           C:\dump\
    Dump filename/mask:    PROCESSNAME_YYMMDD_HHMMSS


    Press Ctrl-C to end monitoring without terminating the process.

    CLR Version: v4.0.30319

    [16:33:42] Exception: E0434F4D.System.IO.FileLoadException ("Could not load file
     or assembly 'KinectV2ConfigurationVerifier, Version=1.0.0.0, Culture=neutral, P
    ublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly
    's manifest definition does not match the assembly reference. (Exception from HR
    ESULT: 0x80131040)")
    [16:33:42] Exception: E0434F4D.System.IO.FileLoadException ("Could not load file
     or assembly 'KinectV2ConfigurationVerifier, Version=1.0.0.0, Culture=neutral, P
    ublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly
    's manifest definition does not match the assembly reference. (Exception from HR
    ESULT: 0x80131040)")
    [16:33:42] Exception: E0434F4D.System.IO.FileLoadException ("Could not load file
     or assembly 'KinectV2ConfigurationVerifier, Version=1.0.0.0, Culture=neutral, P
    ublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly
    's manifest definition does not match the assembly reference. (Exception from HR
    ESULT: 0x80131040)")
    [16:33:43] Exception: E0434F4D.System.IO.FileLoadException ("Could not load file
     or assembly 'KinectV2ConfigurationVerifier, Version=1.0.0.0, Culture=neutral, P
    ublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly
    's manifest definition does not match the assembly reference. (Exception from HR
    ESULT: 0x80131040)")
    [16:33:43] Exception: E0434F4D.System.IO.FileLoadException ("Could not load file
     or assembly 'KinectV2ConfigurationVerifier, Version=1.0.0.0, Culture=neutral, P
    ublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly
    's manifest definition does not match the assembly reference. (Exception from HR
    ESULT: 0x80131040)")
    [16:33:43] Exception: E0434F4D.System.IO.FileLoadException ("Could not load file
     or assembly 'KinectV2ConfigurationVerifier, Version=1.0.0.0, Culture=neutral, P
    ublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly
    's manifest definition does not match the assembly reference. (Exception from HR
    ESULT: 0x80131040)")
    [16:33:43] Exception: E0434F4D.System.IO.FileLoadException ("Could not load file
     or assembly 'KinectV2ConfigurationVerifier, Version=1.0.0.0, Culture=neutral, P
    ublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly
    's manifest definition does not match the assembly reference. (Exception from HR
    ESULT: 0x80131040)")
    [16:33:43] Exception: E0434F4D.System.IO.FileLoadException ("Could not load file
     or assembly 'KinectV2ConfigurationVerifier, Version=1.0.0.0, Culture=neutral, P
    ublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly
    's manifest definition does not match the assembly reference. (Exception from HR
    ESULT: 0x80131040)")
    [16:33:43] Exception: E0434F4D.System.IO.FileLoadException ("Could not load file
     or assembly 'KinectV2ConfigurationVerifier, Version=1.0.0.0, Culture=neutral, P
    ublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly
    's manifest definition does not match the assembly reference. (Exception from HR
    ESULT: 0x80131040)")
    [16:33:43] Exception: E0434F4D.System.IO.FileLoadException ("Could not load file
     or assembly 'KinectV2ConfigurationVerifier, Version=1.0.0.0, Culture=neutral, P
    ublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly
    's manifest definition does not match the assembly reference. (Exception from HR
    ESULT: 0x80131040)")
    [16:33:45] Exception: E0434F4D.System.IO.FileNotFoundException ("Could not load
    file or assembly 'KinectV2ConfigurationVerifier.XmlSerializers, Version=2.0.0.0,
     Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. T
    he system cannot find the file specified.")
    [16:33:45] Exception: E0434F4D.System.Management.ManagementException ("Critical
    error ")
    [16:33:45] Exception: E0434F4D.System.Management.ManagementException ("Critical
    error ")
    [16:33:45] The process has exited.
    [16:33:45] Dump count not reached.

    Wednesday, October 8, 2014 2:35 PM
  • hmm... the "FileNotFoundException" can be ignored since that will happen in a working scenario. These 2 lines seem to be where the issue is coming from:

    [16:33:45] Exception: E0434F4D.System.Management.ManagementException ("Critical
     error ")
     [16:33:45] Exception: E0434F4D.System.Management.ManagementException ("Critical
     error ")
    Was the install of the SDK a clean September release, or did you have a previous version installed? If so, did you uninstall the previous version before installing the new one. Let me discuss with the team for next steps.


    Carmine Sirignano - MSFT


    Wednesday, October 8, 2014 5:51 PM