![]() |
#1
|
|||
|
![]() I have been away from home for about a week..when i got home this morning i tried to play...it started up right went all the way to the server selct screeen i hit the server ruins of kunark p1999 then it waits a second and says
EVERQUEST: windows application error...the instruction at 0x02b91c6b referenced memort at 0x00000018 Them memory could not be read..Click OK to terminate program...if anyone has a solution or similar problem id really appreciate any help | ||
|
#2
|
|||
|
![]() Not being able to play sucks, but you're in the wrong place; please try the technical forum instead.
| ||
|
#3
|
||||
|
![]() Quote:
| |||
|
#4
|
|||
|
![]() duhh.. thanks bro
| ||
|
#5
|
||||
|
![]() Quote:
I've tried editing the eqclient.ini resolutions to various sizes, and told it to start in windowed, but it keeps starting fullscreen! Any ideas why it would do this and how do I fix it?!? The last time I was in game (yesterday!) I did have it running fullscreen.... | |||
|
#6
|
|||
|
![]() I stopped trying to use the EQEmuLauncher and tried running from the default EQ profile using WinEQ 2.0 program...
It works like a charm now. Started up in windowed mode and loaded in quite fast... so I guess the problem was the EmuLauncher | ||
|
#7
|
|||
|
![]() Edit: NEVERMIND, I see you got it to work!
/offtopic... Im currently taking x86 MASM classes (Im a Java / C++ developer for retail self checkouts), and really intrigued in that I wish I could see what the instruction at that memory location is attempting to accomplish. /ontopic... If the application was working just fine before you left, and there has not been ANY changes to the OS (such as installed drivers, updated drivers, windows updates, etc...) and now that your back the EQ app is now attempting to access protected memory (which NO app should do).. could be a malicious reason? (aka virus) Granted, there could be many causes... HAREWARE related... 1) HDD is starting to fail, and thus when loading into memory, the instruction(s) are corrupting, hence an attempted read in high protected memory (which no app should ever do)... 2) Memory is failing, same problem as number 1 above... SOFTWARE related... 3) Shared libraries are corrupted.. 4) and 5) As mentioned, changes in the driver libraries or Windows libraries changed the composition of EQ's calls into those libraries, pointers going everywhere... But the reason I mention possible malicious change (injected code by a virus re-directing calls elsewhere) is the fact that its attempting to address 0x00000018. That says to me a very specific address in particular to me. In any case, start with a virus scan... the follow it up with an uninstall / reinstall.. and then see where you are after that | ||
Last edited by HellHound989; 05-19-2014 at 03:34 PM..
Reason: solved
|
|
![]() |
|
|