Results 1 to 5 of 5

Hybrid View

  1. #1
    Stat Tracker Development Team
    Recursion Member
    Silencer's Avatar
    Join Date
    Feb 2014
    Location
    Chandler, Arizona
    Posts
    507
    I downloaded EMET 4.1 update 1 and set it to run with maximum settings and restarted, running on Windows 7 Ultimate x64. RTST opened fine, all though noticeably slower.

    This may not end up being a simple fix. Our program should always handle exceptions unless this is occurring on a static load which even then should be encompassed. Some basic things you can try right now would be removing our config file completely. It is located under C:\Users\USER\AppData\Local\RealTimeStatTracker (this may or may not have been created since your RTST crashes right away)

    The other idea is to run system file checker since the faulting module is an included Windows library which I doubt reinstalling the .NET framework would have affected.


    If those do not work I would like to take some time to troubleshoot this more specifically with you, but first get you on our newest version. It's not quite ready but it may fix your problem as we change how the program starts up and what libraries load. Either way it will make troubleshooting easier. If you want to give me your e-mail I can let you know when it is ready with instructions on how to get it. You can also reach me at silencer@recursion.tk

    And thank you for providing the detailed information that you did. I haven't seen this problem come up before and would like to get it fixed for you.

  2. #2
    Quote Originally Posted by Silencer View Post
    Some basic things you can try right now would be removing our config file completely. It is located under C:\Users\USER\AppData\Local\RealTimeStatTracker (this may or may not have been created since your RTST crashes right away)

    The other idea is to run system file checker since the faulting module is an included Windows library which I doubt reinstalling the .NET framework would have affected.
    The config file doesn't exist (neither does the directory). I ran sfc /scannow which reported "Windows Resource Protection did not find any integrity violations". I'll email you in a second about the new version.
    Thanks for your help on this.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •