Application obfuscated using SmartAssembly (SmartAssembly installed in Windows 8.1) stopped working

PetchiPetchi Posts: 6 New member
Hi,

I have installed the SmartAssembly 6 in a PC of OS version Windows 8.1. I have obfuscated a Windows forms application "AppSamp" using SmartAssembly.  I installed this obfuscation application in some pc's. But in all those PC's my application "AppSamp" stopped working after 2 days with some error pointing some dll's.

I have attached the error's below:

Error 1:
   Faulting application name: AppSamp.exe, version: 0.0.0.1, time stamp: 0x5943c716
   Faulting module name: clr.dll, version: 4.6.1590.0, time stamp: 0x5787ef69
   Exception code: 0xc00000fd
  Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
  Report Id: f35cbe09-928f-11e7-8c55-28cfe911f9dc

Error 2:
  Faulting application name:  AppSamp.exe, version: 0.0.0.1, time stamp: 0x5943bbe5
  Faulting module name: GDI32.dll, version: 6.3.9600.17925, time stamp: 0x5596958b
  Exception code: 0xc00000fd
  Faulting module path: C:\Windows\SYSTEM32\GDI32.dll
  Report Id: 0d9c5dfe-8790-11e7-849d-fa97bf5688ac

Error 3:
    Faulting application name:  AppSamp.exe, version: 0.0.0.1, time stamp: 0x5943bbe5
    Faulting module name: ntdll.dll, version: 6.3.9600.17936, time stamp: 0x55a68dd1
    Exception code: 0xc00000fd
    Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
    Report Id: 15c25253-7bec-11e7-80d0-c03fd5fcb472

Error 4:
     Faulting application name: AppSamp.exe, version: 0.0.0.1, time stamp: 0x5943c716
    Faulting module name: USP10.dll, version: 1.626.7601.18009, time stamp: 0x50adbbd0
    Exception code: 0xc00000fd
    Faulting module path: C:\Windows\system32\USP10.dll
    Report Id: 8ad2b180-93ff-11e7-82d7-a886dda46e44



Can please give me a solution for this ?

Thanks.





Tagged:

Answers

  • Alex BAlex B Posts: 757 Diamond 1
    Hi @Petchi

    The "Exception code: 0xc00000fd" is a stack overflow exception and it may not necessarily be the processing by SmartAssembly that is causing the issue.

    This Stack Overflow article gives a good example of how to troubleshoot what may be causing the exception using WinDbg.  If you see that it is a SmartAssembly component that has been added which is causing the exception then we can investigate further in that regard but it seems likely something within your code as we haven't had reports of this occurring for others using the tool.

    Kind regards,
    Alex
    Product Support Engineer | Redgate Software

    Have you visited our Help Center?
Sign In or Register to comment.