View Full Version : Memory could not be read
GuyBrush Threepwood
05-19-2022, 12:29 PM
I'm having an issue which happens randomly. After a random amount of time in game eventually a window pops up saying:
The instruction at 0x00000000CECECECE referenced memory at 0x00000000CECECECE. The memory could not be read.
Click on OK to terminate the program.
I have found many threads pertaining to this issue but all of them are about crashing when opening the game usually because screen resolution. I have tried every fix i found and nothing has worked.
This happens either randomly during play after 10 minutes to many hours or upon zoning sometimes. If this window pops up I can drag it off screen and it will remain while I play until I zone or camp at which point the game will crash.
I play daily but recently came back from a little break the game worked fine before and I haven't changed anything.
System specs:
Intel Core i5 8300H CPU 2.3ghz
8gb ram
Windows 11
Nvidia GeForce 1050 graphics card
GuyBrush Threepwood
05-19-2022, 01:51 PM
New issue found out eq was running on my integrated graphics from the cpu so i disabled the integrated graphics. Now eq uses 100% of my cpu and wont load character models. Not sure what to do about that.
Update:
Fixed this issue by changing windows graphics settings for the program under display and telling it not to use auto HDR. Sincerely hoping that disabling integrated graphics has fixed the memory read issue if i don't post again then it worked.
GuyBrush Threepwood
05-19-2022, 03:15 PM
Memory read error is still happening.
So you want to be a pirate 'eh? Well, real pirates use dgvoodoo2 and CPU affinity:
https://www.project1999.com/forums/showthread.php?t=4978
-Mcoy
https://imgur.com/a9ZhuEx.jpg
GuyBrush Threepwood
05-20-2022, 10:52 AM
Trying dgvoodoo2 now although im not sure if I did it right, its quite confusing. Copied all the x86 3dfx and ms .dlls over but i don't see any watermarks or anything on screen to know if its working.
GuyBrush Threepwood
05-20-2022, 11:57 AM
Still get memory read error trying all the x64 versions now. Also yeah i was already using CPU affinity not sure if that actually does anything either.
GuyBrush Threepwood
05-20-2022, 03:36 PM
Still get the memory error, am i using dgvoodoo2 wrong? Any other ideas how to fix?
OldManNoPants
07-10-2022, 11:33 PM
Did you have any luck getting this resolved?
Jintle
07-12-2022, 04:26 AM
I get this error under Windows 11, none of the fixes have worked - compatibility mode, run as admin,dgvoodoo2 and Borderless Gaming. Ran out of things to try.
I get this error under Windows 11, none of the fixes have worked - compatibility mode, run as admin,dgvoodoo2 and Borderless Gaming. Ran out of things to try.
Wasn't there some optional windows patch that resolved issues with win11 and some directx games? I'm still on w10 but maybe someone else here has experience with that?
-Mcoy
spoil
07-12-2022, 11:01 AM
I get this error frequently, let me know if anything works for you. I run the game in xp s2 compatibility mode as admin, dgvoodoo, and with cpu affinity.
Danato
07-13-2022, 10:23 AM
How much ram do you have? When I had this issue I had 8gb, tried adjusting virtual memory, bit didn't help. I upgraded to16gb of ram and have not seen it. Curious what others have to know if maybe the amount of physical memory is the issue.
Jimjam
07-13-2022, 11:14 AM
Downgrade your textures to lower memory versions, clear your texture cache files, back up your logs.
Jintle
07-13-2022, 01:27 PM
Wasn't there some optional windows patch that resolved issues with win11 and some directx games? I'm still on w10 but maybe someone else here has experience with that?
-Mcoy
Oh yeah, forgot about that, didn't work either.
Oh, and I have 16GB RAM
Zenren
07-19-2022, 01:58 AM
I get this error. I've found that you don't crash unless you click "ok", the game continues to play. The only issue is that when you zone or try to camp, you crash and remain in the game, which means certain activities, like raids where you need to camp out, or when you zone into a zone that is frequently trained, are dicey at best. I have been searching extensively for a fix and tried every trick I can find and still haven't resolved it. I have semi-retired from the game due to this issue. Windows 11, AMD Ryzen 7 5800x, RTX 3080 video card, 16 GB DDR4, and a 1 TB SSD.
I get this error. I've found that you don't crash unless you click "ok", the game continues to play. The only issue is that when you zone or try to camp, you crash and remain in the game, which means certain activities, like raids where you need to camp out, or when you zone into a zone that is frequently trained, are dicey at best. I have been searching extensively for a fix and tried every trick I can find and still haven't resolved it. I have semi-retired from the game due to this issue. Windows 11, AMD Ryzen 7 5800x, RTX 3080 video card, 16 GB DDR4, and a 1 TB SSD.
A ryzen 7 5800x has a boost of over 4.2GHz. The client doesn't like anything above 4.2 (or 4.1). Try lowering your max turbo, or temporarily disabling it.
-Mcoy
Kealenfists
07-21-2022, 11:36 PM
So you want to be a pirate 'eh? Well, real pirates use dgvoodoo2 and CPU affinity:
https://www.project1999.com/forums/showthread.php?t=4978
-Mcoy
https://imgur.com/a9ZhuEx.jpg
yeah dgvoodoo doesn't fix this.
Kealenfists
07-22-2022, 06:03 PM
A ryzen 7 5800x has a boost of over 4.2GHz. The client doesn't like anything above 4.2 (or 4.1). Try lowering your max turbo, or temporarily disabling it.
-Mcoy
Running AMD Ryzen 7 4800H Nvidia RTX3060 GDDR6 @ 6GB
I cant get mine to even push over 4.2 and I get it super often
Kealenfists
07-22-2022, 06:30 PM
Also monitored the system long enough to get two crashes and both happened under 4000. Appreciate the idea though
Kealenfists
07-31-2022, 06:17 PM
The issue is Windows 11
Yeah I think the majority of us have figured that out but we need a fix.
Lobster1071
08-13-2022, 06:26 PM
I'm having an issue which happens randomly. After a random amount of time in game eventually a window pops up saying:
The instruction at 0x00000000CECECECE referenced memory at 0x00000000CECECECE. The memory could not be read.
...
This happens either randomly during play after 10 minutes to many hours or upon zoning sometimes.
Exact same issue for me. Exact error and exact randomness.
I came back after a long break as well. Used to have a Windows 10 machine, and P99 ran nearly flawless for years. Now have a new Windows 11 machine game crashes randomly every time with that error. Disappointing if this is what will stop me from playing again.
I didn't know the error window could be dragged away and still play. I'll have to try that instead of just clicking OK.
Going to poke around for some other solutions which I know I haven't checked everywhere for yet.
Intel i9-12900KF 3.19GHz
32gb RAM
Windows 11
Nvidia GeForce RTX 3060 Ti
khandman
08-14-2022, 03:29 AM
I'm on Windows 11 and thankfully I've not happened across this issue yet
Corso
08-14-2022, 04:54 AM
Never had this issue before switching to Windows 11, now it happens from time to time.
I use wineq2 (+ compat win xp sp2), ran flawlessly until Windows upgrade.
Specs for posterity:
Intel i9-something
Dual GPU: intel something + RTX 2080 (p99 runs on the latter)
khandman
08-14-2022, 05:01 AM
I play exclusively in Windowed mode, so don't use Full Screen at all, if that may have any bearing.
Corso
08-14-2022, 06:27 AM
I play using windowed mode also.
Would you care to post your specs, khandman? It could help narrow down the issue.
khandman
08-14-2022, 09:12 AM
https://www.userbenchmark.com/UserRun/52753115
Link to a User Benchmark when I got my now current machine.
Lobster1071
08-15-2022, 08:08 PM
I play exclusively in Windowed mode, so don't use Full Screen at all, if that may have any bearing.
I always play in Windowed mode as well.
I am now trying the "Affinity" fix, and it seems to have cut down the number of times it crashes, but it does still happen.
This is what I tried in case you don't know:
https://wiki.project1999.com/Players:Technical/Affinity
GuyBrush Threepwood
08-18-2022, 07:59 AM
Sorry haven't checked this thread in a bit, no fixes have worked. I can confirm I do use windows 11 I have 8gb of ram but never come close to that limit. I suppose windows 11 may be the culprit, I'm not sure what to do about that short of running a virtual machine with whatever operating system (probably windows XP SP3 should work flawlessly) or downgrading back to 10.
Lobster1071
08-24-2022, 09:38 AM
Sorry haven't checked this thread in a bit, no fixes have worked. I can confirm I do use windows 11 I have 8gb of ram but never come close to that limit. I suppose windows 11 may be the culprit, I'm not sure what to do about that short of running a virtual machine with whatever operating system (probably windows XP SP3 should work flawlessly) or downgrading back to 10.
Has anyone ever tried running EQ in a virtual environment?
I was thinking about that, running Windows 10 in VirtualBox, but thought the performance might be horrible. Anyone have experience with this?
Darksinga
08-26-2022, 04:02 PM
Windows 11 is meh. The unfortunate thing is a lot of newer PCs are loaded with Windows 11 by default.
I’d do the Media Creation Tool and downgrade to Windows 10 personally. Just make sure you back up your files before deleting any partitions.
https://www.microsoft.com/en-us/software-download/windows10ISO
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.