Problem - Repeated Crashes (1 Viewer)

[Mattheux]

Hi,

I am getting crashes on a regular basis over the last couple of days. Happens at random on different characters. I have updated drivers, tried with and without ESET antivirus running, etc. I know you get the crash dumps, here are the names of them:

6d28f1fa-6dbb-4dbe-8b44-c216eade78a4
9b853a66-98da-490f-96c3-c7649817649e
9c846c95-1347-4d88-b033-819a7d44ad7d
026d96a6-5c6e-44f0-b0df-fe4d302cf8b44
251dc686-d1a3-4684-925c-ac34ee53bad8
546e17f2-ae12-4342-8120-fd9a1dde036b
234260bf-44ef-4eec-8eec-f4011224f5ad
592460c0-8539-4f21-902d-3fd90ff68d58
2553005d-d331-4fc6-bb51-33641e12d3a5
a38dec9e-ca91-4b16-b57f-207931614cb3
acae1981-3a99-41d8-84ef-6535c5d034cd
c5164057-bbfe-41b5-9d07-3b7b47a52499
e41580d3-3f16-46cb-bfd1-d7071d168302

 

[Sic]

Hi,

I am getting crashes on a regular basis over the last couple of days. Happens at random on different characters. I have updated drivers, tried with and without ESET antivirus running, etc. I know you get the crash dumps, here are the names of them:

6d28f1fa-6dbb-4dbe-8b44-c216eade78a4
9b853a66-98da-490f-96c3-c7649817649e
9c846c95-1347-4d88-b033-819a7d44ad7d
026d96a6-5c6e-44f0-b0df-fe4d302cf8b44
251dc686-d1a3-4684-925c-ac34ee53bad8
546e17f2-ae12-4342-8120-fd9a1dde036b
234260bf-44ef-4eec-8eec-f4011224f5ad
592460c0-8539-4f21-902d-3fd90ff68d58
2553005d-d331-4fc6-bb51-33641e12d3a5
a38dec9e-ca91-4b16-b57f-207931614cb3
acae1981-3a99-41d8-84ef-6535c5d034cd
c5164057-bbfe-41b5-9d07-3b7b47a52499
e41580d3-3f16-46cb-bfd1-d7071d168302

You would need to post your crash ID

 

[Mattheux]

This is the most recent one, I can make sure I save them going forward.

Just happened again.......

 

[Knightly]

I haven't looked at the upload, but that looks a lot like you have the nvidia overlay turned on and it's having problems.

 

[Mattheux]

This is a new computer. Last one was seven years old, ran Windows 10. I am still trying to get used to the settings on this new one. I will figure out how to shut off the Nvidia overlay for now.

I had not downloaded the GEForce Experience because I did not want the overlay, but looks like the overlay was automatic and I had to download Experience just to turn it off. Will see if this fixes the issues.

 

[sheijo]

I’m getting similar crashes with an IMac 5k running windows. Has an ATI 290, next crash I get I’ll post the info.

 

[Knightly]

f1cd4ees-d125-4615-9750-7ac959a8f3e2
5388a50b-9f66-4984-92a1-0094e61ababb

Just a tip if you're grabbing it, you can hit CTRL+C on that screen and paste it in, the CrashID will then be in text form for us so that we can easily paste it elsewhere rather than retyping or screengrabbing it ourselves (better than a screenshot of the error message)

So, I did look and this is straight up a graphics crash. I'd be curious if it happens without MQ. It doesn't look to be with the overlay.

I'd look at your graphics drivers and run updates/reversions until it works.

 

[Mattheux]

It might explain why I am sometimes having a problem with signal to the two monitors. One or both will just stop getting signal and go into sleep mode. Read that Win 11 had some problems with that, so have them set to not go to sleep, but maybe this will help as well. I will post as I experiment more with this.

 

[Sic]

It might explain why I am sometimes having a problem with signal to the two monitors. One or both will just stop getting signal and go into sleep mode. Read that Win 11 had some problems with that, so have them set to not go to sleep, but maybe this will help as well. I will post as I experiment more with this.

Resolution changes, or full screen -> windowed, or monitors sleeping can cause eq crashes (even without mq)

 

[Mattheux]

So, I found that the AMD driver was incorrect and got that fixed. Still got the crash below. Going to run the clients without MQ and leave them parked in guild lobby tonight so I can answer you if it happens without MQ.

---------------------------
EverQuest Crash Detected
---------------------------
MacroQuest caught a crash:
Version: 3.1.0.1712
Location: ReleaseGraphicsEngine+0 (C:\Users\Public\Daybreak Game Company\Installed Games\EverQuest\EQGraphicsDX9.DLL+0000000000018D00)

CrashID: 82936943-6374-4764-bf75-73b2e1398ce9

 

[Mattheux]

Resolution changes, or full screen -> windowed, or monitors sleeping can cause eq crashes (even without mq)

I have two Samsung Odyssey Neo 7 screens. There is a program that comes with the screen software that lets you split the monitor into grids. When you drag a window to the grid, it automatically resizes the window. This is helpful to have all the clients up visible along with MySEQ, Discord and Search engine.

If I am interpreting what you are saying, this could be part of the issue as well?

Am still going to try without MQ anyway overnight.

 

[Knightly]

No, that’s not likely to be the issue (if it was it would happen at the point you moved it). But it’s definitely a graphics issue that’s the problem. The hard part is nailing down what the graphics issue is.

 

[Mattheux]

No, that’s not likely to be the issue (if it was it would happen at the point you moved it). But it’s definitely a graphics issue that’s the problem. The hard part is nailing down what the graphics issue is.

Ok, I left it on all night without MQ and there was not a problem. What would you want me to test out from here?

 

[brainiac]

Did you run the dx9 setup package

 

[tomahawkeer]

I had similar issues, and turning off screen saver, and power saver settings to force the monitor to stay on is what fixed the crashes for me. I will say though, if you accidentially move a windowed instance, or switch from window to full screen or vice versa, it will still occasionally crash.

 

[Mattheux]

So I spoke too soon, I just came down and two of the six were crashed. I will check the dx9 setup, it may have had problems. As for the size, I do manipulate the sizes after they start. I used to run all six on one screen, layered in the same window size, and then map and internet on other screen. I would just alt-tab as needed between windows. Everquest starts with the window size of whatever the size of window you last closed, so I am constantly resizing as I start up a session. Seems like the only thing to try is to go back to the way I used to do it and have all the instances set to full screen and see if that solves it.

Since the size of the Everquest window upon launce is the same size as the last window closed, I have to resize everything and move them around when I start. Sounds like I need to go back to leaving them to fit one full screen and just alt-tabbing between them. Not what I wanted, but better than crashing. I will also run the dx9 setup again to be sure that is not the problem. I appreciate the suggestions and will keep working at this.

Another thought is resolution size. The suggested size for the displays are 3840x2160 at 300% scale. That makes the icons too big, so I set it to 125% scale. Inside EQ, 3840x2160 is a choice, but I cannot tell if it is sticking. In the launchpad advanced tools, it is set to 640x480 as default and does not give an option for 3840x2160. Any thoughts on how to set this? I can set the display resolution to lower and mess with the scale to make my desktop look the way I want to if that helps with the EQ window.

 

[Knightly]

Scaling isn't going to cause this issue. You can exclude EQ from scaling if you'd like so that you can control everything within EQ itself, but that's not causing you to crash. Nor is resizing the window or going full screen/windowed. Typical crashes from what Sic and tomahawkeer are talking about are related to changes while EQ is running (monitor going off is a resolution change because there is no resolution).

 

[Mattheux]

Ok, that makes sense. I do get these random flickers to the screen. I can call the place I got the computer from and talk to them about that. If I get that fixed, maybe that will take care of this situation.

 

[Doc James]

Simple things first. You said it's a new computer. Assuming you have an AV, maybe even the one baked in with Windows. Did you add exclusions for MQ, Redguides and the EQ directories? AV can be a PITA.

 

[Mattheux]

I did do that. I am keeping a timeline log of crashes and what I do starting today. Read about the new UI box in Display settings. Currently testing that checked off, which fixes the bag issue. The antivirus is ESET, btw.

 

[Knightly]

Screen flickering probably means something like a driver crash (of course, it could be hardware too) and that's going to be an issue. Before troubleshooting anything else, get that part fixed so you're not having direct display issues.

 

[Mattheux]

Going to go out on a limb here. Following a suggestion I read in here, wish I could remember the thread, I copied the EQ folder and VeryVanilla folder from my old Win10 computer to this new Win11 computer. Could that be causing the issues? Do I need to just completely delete EQ, RedGuides and MQ and start fresh?

If so, what files can I keep for my settings? The whole config file in MQ? Think there are two files in EQ for each character.

 

[Knightly]

Copying the folder is fine, but you need to install DX9 (as brainiac mentioned) since you didn't do the EQ install (which would have done it for you). https://www.microsoft.com/en-us/download/details.aspx?id=8109

 

[Mattheux]

FYI, the place I bought my computer from told me to bring it in. They had me test it with one screen off, with only one monitor plugged in and with other apps. Still getting the crash. Will update once I get it back.

 

[Knightly]

And Mattheux was never seen again.

 

[Mattheux]

And Mattheux was never seen again.

But he valiantly reappears!!!

I FINALLY got my computer back two days ago and spent yesterday making sure before I posted in here.

The issue had to do with the processor. One of the four cores was bad. So, from what I was told, whenever I go to the point that all four cores were needed, then crash. Got through yesterday with no crashes except from the known issues being talked about with the bad *.dll's.

I appreciate the suggestions and help troubleshooting from everyone.