Has the same issue with hdmi, though now I can only go up to 60hz for some reason.
Now I believe it is a hardware issue. Can you try testing that card on another pc?
Has the same issue with hdmi, though now I can only go up to 60hz for some reason.
Has the same issue with hdmi, though now I can only go up to 60hz for some reason.
Downloading furmark now.
GPU took the stress test like a champ, no crashes. I should mention again, this only happens in certain circumstances. Forza horizon 4 pushes my gpu to its absolute limit and does not exhibit this issue, the same can be said about the Witcher 3 and monster hunter world. Also yes, I did see the display driver crash in the event viewer.This is almost 100% a GPU driver crash.
If you open up the windows event viewer, you will in all likelyhood see an error stating something like "Display driver XXXXXXXXX stopped responding and has successfully recovered."
Try grinding your GPU with Furmark on max settings and see if you can create the crash again. If possible, just to rule out any inconsistencies, use a monitoring tool like afterburner and record all the logs. You might notice something funky in the logs which could be your clue as to why it's crashing, like perhaps VRAM is being oversaturated.
They're just standards, so if you have an old standard, a newer one could be better than it.
I do not have access to a non laptop computer atm. I'm also too incompetent to do that without messing something up, me and a friend put this pc together. I could do it if I absolutely needed to, but at the moment I would rather not risk it.Now I believe it is a hardware issue. Can you try testing that card on another pc?
Still taking it like a champHmmm... If it even happens at 1080p60hz through HDMI, then I am stumped. Seems the only commonality is the monitor, but you said it only happens in games, and other situations which push the GPU... Weird.
Will be interested to see the outcome of this thread.
P.S. - I've had weird issues in the past with some of the memory on a GPU being bad. Still wouldn't explain why it's only an issue on that monitor, but you can perform a VRAM test with this utility as a "Hail Mary" pass: http://mikelab.kiev.ua/index_en.php?page=PROGRAMS/vmt_en
Still taking it like a champ
I didn't actually change my resolution, it just happened to crash when I got that far . Also happens in game in those games more often than menus, I just happened to get lucky in my video.Does this only happen when you are running the monitor at non-native fullscreen resolutions? In the video you posted, the crash happens when you try to change resolution. You also said it happens going into menus in some games (some of which use different resolution than the actual game) and at startup (when the game actually gets the dedicated window and sets the resolution).
Do the crashes still happen if you run the game(s) in windowed mode?
May be linked to resolution?
I didn't actually change my resolution, it just happened to crash when I got that far . Also happens in game in those games more often than menus, I just happened to get lucky in my video.
GPU took the stress test like a champ, no crashes. I should mention again, this only happens in certain circumstances. Forza horizon 4 pushes my gpu to its absolute limit and does not exhibit this issue, the same can be said about the Witcher 3 and monster hunter world. Also yes, I did see the display driver crash in the event viewer.
I wanna bring up something else. I just changed doom 2016,another game which consistently had this issue, from vulkan to opengl. I don't know if this means anything or if it was just a fluke. Doing a vulkan benchmark did not cause my display drivers to crash.Welp, then what I'm about to say is gonna suck. It's entirely possible that you can't fix it. I've had similar issues where the problem was a game calling the display driver in a bad way and it would crash the game. It was only that game too. Your options are probably limited to coping ability:
Overall, the solutions that would fix the things perfectly are probably out of your control. Since furmark didn't crash your card, the silver lining is that your hardware probably isn't going bad.
- Try using an older display driver from 6 months back. This might be a change in the driver that screwed up the call the game was making.
- Try lowering the monitor that crashes the game down to the spec to the one that doesn't with a custom resolution using your display panel. Refresh rate, resolution, and everything else. It could entirely be the way that the driver is handling the information while doing the math and sending it to the monitor causes issues in this one specific circumstance.
- You could try and increase the resolution of the monitor. NVidia has supersampling which effectively renders the game at a higher resolution then downscales. I've had this fix artifacting in a game.
- Try using a default windows generic display driver. It's going to suck, and probably not give you the experience that you want, but in my experience, default windows drivers have never crashed on me. It's always 3rd party drivers that cause issues
Yeah, it's 100% games calling on the driver in a faulty way then, or rather the driver handling the game requests in a faulty manner. Either way, it's outside of your control to "fix" the issue. You might be able to tinker with the config files of the game to set the video backend before the game boots to try and solve the issue. Unfortunately, looking at the settings menu of NierR suggests that changing the backend isn't an option. Instead you might try turning the shadows off, AO off, or just tinkering with the settings in general.I wanna bring up something else. I just changed doom 2016,another game which consistently had this issue, from vulkan to opengl. I don't know if this means anything or if it was just a fluke. Doing a vulkan benchmark did not cause my display drivers to crash.
Nonedefinitely sounds like the driver for your GPU is crashing. Did you apply an overclock?