【问题标题】:WPF application fails to start due to strange dll error由于奇怪的 dll 错误,WPF 应用程序无法启动
【发布时间】:2015-05-13 07:25:56
【问题描述】:

更新:空的 Windows 窗体应用程序也会发生下面描述的错误。

我在 C# 中有一个简单的 WPF 应用程序,它与 Bing 地图 API 一起使用。

该应用程序除了显示通过 xaml 代码集成的 Bing 地图之外什么都不做:

<m:Map CredentialsProvider="my api key that I removed here" 
       x:Name="myMap"
       Center="47.620574,-122.34942" ZoomLevel="12" Height="Auto" 
       "/>

除了Microsoft.Maps.MapControl.WPF,我没有引用任何特定的第三方库。

当我运行应用程序时,它会退出而不给出任何特定的错误消息。通过使用eventvwr 检查错误日志,我发现存储在我的AppData\Local\Admworks 文件夹中的某些dll 文件存在问题。该文件可能是动态生成的,因为每次我重新启动计算机时它都有不同的名称。第一次是jgmrysmv.dll,第二次是gfphosrs.dll,以此类推。 如果我重命名 Admworks 文件夹,则应用程序可以工作。但是,当我重新启动计算机时,问题又回来了。 Admworks 文件夹还在,dll 文件名不同。

这是事件查看器中报告的错误:

Faulting application name: WpfApplication2.vshost.exe, version: 12.0.30723.0, time stamp: 0x53cf4fe5
Faulting module name: gfphosrs.dll, version: 0.0.0.0, time stamp: 0x5547e370
Exception code: 0xc000041d
Fault offset: 0x000024ce
Faulting process ID: 0xcbc
Faulting application start time: 0x01d08d4c5b92cf13
Faulting application path: C:\Users\alber_000\documents\visual studio 2013\Projects\WpfApplication2\WpfApplication2\bin\Debug\WpfApplication2.vshost.exe
Faulting module path: C:\Users\alber_000\AppData\Local\Admworks\gfphosrs.dll
Report ID: 9a3939cb-f93f-11e4-bf2f-74e5437876cd
Faulting package full name: 
Faulting package-relative application ID: 

这是我在调试窗口中得到的输出:

'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_32\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualStudio.HostingProcess.Utilities\12.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.HostingProcess.Utilities.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualStudio.HostingProcess.Utilities.Sync\12.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.HostingProcess.Utilities.Sync.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualStudio.Debugger.Runtime\12.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Debugger.Runtime.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\Users\alber_000\documents\visual studio 2013\Projects\WpfApplication2\WpfApplication2\bin\Debug\WpfApplication2.vshost.exe'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_32\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.CSharp\v4.0_4.0.0.0__b03f5f7f11d50a3a\Microsoft.CSharp.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xml.Linq\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.Linq.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Data.DataSetExtensions\v4.0_4.0.0.0__b77a5c561934e089\System.Data.DataSetExtensions.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xaml\v4.0_4.0.0.0__b77a5c561934e089\System.Xaml.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\WindowsBase\v4.0_4.0.0.0__31bf3856ad364e35\WindowsBase.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_32\PresentationCore\v4.0_4.0.0.0__31bf3856ad364e35\PresentationCore.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\PresentationFramework\v4.0_4.0.0.0__31bf3856ad364e35\PresentationFramework.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
The thread 0x1db0 has exited with code 259 (0x103).
The thread 0x1d78 has exited with code 0 (0x0).
The thread 0x1d80 has exited with code 259 (0x103).
'WpfApplication2.vshost.exe' (CLR v4.0.30319: WpfApplication2.vshost.exe): Loaded 'C:\Users\alber_000\documents\visual studio 2013\Projects\WpfApplication2\WpfApplication2\bin\Debug\WpfApplication2.exe'. Symbols loaded.
The program '[7516] WpfApplication2.vshost.exe' has exited with code -1073740771 (0xc000041d).

我尝试将断点放在InitializeComponent() in

public MainWindow()
{
  InitializeComponent();
} 

但应用程序在到达该点之前停止。

【问题讨论】:

  • 也许是一点代码?有关使用的第三方程序集等的更多信息?您是否在带断点的调试模式下运行?
  • 更新了问题。
  • 什么是 Admworks?第三方? Visual Studio 中的插件?恶意软件(病毒)?
  • 我不知道。我检查了恶意软件,似乎没有。没有具有该名称的应用程序或库。我磁盘上唯一具有该名称的文件夹是AppData\Local 中的文件夹。真奇怪。

标签: c# wpf dll


【解决方案1】:

还没解决?尝试编译为 32 位而不是 64 位? dll问题的常见原因。

【讨论】:

  • 它似乎是恶意软件。用反恶意软件清理系统后,问题就消失了。但我不能百分百肯定地说。不过,谢谢你的建议。它可能对遇到 dll 问题的其他人有用。
猜你喜欢
  • 1970-01-01
  • 1970-01-01
  • 2023-03-08
  • 1970-01-01
  • 2012-10-31
  • 2011-04-11
  • 1970-01-01
  • 2014-07-29
  • 1970-01-01
相关资源
最近更新 更多