PDA

View Full Version : Can't log in


Carthr
04-13-2010, 01:01 AM
<p>I've tried using the station launcher, launch pad, directly clicking the EQ2 and Everquest 2 exe's..  I'm pretty sure it's some stupid type of virus or something, as steam gives me weird error messages to.  I've reverted to a good clean ghost image and it doesn't make any difference.. Here's the EQ_crashlog thing:</p><p>EVERQUEST2 CRASH LOG=============================================== ================================================== =Unhandled exception EXCEPTION_ACCESS_VIOLATION at 0x008EA721Application was trying to read from 0x00000000    Region Begins At:  0x00000000    Region Ends At:    0x00010000    Region Size Is:    0x00010000 bytes    Memory Protection: PAGE_NOACCESS (00000001)    Memory State:      MEM_FREE    Memory Type:       FreeGame Data:    SOEBuild: SOEBuild=6369L    SOEVersionString: SOEVersionString=2010/4/5 16:36:46</p><p>I honestly have no clue what to do now..  The reverting back to the old ghost should have fixed it, but it didn't..</p>

Carthr
04-13-2010, 11:26 AM
<p>Problem signature:  Problem Event Name:    APPCRASH  Application Name:    StationLauncher.exe  Application Version:    0.0.0.0  Application Timestamp:    4b081deb  Fault Module Name:    StationLauncher.exe  Fault Module Version:    0.0.0.0  Fault Module Timestamp:    4b081deb  Exception Code:    c0000005  Exception Offset:    00034729  OS Version:    6.1.7600.2.0.0.256.1  Locale ID:    1033  Additional Information 1:    0a9e  Additional Information 2:    0a9e372d3b4ad19135b953a78882e789  Additional Information 3:    0a9e  Additional Information 4:    0a9e372d3b4ad19135b953a78882e789</p><p>Clean install of Win7.  I'm about to format all 2TB and start completely over..</p>

Carthr
04-13-2010, 04:45 PM
<p>Fixed...  I guess Win7 didn't like being operated in the supposed year of 2068 :/</p>

TSR-DanielH
04-13-2010, 10:04 PM
<p><cite>Carthrax wrote:</cite></p><blockquote><p>Fixed...  I guess Win7 didn't like being operated in the supposed year of 2068 :/</p></blockquote><p>It sounds like you experienced the dreaded y2.068k bug.  I'm glad to hear you survived the ordeal.  Let us know if you need any help in the future.</p>