Nortstrad

Yes, it happens around 2-5 seconds after I double-click Epsilon's .exe. Here's the information you requested. • OS: Windows 7 Home Premium (I can update to 10 if needed) • Nvidia GeForce GT 230 • DirectX 11

@Ross, while executing Epsilon to print the error window, a new one popped that hadn't shown before. It was also greyed-out, and I could hardly reach it. I still managed to screen it. Do you think this helps?

Hello and thanks for the swift response. The error is the basic Windows window (... per se) saying the program stopped working. It's the default error window you see when your game stops responding. I can post it here, it just doesn't contain any information.

Hello, I have not yet been able to log on Epsilon due to a multitude of issues. So far I have solved error 132 and error 134, followed by the CAS error. When I thought I was good to go, my client crashed shortly after running the execute. I will list down more details so this topic is not turned into a bothersome wall of text. • Read the megathread on Technical Support for a solution ✔ • Check if other users have had this issue and were given a fix ✔ • Attained ownership of the Epsilon folder ✔ • Place the folder in Programs, Programs (x86) and/or C:/ ✔ • Executed .exe as administrator ✔ • Tried installing via torrent ✔ • Tried installing via the tiny client ✔ • Attained ownership of the AppLocale folder ✔ • Marked the relevant folders as not Read-only ✔ • Checked the type of crash (it's a Windows-based crash, not a WoW client one) ✔ • Logged as PC administrator ✔ I'm not entirely sure what to do further, so I figured I should report the issue here. Thanks in advance.