View Single Post
  #1  
Old 09-07-2020, 07:35 AM
evelynbb evelynbb is offline
Orc

evelynbb's Avatar

Join Date: Oct 2016
Posts: 39
Default Crashing a lot. Issue is reproducable. Logs & info inside.

Hey fellas, tl;dr my EQ's been crashing for a few months now, and a lot more than I'm happy with. I've gone through a lot of threads on the net about this same issue, but none of them have come to a concrete resolution and I haven't been able to figure anything out.

Info:
OS: Windows 10 Home 64-bit
GFX card: 2047MB NVIDIA GeForce GTX 1660
Monitors: SB220Q (1920x1080@75Hz) & S200HL (1600x900@60Hz)
CPU: Intel Core i5 @ 2.90GHz

I'm running WinEQ2 + RAMDisk. Game runs fine outside of the crashes. The crashes generally happen a short while after zoning; OT hammer, death, or even just the initial log-in given enough time. Pre-crash logs are always the same, and I mean always. I've reproduced the following errors quite consistently by making a new character, running up to a guard and getting myself killed by them, then doing it again until I crash. The game will consistently crash after 1-4 cycles of this -- not as I'm loading, but after that as I'm doing anything, even something simple like keyboard turning or walking forwards.

My crash log: https://pastebin.com/JXsqWzWV

Basically, this is looped multiple times before the game completely ceases to function:

2020-09-07 05:56:14 IDirect3DIndexBuffer::Lock() failed.
2020-09-07 05:56:14 CBufferSet::AllocateIndexBuffer() failed.
2020-09-07 05:56:14 CBufferSet::AllocateIndices() failed.
2020-09-07 05:56:14 CRender::CreateBatchDefinitionSimpleModel() failed.

after a few of that, you get this, and quite a few of them as well:

2020-09-07 05:56:14 CRender::CreateBatchDefinitionRegion() failed.
2020-09-07 05:56:14 IDirect3DIndexBuffer::Lock() failed.
2020-09-07 05:56:14 CBufferSet::AllocateIndexBuffer() failed.
2020-09-07 05:56:14 CBufferSet::AllocateIndices() failed.

A google search of "IDirect3DIndexBuffer::Lock()" brings up microsoft documentation for DirectX. Perhaps this has something to do with the version of DirectX being run by default? I feel like this is the best lead.

Other misc. things I've tried in an attempt to fix it which didn't work:

- deleting eqclient.ini
- ensuring that all of the resolutions match up within eqclient.ini
- ensuring that i am using a window resolution native to everquest
- updating graphics drivers
- completely reinstalling EQ
- changing monitor refresh rate to 60 (though this did fix mouse movement issues)
- running eqgame in windows xp (service pack 2) compatibility mode
- using wineq2 to play
- disabling my second monitor
- ensuring my graphics card is set to optimal performance
- sfcscan, repair, DISM
- crying

And... yeah. No dice on this so far. Any tech savvy folk wanna help out?
Reply With Quote