Problem - ResetDevice failed! (1 Viewer)

[tomahawkeer]

ive been getting this error ever since I updated the client and MQ to the most recent patch. Anybody else having this issue?



That box generally means one of the toons has crashed. Ive had a few times where there were more than 1 at the same time. Is it an EQ / MQ thing or possibly a driver thing?

 

[durango773]

Thats a EQ crash (audio or visual) most of the time.

 

[Sic]

ive been getting this error ever since I updated the client and MQ to the most recent patch. Anybody else having this issue?

View attachment 50551

That box generally means one of the toons has crashed. Ive had a few times where there were more than 1 at the same time. Is it an EQ / MQ thing or possibly a driver thing?

are you having any devices go to sleep? or things like usb headset getting unplugged?

 

[knave23]

or playing another game that goes full screen and changes your resolution? I get this if I have a windowed toon logged in and try to open a game that takes over full screen. EQ does not play nicely with resolution changes

 

[tomahawkeer]

Hmmm....Monitors will go to sleep after an hour, but this last time it happened the monitor didnt go to sleep just the screen saver kicked. Nothing getting unplugged or what not.

or playing another game that goes full screen and changes your resolution? I get this if I have a windowed toon logged in and try to open a game that takes over full screen. EQ does not play nicely with resolution changes

Just a few minutes, my toons are in guild lobby, and I went and took a shower. Came back the screen saver was on, and I went to look at my main, and I had that box. His EQ instance was still open, but once you click the OK on that windows it will close. The toon was still showing logged in as well until I hit the ok button. he would then be kicked when I tried to log back in.

Updated video driver and rebooted. Gonna leave my guys in guild hall over night and see if any crash

 

[knave23]

I would bet redcents it's your screen saver if it crashed right after it turned on. Try turning that off and see if it still happens, or manually trigger it and see if it crashes your game.

 

[tomahawkeer]

Well, I let my guys sit in GH all night and no crash. Screen saver kicked and monitors went to sleep and no issues. No idea at this point.

 

[eqsubi15]

ive been getting this error ever since I updated the client and MQ to the most recent patch. Anybody else having this issue?

View attachment 50551

That box generally means one of the toons has crashed. Ive had a few times where there were more than 1 at the same time. Is it an EQ / MQ thing or possibly a driver thing?

I've had the same issue happen intermittently. No idea what causes it. Sometimes it's with 1 toon and sometimes it's with all of them.

 

[tomahawkeer]

I've had the same issue happen intermittently. No idea what causes it. Sometimes it's with 1 toon and sometimes it's with all of them.

The most ive had it happen on is 2 toons. It happened to drop my tank and my cleric in the middle of the fight, which of course, caused a wipe :-(

 

[durango773]

TLDR: Not MQ related.

This is a common EQ and Windows bug. It has been a thing for many many many years. It is less in Win11 (that i have seen), but anything getting a I/O change can causes EQ to poop itself. No promises, no "this will always do it", it happens. There is a bug report on the EQ forums from.. 2013? but its been happening before even then.

 

[Sic]

TLDR: Not MQ related.

This is a common EQ and Windows bug. It has been a thing for many many many years. It is less in Win11 (that i have seen), but anything getting a I/O change can causes EQ to poop itself. No promises, no "this will always do it", it happens. There is a bug report on the EQ forums from.. 2013? but its been happening before even then.

yep. almost always a device going to sleep, or getting unplugged / power savings etc.


I would also double check you don't have anything in your Compat Layers (registry) for shits - some searching shows several years ago there were some issues with that.

Check these locations in your registry for anything eq/mq related and delete.

HKEY_CURRENT_USER\Software\Microsoft\WindowsNT\CurrentVersion\AppCompatFlags\Layers
and 
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\AppCompatFlags\Layers

 

[tomahawkeer]

yep. almost always a device going to sleep, or getting unplugged / power savings etc.


I would also double check you don't have anything in your Compat Layers (registry) for shits - some searching shows several years ago there were some issues with that.

Check these locations in your registry for anything eq/mq related and delete.

HKEY_CURRENT_USER\Software\Microsoft\WindowsNT\CurrentVersion\AppCompatFlags\Layers
and
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\AppCompatFlags\Layers

Yeah nothing MQ / EQ related in there. And literally as I was going to regedit, I had 2 boxes die on me with this error. First time since reboot. Grrr

 

[Cybris]

I've only had this happen when I try to switch from Full Screen to Window Mode or I try running another game while EQ is running in the background.
As Durango stated this has been going on since early 2000's. Back then they would tell you to make sure Direct X and Video Card Drivers were updated. Now the error seems less frequent and I have not seen it popup on Win11.

 

[tomahawkeer]

I've only had this happen when I try to switch from Full Screen to Window Mode or I try running another game while EQ is running in the background.
As Durango stated this has been going on since early 2000's. Back then they would tell you to make sure Direct X and Video Card Drivers were updated. Now the error seems less frequent and I have not seen it popup on Win11.

I'm running windows 10 with them all windowed. I didn't have this problem until the small patch they had the other day.

 

[Hulda99]

Did you switch back to the "old" ui engine? For whatever reason after I switched back I see it more often.

 

[Doc James]

Update your audio and video drivers. Make sure you don't have audio drivers fighting over output. Meaning disable all audio devices you do not use such as if you have main speakers, you want to disable say the monitor speakers if you have a video card with audio over HDMI connections.

 

[postleaf]

Seems like there may be many causes of this problem. I had some recent experience with this error that appears to have gone away since I added some more RAM.
For context, this would happen periodically when I tried to run more than about 7 clients on 8G ram. Since updating to 32, I haven't seen it happen again (correlation or causation unknown )