Reset Device. Losing hope

[beaon]

Hi P99ers

I've been struggling with this reset device() issue on my new machine since last spring. I feel like I've spent months trying so many things to eliminate it.

In my troubleshooting I got things to what seemed like a stable running game about 99% of the time however recently I seem to have taken 3 steps back and am now crashing, routinely, in my favorite goto exp zone.

One thing unique is that I seem to crash in the same vicinity every time. If I am going to crash I kind of know where in the zone its going to happen, this is not always avoidable and certainly not preferred.

All the online troubleshooting talks about switching from full screen to windowed mode. That is not my case. I get this error just by simply playing.

Last night I hit a new low coming out of sky hoping to get a little exp. I died twice from two crashes and ended up with less XP than I had going in.

I am wondering if anyone else has encountered this? I am not sure what else I can do? It is very disappointing.

So far the biggest improvement has been running EQ in windeq2 but even still I crash at specific spots. Does anyone have any other advice?

Basic System Specs
AMD 3700x
32GB memory
RTX 2070 Super

I run in winEQ2. I have play nice turned off but am now experimenting with turning it on, it makes some things slow. I have CPU affinity set to a single core. I limit frames to 60fps. My monitor is 4k but I run EQ in wineq2 at 1080.

Let me know if there is anything else I can share. I am getting a bit desperate so any advice is appreciated.

[mcoy]

Looks like that CPU can boost to 4.4GHz. EQ doesn't like anything over 4.2 (iirc). Maybe try limiting your boost clock?

-Mcoy

[beaon]

Confirm that turning on eqplaynice in wineq2 does not help. What is interesting is I do crash in specific locations.

Ok looking into this cpu clock speed thing noted by mcoy.

[beaon]

@mcoy I have turned off my auto boost mode so now my CPU won't run past 3.6ghz. I ran past a spot that normally crashes me and it didn't. So if that ends up being a reliable fix I'll respond here.

So I guess so far so good but more testing needs to validate this.

[beaon]

Confirmed limiting my CPU to 3600mhz did not solve the problem.

I have also tried:
Disabling windows 10 UAC.
Updated drivers numerous times.

[YendorLootmonkey]

Hi P99ers

I've been struggling with this reset device() issue on my new machine since last spring. I feel like I've spent months trying so many things to eliminate it.

In my troubleshooting I got things to what seemed like a stable running game about 99% of the time however recently I seem to have taken 3 steps back and am now crashing, routinely, in my favorite goto exp zone.

One thing unique is that I seem to crash in the same vicinity every time. If I am going to crash I kind of know where in the zone its going to happen, this is not always avoidable and certainly not preferred.

All the online troubleshooting talks about switching from full screen to windowed mode. That is not my case. I get this error just by simply playing.

Last night I hit a new low coming out of sky hoping to get a little exp. I died twice from two crashes and ended up with less XP than I had going in.

I am wondering if anyone else has encountered this? I am not sure what else I can do? It is very disappointing.

So far the biggest improvement has been running EQ in windeq2 but even still I crash at specific spots. Does anyone have any other advice?

Basic System Specs
AMD 3700x
32GB memory
RTX 2070 Super

I run in winEQ2. I have play nice turned off but am now experimenting with turning it on, it makes some things slow. I have CPU affinity set to a single core. I limit frames to 60fps. My monitor is 4k but I run EQ in wineq2 at 1080.

Let me know if there is anything else I can share. I am getting a bit desperate so any advice is appreciated.

Have you read/tried any of this:

https://www.project1999.com/forums/showthread.php?t=120438

[beaon]

I did read that. My problem isn't related to alt-tabbing or going in and out of windowed mode. It happens mid game, while game is in focus.

However I did see their notes about eqclient.ini settings. Mine do not match but I am not sure they should.

Here is what I have. Thoughts?

[VideoMode]
WindowedWidth=1920
WindowedHeight=1080
Width=1920
Height=1080
FullscreenBitsPerPixel=32
FullscreenRefreshRate=0
WinEQWidth=1920
WinEQHeight=1080

[zactical]

This is happening to me as well. I have read everything I can find about it and mostly the discussion is around alt-tabbing or going in and out of fullscreen. My lockups happen mid playing, certain death when charming in HS.

Anecdotally wineq2 seems to help a bit, but it still happens. Very frustrating.

[Tunabros]

I had this same issue before
I reccomend using WIN EQ (https://www.lavishsoft.com/) it's really easy to use but you have to make an account

It helped with all my problems and it forces p99 to be in windowed

Hope it helps
Cheers

[Tunabros]

Basically what you do is download it after creating an account and set your EQ directory to it
follow the prompts blah blah blah

Then click on WIN EQ and go to your everquest default profile and the rest should run like butter

[xaix1999]

if your device is resetting you can try three things

install your gpu drivers from your manufacturers website
install dgvoodoo drivers in place of dx8/9 dlls to convert to dx11/12 api calls
install wined3d for dx8/9 translation to opengl or Vulkan

Live Long and Prosper

[xaix1999]

if your modern gpu is sending device reset
chances are you are getting memory heaps of of range
not as in to big but to small
the whole of titanium client is less than 4gb (i think)
i have a 8gb card
at max it uses about 200mb of ram
meaning i can address about half of my gpu ram to run the game and still have enough room for a second install on my gpu before i run out of ram
the game uses old tech
we have cheap gpus now that have 128 bit wide ram
back in the day 64 bit was like hot dang
the 2nd and 3rd options are your best bet

[zactical]

For some more context, here is the warning that is seen in the windows event viewer

Display driver nvlddmkm stopped responding and has successfully recovered.

One of the difficult things about troubleshooting this is that it is hard to know if any one change actually did anything. The game might run fine for several hours and then still end up crashing. I am experimenting with different resolutions and refresh rates in the eqclient.ini.




install wined3d for dx8/9 translation to opengl or Vulkan

I am going to give this a shot as well, thanks for the tip.

[xaix1999]

also did some light google'ing

Rolled back to 446.14 DCH and haven't had any issues (did not need to change any graphics or power settings).

source problem is a laptop with a type of 2070
https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/179540/display-driver-nvlddmkm-stopped-responding-and-has/
and found that 451.48 DCH and 451.67 DCH were the only releases to cause this issue for our setups

[beaon]

@Zatical I Also see those messages in my event viewer. I question whether those modifications will help though. Keep me posted if you find something.

[beaon]

OK I got dgvoodoo2 working but only when I don't use WINeq2. Is there a way to use both?

[xaix1999]

no
wineq2 uses dx8/9
dgvoodoo uses dx11/12

[beaon]

So that is a massive quality of life drop from wineq2 since you can set a lower resolution and scale it up on a 4k monitor with wineq2.

So far dgvoodo2 has returned the reset device when alt-tabbing or moving from full-screen and back. This problem was completely eliminated with wineq2.

Still that doesn't mean there aren't improvements. The original test was to see if in-game stability improved. I will find out next week when I return from a short vacation trip. If it does stabilize the game in certain spots than it will be worth it to me but losing wineq2 is a bummer in that case.

[xaix1999]

So that is a massive quality of life drop from wineq2 since you can set a lower resolution and scale it up on a 4k monitor with wineq2.

you can do this natively in windows

[xaix1999]

Here’s how:

In the search box, type the name of the app.
Select the app’s tile and tap or click Open file location to open File Explorer on the desktop.
In File Explorer, tap and hold (or right-click) the app’s executable (.exe) file and select Properties.
Select the Compatibility tab.
In the Settings section, select display scaling on high DPI settings.
Click OK and check with the results.

Hope the above information is helpful.

[xaix1999]

also did some light google'ing
Quote:
Rolled back to 446.14 DCH and haven't had any issues (did not need to change any graphics or power settings).
source problem is a laptop with a type of 2070
https://www.nvidia.com/en-us/geforce...nding-and-has/
Quote:
and found that 451.48 DCH and 451.67 DCH were the only releases to cause this issue for our setups

also finding a better version of your driver's will help

[xaix1999]

here's another app to help

http://www.brianapps.net/sizer4/

[zactical]

Wanted to follow up with my findings. I experimented with wined3d and different versions of the directx dlls. Some of them are incompatible with wineq2, it won't even launch. The ones that would allow it to launch seemed to help a bit, but still had several bad device failed messages. I eventually tried without wineq2 and have not had a crash since when using the directx 8 dlls. There was a certain spot in both howling stones and tower of frozen shadow that was giving me the error all the time. Since the change, I haven't had any issue there or anywhere else. I don't know if its completely solved, but sure seems to be.

[xaix1999]

awesome!
can you give us a bit more details?
what did you settle on?
where did you get your files from?
what is your gpu?

just for the next person so they have some direction

[zactical]

awesome!
can you give us a bit more details?
what did you settle on?
where did you get your files from?
what is your gpu?

just for the next person so they have some direction

Yeah, good idea. I downloaded the WineD3D files from https://fdossena.com/?p=wined3d/index.frag or just google "WineD3D".

Unzip the package and view the readme. It gives instructions for how to use the files for different directX versions. It is working well for me with the DirectX 8 files. All you have to do is copy the files the readme specifies into your EQ directory. From there, just launch the game as normal. Notably, this did not solve the problem when I tried to combine wineq2 with wineD3D, so it maybe be an either/or situation.

Here is the video mode settings from my ini.
[VideoMode]
WindowedWidth=1900
WindowedHeight=1050
Width=1900
Height=1050
FullscreenBitsPerPixel=32
FullscreenRefreshRate=0
WidthWindowed=1900
HeightWindowed=1050
WinEQWidth=1900
WinEQHeight=1050

I have a Nvidia GTX 1660 Ti, running driver version 456.71. I always run in windowed mode and never use alt+enter to go to fullscreen. Hope this helps someone in the future.

[spiz]

Yeah, good idea. I downloaded the WineD3D files from https://fdossena.com/?p=wined3d/index.frag or just google "WineD3D".

I tried this solution, but my NVidia card still locked up.

Just to make sure everyone knows, there are many threads that I believe relate to this issue. Here are a few:

https://www.project1999.com/forums/showthread.php?t=363133
https://www.project1999.com/forums/showthread.php?t=359131
https://www.project1999.com/forums/showthread.php?t=369607
https://www.project1999.com/forums/showthread.php?p=3185543

Hopefully some smart people will be able to find a solution for us soon. These random crashes are making me a worse cleric than I already was.

~ Faart

[xaix1999]

if you change the version of your nvidia drivers you can get better results

also did some light google'ing
Quote:
Rolled back to 446.14 DCH and haven't had any issues (did not need to change any graphics or power settings).
source problem is a laptop with a type of 2070
https://www.nvidia.com/en-us/geforce...nding-and-has/
Quote:
and found that 451.48 DCH and 451.67 DCH were the only releases to cause this issue for our setups

if you use wineq2, dgvoodoo and wined3d wont work.
wineq2 needs directx9

[xaix1999]

i dont use direct x at all, i use mesa plus dxvk which is vulkan.
if you only play p99, use linux as the setup that many use is reproducible.
there is almost no bugs or problems. reason i say almost is, i use p99-mimd to fix my only problem.

[Jamesstone714]

The dgvoodoo thing worked for my reset device/screen lockups on my Nvidia RTX win10 machine.

[xaix1999]

The dgvoodoo thing worked for my reset device/screen lockups on my Nvidia RTX win10 machine.

FanTasTic! I look forward to playing with you!

[beaon]

Huh. I crashed twice today. Ill have to try WineD3D. dgvoodoo sadly didnt help me.

[beaon]

So interestingly enough. I didn't crash with WineD3D but my game client did something very funky at the exact spot where Wineq2 typically crashes.

The screen went completely black but I could hear the environment around me. Flipping in and out of full screen recovered it. I forgot all about this behavior when switching to wineq2. It seems that whatever is happening at this moment is causing wineq2 to crash.

At least with wined3d things are recoverable. So mid charm kite hopefully I don't die to a client crash.

[koala]

Did anyone ever find a solution for this? I'm in exactly the same boat as beaon.

There's hundreds of recommendations out there around compatibility mode, using WinEQ, EQPlayNice, disabling mip mapping, setting the max FPS to match the monitor, setting the refresh rate in the INI, etc etc etc. None of these work -- and also, it seems like it's only a few of us that encounter the issue in this specific way (random times, not when alt+tab or alt+enter'ing).

I'm also using an RTX 2070 and another person who is also having this issue is using one as well. I'm starting to suspect faulty GPU or driver here.

[Jamesstone714]

I have the RTX2070 and had done a bunch of stuff, moving EQ into the root directory, trying to run it using different graphics settings, etc. The issue was so random it was very frustrating to find what I thought was working did not actually work.

The solution that worked for me was the DGVOODOO, which involved downloading a couple of small DLL files and putting them in your EQ folder. When you run the game there is a watermark that says DGVOODOO in the lower right corner of your window if it is working correctly. Never had an issue since then.

[Naethyn]

Set your windowed and full screen modes to 20 pixels less than maximum for height and width.

[mcoy]

I have the RTX2070 and had done a bunch of stuff, moving EQ into the root directory, trying to run it using different graphics settings, etc. The issue was so random it was very frustrating to find what I thought was working did not actually work.

The solution that worked for me was the DGVOODOO, which involved downloading a couple of small DLL files and putting them in your EQ folder. When you run the game there is a watermark that says DGVOODOO in the lower right corner of your window if it is working correctly. Never had an issue since then.

You can remove the watermark in the config file or using the dgvoodoocpl utility (point it to your eq folder).

-Mcoy

[beaon]

For me DGVOODOO did not solve the problem.

[beaon]

Set your windowed and full screen modes to 20 pixels less than maximum for height and width.


Less than the maximum what? Less than the full screen resolution? Or less than what my monitor allows?

[Ravager]

I had this problem on one of my old laptops. It was a crappy onboard Intel Graphics Chipset thing. It always crashed when it tried to draw certain spell particles (specifically AE spell particles, so maybe it was trying to draw more than it could at once). Once I disabled particle effects in options, it never happened again on that PC.

[Bones]

Less than the maximum what? Less than the full screen resolution? Or less than what my monitor allows?

less than full screen resolution, or whatever resolution you use natively. However I tried this suggestion myself and I still get reset device errors anyways. Seems to happen most often when turning the camera too fast in either third person or first.