在Framework 4.5.2上发生故障CLR.dll

时间:2017-03-17 11:12:39

标签: .net

我仍然遇到故障模块clr.dll的问题,这会导致客户使用设备时应用程序崩溃...

我们使用Framework 4.0并发现了这个问题,因此我们将操作系统从Windows 7升级到Windows 8,将Framework从4.0升级到4.5.2。问题仍然存在......

*Information from Eventviewer:
*Faulting application name: Mikro.FareOn.Modules.Cards.Client.KioskJihlava.exe, version: 3.0.804.3406, time stamp: 0x56cb21bd
Faulting module name: clr.dll, version: 4.0.30319.18408, time stamp: 0x52310b2d
Exception code: 0xc0000409
Fault offset: 0x0047cb35
Faulting process id: 0xba4
Faulting application start time: 0x01d29eef3c327226
Faulting application path: c:\mikroelektronika\kiosk\Mikro.FareOn.Modules.Cards.Client.KioskJihlava.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: b9419dac-0aed-11e7-a037-00045f8f3145
Faulting package full name: 
Faulting package-relative application ID:*

*Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: Mikro.FareOn.Modules.Cards.Client.KioskJihlava.exe
P2: 3.0.804.3406
P3: 56cb21bd
P4: clr.dll
P5: 4.0.30319.18408
P6: 52310b2d
P7: 0047cb35
P8: c0000409
P9: 00000002
P10: 
Attached files:
These files may be available here:
C:\Users\kiosk1\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppCrash_Mikro.FareOn.Mod_91f327b9c548e7d593481687d6a18516e131862d_091355f6
Analysis symbol: 
Rechecking for solution: 0
Report Id: b9419dac-0aed-11e7-a037-00045f8f3145
Report Status: 4
Hashed bucket:* 

我已经安装了.Net Framework 4.5.2

enter image description here

有人可以帮帮我吗?

1 个答案:

答案 0 :(得分:1)

异常代码The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application. 表示STATUS_STACK_BUFFER_OVERRUN。 ntstatus.h说:

<platform name="ios">
    <config-file platform="ios" target="*-Info.plist" parent="NSMainNibFile">
        <string></string>
    </config-file>
</platform>
<platform name="ios">
    <config-file platform="ios" target="*-Info.plist" parent="NSMainNibFile~ipad">
        <string></string>
    </config-file>
</platform>

由于clr检查缓冲区大小,我猜你的应用程序中未经检查或本机代码有问题。

如果只在您的客户PC上发生这种情况,可能是客户PC上安装了其他应用程序,这可能会导致DLL注入并导致问题。我知道使用这些技术的防病毒工具和拼写检查/翻译应用程序。