none
APPCRASH, Fault Module Name: KERNELBASE.dll

    Question

  • I had this application which can run smoothly in Win XP OS, but with the Win 7 OS, it has the error below:

    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: TPUMonitorSystem.exe
      Application Version: 1.0.0.0
      Application Timestamp: 52258461
      Fault Module Name: KERNELBASE.dll
      Fault Module Version: 6.1.7601.18015
      Fault Module Timestamp: 50b83b16
      Exception Code: e0434352
      Exception Offset: 0000812f
      OS Version: 6.1.7601.2.1.0.256.4
      Locale ID: 1033
      Additional Information 1: 4fe1
      Additional Information 2: 4fe16bb058be9b8346a2eae9a8bbe4f1
      Additional Information 3: f254
      Additional Information 4: f2542ff3515f28520a0a445c873a8c09

    I had follow all advices from internet, 
    (1) try SFC -SCANNOW Command to check for System file damage, it has Verification 100% complete, Windows Resource Protection did not find any integrity violations.

    (2) try to set the platform of your application from 
    x86 to Any CPU in Configuration Manager in Visual Studio

    (3) try this: 
    http://www.twcenter.net/forums/showthread.php?529548-just-got-the-solution-about-appcrash-from-the-module-name-gt-kernelbase-dll

    all do not work. Can someone suggest something to check out?
    Tuesday, September 03, 2013 9:00 AM

Answers

All replies

  • Are you running it from Visual Studio with a debugger or from a built exe file? If you are not using a debugger, try attaching one and see what it says. You can also take a look in the system log to try to find more details on what caused the problem.

    Some other questions that I have:

    • What version of the .Net framework are you using?
    • Are you building it on XP or Windows 7?
    • Are the right frameworks installed and enabled on all computers? If the framework that you are using is disabled in Win7 by default, that might explain the problem.

    Wasabi Fan

    Tuesday, September 03, 2013 7:49 PM
  • solved it already, thanks. it is due to certain directory not given the appropriate rights.
    Friday, September 06, 2013 7:38 AM